Klog high failures on B200 and B420

Bug #1269654 reported by Samantha Jian-Pielak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Firmware Test Suite
Won't Fix
High
Ivan Hu
fwts (Ubuntu)
Won't Fix
High
Firmware Testing Team

Bug Description

The following klog high failures were reported by fwts during the cert evaluation testing on Cisco B200 and B420 M3. Please advise whether these failures have severe impact to block certification.

Test 1 of 1: Kernel log error check.
FAILED [HIGH] KlogOscInvalidUuid: Test 1, HIGH Kernel message: [ 2.004509] \_SB_
:_OSC invalid UUID

ADVICE: The _OSC method indicates it has been passed an invalid UUID, see
section 6.2.10 _OSC (Operating System Capabilities) of the ACPI specification
for more details. Note that it has been observed on some systems that this error
is returned because the _OSC has evaluated incorrectly and it returns with an
incorrect error setting the OSC invalid UUID error bit.

FAILED [HIGH] KlogAcpiSleepStateEvalFailed: Test 1, HIGH Kernel message: [
2.012634] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_]
(20130517/hwxface-571)

ADVICE: Failed to evaluate _Sx namespace object that contains the register
values for the sleep state.

FAILED [HIGH] KlogAcpiSleepStateEvalFailed: Test 1, HIGH Kernel message: [
2.012640] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_]
(20130517/hwxface-571)

ADVICE: Failed to evaluate _Sx namespace object that contains the register
values for the sleep state.

FAILED [HIGH] KlogAcpiSleepStateEvalFailed: Test 1, HIGH Kernel message: [
2.012644] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_]
(20130517/hwxface-571)

ADVICE: Failed to evaluate _Sx namespace object that contains the register
values for the sleep state.

FAILED [HIGH] KlogAcpiSleepStateEvalFailed: Test 1, HIGH Kernel message: [
2.012649] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S4_]
(20130517/hwxface-571)

ADVICE: Failed to evaluate _Sx namespace object that contains the register
values for the sleep state.

FAILED [HIGH] KlogAcpiNoHandlerForRegion: Test 1, HIGH Kernel message: [
2709.142899] ACPI Error: No handler for Region [POWS] (ffff880c69c51000) [IPMI]
(20130517/evregion-162)
Message repeated 7 times.

ADVICE: ACPI attempted to read or write to a region however the ACPI driver does
not have a handler implemented for this particular region space. The read/write
will fail and undefined behaviour will occur.

FAILED [HIGH] KlogAcpiKlogRegionNoHandler: Test 1, HIGH Kernel message: [
2709.142911] ACPI Error: Region IPMI (ID=7) has no handler (20130517
/exfldio-305)
Message repeated 7 times.

ADVICE: An access (read or write) to an operation region has been attempted and
a region handler for this has not been implemented, this may need to be
implemented to provide the expected behaviour. See acpi_ex_access_region().

FAILED [HIGH] KlogAcpiObjectDoesNotExist: Test 1, HIGH Kernel message: [
2709.142918] ACPI Error: Method parse/execution failed [\_SB_.M111._GAI] (Node
ffff880469871050), AE_NOT_EXIST (20130517/psparse-536)
Message repeated 3 times.

ADVICE: The ACPI interpreter failed to execute or parse some AML because a
object or control did not exist. This normally occurs because of buggy firmware
and may lead to unexpected behaviour or loss of functionality.

FAILED [HIGH] KlogAcpiObjectDoesNotExist: Test 1, HIGH Kernel message: [
2709.143045] ACPI Error: Method parse/execution failed [\_SB_.M111._PMM] (Node
ffff880469871000), AE_NOT_EXIST (20130517/psparse-536)
Message repeated 3 times.

ADVICE: The ACPI interpreter failed to execute or parse some AML because a
object or control did not exist. This normally occurs because of buggy firmware
and may lead to unexpected behaviour or loss of functionality.

Found 9 unique errors in kernel log.

================================================================================
0 passed, 9 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
================================================================================

0 passed, 9 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.

Test Failure Summary
================================================================================

Critical failures: NONE

High failures: 9
 klog: HIGH Kernel message: [ 2.004509] \_SB_:_OSC invalid UUID
 klog: HIGH Kernel message: [ 2.012634] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571)
 klog: HIGH Kernel message: [ 2.012640] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
 klog: HIGH Kernel message: [ 2.012644] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20130517/hwxface-571)
 klog: HIGH Kernel message: [ 2.012649] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S4_] (20130517/hwxface-571)
 klog: HIGH Kernel message: [ 2709.142899] ACPI Error: No handler for Region [POWS] (ffff880c69c51000) [IPMI] (20130517/evregion-162)
 klog: HIGH Kernel message: [ 2709.142911] ACPI Error: Region IPMI (ID=7) has no handler (20130517/exfldio-305)
 klog: HIGH Kernel message: [ 2709.142918] ACPI Error: Method parse/execution failed [\_SB_.M111._GAI] (Node ffff880469871050), AE_NOT_EXIST (20130517/psparse-536)
 klog: HIGH Kernel message: [ 2709.143045] ACPI Error: Method parse/execution failed [\_SB_.M111._PMM] (Node ffff880469871000), AE_NOT_EXIST (20130517/psparse-536)

Medium failures: NONE

Low failures: NONE

Other failures: NONE

summary: - Klog high failures on B220 and B420
+ Klog high failures on B200 and B420
Revision history for this message
Keng-Yu Lin (lexical) wrote :

For the Sleep State [\_S1_], Sleep State [\_S2_], Sleep State [\_S3_] and Sleep State [\_S4_], please contact the ODM please contact the ODM if this machine support these sleep states. (for the server, it is likely just not to support these sleep modes at all. But we have to get confirmed).

To analyze the other errors, the dumped data is needed (generated by `sudo fwts --dump`).

Changed in fwts:
status: New → Incomplete
importance: Undecided → High
assignee: nobody → Firmware Testing Team (firmware-testing-team)
Changed in fwts (Ubuntu):
status: New → Incomplete
importance: Undecided → High
assignee: nobody → Firmware Testing Team (firmware-testing-team)
Revision history for this message
Paul (pachen2) wrote :

More logs: attached are the B200M3 IVB fwts dump logs. Thank you.

Revision history for this message
Paul (pachen2) wrote :

More logs: attached is another different blade model with same error. Thank you.

Changed in fwts (Ubuntu):
status: Incomplete → Confirmed
Changed in fwts:
status: Incomplete → Confirmed
Revision history for this message
Paul (pachen2) wrote :

Updated status.

Revision history for this message
Samantha Jian-Pielak (samantha-jian) wrote :

@Keng-Yu,
It's confirmed that the system doesn't support S1, S2, S3 and S4.

Revision history for this message
Srinivas (srinira) wrote :
Revision history for this message
Srinivas (srinira) wrote :
Revision history for this message
Samantha Jian-Pielak (samantha-jian) wrote :

The same failures reported on C220 and C240 as well. Please see fwts dump logs above. These system don't support S1, S2, S3 or S4, either.

Keng-Yu Lin (lexical)
Changed in fwts:
assignee: Firmware Testing Team (firmware-testing-team) → Ivan Hu (ivan.hu)
Revision history for this message
Ivan Hu (ivan.hu) wrote :

For the S1, S2, S3, S4 failures,
The failures come from firmware not provide _S1,_S2,_S3 and _S4 objects, so that the kernel complains about cannot find _S1,_S2, _S3,_S4 namespace objects that contains the register values for the sleep state when kernel would like to setup all the sleep state information. This means kernel don't know how to enter S1,S2,_S3,_S4 sleep state, it makes no function of these sleep states.
But it should not be a problem if these sleep state isn't supported intentionally.

I've sent a patch to lower the failure level on fwts of the _S1 and _S2 objects cannot be find, since these sleep states are not used in most of the machines. Please refer to and follow by the bug#1279714.

Revision history for this message
Ivan Hu (ivan.hu) wrote :

As for the failures,
 klog: HIGH Kernel message: [ 2709.142899] ACPI Error: No handler for Region [POWS] (ffff880c69c51000) [IPMI] (20130517/evregion-162)
 klog: HIGH Kernel message: [ 2709.142911] ACPI Error: Region IPMI (ID=7) has no handler (20130517/exfldio-305)
 klog: HIGH Kernel message: [ 2709.142918] ACPI Error: Method parse/execution failed [\_SB_.M111._GAI] (Node ffff880469871050), AE_NOT_EXIST (20130517/psparse-536)
 klog: HIGH Kernel message: [ 2709.143045] ACPI Error: Method parse/execution failed [\_SB_.M111._PMM] (Node ffff880469871000), AE_NOT_EXIST (20130517/psparse-536)

These should not be a big concern, if the IPMI works fine.
It is the same cause as the bug#1257353, they have a lot discuss with it.
Please refer to,
https://bugs.launchpad.net/fwts/+bug/1257353

Ivan Hu (ivan.hu)
Changed in fwts:
status: Confirmed → Won't Fix
Changed in fwts (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.