[PATCH] fwts-test: sync up with the klog test
Ivan Hu
ivan.hu at canonical.com
Wed Jul 27 04:49:59 UTC 2016
Signed-off-by: Ivan Hu <ivan.hu at canonical.com>
---
fwts-test/arg-klog-0001/klog-0001.log | 12 +-
fwts-test/arg-log-format-0001/klog-0001.log | 546 ++++++++++-----------
fwts-test/arg-log-format-0001/klog-0002.log | 17 +-
fwts-test/arg-log-format-0001/klog-0003.log | 378 +++++++-------
fwts-test/arg-log-format-0001/klog-0004.log | 424 ++++++++--------
fwts-test/arg-results-0001/results-0005.log | 24 +-
fwts-test/arg-results-0001/results.log | 12 +-
.../arg-results-no-separators-0001/klog-0001.log | 12 +-
fwts-test/klog-0001/klog-0001.log | 12 +-
fwts-test/klog-0001/klog-0002.log | 6 +-
10 files changed, 711 insertions(+), 732 deletions(-)
diff --git a/fwts-test/arg-klog-0001/klog-0001.log b/fwts-test/arg-klog-0001/klog-0001.log
index aa95c94..4baddd7 100644
--- a/fwts-test/arg-klog-0001/klog-0001.log
+++ b/fwts-test/arg-klog-0001/klog-0001.log
@@ -1,16 +1,14 @@
klog klog: Scan kernel log for errors and warnings.
klog ----------------------------------------------------------
klog Test 1 of 1: Kernel log error check.
-klog FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
+klog FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM
klog Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC
klog /MADT found, using 0
klog
-klog ADVICE: The kernel has detected more than one ACPI
-klog Multiple APIC Description Table (MADT) (these tables have
-klog the "APIC" signature). There should only be one MADT and
-klog the kernel will by default select the first one. However,
-klog one can override this and select the Nth MADT using
-klog acpi_apic_instance=N.
+klog ADVICE: The BIOS is supposed to supply just one APIC/MADT,
+klog however, more than one has been found. One can use
+klog acpi_apic_instance=N to specify the Nth ACPI/MADT to use
+klog as an override if required.
klog
klog Kernel message: [ 0.228089] [Firmware Bug]: ACPI: BIOS
klog _OSI(Linux) query ignored
diff --git a/fwts-test/arg-log-format-0001/klog-0001.log b/fwts-test/arg-log-format-0001/klog-0001.log
index db134e0..87aba7b 100644
--- a/fwts-test/arg-log-format-0001/klog-0001.log
+++ b/fwts-test/arg-log-format-0001/klog-0001.log
@@ -1,275 +1,271 @@
-klog (00021) <10/02/14> HED : klog: Scan kernel log for errors and
-klog (00022) <10/02/14> HED : warnings.
-klog (00023) <10/02/14> SEP : --------------------------------------
-klog (00024) <10/02/14> INF : Test 1 of 1: Kernel log error check.
-klog (00025) <10/02/14> FAL H: FAILED [HIGH]
-klog (00026) <10/02/14> FAL H: KlogAcpiMultipleApicMadtFound: Test 1,
-klog (00027) <10/02/14> FAL H: HIGH Kernel message: [ 0.000000] ACPI:
-klog (00028) <10/02/14> FAL H: BIOS bug: multiple APIC/MADT found,
-klog (00029) <10/02/14> FAL H: using 0
-klog (00030) <10/02/14> NLN :
-klog (00031) <10/02/14> ADV : ADVICE: The kernel has detected more
-klog (00032) <10/02/14> ADV : than one ACPI Multiple APIC
-klog (00033) <10/02/14> ADV : Description Table (MADT) (these tables
-klog (00034) <10/02/14> ADV : have the "APIC" signature). There
-klog (00035) <10/02/14> ADV : should only be one MADT and the kernel
-klog (00036) <10/02/14> ADV : will by default select the first one.
-klog (00037) <10/02/14> ADV : However, one can override this and
-klog (00038) <10/02/14> ADV : select the Nth MADT using
-klog (00039) <10/02/14> ADV : acpi_apic_instance=N.
-klog (00040) <10/02/14> NLN :
-klog (00041) <10/02/14> FAL H: FAILED [HIGH]
-klog (00042) <10/02/14> FAL H: KlogAcpi32Bit64BitAddressMismatch:
-klog (00043) <10/02/14> FAL H: Test 1, HIGH Kernel message: [
-klog (00044) <10/02/14> FAL H: 0.000000] ACPI Error: 32/64X address
-klog (00045) <10/02/14> FAL H: mismatch in Gpe0Block: 00008018
-klog (00046) <10/02/14> FAL H: /0000000000008028, using 32 (20090903
-klog (00047) <10/02/14> FAL H: /tbfadt-427)
-klog (00048) <10/02/14> NLN :
-klog (00049) <10/02/14> ADV : ADVICE: The FADT table contains a
-klog (00050) <10/02/14> ADV : mismatch between a 32 bit pointer and
-klog (00051) <10/02/14> ADV : a 64 bit Generic Address pointer.
-klog (00052) <10/02/14> ADV : Because these pointers are different,
-klog (00053) <10/02/14> ADV : it suggests either one of them is
-klog (00054) <10/02/14> ADV : incorrect. If a non-null 32 bit
-klog (00055) <10/02/14> ADV : pointer exists, then the kernel will
-klog (00056) <10/02/14> ADV : opt for this in preference to the 64
-klog (00057) <10/02/14> ADV : bit pointer even though this is not in
-klog (00058) <10/02/14> ADV : accordance to the ACPI specification.
-klog (00059) <10/02/14> NLN :
-klog (00060) <10/02/14> FAL C: FAILED [CRITICAL]
-klog (00061) <10/02/14> FAL C: KlogAcpiValidRsdpNotFound: Test 1,
-klog (00062) <10/02/14> FAL C: CRITICAL Kernel message: [ 0.000000]
-klog (00063) <10/02/14> FAL C: ACPI Error: A valid RSDP was not found
-klog (00064) <10/02/14> FAL C: (20090903/tbxfroot-219)
-klog (00065) <10/02/14> NLN :
-klog (00066) <10/02/14> ADV : ADVICE: An ACPI compatible system must
-klog (00067) <10/02/14> ADV : provide an RSDP (Root System
-klog (00068) <10/02/14> ADV : Description Pointer). This structure
-klog (00069) <10/02/14> ADV : provides the physical address of the
-klog (00070) <10/02/14> ADV : RSDT and XSDT. Since this could not be
-klog (00071) <10/02/14> ADV : found, the ACPI driver has had to
-klog (00072) <10/02/14> ADV : disable ACPI support.
-klog (00073) <10/02/14> NLN :
-klog (00074) <10/02/14> FAL H: FAILED [HIGH] KlogAcpiTwoFacs: Test 1,
-klog (00075) <10/02/14> FAL H: HIGH Kernel message: [ 0.000000] ACPI
-klog (00076) <10/02/14> FAL H: Warning: 32/64 FACS address mismatch
-klog (00077) <10/02/14> FAL H: in FADT - two FACS tables! (20090903
-klog (00078) <10/02/14> FAL H: /tbfadt-369)
-klog (00079) <10/02/14> NLN :
-klog (00080) <10/02/14> ADV : ADVICE: The FADT table contains a
-klog (00081) <10/02/14> ADV : mismatch between the 32 bit pointer
-klog (00082) <10/02/14> ADV : (FIRMWARE_CTRL) and 64 bit pointer
-klog (00083) <10/02/14> ADV : (X_FIRMWARE_CTRL) pointer to the FACS
-klog (00084) <10/02/14> ADV : table. Section 5.2.9 of version 4.0a
-klog (00085) <10/02/14> ADV : of the ACPI specification states that
-klog (00086) <10/02/14> ADV : X_FIRMWARE_CTRL should be zero if
-klog (00087) <10/02/14> ADV : FIRMWARE_CTRL is defined, or
-klog (00088) <10/02/14> ADV : FIRMWARE_CTRL should be zero if
-klog (00089) <10/02/14> ADV : X_FIRMWARE_CTRL is zero. With two
-klog (00090) <10/02/14> ADV : different pointers defined, the kernel
-klog (00091) <10/02/14> ADV : has to make a choice, and opts for the
-klog (00092) <10/02/14> ADV : 32 bit pointer. Because these pointers
-klog (00093) <10/02/14> ADV : are different, it suggests either one
-klog (00094) <10/02/14> ADV : of them is incorrect, or different 32
-klog (00095) <10/02/14> ADV : bit and 64 bit FACS tables are present
-klog (00096) <10/02/14> ADV : in your system, which is NOT complaint
-klog (00097) <10/02/14> ADV : with the ACPI specification. The
-klog (00098) <10/02/14> ADV : kernel has to make a choice and opts
-klog (00099) <10/02/14> ADV : for the 32 bit FIRMWARE_CTRL.
-klog (00100) <10/02/14> NLN :
-klog (00101) <10/02/14> FAL H: FAILED [HIGH]
-klog (00102) <10/02/14> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt
-klog (00103) <10/02/14> FAL H: : Test 1, HIGH Kernel message: [
-klog (00104) <10/02/14> FAL H: 0.000000] ACPI Warning: 32/64X FACS
-klog (00105) <10/02/14> FAL H: address mismatch in FADT - DEF2DF40
-klog (00106) <10/02/14> FAL H: /00000000DEF30D40, using 32 (20090903
-klog (00107) <10/02/14> FAL H: /tbfadt-486)
-klog (00108) <10/02/14> NLN :
-klog (00109) <10/02/14> ADV : ADVICE: The FADT table contains
-klog (00110) <10/02/14> ADV : Generic Address Structure that has a
-klog (00111) <10/02/14> ADV : mismatch between the 32 bit and 64 bit
-klog (00112) <10/02/14> ADV : versions of an address. This should be
-klog (00113) <10/02/14> ADV : fixed so there are no mismatches.
-klog (00114) <10/02/14> NLN :
-klog (00115) <10/02/14> FAL H: FAILED [HIGH]
-klog (00116) <10/02/14> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt
-klog (00117) <10/02/14> FAL H: : Test 1, HIGH Kernel message: [
-klog (00118) <10/02/14> FAL H: 0.000000] ACPI Warning: 32/64X length
-klog (00119) <10/02/14> FAL H: mismatch in Gpe1Block: 0/32 20090521
-klog (00120) <10/02/14> FAL H: tbfadt-527
-klog (00121) <10/02/14> NLN :
-klog (00122) <10/02/14> ADV : ADVICE: The FADT table contains
-klog (00123) <10/02/14> ADV : Generic Address Structure that has a
-klog (00124) <10/02/14> ADV : mismatch between the 32 bit and 64 bit
-klog (00125) <10/02/14> ADV : versions of an address. This should be
-klog (00126) <10/02/14> ADV : fixed so there are no mismatches.
-klog (00127) <10/02/14> NLN :
-klog (00128) <10/02/14> FAL H: FAILED [HIGH] KlogAcpiBadAmlCode: Test
-klog (00129) <10/02/14> FAL H: 1, HIGH Kernel message: [ 0.000000]
-klog (00130) <10/02/14> FAL H: ACPI Warning: BIOS XSDT has NULL entry
-klog (00131) <10/02/14> FAL H: , using RSDT (20110112/tbutils-663)
-klog (00132) <10/02/14> NLN :
-klog (00133) <10/02/14> ADV : ADVICE: ACPI AML intepreter has found
-klog (00134) <10/02/14> ADV : some non-conforming AML code. This
-klog (00135) <10/02/14> ADV : should be investigated and fixed.
-klog (00136) <10/02/14> NLN :
-klog (00137) <10/02/14> FAL H: FAILED [HIGH]
-klog (00138) <10/02/14> FAL H: KlogAcpiFadtInvalidLength: Test 1,
-klog (00139) <10/02/14> FAL H: HIGH Kernel message: [ 0.000000] ACPI
-klog (00140) <10/02/14> FAL H: Warning: Invalid length for
-klog (00141) <10/02/14> FAL H: Pm1aControlBlock: 32, using default 16
-klog (00142) <10/02/14> FAL H: (20090903/tbfadt-607)
-klog (00143) <10/02/14> NLN :
-klog (00144) <10/02/14> ADV : ADVICE: This item in the FADT is the
-klog (00145) <10/02/14> ADV : incorrect length. Should be corrected.
-klog (00146) <10/02/14> NLN :
-klog (00147) <10/02/14> FAL H: FAILED [HIGH]
-klog (00148) <10/02/14> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
-klog (00149) <10/02/14> FAL H: : Test 1, HIGH Kernel message: [
-klog (00150) <10/02/14> FAL H: 0.000000] ACPI Warning: Optional field
-klog (00151) <10/02/14> FAL H: Gpe1Block has zero address or length:
-klog (00152) <10/02/14> FAL H: 000000000000102C/0 20090521 tbfadt-558
-klog (00153) <10/02/14> NLN :
-klog (00154) <10/02/14> ADV : ADVICE: An ACPI table contains Generic
-klog (00155) <10/02/14> ADV : Address Structure that has an address
-klog (00156) <10/02/14> ADV : that is incorrectly set to zero, or a
-klog (00157) <10/02/14> ADV : zero length. This needs to be fixed.
-klog (00158) <10/02/14> NLN :
-klog (00159) <10/02/14> FAL H: FAILED [HIGH]
-klog (00160) <10/02/14> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
-klog (00161) <10/02/14> FAL H: : Test 1, HIGH Kernel message: [
-klog (00162) <10/02/14> FAL H: 0.000000] ACPI Warning: Optional field
-klog (00163) <10/02/14> FAL H: Pm2ControlBlock has zero address or
-klog (00164) <10/02/14> FAL H: length: 0000000000000000/1 20090521
-klog (00165) <10/02/14> FAL H: tbfadt-558
-klog (00166) <10/02/14> NLN :
-klog (00167) <10/02/14> ADV : ADVICE: An ACPI table contains Generic
-klog (00168) <10/02/14> ADV : Address Structure that has an address
-klog (00169) <10/02/14> ADV : that is incorrectly set to zero, or a
-klog (00170) <10/02/14> ADV : zero length. This needs to be fixed.
-klog (00171) <10/02/14> NLN :
-klog (00172) <10/02/14> FAL H: FAILED [HIGH]
-klog (00173) <10/02/14> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
-klog (00174) <10/02/14> FAL H: : Test 1, HIGH Kernel message: [
-klog (00175) <10/02/14> FAL H: 0.000000] ACPI Warning (tbfadt-0460):
-klog (00176) <10/02/14> FAL H: Optional field "Gpe1Block" has zero
-klog (00177) <10/02/14> FAL H: address or length: 000000000000102C/0
-klog (00178) <10/02/14> FAL H: [20080926]
-klog (00179) <10/02/14> NLN :
-klog (00180) <10/02/14> ADV : ADVICE: An ACPI table contains Generic
-klog (00181) <10/02/14> ADV : Address Structure that has an address
-klog (00182) <10/02/14> ADV : that is incorrectly set to zero, or a
-klog (00183) <10/02/14> ADV : zero length. This needs to be fixed.
-klog (00184) <10/02/14> NLN :
-klog (00185) <10/02/14> FAL M: FAILED [MEDIUM]
-klog (00186) <10/02/14> FAL M: KlogBiosMtrrIncorrectMask: Test 1,
-klog (00187) <10/02/14> FAL M: MEDIUM Kernel message: [ 0.000000]
-klog (00188) <10/02/14> FAL M: mtrr: your BIOS has configured an
-klog (00189) <10/02/14> FAL M: incorrect mask, fixing it.
-klog (00190) <10/02/14> NLN :
-klog (00191) <10/02/14> ADV : ADVICE: The Memory Type Range
-klog (00192) <10/02/14> ADV : Registers (MTRRs) which define memory
-klog (00193) <10/02/14> ADV : caching policy are misconfigued by the
-klog (00194) <10/02/14> ADV : BIOS. In this case, the mask is
-klog (00195) <10/02/14> ADV : incorrectly set and the kernel has
-klog (00196) <10/02/14> ADV : detected this and worked around the
-klog (00197) <10/02/14> ADV : firmware bug.
-klog (00198) <10/02/14> NLN :
-klog (00199) <10/02/14> FAL C: FAILED [CRITICAL]
-klog (00200) <10/02/14> FAL C: KlogBiosCpuMtrrMisconfigured: Test 1,
-klog (00201) <10/02/14> FAL C: CRITICAL Kernel message: [ 0.000000]
-klog (00202) <10/02/14> FAL C: WARNING: BIOS bug: CPU MTRRs don't
-klog (00203) <10/02/14> FAL C: cover all of memory, losing 1408MB of
-klog (00204) <10/02/14> FAL C: RAM.
-klog (00205) <10/02/14> NLN :
-klog (00206) <10/02/14> ADV : ADVICE: The Memory Type Range
-klog (00207) <10/02/14> ADV : Registers (MTRRs) which define memory
-klog (00208) <10/02/14> ADV : caching policy are misconfigued by the
-klog (00209) <10/02/14> ADV : BIOS and don't appear to cover all
-klog (00210) <10/02/14> ADV : available physical memory. The kernel
-klog (00211) <10/02/14> ADV : has detected this and has reduced the
-klog (00212) <10/02/14> ADV : amount of memory available to be safe.
-klog (00213) <10/02/14> ADV : Either check that the BIOS memory
-klog (00214) <10/02/14> ADV : caching options are set correctly or
-klog (00215) <10/02/14> ADV : contact your BIOS vendor to get this
-klog (00216) <10/02/14> ADV : fixed.
-klog (00217) <10/02/14> NLN :
-klog (00218) <10/02/14> FAL H: FAILED [HIGH] KlogAcpiUnknownAmlOpcode
-klog (00219) <10/02/14> FAL H: : Test 1, HIGH Kernel message: [
-klog (00220) <10/02/14> FAL H: 0.022719] ACPI Error: Found unknown
-klog (00221) <10/02/14> FAL H: opcode 0xFD at AML address f7ffe14c
-klog (00222) <10/02/14> FAL H: offset 0xE8, ignoring (20110112
-klog (00223) <10/02/14> FAL H: /psloop-141)
-klog (00224) <10/02/14> NLN :
-klog (00225) <10/02/14> ADV : ADVICE: ACPI execution run time error:
-klog (00226) <10/02/14> ADV : The ACPI interpreter has reached an
-klog (00227) <10/02/14> ADV : opcode that is unknown, this normally
-klog (00228) <10/02/14> ADV : is a bug in the underlying AML code
-klog (00229) <10/02/14> ADV : either because of badly written AML
-klog (00230) <10/02/14> ADV : code or the compiler has produced code
-klog (00231) <10/02/14> ADV : that is incorrect or the ACPI
-klog (00232) <10/02/14> ADV : interpreter does not support this
-klog (00233) <10/02/14> ADV : valid opcode.
-klog (00234) <10/02/14> NLN :
-klog (00235) <10/02/14> FAL C: FAILED [CRITICAL]
-klog (00236) <10/02/14> FAL C: KlogAcpiDetectedUnsupportedOpCode:
-klog (00237) <10/02/14> FAL C: Test 1, CRITICAL Kernel message: [
-klog (00238) <10/02/14> FAL C: 0.025463] ACPI Warning: Detected an
-klog (00239) <10/02/14> FAL C: unsupported executable opcode at
-klog (00240) <10/02/14> FAL C: module-level: [0x007B] at table offset
-klog (00241) <10/02/14> FAL C: 0x00C3 (20110112/psloop-526)
-klog (00242) <10/02/14> NLN :
-klog (00243) <10/02/14> ADV : ADVICE: An illegal AML opcode has been
-klog (00244) <10/02/14> ADV : found and is ignored. This indicates
-klog (00245) <10/02/14> ADV : either badly compiled code or opcode
-klog (00246) <10/02/14> ADV : corruption in the DSDT or SSDT tables
-klog (00247) <10/02/14> ADV : or a bug in the ACPI execution engine.
-klog (00248) <10/02/14> ADV : Recommend disassembing using iasl to
-klog (00249) <10/02/14> ADV : find any offending code.
-klog (00250) <10/02/14> NLN :
-klog (00251) <10/02/14> FAL H: FAILED [HIGH]
-klog (00252) <10/02/14> FAL H: KlogAcpiObjectAlreadyExists: Test 1,
-klog (00253) <10/02/14> FAL H: HIGH Kernel message: [ 0.034090] ACPI
-klog (00254) <10/02/14> FAL H: Error: Method parse/execution failed
-klog (00255) <10/02/14> FAL H: [_SB_.PCI0._OSC] (Node ee025630),
-klog (00256) <10/02/14> FAL H: AE_ALREADY_EXISTS (20110112
-klog (00257) <10/02/14> FAL H: /psparse-536)
-klog (00258) <10/02/14> NLN :
-klog (00259) <10/02/14> ADV : ADVICE: This is a bug picked up by the
-klog (00260) <10/02/14> ADV : kernel, but as yet, the firmware test
-klog (00261) <10/02/14> ADV : suite has no diagnostic advice for
-klog (00262) <10/02/14> ADV : this particular problem.
-klog (00263) <10/02/14> NLN :
-klog (00264) <10/02/14> FAL H: FAILED [HIGH] KlogAcpiFirmwareError:
-klog (00265) <10/02/14> FAL H: Test 1, HIGH Kernel message: [
-klog (00266) <10/02/14> FAL H: 0.040119] [Firmware Bug]: the BIOS has
-klog (00267) <10/02/14> FAL H: corrupted hw-PMU resources (MSR 186 is
-klog (00268) <10/02/14> FAL H: 400000)
-klog (00269) <10/02/14> NLN :
-klog (00270) <10/02/14> ADV : ADVICE: The kernel has detected a
-klog (00271) <10/02/14> ADV : Firmware bug in the BIOS or ACPI which
-klog (00272) <10/02/14> ADV : needs investigating and fixing.
-klog (00273) <10/02/14> NLN :
-klog (00274) <10/02/14> FAL C: FAILED [CRITICAL]
-klog (00275) <10/02/14> FAL C: KlogAcpiDetectedUnsupportedOpCode:
-klog (00276) <10/02/14> FAL C: Test 1, CRITICAL Kernel message: [
-klog (00277) <10/02/14> FAL C: 0.042222] ACPI Warning: Detected an
-klog (00278) <10/02/14> FAL C: unsupported executable opcode at
-klog (00279) <10/02/14> FAL C: module-level: [0x0070] at table offset
-klog (00280) <10/02/14> FAL C: 0x2366 (20100121/psloop-526)
-klog (00281) <10/02/14> NLN :
-klog (00282) <10/02/14> ADV : ADVICE: An illegal AML opcode has been
-klog (00283) <10/02/14> ADV : found and is ignored. This indicates
-klog (00284) <10/02/14> ADV : either badly compiled code or opcode
-klog (00285) <10/02/14> ADV : corruption in the DSDT or SSDT tables
-klog (00286) <10/02/14> ADV : or a bug in the ACPI execution engine.
-klog (00287) <10/02/14> ADV : Recommend disassembing using iasl to
-klog (00288) <10/02/14> ADV : find any offending code.
-klog (00289) <10/02/14> NLN :
-klog (00290) <10/02/14> INF : Found 18 unique errors in kernel log.
-klog (00291) <10/02/14> NLN :
-klog (00292) <10/02/14> SEP : ======================================
-klog (00293) <10/02/14> SUM : 0 passed, 18 failed, 0 warning, 0
-klog (00294) <10/02/14> SUM : aborted, 0 skipped, 0 info only.
-klog (00295) <10/02/14> SEP : ======================================
+klog (00023) <27/07/16> HED : klog: Scan kernel log for errors and
+klog (00024) <27/07/16> HED : warnings.
+klog (00025) <27/07/16> SEP : --------------------------------------
+klog (00026) <27/07/16> INF : Test 1 of 1: Kernel log error check.
+klog (00027) <27/07/16> FAL M: FAILED [MEDIUM] KlogAcpiMultipleMadt:
+klog (00028) <27/07/16> FAL M: Test 1, MEDIUM Kernel message: [
+klog (00029) <27/07/16> FAL M: 0.000000] ACPI: BIOS bug: multiple
+klog (00030) <27/07/16> FAL M: APIC/MADT found, using 0
+klog (00031) <27/07/16> NLN :
+klog (00032) <27/07/16> ADV : ADVICE: The BIOS is supposed to supply
+klog (00033) <27/07/16> ADV : just one APIC/MADT, however, more than
+klog (00034) <27/07/16> ADV : one has been found. One can use
+klog (00035) <27/07/16> ADV : acpi_apic_instance=N to specify the
+klog (00036) <27/07/16> ADV : Nth ACPI/MADT to use as an override if
+klog (00037) <27/07/16> ADV : required.
+klog (00038) <27/07/16> NLN :
+klog (00039) <27/07/16> FAL H: FAILED [HIGH]
+klog (00040) <27/07/16> FAL H: KlogAcpi32Bit64BitAddressMismatch:
+klog (00041) <27/07/16> FAL H: Test 1, HIGH Kernel message: [
+klog (00042) <27/07/16> FAL H: 0.000000] ACPI Error: 32/64X address
+klog (00043) <27/07/16> FAL H: mismatch in Gpe0Block: 00008018
+klog (00044) <27/07/16> FAL H: /0000000000008028, using 32 (20090903
+klog (00045) <27/07/16> FAL H: /tbfadt-427)
+klog (00046) <27/07/16> NLN :
+klog (00047) <27/07/16> ADV : ADVICE: The FADT table contains a
+klog (00048) <27/07/16> ADV : mismatch between a 32 bit pointer and
+klog (00049) <27/07/16> ADV : a 64 bit Generic Address pointer.
+klog (00050) <27/07/16> ADV : Because these pointers are different,
+klog (00051) <27/07/16> ADV : it suggests either one of them is
+klog (00052) <27/07/16> ADV : incorrect. If a non-null 32 bit
+klog (00053) <27/07/16> ADV : pointer exists, then the kernel will
+klog (00054) <27/07/16> ADV : opt for this in preference to the 64
+klog (00055) <27/07/16> ADV : bit pointer even though this is not in
+klog (00056) <27/07/16> ADV : accordance to the ACPI specification.
+klog (00057) <27/07/16> NLN :
+klog (00058) <27/07/16> FAL C: FAILED [CRITICAL]
+klog (00059) <27/07/16> FAL C: KlogAcpiValidRsdpNotFound: Test 1,
+klog (00060) <27/07/16> FAL C: CRITICAL Kernel message: [ 0.000000]
+klog (00061) <27/07/16> FAL C: ACPI Error: A valid RSDP was not found
+klog (00062) <27/07/16> FAL C: (20090903/tbxfroot-219)
+klog (00063) <27/07/16> NLN :
+klog (00064) <27/07/16> ADV : ADVICE: An ACPI compatible system must
+klog (00065) <27/07/16> ADV : provide an RSDP (Root System
+klog (00066) <27/07/16> ADV : Description Pointer). This structure
+klog (00067) <27/07/16> ADV : provides the physical address of the
+klog (00068) <27/07/16> ADV : RSDT and XSDT. Since this could not be
+klog (00069) <27/07/16> ADV : found, the ACPI driver has had to
+klog (00070) <27/07/16> ADV : disable ACPI support.
+klog (00071) <27/07/16> NLN :
+klog (00072) <27/07/16> FAL H: FAILED [HIGH] KlogAcpiTwoFacs: Test 1,
+klog (00073) <27/07/16> FAL H: HIGH Kernel message: [ 0.000000] ACPI
+klog (00074) <27/07/16> FAL H: Warning: 32/64 FACS address mismatch
+klog (00075) <27/07/16> FAL H: in FADT - two FACS tables! (20090903
+klog (00076) <27/07/16> FAL H: /tbfadt-369)
+klog (00077) <27/07/16> NLN :
+klog (00078) <27/07/16> ADV : ADVICE: The FADT table contains a
+klog (00079) <27/07/16> ADV : mismatch between the 32 bit pointer
+klog (00080) <27/07/16> ADV : (FIRMWARE_CTRL) and 64 bit pointer
+klog (00081) <27/07/16> ADV : (X_FIRMWARE_CTRL) pointer to the FACS
+klog (00082) <27/07/16> ADV : table. Section 5.2.9 of version 4.0a
+klog (00083) <27/07/16> ADV : of the ACPI specification states that
+klog (00084) <27/07/16> ADV : X_FIRMWARE_CTRL should be zero if
+klog (00085) <27/07/16> ADV : FIRMWARE_CTRL is defined, or
+klog (00086) <27/07/16> ADV : FIRMWARE_CTRL should be zero if
+klog (00087) <27/07/16> ADV : X_FIRMWARE_CTRL is zero. With two
+klog (00088) <27/07/16> ADV : different pointers defined, the kernel
+klog (00089) <27/07/16> ADV : has to make a choice, and opts for the
+klog (00090) <27/07/16> ADV : 32 bit pointer. Because these pointers
+klog (00091) <27/07/16> ADV : are different, it suggests either one
+klog (00092) <27/07/16> ADV : of them is incorrect, or different 32
+klog (00093) <27/07/16> ADV : bit and 64 bit FACS tables are present
+klog (00094) <27/07/16> ADV : in your system, which is NOT complaint
+klog (00095) <27/07/16> ADV : with the ACPI specification. The
+klog (00096) <27/07/16> ADV : kernel has to make a choice and opts
+klog (00097) <27/07/16> ADV : for the 32 bit FIRMWARE_CTRL.
+klog (00098) <27/07/16> NLN :
+klog (00099) <27/07/16> FAL H: FAILED [HIGH]
+klog (00100) <27/07/16> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt
+klog (00101) <27/07/16> FAL H: : Test 1, HIGH Kernel message: [
+klog (00102) <27/07/16> FAL H: 0.000000] ACPI Warning: 32/64X FACS
+klog (00103) <27/07/16> FAL H: address mismatch in FADT - DEF2DF40
+klog (00104) <27/07/16> FAL H: /00000000DEF30D40, using 32 (20090903
+klog (00105) <27/07/16> FAL H: /tbfadt-486)
+klog (00106) <27/07/16> NLN :
+klog (00107) <27/07/16> ADV : ADVICE: The FADT table contains
+klog (00108) <27/07/16> ADV : Generic Address Structure that has a
+klog (00109) <27/07/16> ADV : mismatch between the 32 bit and 64 bit
+klog (00110) <27/07/16> ADV : versions of an address. This should be
+klog (00111) <27/07/16> ADV : fixed so there are no mismatches.
+klog (00112) <27/07/16> NLN :
+klog (00113) <27/07/16> FAL H: FAILED [HIGH]
+klog (00114) <27/07/16> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt
+klog (00115) <27/07/16> FAL H: : Test 1, HIGH Kernel message: [
+klog (00116) <27/07/16> FAL H: 0.000000] ACPI Warning: 32/64X length
+klog (00117) <27/07/16> FAL H: mismatch in Gpe1Block: 0/32 20090521
+klog (00118) <27/07/16> FAL H: tbfadt-527
+klog (00119) <27/07/16> NLN :
+klog (00120) <27/07/16> ADV : ADVICE: The FADT table contains
+klog (00121) <27/07/16> ADV : Generic Address Structure that has a
+klog (00122) <27/07/16> ADV : mismatch between the 32 bit and 64 bit
+klog (00123) <27/07/16> ADV : versions of an address. This should be
+klog (00124) <27/07/16> ADV : fixed so there are no mismatches.
+klog (00125) <27/07/16> NLN :
+klog (00126) <27/07/16> FAL H: FAILED [HIGH] KlogAcpiBadAmlCode: Test
+klog (00127) <27/07/16> FAL H: 1, HIGH Kernel message: [ 0.000000]
+klog (00128) <27/07/16> FAL H: ACPI Warning: BIOS XSDT has NULL entry
+klog (00129) <27/07/16> FAL H: , using RSDT (20110112/tbutils-663)
+klog (00130) <27/07/16> NLN :
+klog (00131) <27/07/16> ADV : ADVICE: ACPI AML intepreter has found
+klog (00132) <27/07/16> ADV : some non-conforming AML code. This
+klog (00133) <27/07/16> ADV : should be investigated and fixed.
+klog (00134) <27/07/16> NLN :
+klog (00135) <27/07/16> FAL H: FAILED [HIGH]
+klog (00136) <27/07/16> FAL H: KlogAcpiFadtInvalidLength: Test 1,
+klog (00137) <27/07/16> FAL H: HIGH Kernel message: [ 0.000000] ACPI
+klog (00138) <27/07/16> FAL H: Warning: Invalid length for
+klog (00139) <27/07/16> FAL H: Pm1aControlBlock: 32, using default 16
+klog (00140) <27/07/16> FAL H: (20090903/tbfadt-607)
+klog (00141) <27/07/16> NLN :
+klog (00142) <27/07/16> ADV : ADVICE: This item in the FADT is the
+klog (00143) <27/07/16> ADV : incorrect length. Should be corrected.
+klog (00144) <27/07/16> NLN :
+klog (00145) <27/07/16> FAL H: FAILED [HIGH]
+klog (00146) <27/07/16> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
+klog (00147) <27/07/16> FAL H: : Test 1, HIGH Kernel message: [
+klog (00148) <27/07/16> FAL H: 0.000000] ACPI Warning: Optional field
+klog (00149) <27/07/16> FAL H: Gpe1Block has zero address or length:
+klog (00150) <27/07/16> FAL H: 000000000000102C/0 20090521 tbfadt-558
+klog (00151) <27/07/16> NLN :
+klog (00152) <27/07/16> ADV : ADVICE: An ACPI table contains Generic
+klog (00153) <27/07/16> ADV : Address Structure that has an address
+klog (00154) <27/07/16> ADV : that is incorrectly set to zero, or a
+klog (00155) <27/07/16> ADV : zero length. This needs to be fixed.
+klog (00156) <27/07/16> NLN :
+klog (00157) <27/07/16> FAL H: FAILED [HIGH]
+klog (00158) <27/07/16> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
+klog (00159) <27/07/16> FAL H: : Test 1, HIGH Kernel message: [
+klog (00160) <27/07/16> FAL H: 0.000000] ACPI Warning: Optional field
+klog (00161) <27/07/16> FAL H: Pm2ControlBlock has zero address or
+klog (00162) <27/07/16> FAL H: length: 0000000000000000/1 20090521
+klog (00163) <27/07/16> FAL H: tbfadt-558
+klog (00164) <27/07/16> NLN :
+klog (00165) <27/07/16> ADV : ADVICE: An ACPI table contains Generic
+klog (00166) <27/07/16> ADV : Address Structure that has an address
+klog (00167) <27/07/16> ADV : that is incorrectly set to zero, or a
+klog (00168) <27/07/16> ADV : zero length. This needs to be fixed.
+klog (00169) <27/07/16> NLN :
+klog (00170) <27/07/16> FAL H: FAILED [HIGH]
+klog (00171) <27/07/16> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
+klog (00172) <27/07/16> FAL H: : Test 1, HIGH Kernel message: [
+klog (00173) <27/07/16> FAL H: 0.000000] ACPI Warning (tbfadt-0460):
+klog (00174) <27/07/16> FAL H: Optional field "Gpe1Block" has zero
+klog (00175) <27/07/16> FAL H: address or length: 000000000000102C/0
+klog (00176) <27/07/16> FAL H: [20080926]
+klog (00177) <27/07/16> NLN :
+klog (00178) <27/07/16> ADV : ADVICE: An ACPI table contains Generic
+klog (00179) <27/07/16> ADV : Address Structure that has an address
+klog (00180) <27/07/16> ADV : that is incorrectly set to zero, or a
+klog (00181) <27/07/16> ADV : zero length. This needs to be fixed.
+klog (00182) <27/07/16> NLN :
+klog (00183) <27/07/16> FAL M: FAILED [MEDIUM]
+klog (00184) <27/07/16> FAL M: KlogBiosMtrrIncorrectMask: Test 1,
+klog (00185) <27/07/16> FAL M: MEDIUM Kernel message: [ 0.000000]
+klog (00186) <27/07/16> FAL M: mtrr: your BIOS has configured an
+klog (00187) <27/07/16> FAL M: incorrect mask, fixing it.
+klog (00188) <27/07/16> NLN :
+klog (00189) <27/07/16> ADV : ADVICE: The Memory Type Range
+klog (00190) <27/07/16> ADV : Registers (MTRRs) which define memory
+klog (00191) <27/07/16> ADV : caching policy are misconfigued by the
+klog (00192) <27/07/16> ADV : BIOS. In this case, the mask is
+klog (00193) <27/07/16> ADV : incorrectly set and the kernel has
+klog (00194) <27/07/16> ADV : detected this and worked around the
+klog (00195) <27/07/16> ADV : firmware bug.
+klog (00196) <27/07/16> NLN :
+klog (00197) <27/07/16> FAL C: FAILED [CRITICAL]
+klog (00198) <27/07/16> FAL C: KlogBiosCpuMtrrMisconfigured: Test 1,
+klog (00199) <27/07/16> FAL C: CRITICAL Kernel message: [ 0.000000]
+klog (00200) <27/07/16> FAL C: WARNING: BIOS bug: CPU MTRRs don't
+klog (00201) <27/07/16> FAL C: cover all of memory, losing 1408MB of
+klog (00202) <27/07/16> FAL C: RAM.
+klog (00203) <27/07/16> NLN :
+klog (00204) <27/07/16> ADV : ADVICE: The Memory Type Range
+klog (00205) <27/07/16> ADV : Registers (MTRRs) which define memory
+klog (00206) <27/07/16> ADV : caching policy are misconfigued by the
+klog (00207) <27/07/16> ADV : BIOS and don't appear to cover all
+klog (00208) <27/07/16> ADV : available physical memory. The kernel
+klog (00209) <27/07/16> ADV : has detected this and has reduced the
+klog (00210) <27/07/16> ADV : amount of memory available to be safe.
+klog (00211) <27/07/16> ADV : Either check that the BIOS memory
+klog (00212) <27/07/16> ADV : caching options are set correctly or
+klog (00213) <27/07/16> ADV : contact your BIOS vendor to get this
+klog (00214) <27/07/16> ADV : fixed.
+klog (00215) <27/07/16> NLN :
+klog (00216) <27/07/16> FAL H: FAILED [HIGH] KlogAcpiUnknownAmlOpcode
+klog (00217) <27/07/16> FAL H: : Test 1, HIGH Kernel message: [
+klog (00218) <27/07/16> FAL H: 0.022719] ACPI Error: Found unknown
+klog (00219) <27/07/16> FAL H: opcode 0xFD at AML address f7ffe14c
+klog (00220) <27/07/16> FAL H: offset 0xE8, ignoring (20110112
+klog (00221) <27/07/16> FAL H: /psloop-141)
+klog (00222) <27/07/16> NLN :
+klog (00223) <27/07/16> ADV : ADVICE: ACPI execution run time error:
+klog (00224) <27/07/16> ADV : The ACPI interpreter has reached an
+klog (00225) <27/07/16> ADV : opcode that is unknown, this normally
+klog (00226) <27/07/16> ADV : is a bug in the underlying AML code
+klog (00227) <27/07/16> ADV : either because of badly written AML
+klog (00228) <27/07/16> ADV : code or the compiler has produced code
+klog (00229) <27/07/16> ADV : that is incorrect or the ACPI
+klog (00230) <27/07/16> ADV : interpreter does not support this
+klog (00231) <27/07/16> ADV : valid opcode.
+klog (00232) <27/07/16> NLN :
+klog (00233) <27/07/16> FAL C: FAILED [CRITICAL]
+klog (00234) <27/07/16> FAL C: KlogAcpiDetectedUnsupportedOpCode:
+klog (00235) <27/07/16> FAL C: Test 1, CRITICAL Kernel message: [
+klog (00236) <27/07/16> FAL C: 0.025463] ACPI Warning: Detected an
+klog (00237) <27/07/16> FAL C: unsupported executable opcode at
+klog (00238) <27/07/16> FAL C: module-level: [0x007B] at table offset
+klog (00239) <27/07/16> FAL C: 0x00C3 (20110112/psloop-526)
+klog (00240) <27/07/16> NLN :
+klog (00241) <27/07/16> ADV : ADVICE: An illegal AML opcode has been
+klog (00242) <27/07/16> ADV : found and is ignored. This indicates
+klog (00243) <27/07/16> ADV : either badly compiled code or opcode
+klog (00244) <27/07/16> ADV : corruption in the DSDT or SSDT tables
+klog (00245) <27/07/16> ADV : or a bug in the ACPI execution engine.
+klog (00246) <27/07/16> ADV : Recommend disassembing using iasl to
+klog (00247) <27/07/16> ADV : find any offending code.
+klog (00248) <27/07/16> NLN :
+klog (00249) <27/07/16> FAL H: FAILED [HIGH]
+klog (00250) <27/07/16> FAL H: KlogAcpiObjectAlreadyExists: Test 1,
+klog (00251) <27/07/16> FAL H: HIGH Kernel message: [ 0.034090] ACPI
+klog (00252) <27/07/16> FAL H: Error: Method parse/execution failed
+klog (00253) <27/07/16> FAL H: [_SB_.PCI0._OSC] (Node ee025630),
+klog (00254) <27/07/16> FAL H: AE_ALREADY_EXISTS (20110112
+klog (00255) <27/07/16> FAL H: /psparse-536)
+klog (00256) <27/07/16> NLN :
+klog (00257) <27/07/16> ADV : ADVICE: This is a bug picked up by the
+klog (00258) <27/07/16> ADV : kernel, but as yet, the firmware test
+klog (00259) <27/07/16> ADV : suite has no diagnostic advice for
+klog (00260) <27/07/16> ADV : this particular problem.
+klog (00261) <27/07/16> NLN :
+klog (00262) <27/07/16> FAL H: FAILED [HIGH] KlogAcpiFirmwareError:
+klog (00263) <27/07/16> FAL H: Test 1, HIGH Kernel message: [
+klog (00264) <27/07/16> FAL H: 0.040119] [Firmware Bug]: the BIOS has
+klog (00265) <27/07/16> FAL H: corrupted hw-PMU resources (MSR 186 is
+klog (00266) <27/07/16> FAL H: 400000)
+klog (00267) <27/07/16> NLN :
+klog (00268) <27/07/16> ADV : ADVICE: The kernel has detected a
+klog (00269) <27/07/16> ADV : Firmware bug in the BIOS or ACPI which
+klog (00270) <27/07/16> ADV : needs investigating and fixing.
+klog (00271) <27/07/16> NLN :
+klog (00272) <27/07/16> FAL C: FAILED [CRITICAL]
+klog (00273) <27/07/16> FAL C: KlogAcpiDetectedUnsupportedOpCode:
+klog (00274) <27/07/16> FAL C: Test 1, CRITICAL Kernel message: [
+klog (00275) <27/07/16> FAL C: 0.042222] ACPI Warning: Detected an
+klog (00276) <27/07/16> FAL C: unsupported executable opcode at
+klog (00277) <27/07/16> FAL C: module-level: [0x0070] at table offset
+klog (00278) <27/07/16> FAL C: 0x2366 (20100121/psloop-526)
+klog (00279) <27/07/16> NLN :
+klog (00280) <27/07/16> ADV : ADVICE: An illegal AML opcode has been
+klog (00281) <27/07/16> ADV : found and is ignored. This indicates
+klog (00282) <27/07/16> ADV : either badly compiled code or opcode
+klog (00283) <27/07/16> ADV : corruption in the DSDT or SSDT tables
+klog (00284) <27/07/16> ADV : or a bug in the ACPI execution engine.
+klog (00285) <27/07/16> ADV : Recommend disassembing using iasl to
+klog (00286) <27/07/16> ADV : find any offending code.
+klog (00287) <27/07/16> NLN :
+klog (00288) <27/07/16> INF : Found 18 unique errors in kernel log.
+klog (00289) <27/07/16> NLN :
+klog (00290) <27/07/16> SEP : ======================================
+klog (00291) <27/07/16> SUM : 0 passed, 18 failed, 0 warning, 0
+klog (00292) <27/07/16> SUM : aborted, 0 skipped, 0 info only.
+klog (00293) <27/07/16> SEP : ======================================
diff --git a/fwts-test/arg-log-format-0001/klog-0002.log b/fwts-test/arg-log-format-0001/klog-0002.log
index cb74c1f..d4accd9 100644
--- a/fwts-test/arg-log-format-0001/klog-0002.log
+++ b/fwts-test/arg-log-format-0001/klog-0002.log
@@ -1,15 +1,14 @@
klog : klog: Scan kernel log for errors and warnings.
klog : ---------------------------------------------------------------
klog : Test 1 of 1: Kernel log error check.
-klog : FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
-klog : Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC/MADT
-klog : found, using 0
-klog :
-klog : ADVICE: The kernel has detected more than one ACPI Multiple
-klog : APIC Description Table (MADT) (these tables have the "APIC"
-klog : signature). There should only be one MADT and the kernel will
-klog : by default select the first one. However, one can override this
-klog : and select the Nth MADT using acpi_apic_instance=N.
+klog : FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM Kernel
+klog : message: [ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found,
+klog : using 0
+klog :
+klog : ADVICE: The BIOS is supposed to supply just one APIC/MADT,
+klog : however, more than one has been found. One can use
+klog : acpi_apic_instance=N to specify the Nth ACPI/MADT to use as an
+klog : override if required.
klog :
klog : FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1, HIGH
klog : Kernel message: [ 0.000000] ACPI Error: 32/64X address mismatch
diff --git a/fwts-test/arg-log-format-0001/klog-0003.log b/fwts-test/arg-log-format-0001/klog-0003.log
index 3bc32af..a98f22a 100644
--- a/fwts-test/arg-log-format-0001/klog-0003.log
+++ b/fwts-test/arg-log-format-0001/klog-0003.log
@@ -1,197 +1,195 @@
klog 00016: klog: Scan kernel log for errors and warnings.
klog 00017: ---------------------------------------------------------
klog 00018: Test 1 of 1: Kernel log error check.
-klog 00019: FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
+klog 00019: FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM
klog 00020: Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC
klog 00021: /MADT found, using 0
klog 00022:
-klog 00023: ADVICE: The kernel has detected more than one ACPI
-klog 00024: Multiple APIC Description Table (MADT) (these tables have
-klog 00025: the "APIC" signature). There should only be one MADT and
-klog 00026: the kernel will by default select the first one. However,
-klog 00027: one can override this and select the Nth MADT using
-klog 00028: acpi_apic_instance=N.
-klog 00029:
-klog 00030: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1,
-klog 00031: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X
-klog 00032: address mismatch in Gpe0Block: 00008018/0000000000008028,
-klog 00033: using 32 (20090903/tbfadt-427)
-klog 00034:
-klog 00035: ADVICE: The FADT table contains a mismatch between a 32
-klog 00036: bit pointer and a 64 bit Generic Address pointer. Because
-klog 00037: these pointers are different, it suggests either one of
-klog 00038: them is incorrect. If a non-null 32 bit pointer exists,
-klog 00039: then the kernel will opt for this in preference to the 64
-klog 00040: bit pointer even though this is not in accordance to the
-klog 00041: ACPI specification.
-klog 00042:
-klog 00043: FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1,
-klog 00044: CRITICAL Kernel message: [ 0.000000] ACPI Error: A valid
-klog 00045: RSDP was not found (20090903/tbxfroot-219)
-klog 00046:
-klog 00047: ADVICE: An ACPI compatible system must provide an RSDP
-klog 00048: (Root System Description Pointer). This structure
-klog 00049: provides the physical address of the RSDT and XSDT. Since
-klog 00050: this could not be found, the ACPI driver has had to
-klog 00051: disable ACPI support.
-klog 00052:
-klog 00053: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel
-klog 00054: message: [ 0.000000] ACPI Warning: 32/64 FACS address
-klog 00055: mismatch in FADT - two FACS tables! (20090903/tbfadt-369)
-klog 00056:
-klog 00057: ADVICE: The FADT table contains a mismatch between the 32
-klog 00058: bit pointer (FIRMWARE_CTRL) and 64 bit pointer
-klog 00059: (X_FIRMWARE_CTRL) pointer to the FACS table. Section
-klog 00060: 5.2.9 of version 4.0a of the ACPI specification states
-klog 00061: that X_FIRMWARE_CTRL should be zero if FIRMWARE_CTRL is
-klog 00062: defined, or FIRMWARE_CTRL should be zero if
-klog 00063: X_FIRMWARE_CTRL is zero. With two different pointers
-klog 00064: defined, the kernel has to make a choice, and opts for
-klog 00065: the 32 bit pointer. Because these pointers are different,
-klog 00066: it suggests either one of them is incorrect, or different
-klog 00067: 32 bit and 64 bit FACS tables are present in your system,
-klog 00068: which is NOT complaint with the ACPI specification. The
-klog 00069: kernel has to make a choice and opts for the 32 bit
-klog 00070: FIRMWARE_CTRL.
-klog 00071:
-klog 00072: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt:
-klog 00073: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32
-klog 00074: /64X FACS address mismatch in FADT - DEF2DF40
-klog 00075: /00000000DEF30D40, using 32 (20090903/tbfadt-486)
-klog 00076:
-klog 00077: ADVICE: The FADT table contains Generic Address Structure
-klog 00078: that has a mismatch between the 32 bit and 64 bit
-klog 00079: versions of an address. This should be fixed so there are
-klog 00080: no mismatches.
-klog 00081:
-klog 00082: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt:
-klog 00083: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32
-klog 00084: /64X length mismatch in Gpe1Block: 0/32 20090521
-klog 00085: tbfadt-527
-klog 00086:
-klog 00087: ADVICE: The FADT table contains Generic Address Structure
-klog 00088: that has a mismatch between the 32 bit and 64 bit
-klog 00089: versions of an address. This should be fixed so there are
-klog 00090: no mismatches.
-klog 00091:
-klog 00092: FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel
-klog 00093: message: [ 0.000000] ACPI Warning: BIOS XSDT has NULL
-klog 00094: entry, using RSDT (20110112/tbutils-663)
-klog 00095:
-klog 00096: ADVICE: ACPI AML intepreter has found some non-conforming
-klog 00097: AML code. This should be investigated and fixed.
-klog 00098:
-klog 00099: FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1, HIGH
-klog 00100: Kernel message: [ 0.000000] ACPI Warning: Invalid length
-klog 00101: for Pm1aControlBlock: 32, using default 16 (20090903
-klog 00102: /tbfadt-607)
-klog 00103:
-klog 00104: ADVICE: This item in the FADT is the incorrect length.
-klog 00105: Should be corrected.
-klog 00106:
-klog 00107: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
-klog 00108: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning:
-klog 00109: Optional field Gpe1Block has zero address or length:
-klog 00110: 000000000000102C/0 20090521 tbfadt-558
-klog 00111:
-klog 00112: ADVICE: An ACPI table contains Generic Address Structure
-klog 00113: that has an address that is incorrectly set to zero, or a
-klog 00114: zero length. This needs to be fixed.
-klog 00115:
-klog 00116: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
-klog 00117: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning:
-klog 00118: Optional field Pm2ControlBlock has zero address or length
-klog 00119: : 0000000000000000/1 20090521 tbfadt-558
-klog 00120:
-klog 00121: ADVICE: An ACPI table contains Generic Address Structure
-klog 00122: that has an address that is incorrectly set to zero, or a
-klog 00123: zero length. This needs to be fixed.
-klog 00124:
-klog 00125: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
-klog 00126: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning
-klog 00127: (tbfadt-0460): Optional field "Gpe1Block" has zero
-klog 00128: address or length: 000000000000102C/0 [20080926]
-klog 00129:
-klog 00130: ADVICE: An ACPI table contains Generic Address Structure
-klog 00131: that has an address that is incorrectly set to zero, or a
-klog 00132: zero length. This needs to be fixed.
-klog 00133:
-klog 00134: FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1, MEDIUM
-klog 00135: Kernel message: [ 0.000000] mtrr: your BIOS has
-klog 00136: configured an incorrect mask, fixing it.
-klog 00137:
-klog 00138: ADVICE: The Memory Type Range Registers (MTRRs) which
-klog 00139: define memory caching policy are misconfigued by the
-klog 00140: BIOS. In this case, the mask is incorrectly set and the
-klog 00141: kernel has detected this and worked around the firmware
-klog 00142: bug.
-klog 00143:
-klog 00144: FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test 1,
-klog 00145: CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug:
-klog 00146: CPU MTRRs don't cover all of memory, losing 1408MB of
-klog 00147: RAM.
-klog 00148:
-klog 00149: ADVICE: The Memory Type Range Registers (MTRRs) which
-klog 00150: define memory caching policy are misconfigued by the BIOS
-klog 00151: and don't appear to cover all available physical memory.
-klog 00152: The kernel has detected this and has reduced the amount
-klog 00153: of memory available to be safe. Either check that the
-klog 00154: BIOS memory caching options are set correctly or contact
-klog 00155: your BIOS vendor to get this fixed.
-klog 00156:
-klog 00157: FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH
-klog 00158: Kernel message: [ 0.022719] ACPI Error: Found unknown
-klog 00159: opcode 0xFD at AML address f7ffe14c offset 0xE8, ignoring
-klog 00160: (20110112/psloop-141)
-klog 00161:
-klog 00162: ADVICE: ACPI execution run time error: The ACPI
-klog 00163: interpreter has reached an opcode that is unknown, this
-klog 00164: normally is a bug in the underlying AML code either
-klog 00165: because of badly written AML code or the compiler has
-klog 00166: produced code that is incorrect or the ACPI interpreter
-klog 00167: does not support this valid opcode.
-klog 00168:
-klog 00169: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test
-klog 00170: 1, CRITICAL Kernel message: [ 0.025463] ACPI Warning:
-klog 00171: Detected an unsupported executable opcode at module-level
-klog 00172: : [0x007B] at table offset 0x00C3 (20110112/psloop-526)
-klog 00173:
-klog 00174: ADVICE: An illegal AML opcode has been found and is
-klog 00175: ignored. This indicates either badly compiled code or
-klog 00176: opcode corruption in the DSDT or SSDT tables or a bug in
-klog 00177: the ACPI execution engine. Recommend disassembing using
-klog 00178: iasl to find any offending code.
-klog 00179:
-klog 00180: FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1, HIGH
-klog 00181: Kernel message: [ 0.034090] ACPI Error: Method parse
-klog 00182: /execution failed [_SB_.PCI0._OSC] (Node ee025630),
-klog 00183: AE_ALREADY_EXISTS (20110112/psparse-536)
-klog 00184:
-klog 00185: ADVICE: This is a bug picked up by the kernel, but as yet
-klog 00186: , the firmware test suite has no diagnostic advice for
-klog 00187: this particular problem.
-klog 00188:
-klog 00189: FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH Kernel
-klog 00190: message: [ 0.040119] [Firmware Bug]: the BIOS has
-klog 00191: corrupted hw-PMU resources (MSR 186 is 400000)
-klog 00192:
-klog 00193: ADVICE: The kernel has detected a Firmware bug in the
-klog 00194: BIOS or ACPI which needs investigating and fixing.
-klog 00195:
-klog 00196: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test
-klog 00197: 1, CRITICAL Kernel message: [ 0.042222] ACPI Warning:
-klog 00198: Detected an unsupported executable opcode at module-level
-klog 00199: : [0x0070] at table offset 0x2366 (20100121/psloop-526)
-klog 00200:
-klog 00201: ADVICE: An illegal AML opcode has been found and is
-klog 00202: ignored. This indicates either badly compiled code or
-klog 00203: opcode corruption in the DSDT or SSDT tables or a bug in
-klog 00204: the ACPI execution engine. Recommend disassembing using
-klog 00205: iasl to find any offending code.
+klog 00023: ADVICE: The BIOS is supposed to supply just one APIC/MADT
+klog 00024: , however, more than one has been found. One can use
+klog 00025: acpi_apic_instance=N to specify the Nth ACPI/MADT to use
+klog 00026: as an override if required.
+klog 00027:
+klog 00028: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1,
+klog 00029: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X
+klog 00030: address mismatch in Gpe0Block: 00008018/0000000000008028,
+klog 00031: using 32 (20090903/tbfadt-427)
+klog 00032:
+klog 00033: ADVICE: The FADT table contains a mismatch between a 32
+klog 00034: bit pointer and a 64 bit Generic Address pointer. Because
+klog 00035: these pointers are different, it suggests either one of
+klog 00036: them is incorrect. If a non-null 32 bit pointer exists,
+klog 00037: then the kernel will opt for this in preference to the 64
+klog 00038: bit pointer even though this is not in accordance to the
+klog 00039: ACPI specification.
+klog 00040:
+klog 00041: FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1,
+klog 00042: CRITICAL Kernel message: [ 0.000000] ACPI Error: A valid
+klog 00043: RSDP was not found (20090903/tbxfroot-219)
+klog 00044:
+klog 00045: ADVICE: An ACPI compatible system must provide an RSDP
+klog 00046: (Root System Description Pointer). This structure
+klog 00047: provides the physical address of the RSDT and XSDT. Since
+klog 00048: this could not be found, the ACPI driver has had to
+klog 00049: disable ACPI support.
+klog 00050:
+klog 00051: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel
+klog 00052: message: [ 0.000000] ACPI Warning: 32/64 FACS address
+klog 00053: mismatch in FADT - two FACS tables! (20090903/tbfadt-369)
+klog 00054:
+klog 00055: ADVICE: The FADT table contains a mismatch between the 32
+klog 00056: bit pointer (FIRMWARE_CTRL) and 64 bit pointer
+klog 00057: (X_FIRMWARE_CTRL) pointer to the FACS table. Section
+klog 00058: 5.2.9 of version 4.0a of the ACPI specification states
+klog 00059: that X_FIRMWARE_CTRL should be zero if FIRMWARE_CTRL is
+klog 00060: defined, or FIRMWARE_CTRL should be zero if
+klog 00061: X_FIRMWARE_CTRL is zero. With two different pointers
+klog 00062: defined, the kernel has to make a choice, and opts for
+klog 00063: the 32 bit pointer. Because these pointers are different,
+klog 00064: it suggests either one of them is incorrect, or different
+klog 00065: 32 bit and 64 bit FACS tables are present in your system,
+klog 00066: which is NOT complaint with the ACPI specification. The
+klog 00067: kernel has to make a choice and opts for the 32 bit
+klog 00068: FIRMWARE_CTRL.
+klog 00069:
+klog 00070: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt:
+klog 00071: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32
+klog 00072: /64X FACS address mismatch in FADT - DEF2DF40
+klog 00073: /00000000DEF30D40, using 32 (20090903/tbfadt-486)
+klog 00074:
+klog 00075: ADVICE: The FADT table contains Generic Address Structure
+klog 00076: that has a mismatch between the 32 bit and 64 bit
+klog 00077: versions of an address. This should be fixed so there are
+klog 00078: no mismatches.
+klog 00079:
+klog 00080: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt:
+klog 00081: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32
+klog 00082: /64X length mismatch in Gpe1Block: 0/32 20090521
+klog 00083: tbfadt-527
+klog 00084:
+klog 00085: ADVICE: The FADT table contains Generic Address Structure
+klog 00086: that has a mismatch between the 32 bit and 64 bit
+klog 00087: versions of an address. This should be fixed so there are
+klog 00088: no mismatches.
+klog 00089:
+klog 00090: FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel
+klog 00091: message: [ 0.000000] ACPI Warning: BIOS XSDT has NULL
+klog 00092: entry, using RSDT (20110112/tbutils-663)
+klog 00093:
+klog 00094: ADVICE: ACPI AML intepreter has found some non-conforming
+klog 00095: AML code. This should be investigated and fixed.
+klog 00096:
+klog 00097: FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1, HIGH
+klog 00098: Kernel message: [ 0.000000] ACPI Warning: Invalid length
+klog 00099: for Pm1aControlBlock: 32, using default 16 (20090903
+klog 00100: /tbfadt-607)
+klog 00101:
+klog 00102: ADVICE: This item in the FADT is the incorrect length.
+klog 00103: Should be corrected.
+klog 00104:
+klog 00105: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
+klog 00106: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning:
+klog 00107: Optional field Gpe1Block has zero address or length:
+klog 00108: 000000000000102C/0 20090521 tbfadt-558
+klog 00109:
+klog 00110: ADVICE: An ACPI table contains Generic Address Structure
+klog 00111: that has an address that is incorrectly set to zero, or a
+klog 00112: zero length. This needs to be fixed.
+klog 00113:
+klog 00114: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
+klog 00115: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning:
+klog 00116: Optional field Pm2ControlBlock has zero address or length
+klog 00117: : 0000000000000000/1 20090521 tbfadt-558
+klog 00118:
+klog 00119: ADVICE: An ACPI table contains Generic Address Structure
+klog 00120: that has an address that is incorrectly set to zero, or a
+klog 00121: zero length. This needs to be fixed.
+klog 00122:
+klog 00123: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
+klog 00124: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning
+klog 00125: (tbfadt-0460): Optional field "Gpe1Block" has zero
+klog 00126: address or length: 000000000000102C/0 [20080926]
+klog 00127:
+klog 00128: ADVICE: An ACPI table contains Generic Address Structure
+klog 00129: that has an address that is incorrectly set to zero, or a
+klog 00130: zero length. This needs to be fixed.
+klog 00131:
+klog 00132: FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1, MEDIUM
+klog 00133: Kernel message: [ 0.000000] mtrr: your BIOS has
+klog 00134: configured an incorrect mask, fixing it.
+klog 00135:
+klog 00136: ADVICE: The Memory Type Range Registers (MTRRs) which
+klog 00137: define memory caching policy are misconfigued by the
+klog 00138: BIOS. In this case, the mask is incorrectly set and the
+klog 00139: kernel has detected this and worked around the firmware
+klog 00140: bug.
+klog 00141:
+klog 00142: FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test 1,
+klog 00143: CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug:
+klog 00144: CPU MTRRs don't cover all of memory, losing 1408MB of
+klog 00145: RAM.
+klog 00146:
+klog 00147: ADVICE: The Memory Type Range Registers (MTRRs) which
+klog 00148: define memory caching policy are misconfigued by the BIOS
+klog 00149: and don't appear to cover all available physical memory.
+klog 00150: The kernel has detected this and has reduced the amount
+klog 00151: of memory available to be safe. Either check that the
+klog 00152: BIOS memory caching options are set correctly or contact
+klog 00153: your BIOS vendor to get this fixed.
+klog 00154:
+klog 00155: FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH
+klog 00156: Kernel message: [ 0.022719] ACPI Error: Found unknown
+klog 00157: opcode 0xFD at AML address f7ffe14c offset 0xE8, ignoring
+klog 00158: (20110112/psloop-141)
+klog 00159:
+klog 00160: ADVICE: ACPI execution run time error: The ACPI
+klog 00161: interpreter has reached an opcode that is unknown, this
+klog 00162: normally is a bug in the underlying AML code either
+klog 00163: because of badly written AML code or the compiler has
+klog 00164: produced code that is incorrect or the ACPI interpreter
+klog 00165: does not support this valid opcode.
+klog 00166:
+klog 00167: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test
+klog 00168: 1, CRITICAL Kernel message: [ 0.025463] ACPI Warning:
+klog 00169: Detected an unsupported executable opcode at module-level
+klog 00170: : [0x007B] at table offset 0x00C3 (20110112/psloop-526)
+klog 00171:
+klog 00172: ADVICE: An illegal AML opcode has been found and is
+klog 00173: ignored. This indicates either badly compiled code or
+klog 00174: opcode corruption in the DSDT or SSDT tables or a bug in
+klog 00175: the ACPI execution engine. Recommend disassembing using
+klog 00176: iasl to find any offending code.
+klog 00177:
+klog 00178: FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1, HIGH
+klog 00179: Kernel message: [ 0.034090] ACPI Error: Method parse
+klog 00180: /execution failed [_SB_.PCI0._OSC] (Node ee025630),
+klog 00181: AE_ALREADY_EXISTS (20110112/psparse-536)
+klog 00182:
+klog 00183: ADVICE: This is a bug picked up by the kernel, but as yet
+klog 00184: , the firmware test suite has no diagnostic advice for
+klog 00185: this particular problem.
+klog 00186:
+klog 00187: FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH Kernel
+klog 00188: message: [ 0.040119] [Firmware Bug]: the BIOS has
+klog 00189: corrupted hw-PMU resources (MSR 186 is 400000)
+klog 00190:
+klog 00191: ADVICE: The kernel has detected a Firmware bug in the
+klog 00192: BIOS or ACPI which needs investigating and fixing.
+klog 00193:
+klog 00194: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test
+klog 00195: 1, CRITICAL Kernel message: [ 0.042222] ACPI Warning:
+klog 00196: Detected an unsupported executable opcode at module-level
+klog 00197: : [0x0070] at table offset 0x2366 (20100121/psloop-526)
+klog 00198:
+klog 00199: ADVICE: An illegal AML opcode has been found and is
+klog 00200: ignored. This indicates either badly compiled code or
+klog 00201: opcode corruption in the DSDT or SSDT tables or a bug in
+klog 00202: the ACPI execution engine. Recommend disassembing using
+klog 00203: iasl to find any offending code.
+klog 00204:
+klog 00205: Found 18 unique errors in kernel log.
klog 00206:
-klog 00207: Found 18 unique errors in kernel log.
-klog 00208:
-klog 00209: =========================================================
-klog 00210: 0 passed, 18 failed, 0 warning, 0 aborted, 0 skipped, 0
-klog 00211: info only.
-klog 00212: =========================================================
+klog 00207: =========================================================
+klog 00208: 0 passed, 18 failed, 0 warning, 0 aborted, 0 skipped, 0
+klog 00209: info only.
+klog 00210: =========================================================
diff --git a/fwts-test/arg-log-format-0001/klog-0004.log b/fwts-test/arg-log-format-0001/klog-0004.log
index 80ae876..794501c 100644
--- a/fwts-test/arg-log-format-0001/klog-0004.log
+++ b/fwts-test/arg-log-format-0001/klog-0004.log
@@ -1,213 +1,211 @@
-klog 10/10/11 : klog: Scan kernel log for errors and warnings.
-klog 10/10/11 : ----------------------------------------------------
-klog 10/10/11 : Test 1 of 1: Kernel log error check.
-klog 10/10/11 H: FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1,
-klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI: BIOS bug:
-klog 10/10/11 H: multiple APIC/MADT found, using 0
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: The kernel has detected more than one ACPI
-klog 10/10/11 : Multiple APIC Description Table (MADT) (these tables
-klog 10/10/11 : have the "APIC" signature). There should only be one
-klog 10/10/11 : MADT and the kernel will by default select the first
-klog 10/10/11 : one. However, one can override this and select the
-klog 10/10/11 : Nth MADT using acpi_apic_instance=N.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch:
-klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI Error:
-klog 10/10/11 H: 32/64X address mismatch in Gpe0Block: 00008018
-klog 10/10/11 H: /0000000000008028, using 32 (20090903/tbfadt-427)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: The FADT table contains a mismatch between a
-klog 10/10/11 : 32 bit pointer and a 64 bit Generic Address pointer.
-klog 10/10/11 : Because these pointers are different, it suggests
-klog 10/10/11 : either one of them is incorrect. If a non-null 32
-klog 10/10/11 : bit pointer exists, then the kernel will opt for
-klog 10/10/11 : this in preference to the 64 bit pointer even though
-klog 10/10/11 : this is not in accordance to the ACPI specification.
-klog 10/10/11 :
-klog 10/10/11 C: FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1,
-klog 10/10/11 C: CRITICAL Kernel message: [ 0.000000] ACPI Error: A
-klog 10/10/11 C: valid RSDP was not found (20090903/tbxfroot-219)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: An ACPI compatible system must provide an
-klog 10/10/11 : RSDP (Root System Description Pointer). This
-klog 10/10/11 : structure provides the physical address of the RSDT
-klog 10/10/11 : and XSDT. Since this could not be found, the ACPI
-klog 10/10/11 : driver has had to disable ACPI support.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel
-klog 10/10/11 H: message: [ 0.000000] ACPI Warning: 32/64 FACS
-klog 10/10/11 H: address mismatch in FADT - two FACS tables!
-klog 10/10/11 H: (20090903/tbfadt-369)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: The FADT table contains a mismatch between
-klog 10/10/11 : the 32 bit pointer (FIRMWARE_CTRL) and 64 bit
-klog 10/10/11 : pointer (X_FIRMWARE_CTRL) pointer to the FACS table.
-klog 10/10/11 : Section 5.2.9 of version 4.0a of the ACPI
-klog 10/10/11 : specification states that X_FIRMWARE_CTRL should be
-klog 10/10/11 : zero if FIRMWARE_CTRL is defined, or FIRMWARE_CTRL
-klog 10/10/11 : should be zero if X_FIRMWARE_CTRL is zero. With two
-klog 10/10/11 : different pointers defined, the kernel has to make a
-klog 10/10/11 : choice, and opts for the 32 bit pointer. Because
-klog 10/10/11 : these pointers are different, it suggests either one
-klog 10/10/11 : of them is incorrect, or different 32 bit and 64 bit
-klog 10/10/11 : FACS tables are present in your system, which is NOT
-klog 10/10/11 : complaint with the ACPI specification. The kernel
-klog 10/10/11 : has to make a choice and opts for the 32 bit
-klog 10/10/11 : FIRMWARE_CTRL.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH]
-klog 10/10/11 H: KlogAcpi32Bit64BitAddressMismatchInFadt: Test 1,
-klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Warning: 32
-klog 10/10/11 H: /64X FACS address mismatch in FADT - DEF2DF40
-klog 10/10/11 H: /00000000DEF30D40, using 32 (20090903/tbfadt-486)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: The FADT table contains Generic Address
-klog 10/10/11 : Structure that has a mismatch between the 32 bit and
-klog 10/10/11 : 64 bit versions of an address. This should be fixed
-klog 10/10/11 : so there are no mismatches.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH]
-klog 10/10/11 H: KlogAcpi32Bit64BitAddressMismatchInFadt: Test 1,
-klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Warning: 32
-klog 10/10/11 H: /64X length mismatch in Gpe1Block: 0/32 20090521
-klog 10/10/11 H: tbfadt-527
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: The FADT table contains Generic Address
-klog 10/10/11 : Structure that has a mismatch between the 32 bit and
-klog 10/10/11 : 64 bit versions of an address. This should be fixed
-klog 10/10/11 : so there are no mismatches.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH
-klog 10/10/11 H: Kernel message: [ 0.000000] ACPI Warning: BIOS XSDT
-klog 10/10/11 H: has NULL entry, using RSDT (20110112/tbutils-663)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: ACPI AML intepreter has found some
-klog 10/10/11 : non-conforming AML code. This should be investigated
-klog 10/10/11 : and fixed.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1,
-klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Warning:
-klog 10/10/11 H: Invalid length for Pm1aControlBlock: 32, using
-klog 10/10/11 H: default 16 (20090903/tbfadt-607)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: This item in the FADT is the incorrect
-klog 10/10/11 : length. Should be corrected.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH]
-klog 10/10/11 H: KlogAcpiOptionalFieldZeroAddressOrLength: Test 1,
-klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Warning:
-klog 10/10/11 H: Optional field Gpe1Block has zero address or length:
-klog 10/10/11 H: 000000000000102C/0 20090521 tbfadt-558
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: An ACPI table contains Generic Address
-klog 10/10/11 : Structure that has an address that is incorrectly
-klog 10/10/11 : set to zero, or a zero length. This needs to be
-klog 10/10/11 : fixed.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH]
-klog 10/10/11 H: KlogAcpiOptionalFieldZeroAddressOrLength: Test 1,
-klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Warning:
-klog 10/10/11 H: Optional field Pm2ControlBlock has zero address or
-klog 10/10/11 H: length: 0000000000000000/1 20090521 tbfadt-558
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: An ACPI table contains Generic Address
-klog 10/10/11 : Structure that has an address that is incorrectly
-klog 10/10/11 : set to zero, or a zero length. This needs to be
-klog 10/10/11 : fixed.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH]
-klog 10/10/11 H: KlogAcpiOptionalFieldZeroAddressOrLength: Test 1,
-klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Warning
-klog 10/10/11 H: (tbfadt-0460): Optional field "Gpe1Block" has zero
-klog 10/10/11 H: address or length: 000000000000102C/0 [20080926]
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: An ACPI table contains Generic Address
-klog 10/10/11 : Structure that has an address that is incorrectly
-klog 10/10/11 : set to zero, or a zero length. This needs to be
-klog 10/10/11 : fixed.
-klog 10/10/11 :
-klog 10/10/11 M: FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1,
-klog 10/10/11 M: MEDIUM Kernel message: [ 0.000000] mtrr: your BIOS
-klog 10/10/11 M: has configured an incorrect mask, fixing it.
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: The Memory Type Range Registers (MTRRs)
-klog 10/10/11 : which define memory caching policy are misconfigued
-klog 10/10/11 : by the BIOS. In this case, the mask is incorrectly
-klog 10/10/11 : set and the kernel has detected this and worked
-klog 10/10/11 : around the firmware bug.
-klog 10/10/11 :
-klog 10/10/11 C: FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test
-klog 10/10/11 C: 1, CRITICAL Kernel message: [ 0.000000] WARNING:
-klog 10/10/11 C: BIOS bug: CPU MTRRs don't cover all of memory,
-klog 10/10/11 C: losing 1408MB of RAM.
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: The Memory Type Range Registers (MTRRs)
-klog 10/10/11 : which define memory caching policy are misconfigued
-klog 10/10/11 : by the BIOS and don't appear to cover all available
-klog 10/10/11 : physical memory. The kernel has detected this and
-klog 10/10/11 : has reduced the amount of memory available to be
-klog 10/10/11 : safe. Either check that the BIOS memory caching
-klog 10/10/11 : options are set correctly or contact your BIOS
-klog 10/10/11 : vendor to get this fixed.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH
-klog 10/10/11 H: Kernel message: [ 0.022719] ACPI Error: Found
-klog 10/10/11 H: unknown opcode 0xFD at AML address f7ffe14c offset
-klog 10/10/11 H: 0xE8, ignoring (20110112/psloop-141)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: ACPI execution run time error: The ACPI
-klog 10/10/11 : interpreter has reached an opcode that is unknown,
-klog 10/10/11 : this normally is a bug in the underlying AML code
-klog 10/10/11 : either because of badly written AML code or the
-klog 10/10/11 : compiler has produced code that is incorrect or the
-klog 10/10/11 : ACPI interpreter does not support this valid opcode.
-klog 10/10/11 :
-klog 10/10/11 :
-klog 10/10/11 C: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode:
-klog 10/10/11 C: Test 1, CRITICAL Kernel message: [ 0.025463] ACPI
-klog 10/10/11 C: Warning: Detected an unsupported executable opcode
-klog 10/10/11 C: at module-level: [0x007B] at table offset 0x00C3
-klog 10/10/11 C: (20110112/psloop-526)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: An illegal AML opcode has been found and is
-klog 10/10/11 : ignored. This indicates either badly compiled code
-klog 10/10/11 : or opcode corruption in the DSDT or SSDT tables or a
-klog 10/10/11 : bug in the ACPI execution engine. Recommend
-klog 10/10/11 : disassembing using iasl to find any offending code.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1,
-klog 10/10/11 H: HIGH Kernel message: [ 0.034090] ACPI Error: Method
-klog 10/10/11 H: parse/execution failed [_SB_.PCI0._OSC] (Node
-klog 10/10/11 H: ee025630), AE_ALREADY_EXISTS (20110112/psparse-536)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: This is a bug picked up by the kernel, but
-klog 10/10/11 : as yet, the firmware test suite has no diagnostic
-klog 10/10/11 : advice for this particular problem.
-klog 10/10/11 :
-klog 10/10/11 H: FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH
-klog 10/10/11 H: Kernel message: [ 0.040119] [Firmware Bug]: the BIOS
-klog 10/10/11 H: has corrupted hw-PMU resources (MSR 186 is 400000)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: The kernel has detected a Firmware bug in
-klog 10/10/11 : the BIOS or ACPI which needs investigating and
-klog 10/10/11 : fixing.
-klog 10/10/11 :
-klog 10/10/11 C: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode:
-klog 10/10/11 C: Test 1, CRITICAL Kernel message: [ 0.042222] ACPI
-klog 10/10/11 C: Warning: Detected an unsupported executable opcode
-klog 10/10/11 C: at module-level: [0x0070] at table offset 0x2366
-klog 10/10/11 C: (20100121/psloop-526)
-klog 10/10/11 :
-klog 10/10/11 : ADVICE: An illegal AML opcode has been found and is
-klog 10/10/11 : ignored. This indicates either badly compiled code
-klog 10/10/11 : or opcode corruption in the DSDT or SSDT tables or a
-klog 10/10/11 : bug in the ACPI execution engine. Recommend
-klog 10/10/11 : disassembing using iasl to find any offending code.
-klog 10/10/11 :
-klog 10/10/11 : Found 18 unique errors in kernel log.
-klog 10/10/11 :
-klog 10/10/11 : ====================================================
-klog 10/10/11 : 0 passed, 18 failed, 0 warning, 0 aborted, 0 skipped
-klog 10/10/11 : , 0 info only.
-klog 10/10/11 : ====================================================
+klog 27/07/16 : klog: Scan kernel log for errors and warnings.
+klog 27/07/16 : ----------------------------------------------------
+klog 27/07/16 : Test 1 of 1: Kernel log error check.
+klog 27/07/16 M: FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM
+klog 27/07/16 M: Kernel message: [ 0.000000] ACPI: BIOS bug: multiple
+klog 27/07/16 M: APIC/MADT found, using 0
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: The BIOS is supposed to supply just one APIC
+klog 27/07/16 : /MADT, however, more than one has been found. One
+klog 27/07/16 : can use acpi_apic_instance=N to specify the Nth ACPI
+klog 27/07/16 : /MADT to use as an override if required.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch:
+klog 27/07/16 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI Error:
+klog 27/07/16 H: 32/64X address mismatch in Gpe0Block: 00008018
+klog 27/07/16 H: /0000000000008028, using 32 (20090903/tbfadt-427)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: The FADT table contains a mismatch between a
+klog 27/07/16 : 32 bit pointer and a 64 bit Generic Address pointer.
+klog 27/07/16 : Because these pointers are different, it suggests
+klog 27/07/16 : either one of them is incorrect. If a non-null 32
+klog 27/07/16 : bit pointer exists, then the kernel will opt for
+klog 27/07/16 : this in preference to the 64 bit pointer even though
+klog 27/07/16 : this is not in accordance to the ACPI specification.
+klog 27/07/16 :
+klog 27/07/16 C: FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1,
+klog 27/07/16 C: CRITICAL Kernel message: [ 0.000000] ACPI Error: A
+klog 27/07/16 C: valid RSDP was not found (20090903/tbxfroot-219)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: An ACPI compatible system must provide an
+klog 27/07/16 : RSDP (Root System Description Pointer). This
+klog 27/07/16 : structure provides the physical address of the RSDT
+klog 27/07/16 : and XSDT. Since this could not be found, the ACPI
+klog 27/07/16 : driver has had to disable ACPI support.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel
+klog 27/07/16 H: message: [ 0.000000] ACPI Warning: 32/64 FACS
+klog 27/07/16 H: address mismatch in FADT - two FACS tables!
+klog 27/07/16 H: (20090903/tbfadt-369)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: The FADT table contains a mismatch between
+klog 27/07/16 : the 32 bit pointer (FIRMWARE_CTRL) and 64 bit
+klog 27/07/16 : pointer (X_FIRMWARE_CTRL) pointer to the FACS table.
+klog 27/07/16 : Section 5.2.9 of version 4.0a of the ACPI
+klog 27/07/16 : specification states that X_FIRMWARE_CTRL should be
+klog 27/07/16 : zero if FIRMWARE_CTRL is defined, or FIRMWARE_CTRL
+klog 27/07/16 : should be zero if X_FIRMWARE_CTRL is zero. With two
+klog 27/07/16 : different pointers defined, the kernel has to make a
+klog 27/07/16 : choice, and opts for the 32 bit pointer. Because
+klog 27/07/16 : these pointers are different, it suggests either one
+klog 27/07/16 : of them is incorrect, or different 32 bit and 64 bit
+klog 27/07/16 : FACS tables are present in your system, which is NOT
+klog 27/07/16 : complaint with the ACPI specification. The kernel
+klog 27/07/16 : has to make a choice and opts for the 32 bit
+klog 27/07/16 : FIRMWARE_CTRL.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH]
+klog 27/07/16 H: KlogAcpi32Bit64BitAddressMismatchInFadt: Test 1,
+klog 27/07/16 H: HIGH Kernel message: [ 0.000000] ACPI Warning: 32
+klog 27/07/16 H: /64X FACS address mismatch in FADT - DEF2DF40
+klog 27/07/16 H: /00000000DEF30D40, using 32 (20090903/tbfadt-486)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: The FADT table contains Generic Address
+klog 27/07/16 : Structure that has a mismatch between the 32 bit and
+klog 27/07/16 : 64 bit versions of an address. This should be fixed
+klog 27/07/16 : so there are no mismatches.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH]
+klog 27/07/16 H: KlogAcpi32Bit64BitAddressMismatchInFadt: Test 1,
+klog 27/07/16 H: HIGH Kernel message: [ 0.000000] ACPI Warning: 32
+klog 27/07/16 H: /64X length mismatch in Gpe1Block: 0/32 20090521
+klog 27/07/16 H: tbfadt-527
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: The FADT table contains Generic Address
+klog 27/07/16 : Structure that has a mismatch between the 32 bit and
+klog 27/07/16 : 64 bit versions of an address. This should be fixed
+klog 27/07/16 : so there are no mismatches.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH
+klog 27/07/16 H: Kernel message: [ 0.000000] ACPI Warning: BIOS XSDT
+klog 27/07/16 H: has NULL entry, using RSDT (20110112/tbutils-663)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: ACPI AML intepreter has found some
+klog 27/07/16 : non-conforming AML code. This should be investigated
+klog 27/07/16 : and fixed.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1,
+klog 27/07/16 H: HIGH Kernel message: [ 0.000000] ACPI Warning:
+klog 27/07/16 H: Invalid length for Pm1aControlBlock: 32, using
+klog 27/07/16 H: default 16 (20090903/tbfadt-607)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: This item in the FADT is the incorrect
+klog 27/07/16 : length. Should be corrected.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH]
+klog 27/07/16 H: KlogAcpiOptionalFieldZeroAddressOrLength: Test 1,
+klog 27/07/16 H: HIGH Kernel message: [ 0.000000] ACPI Warning:
+klog 27/07/16 H: Optional field Gpe1Block has zero address or length:
+klog 27/07/16 H: 000000000000102C/0 20090521 tbfadt-558
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: An ACPI table contains Generic Address
+klog 27/07/16 : Structure that has an address that is incorrectly
+klog 27/07/16 : set to zero, or a zero length. This needs to be
+klog 27/07/16 : fixed.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH]
+klog 27/07/16 H: KlogAcpiOptionalFieldZeroAddressOrLength: Test 1,
+klog 27/07/16 H: HIGH Kernel message: [ 0.000000] ACPI Warning:
+klog 27/07/16 H: Optional field Pm2ControlBlock has zero address or
+klog 27/07/16 H: length: 0000000000000000/1 20090521 tbfadt-558
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: An ACPI table contains Generic Address
+klog 27/07/16 : Structure that has an address that is incorrectly
+klog 27/07/16 : set to zero, or a zero length. This needs to be
+klog 27/07/16 : fixed.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH]
+klog 27/07/16 H: KlogAcpiOptionalFieldZeroAddressOrLength: Test 1,
+klog 27/07/16 H: HIGH Kernel message: [ 0.000000] ACPI Warning
+klog 27/07/16 H: (tbfadt-0460): Optional field "Gpe1Block" has zero
+klog 27/07/16 H: address or length: 000000000000102C/0 [20080926]
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: An ACPI table contains Generic Address
+klog 27/07/16 : Structure that has an address that is incorrectly
+klog 27/07/16 : set to zero, or a zero length. This needs to be
+klog 27/07/16 : fixed.
+klog 27/07/16 :
+klog 27/07/16 M: FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1,
+klog 27/07/16 M: MEDIUM Kernel message: [ 0.000000] mtrr: your BIOS
+klog 27/07/16 M: has configured an incorrect mask, fixing it.
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: The Memory Type Range Registers (MTRRs)
+klog 27/07/16 : which define memory caching policy are misconfigued
+klog 27/07/16 : by the BIOS. In this case, the mask is incorrectly
+klog 27/07/16 : set and the kernel has detected this and worked
+klog 27/07/16 : around the firmware bug.
+klog 27/07/16 :
+klog 27/07/16 C: FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test
+klog 27/07/16 C: 1, CRITICAL Kernel message: [ 0.000000] WARNING:
+klog 27/07/16 C: BIOS bug: CPU MTRRs don't cover all of memory,
+klog 27/07/16 C: losing 1408MB of RAM.
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: The Memory Type Range Registers (MTRRs)
+klog 27/07/16 : which define memory caching policy are misconfigued
+klog 27/07/16 : by the BIOS and don't appear to cover all available
+klog 27/07/16 : physical memory. The kernel has detected this and
+klog 27/07/16 : has reduced the amount of memory available to be
+klog 27/07/16 : safe. Either check that the BIOS memory caching
+klog 27/07/16 : options are set correctly or contact your BIOS
+klog 27/07/16 : vendor to get this fixed.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH
+klog 27/07/16 H: Kernel message: [ 0.022719] ACPI Error: Found
+klog 27/07/16 H: unknown opcode 0xFD at AML address f7ffe14c offset
+klog 27/07/16 H: 0xE8, ignoring (20110112/psloop-141)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: ACPI execution run time error: The ACPI
+klog 27/07/16 : interpreter has reached an opcode that is unknown,
+klog 27/07/16 : this normally is a bug in the underlying AML code
+klog 27/07/16 : either because of badly written AML code or the
+klog 27/07/16 : compiler has produced code that is incorrect or the
+klog 27/07/16 : ACPI interpreter does not support this valid opcode.
+klog 27/07/16 :
+klog 27/07/16 :
+klog 27/07/16 C: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode:
+klog 27/07/16 C: Test 1, CRITICAL Kernel message: [ 0.025463] ACPI
+klog 27/07/16 C: Warning: Detected an unsupported executable opcode
+klog 27/07/16 C: at module-level: [0x007B] at table offset 0x00C3
+klog 27/07/16 C: (20110112/psloop-526)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: An illegal AML opcode has been found and is
+klog 27/07/16 : ignored. This indicates either badly compiled code
+klog 27/07/16 : or opcode corruption in the DSDT or SSDT tables or a
+klog 27/07/16 : bug in the ACPI execution engine. Recommend
+klog 27/07/16 : disassembing using iasl to find any offending code.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1,
+klog 27/07/16 H: HIGH Kernel message: [ 0.034090] ACPI Error: Method
+klog 27/07/16 H: parse/execution failed [_SB_.PCI0._OSC] (Node
+klog 27/07/16 H: ee025630), AE_ALREADY_EXISTS (20110112/psparse-536)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: This is a bug picked up by the kernel, but
+klog 27/07/16 : as yet, the firmware test suite has no diagnostic
+klog 27/07/16 : advice for this particular problem.
+klog 27/07/16 :
+klog 27/07/16 H: FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH
+klog 27/07/16 H: Kernel message: [ 0.040119] [Firmware Bug]: the BIOS
+klog 27/07/16 H: has corrupted hw-PMU resources (MSR 186 is 400000)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: The kernel has detected a Firmware bug in
+klog 27/07/16 : the BIOS or ACPI which needs investigating and
+klog 27/07/16 : fixing.
+klog 27/07/16 :
+klog 27/07/16 C: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode:
+klog 27/07/16 C: Test 1, CRITICAL Kernel message: [ 0.042222] ACPI
+klog 27/07/16 C: Warning: Detected an unsupported executable opcode
+klog 27/07/16 C: at module-level: [0x0070] at table offset 0x2366
+klog 27/07/16 C: (20100121/psloop-526)
+klog 27/07/16 :
+klog 27/07/16 : ADVICE: An illegal AML opcode has been found and is
+klog 27/07/16 : ignored. This indicates either badly compiled code
+klog 27/07/16 : or opcode corruption in the DSDT or SSDT tables or a
+klog 27/07/16 : bug in the ACPI execution engine. Recommend
+klog 27/07/16 : disassembing using iasl to find any offending code.
+klog 27/07/16 :
+klog 27/07/16 : Found 18 unique errors in kernel log.
+klog 27/07/16 :
+klog 27/07/16 : ====================================================
+klog 27/07/16 : 0 passed, 18 failed, 0 warning, 0 aborted, 0 skipped
+klog 27/07/16 : , 0 info only.
+klog 27/07/16 : ====================================================
diff --git a/fwts-test/arg-results-0001/results-0005.log b/fwts-test/arg-results-0001/results-0005.log
index 0bee2e5..b931cd8 100644
--- a/fwts-test/arg-results-0001/results-0005.log
+++ b/fwts-test/arg-results-0001/results-0005.log
@@ -1,16 +1,14 @@
klog klog: Scan kernel log for errors and warnings.
klog ----------------------------------------------------------
klog Test 1 of 1: Kernel log error check.
-klog FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
+klog FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM
klog Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC
klog /MADT found, using 0
klog
-klog ADVICE: The kernel has detected more than one ACPI
-klog Multiple APIC Description Table (MADT) (these tables have
-klog the "APIC" signature). There should only be one MADT and
-klog the kernel will by default select the first one. However,
-klog one can override this and select the Nth MADT using
-klog acpi_apic_instance=N.
+klog ADVICE: The BIOS is supposed to supply just one APIC/MADT,
+klog however, more than one has been found. One can use
+klog acpi_apic_instance=N to specify the Nth ACPI/MADT to use
+klog as an override if required.
klog
klog Kernel message: [ 0.228089] [Firmware Bug]: ACPI: BIOS
klog _OSI(Linux) query ignored
@@ -58,16 +56,14 @@ klog ==========================================================
klog klog: Scan kernel log for errors and warnings.
klog ----------------------------------------------------------
klog Test 1 of 1: Kernel log error check.
-klog FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
+klog FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM
klog Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC
klog /MADT found, using 0
klog
-klog ADVICE: The kernel has detected more than one ACPI
-klog Multiple APIC Description Table (MADT) (these tables have
-klog the "APIC" signature). There should only be one MADT and
-klog the kernel will by default select the first one. However,
-klog one can override this and select the Nth MADT using
-klog acpi_apic_instance=N.
+klog ADVICE: The BIOS is supposed to supply just one APIC/MADT,
+klog however, more than one has been found. One can use
+klog acpi_apic_instance=N to specify the Nth ACPI/MADT to use
+klog as an override if required.
klog
klog Kernel message: [ 0.228089] [Firmware Bug]: ACPI: BIOS
klog _OSI(Linux) query ignored
diff --git a/fwts-test/arg-results-0001/results.log b/fwts-test/arg-results-0001/results.log
index aa95c94..4baddd7 100644
--- a/fwts-test/arg-results-0001/results.log
+++ b/fwts-test/arg-results-0001/results.log
@@ -1,16 +1,14 @@
klog klog: Scan kernel log for errors and warnings.
klog ----------------------------------------------------------
klog Test 1 of 1: Kernel log error check.
-klog FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
+klog FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM
klog Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC
klog /MADT found, using 0
klog
-klog ADVICE: The kernel has detected more than one ACPI
-klog Multiple APIC Description Table (MADT) (these tables have
-klog the "APIC" signature). There should only be one MADT and
-klog the kernel will by default select the first one. However,
-klog one can override this and select the Nth MADT using
-klog acpi_apic_instance=N.
+klog ADVICE: The BIOS is supposed to supply just one APIC/MADT,
+klog however, more than one has been found. One can use
+klog acpi_apic_instance=N to specify the Nth ACPI/MADT to use
+klog as an override if required.
klog
klog Kernel message: [ 0.228089] [Firmware Bug]: ACPI: BIOS
klog _OSI(Linux) query ignored
diff --git a/fwts-test/arg-results-no-separators-0001/klog-0001.log b/fwts-test/arg-results-no-separators-0001/klog-0001.log
index b7e371d..4f2d0c9 100644
--- a/fwts-test/arg-results-no-separators-0001/klog-0001.log
+++ b/fwts-test/arg-results-no-separators-0001/klog-0001.log
@@ -1,15 +1,13 @@
klog klog: Scan kernel log for errors and warnings.
klog Test 1 of 1: Kernel log error check.
-klog FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
+klog FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM
klog Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC
klog /MADT found, using 0
klog
-klog ADVICE: The kernel has detected more than one ACPI
-klog Multiple APIC Description Table (MADT) (these tables have
-klog the "APIC" signature). There should only be one MADT and
-klog the kernel will by default select the first one. However,
-klog one can override this and select the Nth MADT using
-klog acpi_apic_instance=N.
+klog ADVICE: The BIOS is supposed to supply just one APIC/MADT,
+klog however, more than one has been found. One can use
+klog acpi_apic_instance=N to specify the Nth ACPI/MADT to use
+klog as an override if required.
klog
klog Kernel message: [ 0.228089] [Firmware Bug]: ACPI: BIOS
klog _OSI(Linux) query ignored
diff --git a/fwts-test/klog-0001/klog-0001.log b/fwts-test/klog-0001/klog-0001.log
index 7959b7a..033ae40 100644
--- a/fwts-test/klog-0001/klog-0001.log
+++ b/fwts-test/klog-0001/klog-0001.log
@@ -1,16 +1,14 @@
klog klog: Scan kernel log for errors and warnings.
klog ----------------------------------------------------------
klog Test 1 of 1: Kernel log error check.
-klog FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
+klog FAILED [MEDIUM] KlogAcpiMultipleMadt: Test 1, MEDIUM
klog Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC
klog /MADT found, using 0
klog
-klog ADVICE: The kernel has detected more than one ACPI
-klog Multiple APIC Description Table (MADT) (these tables have
-klog the "APIC" signature). There should only be one MADT and
-klog the kernel will by default select the first one. However,
-klog one can override this and select the Nth MADT using
-klog acpi_apic_instance=N.
+klog ADVICE: The BIOS is supposed to supply just one APIC/MADT,
+klog however, more than one has been found. One can use
+klog acpi_apic_instance=N to specify the Nth ACPI/MADT to use
+klog as an override if required.
klog
klog FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1,
klog HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X
diff --git a/fwts-test/klog-0001/klog-0002.log b/fwts-test/klog-0001/klog-0002.log
index d1d5023..1d18d78 100644
--- a/fwts-test/klog-0001/klog-0002.log
+++ b/fwts-test/klog-0001/klog-0002.log
@@ -30,8 +30,7 @@ summary klog: CRITICAL Kernel message: [ 1.336148] ACPI Error (psparse-
summary klog: CRITICAL Kernel message: [ 1.371180] ACPI Error (psparse-0537): Method parse/execution failed [_SB_._OSC] (Node ffff88044b85e4a0), AE_AML_BUFFER_LIMIT
summary klog: CRITICAL Kernel message: [ 2.949716] ACPI Error: Method parse/execution failed [_SB_._OSC] (Node ffff880297016ca8), AE_AML_BUFFER_LIMIT (20110112/psparse-536)
summary
-summary High failures: 1221
-summary klog: HIGH Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0
+summary High failures: 1220
summary klog: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X address mismatch in Gpe0Block: 00008018/0000000000008028, using 32 (20090903/tbfadt-427)
summary klog: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X address mismatch in Gpe0Block: 00008020/0000000000008028, using 32 (20090903/tbfadt-427)
summary klog: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X address mismatch in Gpe0Block: 0x00008020/0x0000000000008028, using 32 (20110112/tbfadt-427)
@@ -1253,7 +1252,8 @@ summary klog: HIGH Kernel message: [ 44.661543] ACPI Warning for _SB_.P
summary klog: HIGH Kernel message: [ 50.737630] ACPI Warning for _SB_.PCI0.AGP_.VID_.MXMI: Excess arguments - needs 1, found 2 (20090903/nspredef-303)
summary klog: HIGH Kernel message: [ 50.737686] ACPI Warning for _SB_.PCI0.AGP_.VID_.MXMS: Excess arguments - needs 1, found 2 (20090903/nspredef-303)
summary
-summary Medium failures: 330
+summary Medium failures: 331
+summary klog: MEDIUM Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0
summary klog: MEDIUM Kernel message: [ 0.000000] ACPI Warning: Incorrect checksum in table [APIC] - 0x3E, should be 0x41 (20110112/tbutils-314)
summary klog: MEDIUM Kernel message: [ 0.000000] ACPI Warning: Incorrect checksum in table [APIC] - 0x65, should be 0x68 (20110112/tbutils-314)
summary klog: MEDIUM Kernel message: [ 0.000000] ACPI Warning: Incorrect checksum in table [APIC] - 0x69, should be 0x6C (20110112/tbutils-314)
--
1.9.1
More information about the fwts-devel
mailing list