HP Pavilion G7 - FWTS HIGH errors during suspend/resume and batch testing

[Jeff Lane ]

Gonna just start putting them all into a single bug for each machine, otherwise I'll be filing 2 - 4 bugs per machine just about every time I do a certification test ;-)

So this is 12.04.2 plus latest SRU kernel for certification. FWTS reported HIGH errors during Hibernate, Suspend and batch testing. I've attached the logs from each.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: fwts 0.25.06precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Wed Mar 6 00:21:36 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fwts
UpgradeStatus: No upgrade log present (probably fresh install)

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1148649

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Colin Ian King (colin-king)]

please run:

sudo acpidump > acpidump.log

and attach the log to the bug report.

Some triaging of the errors:

FAILED [HIGH] KlogACPIErrorNoHandlerFor: Test 1, HIGH Kernel message: [ 4057.268509] ACPI Error: No
handler for Region [RTCR] (ffff880129042ea0) [SystemCMOS] (20120320/evregion-376)
FAILED [HIGH] KlogACPIErrorRegionHas: Test 1, HIGH Kernel message: [ 4057.268514] ACPI Error: Region
SystemCMOS (ID=5) has no handler (20120320/exfldio-306)

..the kernel does not support a CMOS region handler, so we are getting this error when the firmware is attempting to do some CMOS memory accesses. Not sure why it is doing this, probably benign, but it is worth somebody looking at the AML to see why this is occurring.

FAILED [HIGH] KlogACPIErrorMethodExecutionParse: Test 1, HIGH Kernel message: [ 4057.268519] ACPI
Error: Method parse/execution failed [\_SB_.PCI0.LPC0.EC0_._Q33] (Node ffff880129064230),
AE_NOT_EXIST (20120320/psparse-536)

..this looks more concerning. Need to see why _Q33 is not implemented and what it is triggering a call to it.

FAILED [HIGH] KlogACPIErrorMethodExecutionParse: Test 1, HIGH Kernel message: [ 4057.268528] ACPI
Error: Method parse/execution failed [\S34E] (Node ffff880129034488), AE_NOT_EXIST (20120320
/psparse-536)

..this is also concerning, why S34E is being called when it does not exist. This needs investigating.

FAILED [HIGH] KlogACPIErrorMethodExecutionParse: Test 1, HIGH Kernel message: [ 4057.268534] ACPI
Error: Method parse/execution failed [\_PTS] (Node ffff880129034460), AE_NOT_EXIST (20120320
/psparse-536)

.._PTS not existing is not necessarily an issue. I've put a fix into fwts today so this won't be flagged as a HIGH error.

[Jeff Lane  (bladernr)]

Colin, Here ya go.

[Alex Hung (alexhung)]

I submitted a kernel patch to create a CMOS handler for the problem (https://patchwork.kernel.org/patch/2052901/). If it is accepted, it will fix the bug.

[Alex Hung (alexhung)]

A little more information for #5 and #7

The call trace is like:
_PTS -> S34E -> _Q33 -> no CMOS handler. As a result, they can be grouped as a single bug, which can be solved by the patch in #7.

[Ivan Hu (ivan.hu)]

The fail,

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

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.

ADVICE: It may be worth checking against section 7.23 of the System Management BIOS (SMBIOS)
Reference Specification (see http://www.dmtf.org/standards/smbios).

Seems DMI string indexes appear to be incorrect, so the DMI tables
are a bit buggy in places. Since DMI not used by kernel should be low failures.
A patch has been sent to fwts for setting the DMI not used by kernel to low failure.
http://kernel.ubuntu.com/git?p=hwe/fwts.git;a=commit;h=d69ab3047d467757eb356cf6bb437a05af1a4b8c

[Ivan Hu (ivan.hu)]

For the CMOS issue, still waiting the Patch in comment#7 to be accepted.

[Ivan Hu (ivan.hu)]

for the _Q33 -> no CMOS handler.

The issue is the same as the bug#1143312,

Upstream has a patch to fix this issue. This shall be included in kernel 3.11,
The patch will be backported to 3.9+ kernel and will be included in ubuntu 13.10,
please refer to,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1143312/comments/29
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1143312/comments/30

[lokz (lokz)]

I can confirm that I use:

Linux HP-Pavilion-g7-LV 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

And suspend does not work, nor error reporting.