firmware-testing-team team mailing list archive
-
firmware-testing-team team
-
Mailing list archive
-
Message #00221
[Bug 1257353] Re: FWTS reports CRITICAL and HIGH failures in klog on server
** Changed in: fwts
Assignee: Firmware Testing Team (firmware-testing-team) => Anthony Wong (anthonywong)
** Changed in: fwts
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Firmware
Testing Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/1257353
Title:
FWTS reports CRITICAL and HIGH failures in klog on server
Status in Firmware Test Suite:
New
Bug description:
Ran this on a server and the klog test shows several critical errors.
We need to know if these CRITICAL and HIGH errors should gate the
certificate on this machine.
This test run on 26/11/13 at 14:51:31 on host Linux ubuntu-test1
3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013 x86_64.
Command: "fwts -q --stdout-summary -r /home/srini/.checkbox/fwts_results.log
klog".
Running tests: klog.
klog: Scan kernel log for errors and warnings.
--------------------------------------------------------------------------------
Test 1 of 1: Kernel log error check.
Kernel message: [ 0.039347] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
ADVICE: This is not exactly a failure but a warning from the kernel. The
MSR_IA32_ENERGY_PERF_BIAS was initialized and defaulted to a high performance
bias setting. The kernel has detected this and changed it down to a 'normal'
bias setting.
Kernel message: [ 0.880215] [Firmware Bug]: ACPI: BIOS _OSI(Linux)
query ignored
ADVICE: This is not exactly a failure mode but a warning from the kernel. The
_OSI() method has implemented a match to the 'Linux' query in the DSDT and this
is redundant because the ACPI driver matches onto the Windows _OSI strings by
default.
FAILED [CRITICAL] KlogPciAcpiOscRequestFailed: Test 1, CRITICAL Kernel message:
[ 0.902020] pci0000:7f: ACPI _OSC request failed (AE_NOT_FOUND), returned
control mask: 0x1d
ADVICE: The _OSC method evaluation failed, which will result in disabling PCIe
functionality, for example, the Linux kernel has to disable Active State Power
Management (ASPM) which means that PCIe power management is not optimally
configured.
FAILED [CRITICAL] KlogPciAcpiOscRequestFailed: Test 1, CRITICAL Kernel message:
[ 0.906466] pci0000:ff: ACPI _OSC request failed (AE_NOT_FOUND), returned
control mask: 0x1d
ADVICE: The _OSC method evaluation failed, which will result in disabling PCIe
functionality, for example, the Linux kernel has to disable Active State Power
Management (ASPM) which means that PCIe power management is not optimally
configured.
FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 4.240803]
ACPI Warning: 0x0000000000000460-0x000000000000047f SystemIO conflicts with
Region \PMIO 1 (20120320/utaddress-251)
ADVICE: A resource conflict between an ACPI OperationRegion and a native driver
has been detected. By default the kernel will use a strict policy and will not
allow this region to conflict and -EBUSY will be returned to the caller that was
trying to allocate the already claimed region. If an ACPI driver is available
for this device then this should be used instead of a native driver, so
disabling the native driver may help. (Note that the lpc_ich driver can trigger
these warnings, in which case they can generally be ignored). One can specify
kernel boot parameter acpi_enforce_resources=lax to disable these checks but it
may lead to random problems and system instability. Alternatively, one can
specify acpi_enforce_resources=no and ACPI Operation Region resources will not
be registered.
FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 4.240816]
ACPI Warning: 0x0000000000000460-0x000000000000047f SystemIO conflicts with
Region \_SB_.PCI0.HEC1.TCOS 2 (20120320/utaddress-251)
ADVICE: A resource conflict between an ACPI OperationRegion and a native driver
has been detected. By default the kernel will use a strict policy and will not
allow this region to conflict and -EBUSY will be returned to the caller that was
trying to allocate the already claimed region. If an ACPI driver is available
for this device then this should be used instead of a native driver, so
disabling the native driver may help. (Note that the lpc_ich driver can trigger
these warnings, in which case they can generally be ignored). One can specify
kernel boot parameter acpi_enforce_resources=lax to disable these checks but it
may lead to random problems and system instability. Alternatively, one can
specify acpi_enforce_resources=no and ACPI Operation Region resources will not
be registered.
FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 4.240818]
ACPI Warning: 0x0000000000000460-0x000000000000047f SystemIO conflicts with
Region \_SB_.PCI0.HEC2.TCOS 3 (20120320/utaddress-251)
ADVICE: A resource conflict between an ACPI OperationRegion and a native driver
has been detected. By default the kernel will use a strict policy and will not
allow this region to conflict and -EBUSY will be returned to the caller that was
trying to allocate the already claimed region. If an ACPI driver is available
for this device then this should be used instead of a native driver, so
disabling the native driver may help. (Note that the lpc_ich driver can trigger
these warnings, in which case they can generally be ignored). One can specify
kernel boot parameter acpi_enforce_resources=lax to disable these checks but it
may lead to random problems and system instability. Alternatively, one can
specify acpi_enforce_resources=no and ACPI Operation Region resources will not
be registered.
FAILED [LOW] KlogAcpiSystemIOConflictLpcIchWatchDogTimer: Test 1, LOW Kernel
message: [ 4.240822] lpc_ich: Resource conflict(s) found affecting iTCO_wdt
ADVICE: A resource conflict has occurred between ACPI OperationRegions and the
same I/O region used by the lpc_ich driver for the Intel TCO (Total Cost of
Ownership) timer (iTCO_wdt, this is a watchdog timer that will reboot the
machine after its second expiration). According to Intel Controller Hub (ICH)
specifications, the TCO watchdog has a 32 bytes I/O space resource. ACPI
OperationRegions in the DSDT frequently reserve this TCO I/O space because they
require access to bit 9 (DMISCI_STS) of the TCO1_STS register of the TCO,
however, this bit is never used by the lpc_ich driver, so there is no risk of
conflict. In the vast majority of cases this warning can be ignored as no harm
will occur.
FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 4.240824]
ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with
Region \PMIO 1 (20120320/utaddress-251)
ADVICE: A resource conflict between an ACPI OperationRegion and a native driver
has been detected. By default the kernel will use a strict policy and will not
allow this region to conflict and -EBUSY will be returned to the caller that was
trying to allocate the already claimed region. If an ACPI driver is available
for this device then this should be used instead of a native driver, so
disabling the native driver may help. (Note that the lpc_ich driver can trigger
these warnings, in which case they can generally be ignored). One can specify
kernel boot parameter acpi_enforce_resources=lax to disable these checks but it
may lead to random problems and system instability. Alternatively, one can
specify acpi_enforce_resources=no and ACPI Operation Region resources will not
be registered.
FAILED [LOW] KlogAcpiSystemIOConflict: Test 1, LOW Kernel message: [ 4.240829]
ACPI Warning: 0x0000000000000500-0x000000000000053f SystemIO conflicts with
Region \GINV 1 (20120320/utaddress-251)
ADVICE: A resource conflict between an ACPI OperationRegion and a native driver
has been detected. By default the kernel will use a strict policy and will not
allow this region to conflict and -EBUSY will be returned to the caller that was
trying to allocate the already claimed region. If an ACPI driver is available
for this device then this should be used instead of a native driver, so
disabling the native driver may help. (Note that the lpc_ich driver can trigger
these warnings, in which case they can generally be ignored). One can specify
kernel boot parameter acpi_enforce_resources=lax to disable these checks but it
may lead to random problems and system instability. Alternatively, one can
specify acpi_enforce_resources=no and ACPI Operation Region resources will not
be registered.
FAILED [LOW] KlogAcpiSystemIOConflictLpcIchWatchDogTimer: Test 1, LOW Kernel
message: [ 4.240832] lpc_ich: Resource conflict(s) found affecting gpio_ich
ADVICE: A resource conflict has occurred between ACPI OperationRegions and the
same I/O region used by the lpc_ich driver for the General Purpose I/O (GPIO)
region. Sometimes this GPIO region is used by the firmware for rfkill or LED
controls or very rarely for the Embedded Controller System Control Interrupt.
This may require deeper inspection to check if the conflict will lead to any
real issues. However, in the vast majority of cases this warning can be ignored
as no harm will occur.
FAILED [HIGH] KlogAcpiNoHandlerForRegion: Test 1, HIGH Kernel message: [
75.037261] ACPI Error: No handler for Region [POWS] (ffff881029494120) [IPMI]
(20120320/evregion-376)
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: [
75.037267] ACPI Error: Region IPMI (ID=7) has no handler (20120320/exfldio-306)
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: [
75.037270] ACPI Error: Method parse/execution failed [\_SB_.M111._GAI] (Node
ffff881029493960), AE_NOT_EXIST (20120320/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: [
75.037317] ACPI Error: Method parse/execution failed [\_SB_.M111._PMM] (Node
ffff881029493910), AE_NOT_EXIST (20120320/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 13 unique errors in kernel log.
================================================================================
0 passed, 13 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
================================================================================
0 passed, 13 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
Test Failure Summary
================================================================================
Critical failures: 2
klog: CRITICAL Kernel message: [ 0.902020] pci0000:7f: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
klog: CRITICAL Kernel message: [ 0.906466] pci0000:ff: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
High failures: 4
klog: HIGH Kernel message: [ 75.037261] ACPI Error: No handler for Region [POWS] (ffff881029494120) [IPMI] (20120320/evregion-376)
klog: HIGH Kernel message: [ 75.037267] ACPI Error: Region IPMI (ID=7) has no handler (20120320/exfldio-306)
klog: HIGH Kernel message: [ 75.037270] ACPI Error: Method parse/execution failed [\_SB_.M111._GAI] (Node ffff881029493960), AE_NOT_EXIST (20120320/psparse-536)
klog: HIGH Kernel message: [ 75.037317] ACPI Error: Method parse/execution failed [\_SB_.M111._PMM] (Node ffff881029493910), AE_NOT_EXIST (20120320/psparse-536)
Medium failures: NONE
Low failures: 7
klog: LOW Kernel message: [ 4.240803] ACPI Warning: 0x0000000000000460-0x000000000000047f SystemIO conflicts with Region \PMIO 1 (20120320/utaddress-251)
klog: LOW Kernel message: [ 4.240816] ACPI Warning: 0x0000000000000460-0x000000000000047f SystemIO conflicts with Region \_SB_.PCI0.HEC1.TCOS 2 (20120320/utaddress-251)
klog: LOW Kernel message: [ 4.240818] ACPI Warning: 0x0000000000000460-0x000000000000047f SystemIO conflicts with Region \_SB_.PCI0.HEC2.TCOS 3 (20120320/utaddress-251)
klog: LOW Kernel message: [ 4.240822] lpc_ich: Resource conflict(s) found affecting iTCO_wdt
klog: LOW Kernel message: [ 4.240824] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20120320/utaddress-251)
klog: LOW Kernel message: [ 4.240829] ACPI Warning: 0x0000000000000500-0x000000000000053f SystemIO conflicts with Region \GINV 1 (20120320/utaddress-251)
klog: LOW Kernel message: [ 4.240832] lpc_ich: Resource conflict(s) found affecting gpio_ich
Other failures: NONE
Test |Pass |Fail |Abort|Warn |Skip |Info |
---------------+-----+-----+-----+-----+-----+-----+
klog | | 13| | | | |
---------------+-----+-----+-----+-----+-----+-----+
Total: | 0| 13| 0| 0| 0| 0|
---------------+-----+-----+-----+-----+-----+-----+
Results generated by fwts: Version V13.11.00 (2013-11-15 06:47:53).
Some of this work - Copyright (c) 1999 - 2013, Intel Corp. All rights reserved.
Some of this work - Copyright (c) 2010 - 2013, Canonical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/fwts/+bug/1257353/+subscriptions
References
