HP Pavilion g7 - Assorted FWTS HIGH failures during testing

Bug #1152458 reported by Jeff Lane on 2013-03-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
Undecided
Unassigned
linux (Ubuntu)
High
Unassigned
Quantal
Undecided
Unassigned
Raring
Undecided
Unassigned
Saucy
High
Unassigned

Bug Description

This is another Pavilion G7 model, with assorted HIGH failures encountered during certification of 12.04.2 with various tests that use fwts. I have attached the batch run log and the suspend_30_cycles log.
There were also errors in the Hibernate log, but they were identical to the ones in the suspend log regaring hp_wmi

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1498 F.... pulseaudio
CRDA:
 country TW:
  (2402 - 2472 @ 40), (3, 27)
  (5270 - 5330 @ 40), (3, 17), DFS
  (5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0x52610000 irq 46'
   Mixer name : 'Intel PantherPoint HDMI'
   Components : 'HDA:111d76d9,103c1845,00100107 HDA:80862806,80860101,00100000'
   Controls : 24
   Simple ctrls : 11
Date: Fri Mar 8 01:08:04 2013
HibernationDevice: RESUME=UUID=e65da86c-4522-494e-bee7-2dc02c1a910c
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=92c1ee52-075d-4282-97b3-c43eef01f6cf ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-25-generic N/A
 linux-backports-modules-3.5.0-25-generic N/A
 linux-firmware 1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1845
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 56.32
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.21:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr0798100000005010000630100:rvnHewlett-Packard:rn1845:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 0798100000005010000630100
dmi.sys.vendor: Hewlett-Packard

Jeff Lane (bladernr) wrote :
Jeff Lane (bladernr) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Colin Ian King (colin-king) wrote :

I'd like a second opinion from one of the HWE engineers - but I generally think this is something that may just be innocuous, however, it would be useful to figure out why this event is occurring and if it is important or something we can ignore. Ultimately we should extend the WMI driver to cater for this event. Perhaps we can get some info from HP about this event and what it is meant to be doing.

Jeff Lane (bladernr) on 2013-03-11
tags: added: blocks-hwcert blocks-hwcert-enablement
Changed in linux (Ubuntu):
assignee: Firmware Test Suite Bug Team (firmware-bug-team) → Alex Hung (alexhung)
Changed in linux (Ubuntu):
importance: Undecided → High
Alex Hung (alexhung) wrote :

FAILED [MEDIUM] VirtDisabledByBIOS: Test 1, Virtualization extensions supported but disabled by BIOS.

HP's BIOS spec, virtualization technology is disabled by default and is required to be enabled manually. It seems HP thinks most users do not need this feature. This can be fixed by enabling it in BIOS setup menu, if needed.

Alex Hung (alexhung) wrote :

FAILED [LOW] LowMaxReadReq: Test 1, 1 devices have low MaxReadReq settings. Firmware may have configured these too low.

In Intel's data sheet, this register is Read-Only and is "hardwired to 0 enabling 128B maximum read request size". Therefore this is not a bug but a limited feature.

Alex Hung (alexhung) wrote :

FAILED [LOW] DMIBadDefault: Test 1, String index 0x03 in table entry 'Processor Information (Type 4)' @ 0x000e73b2, field 'Serial Number', offset 0x20 has a default value 'To Be Filled By O.E.M.' and probably has not been updated by the BIOS vendor.

FAILED [LOW] DMIBadDefault: Test 1, String index 0x05 in table entry 'Processor Information (Type 4)' @ 0x000e73b2, field 'Asset Tag', offset 0x21 has a default value 'To Be Filled By O.E.M.' and probably has not been updated by the BIOS vendor.

FAILED [LOW] DMIBadDefault: Test 1, String index 0x06 in table entry 'Processor Information (Type 4)' @ 0x000e73b2, field 'Part Number', offset 0x22 has a default value 'To Be Filled By O.E.M.' and probably has not been updated by the BIOS vendor.

Many DMI information is written during factory process or is not available on sample devices. For the above processor information, it can be the later. It can also be that BIOS did not read them and export to DMI.

If there is BIOS updates, it may worth a try; however, the above DMI are for information only and will not impact functions or stability.

Alex Hung (alexhung) wrote :

FAILED [HIGH] DMIStringIndexOutOfRange: Test 1, Out of range string index 0x06 while accessing entry 'Portable Battery (Type 22)' @ 0x000e728b, field 'Device Chemistry', offset 0x09

This is a real failure but kernel will ignore the information as suggested in fwts.

"ADVICE: DMI strings are stored in a manner that uses a special index to fetch the Nth string from the data. For this particular DMI string the index given is not in range which means this particular entry is broken. The Linux kernel does not use this string, so this error will not cause any system errors."

The information is also available in ACPI's _BIF/_BIX which are read by kernel (ex. "cat /proc/acpi/battery/BAT0/info"). Failing to read chemistry from DMI has nothing to worry about.

Alex Hung (alexhung) on 2013-04-09
Changed in linux (Ubuntu):
status: Confirmed → In Progress
Alex Hung (alexhung) wrote :

Please ignore #5 to to #8 as I checked the incorrect log file.

FAILED [HIGH] KlogHpwmiUnknownEventid: Test 1, HIGH Kernel message: [ 2477.032359] hp_wmi: Unknown event_id - 10 - 0x1

The above error was generated because new event id is defined by HP but is yet included in current hp_wmi driver. A patch was submitted to upstream (http://permalink.gmane.org/gmane.linux.drivers.platform.x86.devel/4276) but it yet accepted by the maintainer.

However, there are no impacts but only an error message. This should not be a cert-blocker.

Anthony Wong (anthonywong) wrote :

Ara, can the blocks-hwcert tag be removed since there is no real impact?

Changed in linux (Ubuntu):
status: In Progress → Confirmed
assignee: Alex Hung (alexhung) → nobody
Alex Hung (alexhung) wrote :

The patch in #9 is in upstream kernel git-tree and will be included in 3.10.

Po-Hsu Lin (cypressyew) wrote :

According to #10 and confirmed with Ara ,tags removed.

tags: removed: blocks-hwcert blocks-hwcert-enablement
Po-Hsu Lin (cypressyew) wrote :

Verified with 201206-11418 (12.04.2 / 3.5.0-34), this bug could be solved by updating the system.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Changed in hwe-next:
status: New → Fix Released
Tim Gardner (timg-tpi) on 2013-07-10
Changed in linux (Ubuntu Raring):
assignee: nobody → Ivan Hu (ivan.hu)
status: New → In Progress
Changed in linux (Ubuntu Quantal):
assignee: nobody → Ivan Hu (ivan.hu)
status: New → In Progress
Andy Whitcroft (apw) on 2013-07-11
Changed in linux (Ubuntu Raring):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Quantal):
status: In Progress → Fix Committed
Brad Figg (brad-figg) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed' to 'verification-done'.

If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-quantal
Brad Figg (brad-figg) on 2013-08-01
tags: added: verification-needed-raring
Ivan Hu (ivan.hu) wrote :

For the Unknown event_id - 10 - 0x1 error,
from the comment#9,
There are no impacts but only an error message. And should not be a cert-blocker.
Set it as Won't Fix.

Changed in linux (Ubuntu Quantal):
status: Fix Committed → Won't Fix
Changed in linux (Ubuntu Raring):
status: Fix Committed → Won't Fix
Changed in linux (Ubuntu Quantal):
assignee: Ivan Hu (ivan.hu) → nobody
Changed in linux (Ubuntu Raring):
assignee: Ivan Hu (ivan.hu) → nobody
Po-Hsu Lin (cypressyew) wrote :

Won't fix in Quantal and Raring.
Tags removed.

tags: removed: verification-needed-quantal verification-needed-raring
Brad Figg (brad-figg) on 2013-08-12
Changed in linux (Ubuntu Quantal):
status: Won't Fix → Fix Committed
Changed in linux (Ubuntu Raring):
status: Won't Fix → Fix Committed
tags: added: verification-needed-quantal verification-needed-raring
Brad Figg (brad-figg) on 2013-08-13
tags: added: verification-done-quantal verification-done-raring
removed: verification-needed-quantal verification-needed-raring
Po-Hsu Lin (cypressyew) wrote :

Verified on 201209-11633, with 12.04.2
Kernel 3.5.0-23 + FWTS 0.25.06precise1
Kernel 3.5.0-25 + FWTS 0.25.06precise1
Kernel 3.5.0-38 + FWTS 0.25.06precise1

Not sure if it was fixed by the other package or not, however, this issue cannot be reproduced.:
FAILED [HIGH] KlogHpwmiUnknownEventid: Test 1, HIGH Kernel message: [ 2477.032359] hp_wmi: Unknown event_id - 10 - 0x1

This message did not appear in these three combinations.

Po-Hsu Lin (cypressyew) wrote :
Po-Hsu Lin (cypressyew) wrote :
Po-Hsu Lin (cypressyew) wrote :

The hp_wmi issue does not appear on 3.8 kernel as well
13.04 + Kernel 3.8.0.19 + FWTS 0.26.08

Launchpad Janitor (janitor) wrote :
Download full text (8.6 KiB)

This bug was fixed in the package linux - 3.5.0-39.60

---------------
linux (3.5.0-39.60) quantal; urgency=low

  [Brad Figg]

  * Release Tracking Bug
    - LP: #1211872

  [ Upstream Kernel Changes ]

  * Revert "veth: avoid a NULL deref in veth_stats_one"
  * Revert "veth: extend device features"
  * Revert "veth: reduce stat overhead"

linux (3.5.0-38.59) quantal; urgency=low

  [Brad Figg]

  * Release Tracking Bug
    - LP: #1205440

  [ Upstream Kernel Changes ]

  * hp-wmi: add more definitions for new event_id's
    - LP: #1152458
  * MFD: rtsx_pcr: Fix probe fail path
    - LP: #1201321
  * mfd: rtsx: Add support for RTL8411B
    - LP: #1201321
  * veth: reduce stat overhead
    - LP: #1201869
  * veth: extend device features
    - LP: #1201869
  * veth: avoid a NULL deref in veth_stats_one
    - LP: #1201869
  * Input: elantech - fix for newer hardware versions (v7)
    - LP: #1166442
  * zram: avoid invalid memory access in zram_exit()
    - LP: #1204600
  * zram: use zram->lock to protect zram_free_page() in swap free notify
    path
    - LP: #1204600
  * zram: destroy all devices on error recovery path in zram_init()
    - LP: #1204600
  * zram: avoid double free in function zram_bvec_write()
    - LP: #1204600
  * zram: avoid access beyond the zram device
    - LP: #1204600
  * zram: protect sysfs handler from invalid memory access
    - LP: #1204600
  * pcmcia: at91_cf: fix gpio_get_value in at91_cf_get_status
    - LP: #1204600
  * usb: gadget: f_mass_storage: add missing memory barrier for
    thread_wakeup_needed
    - LP: #1204600
  * cgroup: fix umount vs cgroup_event_remove() race
    - LP: #1204600
  * xhci: check for failed dma pool allocation
    - LP: #1204600
  * usb: host: xhci-plat: release mem region while removing module
    - LP: #1204600
  * USB: option,qcserial: move Novatel Gobi1K IDs to qcserial
    - LP: #1204600
  * x86: Fix /proc/mtrr with base/size more than 44bits
    - LP: #1204600
  * genirq: Fix can_request_irq() for IRQs without an action
    - LP: #1204600
  * jbd2: move superblock checksum calculation to jbd2_write_superblock()
    - LP: #1204600
  * ext3,ext4: don't mess with dir_file->f_pos in htree_dirblock_to_tree()
    - LP: #1204600
  * jbd2: fix theoretical race in jbd2__journal_restart
    - LP: #1204600
  * cgroup: fix umount vs cgroup_cfts_commit() race
    - LP: #1204600
  * tracing: Use current_uid() for critical time tracing
    - LP: #1204600
  * ahci: Add AMD CZ SATA device ID
    - LP: #1204600
  * i2c-piix4: Add AMD CZ SMBus device ID
    - LP: #1204600
  * ahci: remove pmp link online check in FBS EH
    - LP: #1204600
  * libata: skip SRST for all SIMG [34]7x port-multipliers
    - LP: #1204600
  * ASoC: wm8962: Remove remaining direct register cache accesses
    - LP: #1204600
  * ACPICA: Do not use extended sleep registers unless HW-reduced bit is
    set
    - LP: #1204600
  * ALSA: hda - Cache the MUX selection for generic HDMI
    - LP: #1204600
  * ata_piix: IDE-mode SATA patch for Intel Coleto Creek DeviceIDs
    - LP: #1204600
  * ahci: AHCI-mode SATA patch for Intel Coleto Creek DeviceIDs
    - LP: #1204600
  * ARM: 7765/1: perf: Record the user-mode PC in the call c...

Read more...

Changed in linux (Ubuntu Quantal):
status: Fix Committed → Fix Released
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (12.6 KiB)

This bug was fixed in the package linux - 3.8.0-29.42

---------------
linux (3.8.0-29.42) raring; urgency=low

  [Brad Figg]

  * Release Tracking Bug
    - LP: #1211934

  [ Upstream Kernel Changes ]

  * Revert "veth: avoid a NULL deref in veth_stats_one"
  * Revert "veth: extend device features"
  * Revert "veth: reduce stat overhead"

linux (3.8.0-28.41) raring; urgency=low

  [Brad Figg]

  * Release Tracking Bug
    - LP: #1205373

  [ Andy Whitcroft ]

  * [Config] add iwldvm to nic-modules
    - LP: #1204194

  [ Brad Figg ]

  * [Config] added qlcnic driver to d-i modules
    - LP: #1196597

  [ Rob Herring ]

  * SAUCE: ARM: highbank: Only touch common coherency control register
    fields
    - LP: #1196946

  [ Upstream Kernel Changes ]

  * hp-wmi: add more definitions for new event_id's
    - LP: #1152458
  * MFD: rtsx_pcr: Fix probe fail path
    - LP: #1201321
  * mfd: rtsx: Add support for RTL8411B
    - LP: #1201321
  * veth: reduce stat overhead
    - LP: #1201869
  * veth: extend device features
    - LP: #1201869
  * veth: avoid a NULL deref in veth_stats_one
    - LP: #1201869
  * Input: elantech - fix for newer hardware versions (v7)
    - LP: #1166442
  * UBIFS: correct mount message
    - LP: #1204666
  * zfcp: fix adapter (re)open recovery while link to SAN is down
    - LP: #1204666
  * zfcp: block queue limits with data router
    - LP: #1204666
  * zfcp: status read buffers on first adapter open with link down
    - LP: #1204666
  * ahci: Add AMD CZ SATA device ID
    - LP: #1204666
  * i2c-piix4: Add AMD CZ SMBus device ID
    - LP: #1204666
  * sata_highbank: increase retry count but shorten duration for Calxeda
    controller
    - LP: #1204666
  * clocksource: dw_apb: Fix error check
    - LP: #1204666
  * zram: avoid invalid memory access in zram_exit()
    - LP: #1204666
  * zram: use zram->lock to protect zram_free_page() in swap free notify
    path
    - LP: #1204666
  * zram: destroy all devices on error recovery path in zram_init()
    - LP: #1204666
  * zram: avoid access beyond the zram device
    - LP: #1204666
  * zram: protect sysfs handler from invalid memory access
    - LP: #1204666
  * pcmcia: at91_cf: fix gpio_get_value in at91_cf_get_status
    - LP: #1204666
  * PCI: Fix refcount issue in pci_create_root_bus() error recovery path
    - LP: #1204666
  * ahci: remove pmp link online check in FBS EH
    - LP: #1204666
  * usb: gadget: f_mass_storage: add missing memory barrier for
    thread_wakeup_needed
    - LP: #1204666
  * x86, efi: retry ExitBootServices() on failure
    - LP: #1204666
  * libata: skip SRST for all SIMG [34]7x port-multipliers
    - LP: #1204666
  * ASoC: wm8962: Remove remaining direct register cache accesses
    - LP: #1204666
  * xen/pcifront: Deal with toolstack missing 'XenbusStateClosing' state.
    - LP: #1204666
  * ACPICA: Do not use extended sleep registers unless HW-reduced bit is
    set
    - LP: #1204666
  * ALSA: hda - Cache the MUX selection for generic HDMI
    - LP: #1204666
  * cgroup: fix umount vs cgroup_cfts_commit() race
    - LP: #1204666
  * cgroup: fix umount vs cgroup_event_remove() race
    - LP: #1204666
  * xhci: check for failed dma pool al...

Changed in linux (Ubuntu Raring):
status: Fix Committed → Fix Released
status: Fix Committed → Fix Released
To post a comment you must log in.