| Message ID | 1354187150-6508-1-git-send-email-colin.king@canonical.com |
|---|---|
| State | Accepted |
| Headers | show |
On Thu, Nov 29, 2012 at 7:05 PM, Colin King <colin.king@canonical.com> wrote: > From: Colin Ian King <colin.king@canonical.com> > > Because of the changes in the way the klog test now generates error > labels we have to update the test results here. > > Signed-off-by: Colin Ian King <colin.king@canonical.com> > --- > arg-log-format-0001/klog-0001.log | 504 +++++++++++++++++++------------------- > arg-log-format-0001/klog-0002.log | 98 ++++---- > arg-log-format-0001/klog-0003.log | 274 ++++++++++----------- > arg-log-format-0001/klog-0004.log | 141 +++++------ > 4 files changed, 512 insertions(+), 505 deletions(-) > > diff --git a/arg-log-format-0001/klog-0001.log b/arg-log-format-0001/klog-0001.log > index 973ff4b..a332bea 100644 > --- a/arg-log-format-0001/klog-0001.log > +++ b/arg-log-format-0001/klog-0001.log > @@ -3,7 +3,7 @@ klog (00018) <16/05/12> HED : warnings. > klog (00019) <16/05/12> SEP : -------------------------------------- > klog (00020) <16/05/12> INF : Test 1 of 1: Kernel log error check. > klog (00021) <16/05/12> FAL H: FAILED [HIGH] > -klog (00022) <16/05/12> FAL H: KlogACPIBIOSBugMultipleAPIC: Test 1, > +klog (00022) <16/05/12> FAL H: KlogAcpiMultipleApicMadtFound: Test 1, > klog (00023) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI: > klog (00024) <16/05/12> FAL H: BIOS bug: multiple APIC/MADT found, > klog (00025) <16/05/12> FAL H: using 0 > @@ -19,253 +19,257 @@ klog (00034) <16/05/12> ADV : select the Nth MADT using > klog (00035) <16/05/12> ADV : acpi_apic_instance=N. > klog (00036) <16/05/12> NLN : > klog (00037) <16/05/12> FAL H: FAILED [HIGH] > -klog (00038) <16/05/12> FAL H: KlogACPIError3264XAddress: Test 1, > -klog (00039) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI > -klog (00040) <16/05/12> FAL H: Error: 32/64X address mismatch in > -klog (00041) <16/05/12> FAL H: Gpe0Block: 00008018/0000000000008028, > -klog (00042) <16/05/12> FAL H: using 32 (20090903/tbfadt-427) > -klog (00043) <16/05/12> NLN : > -klog (00044) <16/05/12> ADV : ADVICE: The FADT table contains a > -klog (00045) <16/05/12> ADV : mismatch between a 32 bit pointer and > -klog (00046) <16/05/12> ADV : a 64 bit Generic Address pointer. > -klog (00047) <16/05/12> ADV : Because these pointers are different, > -klog (00048) <16/05/12> ADV : it suggests either one of them is > -klog (00049) <16/05/12> ADV : incorrect. If a non-null 32 bit > -klog (00050) <16/05/12> ADV : pointer exists, then the kernel will > -klog (00051) <16/05/12> ADV : opt for this in preference to the 64 > -klog (00052) <16/05/12> ADV : bit pointer even though this is not in > -klog (00053) <16/05/12> ADV : accordance to the ACPI specification. > -klog (00054) <16/05/12> NLN : > -klog (00055) <16/05/12> FAL C: FAILED [CRITICAL] > -klog (00056) <16/05/12> FAL C: KlogACPIErrorAValidRSDP: Test 1, > -klog (00057) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000] > -klog (00058) <16/05/12> FAL C: ACPI Error: A valid RSDP was not found > -klog (00059) <16/05/12> FAL C: (20090903/tbxfroot-219) > -klog (00060) <16/05/12> NLN : > -klog (00061) <16/05/12> ADV : ADVICE: An ACPI-compatible system must > -klog (00062) <16/05/12> ADV : provide an RSDP (Root System > -klog (00063) <16/05/12> ADV : Description Pointer in the system’s > -klog (00064) <16/05/12> ADV : low address space. This structure’s > -klog (00065) <16/05/12> ADV : only purpose is to provide the > -klog (00066) <16/05/12> ADV : physical address of the RSDT and XSDT. > -klog (00067) <16/05/12> NLN : > -klog (00068) <16/05/12> FAL H: FAILED [HIGH] > -klog (00069) <16/05/12> FAL H: KlogACPIWarningErrortwoFACS: Test 1, > -klog (00070) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI > -klog (00071) <16/05/12> FAL H: Warning: 32/64 FACS address mismatch > -klog (00072) <16/05/12> FAL H: in FADT - two FACS tables! (20090903 > -klog (00073) <16/05/12> FAL H: /tbfadt-369) > -klog (00074) <16/05/12> NLN : > -klog (00075) <16/05/12> ADV : ADVICE: The FADT table contains a > -klog (00076) <16/05/12> ADV : mismatch between the 32 bit pointer > -klog (00077) <16/05/12> ADV : (FIRMWARE_CTRL) and 64 bit pointer > -klog (00078) <16/05/12> ADV : (X_FIRMWARE_CTRL) pointer to the FACS > -klog (00079) <16/05/12> ADV : table. Section 5.2.9 of version 4.0a > -klog (00080) <16/05/12> ADV : of the ACPI specification states that > -klog (00081) <16/05/12> ADV : X_FIRMWARE_CTRL should be zero if > -klog (00082) <16/05/12> ADV : FIRMWARE_CTRL is defined, or > -klog (00083) <16/05/12> ADV : FIRMWARE_CTRL should be zero if > -klog (00084) <16/05/12> ADV : X_FIRMWARE_CTRL is zero. With two > -klog (00085) <16/05/12> ADV : different pointers defined, the kernel > -klog (00086) <16/05/12> ADV : has to make a choice, and opts for the > -klog (00087) <16/05/12> ADV : 32 bit pointer. Because these pointers > -klog (00088) <16/05/12> ADV : are different, it suggests either one > -klog (00089) <16/05/12> ADV : of them is incorrect, or different 32 > -klog (00090) <16/05/12> ADV : bit and 64 bit FACS tables are present > -klog (00091) <16/05/12> ADV : in your system, which is NOT complaint > -klog (00092) <16/05/12> ADV : with the ACPI specification. The > -klog (00093) <16/05/12> ADV : kernel has to make a choice and opts > -klog (00094) <16/05/12> ADV : for the 32 bit FIRMWARE_CTRL. > -klog (00095) <16/05/12> NLN : > -klog (00096) <16/05/12> FAL H: FAILED [HIGH] > -klog (00097) <16/05/12> FAL H: KlogACPIWarningError3264length: Test 1 > -klog (00098) <16/05/12> FAL H: , HIGH Kernel message: [ 0.000000] > -klog (00099) <16/05/12> FAL H: ACPI Warning: 32/64X FACS address > -klog (00100) <16/05/12> FAL H: mismatch in FADT - DEF2DF40 > -klog (00101) <16/05/12> FAL H: /00000000DEF30D40, using 32 (20090903 > -klog (00102) <16/05/12> FAL H: /tbfadt-486) > -klog (00103) <16/05/12> NLN : > -klog (00104) <16/05/12> ADV : ADVICE: The FADT table contains > -klog (00105) <16/05/12> ADV : Generic Address Structure that has a > -klog (00106) <16/05/12> ADV : mismatch between the 32 bit and 64 bit > -klog (00107) <16/05/12> ADV : versions of an address. This should be > -klog (00108) <16/05/12> ADV : fixed so there are no mismatches. > -klog (00109) <16/05/12> NLN : > -klog (00110) <16/05/12> FAL H: FAILED [HIGH] > -klog (00111) <16/05/12> FAL H: KlogACPIWarningError3264length: Test 1 > -klog (00112) <16/05/12> FAL H: , HIGH Kernel message: [ 0.000000] > -klog (00113) <16/05/12> FAL H: ACPI Warning: 32/64X length mismatch > -klog (00114) <16/05/12> FAL H: in Gpe1Block: 0/32 20090521 tbfadt-527 > -klog (00115) <16/05/12> NLN : > -klog (00116) <16/05/12> ADV : ADVICE: The FADT table contains > -klog (00117) <16/05/12> ADV : Generic Address Structure that has a > -klog (00118) <16/05/12> ADV : mismatch between the 32 bit and 64 bit > -klog (00119) <16/05/12> ADV : versions of an address. This should be > -klog (00120) <16/05/12> ADV : fixed so there are no mismatches. > -klog (00121) <16/05/12> NLN : > -klog (00122) <16/05/12> FAL H: FAILED [HIGH] KlogACPIWarning: Test 1, > -klog (00123) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI > -klog (00124) <16/05/12> FAL H: Warning: BIOS XSDT has NULL entry, > -klog (00125) <16/05/12> FAL H: using RSDT (20110112/tbutils-663) > -klog (00126) <16/05/12> NLN : > -klog (00127) <16/05/12> ADV : ADVICE: ACPI AML intepreter has found > -klog (00128) <16/05/12> ADV : some non-conforming AML code. This > -klog (00129) <16/05/12> ADV : should be investigated and fixed. > -klog (00130) <16/05/12> NLN : > -klog (00131) <16/05/12> FAL H: FAILED [HIGH] > -klog (00132) <16/05/12> FAL H: KlogACPIWarningInvalidLengthForfadt: > -klog (00133) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ > -klog (00134) <16/05/12> FAL H: 0.000000] ACPI Warning: Invalid length > -klog (00135) <16/05/12> FAL H: for Pm1aControlBlock: 32, using > -klog (00136) <16/05/12> FAL H: default 16 (20090903/tbfadt-607) > -klog (00137) <16/05/12> NLN : > -klog (00138) <16/05/12> ADV : ADVICE: This item in the FADT is the > -klog (00139) <16/05/12> ADV : incorrect length. Should be corrected. > -klog (00140) <16/05/12> NLN : > -klog (00141) <16/05/12> FAL H: FAILED [HIGH] > -klog (00142) <16/05/12> FAL H: KlogACPIWarningOptionalFieldhasZero: > -klog (00143) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ > -klog (00144) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field > -klog (00145) <16/05/12> FAL H: Gpe1Block has zero address or length: > -klog (00146) <16/05/12> FAL H: 000000000000102C/0 20090521 tbfadt-558 > -klog (00147) <16/05/12> NLN : > -klog (00148) <16/05/12> ADV : ADVICE: An ACPI table contains Generic > -klog (00149) <16/05/12> ADV : Address Structure that has an address > -klog (00150) <16/05/12> ADV : that is incorrectly set to zero, or a > -klog (00151) <16/05/12> ADV : zero length. This needs to be fixed. > -klog (00152) <16/05/12> NLN : > -klog (00153) <16/05/12> FAL H: FAILED [HIGH] > -klog (00154) <16/05/12> FAL H: KlogACPIWarningOptionalFieldhasZero: > -klog (00155) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ > -klog (00156) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field > -klog (00157) <16/05/12> FAL H: Pm2ControlBlock has zero address or > -klog (00158) <16/05/12> FAL H: length: 0000000000000000/1 20090521 > -klog (00159) <16/05/12> FAL H: tbfadt-558 > -klog (00160) <16/05/12> NLN : > -klog (00161) <16/05/12> ADV : ADVICE: An ACPI table contains Generic > -klog (00162) <16/05/12> ADV : Address Structure that has an address > -klog (00163) <16/05/12> ADV : that is incorrectly set to zero, or a > -klog (00164) <16/05/12> ADV : zero length. This needs to be fixed. > -klog (00165) <16/05/12> NLN : > -klog (00166) <16/05/12> FAL H: FAILED [HIGH] > -klog (00167) <16/05/12> FAL H: KlogACPIWarningOptionalFieldhasZero: > -klog (00168) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ > -klog (00169) <16/05/12> FAL H: 0.000000] ACPI Warning (tbfadt-0460): > -klog (00170) <16/05/12> FAL H: Optional field "Gpe1Block" has zero > -klog (00171) <16/05/12> FAL H: address or length: 000000000000102C/0 > -klog (00172) <16/05/12> FAL H: [20080926] > -klog (00173) <16/05/12> NLN : > -klog (00174) <16/05/12> ADV : ADVICE: An ACPI table contains Generic > -klog (00175) <16/05/12> ADV : Address Structure that has an address > -klog (00176) <16/05/12> ADV : that is incorrectly set to zero, or a > -klog (00177) <16/05/12> ADV : zero length. This needs to be fixed. > -klog (00178) <16/05/12> NLN : > -klog (00179) <16/05/12> FAL M: FAILED [MEDIUM] > -klog (00180) <16/05/12> FAL M: KlogMtrryourBIOSHasConfigured: Test 1, > -klog (00181) <16/05/12> FAL M: MEDIUM Kernel message: [ 0.000000] > -klog (00182) <16/05/12> FAL M: mtrr: your BIOS has configured an > -klog (00183) <16/05/12> FAL M: incorrect mask, fixing it. > -klog (00184) <16/05/12> NLN : > -klog (00185) <16/05/12> ADV : ADVICE: The Memory Type Range > -klog (00186) <16/05/12> ADV : Registers (MTRRs) which define memory > -klog (00187) <16/05/12> ADV : caching policy are misconfigued by the > -klog (00188) <16/05/12> ADV : BIOS. In this case, the mask is > -klog (00189) <16/05/12> ADV : incorrectly set and the kernel has > -klog (00190) <16/05/12> ADV : detected this and worked around the > -klog (00191) <16/05/12> ADV : firmware bug. > -klog (00192) <16/05/12> NLN : > -klog (00193) <16/05/12> FAL C: FAILED [CRITICAL] > -klog (00194) <16/05/12> FAL C: KlogWARNINGBIOSBugCPUMTRRsDont: Test 1 > -klog (00195) <16/05/12> FAL C: , CRITICAL Kernel message: [ 0.000000] > -klog (00196) <16/05/12> FAL C: WARNING: BIOS bug: CPU MTRRs don't > -klog (00197) <16/05/12> FAL C: cover all of memory, losing 1408MB of > -klog (00198) <16/05/12> FAL C: RAM. > -klog (00199) <16/05/12> NLN : > -klog (00200) <16/05/12> ADV : ADVICE: The Memory Type Range > -klog (00201) <16/05/12> ADV : Registers (MTRRs) which define memory > -klog (00202) <16/05/12> ADV : caching policy are misconfigued by the > -klog (00203) <16/05/12> ADV : BIOS and don't appear to cover all > -klog (00204) <16/05/12> ADV : available physical memory. The kernel > -klog (00205) <16/05/12> ADV : has detected this and has reduced the > -klog (00206) <16/05/12> ADV : amount of memory available to be safe. > -klog (00207) <16/05/12> ADV : Either check that the BIOS memory > -klog (00208) <16/05/12> ADV : caching options are set correctly or > -klog (00209) <16/05/12> ADV : contact your BIOS vendor to get this > -klog (00210) <16/05/12> ADV : fixed. > -klog (00211) <16/05/12> NLN : > -klog (00212) <16/05/12> FAL C: FAILED [CRITICAL] > -klog (00213) <16/05/12> FAL C: KlogACPIErrorFoundUnknownOpcode: Test > -klog (00214) <16/05/12> FAL C: 1, CRITICAL Kernel message: [ > -klog (00215) <16/05/12> FAL C: 0.022719] ACPI Error: Found unknown > -klog (00216) <16/05/12> FAL C: opcode 0xFD at AML address f7ffe14c > -klog (00217) <16/05/12> FAL C: offset 0xE8, ignoring (20110112 > -klog (00218) <16/05/12> FAL C: /psloop-141) > -klog (00219) <16/05/12> NLN : > -klog (00220) <16/05/12> ADV : ADVICE: An illegal AML opcode has been > -klog (00221) <16/05/12> ADV : found and is ignored. This indicates > -klog (00222) <16/05/12> ADV : either badly compiled code or opcode > -klog (00223) <16/05/12> ADV : corruption in the DSDT or SSDT tables > -klog (00224) <16/05/12> ADV : or a bug in the ACPI execution engine. > -klog (00225) <16/05/12> ADV : Recommend disassembing using iasl to > -klog (00226) <16/05/12> ADV : find any offending code. > -klog (00227) <16/05/12> NLN : > -klog (00228) <16/05/12> FAL C: FAILED [CRITICAL] > -klog (00229) <16/05/12> FAL C: KlogACPIWarningDetectedAnUnsupported: > -klog (00230) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [ > -klog (00231) <16/05/12> FAL C: 0.025463] ACPI Warning: Detected an > -klog (00232) <16/05/12> FAL C: unsupported executable opcode at > -klog (00233) <16/05/12> FAL C: module-level: [0x007B] at table offset > -klog (00234) <16/05/12> FAL C: 0x00C3 (20110112/psloop-526) > -klog (00235) <16/05/12> NLN : > -klog (00236) <16/05/12> ADV : ADVICE: An illegal AML opcode has been > -klog (00237) <16/05/12> ADV : found and is ignored. This indicates > -klog (00238) <16/05/12> ADV : either badly compiled code or opcode > -klog (00239) <16/05/12> ADV : corruption in the DSDT or SSDT tables > -klog (00240) <16/05/12> ADV : or a bug in the ACPI execution engine. > -klog (00241) <16/05/12> ADV : Recommend disassembing using iasl to > -klog (00242) <16/05/12> ADV : find any offending code. > -klog (00243) <16/05/12> NLN : > -klog (00244) <16/05/12> FAL H: FAILED [HIGH] > -klog (00245) <16/05/12> FAL H: KlogACPIErrorMethodExecutionParse: > -klog (00246) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ > -klog (00247) <16/05/12> FAL H: 0.034090] ACPI Error: Method parse > -klog (00248) <16/05/12> FAL H: /execution failed [_SB_.PCI0._OSC] > -klog (00249) <16/05/12> FAL H: (Node ee025630), AE_ALREADY_EXISTS > -klog (00250) <16/05/12> FAL H: (20110112/psparse-536) > -klog (00251) <16/05/12> NLN : > -klog (00252) <16/05/12> ADV : ADVICE: This is a bug picked up by the > -klog (00253) <16/05/12> ADV : kernel, but as yet, the firmware test > -klog (00254) <16/05/12> ADV : suite has no diagnostic advice for > -klog (00255) <16/05/12> ADV : this particular problem. > -klog (00256) <16/05/12> NLN : > -klog (00257) <16/05/12> FAL H: FAILED [HIGH] KlogFirmwareBug: Test 1, > -klog (00258) <16/05/12> FAL H: HIGH Kernel message: [ 0.040119] > -klog (00259) <16/05/12> FAL H: [Firmware Bug]: the BIOS has corrupted > -klog (00260) <16/05/12> FAL H: hw-PMU resources (MSR 186 is 400000) > -klog (00261) <16/05/12> NLN : > -klog (00262) <16/05/12> ADV : ADVICE: The kernel has detected a > -klog (00263) <16/05/12> ADV : Firmware bug in the BIOS or ACPI which > -klog (00264) <16/05/12> ADV : needs investigating and fixing. > +klog (00038) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatch: > +klog (00039) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ > +klog (00040) <16/05/12> FAL H: 0.000000] ACPI Error: 32/64X address > +klog (00041) <16/05/12> FAL H: mismatch in Gpe0Block: 00008018 > +klog (00042) <16/05/12> FAL H: /0000000000008028, using 32 (20090903 > +klog (00043) <16/05/12> FAL H: /tbfadt-427) > +klog (00044) <16/05/12> NLN : > +klog (00045) <16/05/12> ADV : ADVICE: The FADT table contains a > +klog (00046) <16/05/12> ADV : mismatch between a 32 bit pointer and > +klog (00047) <16/05/12> ADV : a 64 bit Generic Address pointer. > +klog (00048) <16/05/12> ADV : Because these pointers are different, > +klog (00049) <16/05/12> ADV : it suggests either one of them is > +klog (00050) <16/05/12> ADV : incorrect. If a non-null 32 bit > +klog (00051) <16/05/12> ADV : pointer exists, then the kernel will > +klog (00052) <16/05/12> ADV : opt for this in preference to the 64 > +klog (00053) <16/05/12> ADV : bit pointer even though this is not in > +klog (00054) <16/05/12> ADV : accordance to the ACPI specification. > +klog (00055) <16/05/12> NLN : > +klog (00056) <16/05/12> FAL C: FAILED [CRITICAL] > +klog (00057) <16/05/12> FAL C: KlogAcpiValidRsdpNotFound: Test 1, > +klog (00058) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000] > +klog (00059) <16/05/12> FAL C: ACPI Error: A valid RSDP was not found > +klog (00060) <16/05/12> FAL C: (20090903/tbxfroot-219) > +klog (00061) <16/05/12> NLN : > +klog (00062) <16/05/12> ADV : ADVICE: An ACPI compatible system must > +klog (00063) <16/05/12> ADV : provide an RSDP (Root System > +klog (00064) <16/05/12> ADV : Description Pointer). This structure > +klog (00065) <16/05/12> ADV : provides the physical address of the > +klog (00066) <16/05/12> ADV : RSDT and XSDT. Since this could not be > +klog (00067) <16/05/12> ADV : found, the ACPI driver has had to > +klog (00068) <16/05/12> ADV : disable ACPI support. > +klog (00069) <16/05/12> NLN : > +klog (00070) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, > +klog (00071) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI > +klog (00072) <16/05/12> FAL H: Warning: 32/64 FACS address mismatch > +klog (00073) <16/05/12> FAL H: in FADT - two FACS tables! (20090903 > +klog (00074) <16/05/12> FAL H: /tbfadt-369) > +klog (00075) <16/05/12> NLN : > +klog (00076) <16/05/12> ADV : ADVICE: The FADT table contains a > +klog (00077) <16/05/12> ADV : mismatch between the 32 bit pointer > +klog (00078) <16/05/12> ADV : (FIRMWARE_CTRL) and 64 bit pointer > +klog (00079) <16/05/12> ADV : (X_FIRMWARE_CTRL) pointer to the FACS > +klog (00080) <16/05/12> ADV : table. Section 5.2.9 of version 4.0a > +klog (00081) <16/05/12> ADV : of the ACPI specification states that > +klog (00082) <16/05/12> ADV : X_FIRMWARE_CTRL should be zero if > +klog (00083) <16/05/12> ADV : FIRMWARE_CTRL is defined, or > +klog (00084) <16/05/12> ADV : FIRMWARE_CTRL should be zero if > +klog (00085) <16/05/12> ADV : X_FIRMWARE_CTRL is zero. With two > +klog (00086) <16/05/12> ADV : different pointers defined, the kernel > +klog (00087) <16/05/12> ADV : has to make a choice, and opts for the > +klog (00088) <16/05/12> ADV : 32 bit pointer. Because these pointers > +klog (00089) <16/05/12> ADV : are different, it suggests either one > +klog (00090) <16/05/12> ADV : of them is incorrect, or different 32 > +klog (00091) <16/05/12> ADV : bit and 64 bit FACS tables are present > +klog (00092) <16/05/12> ADV : in your system, which is NOT complaint > +klog (00093) <16/05/12> ADV : with the ACPI specification. The > +klog (00094) <16/05/12> ADV : kernel has to make a choice and opts > +klog (00095) <16/05/12> ADV : for the 32 bit FIRMWARE_CTRL. > +klog (00096) <16/05/12> NLN : > +klog (00097) <16/05/12> FAL H: FAILED [HIGH] > +klog (00098) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt > +klog (00099) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ > +klog (00100) <16/05/12> FAL H: 0.000000] ACPI Warning: 32/64X FACS > +klog (00101) <16/05/12> FAL H: address mismatch in FADT - DEF2DF40 > +klog (00102) <16/05/12> FAL H: /00000000DEF30D40, using 32 (20090903 > +klog (00103) <16/05/12> FAL H: /tbfadt-486) > +klog (00104) <16/05/12> NLN : > +klog (00105) <16/05/12> ADV : ADVICE: The FADT table contains > +klog (00106) <16/05/12> ADV : Generic Address Structure that has a > +klog (00107) <16/05/12> ADV : mismatch between the 32 bit and 64 bit > +klog (00108) <16/05/12> ADV : versions of an address. This should be > +klog (00109) <16/05/12> ADV : fixed so there are no mismatches. > +klog (00110) <16/05/12> NLN : > +klog (00111) <16/05/12> FAL H: FAILED [HIGH] > +klog (00112) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt > +klog (00113) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ > +klog (00114) <16/05/12> FAL H: 0.000000] ACPI Warning: 32/64X length > +klog (00115) <16/05/12> FAL H: mismatch in Gpe1Block: 0/32 20090521 > +klog (00116) <16/05/12> FAL H: tbfadt-527 > +klog (00117) <16/05/12> NLN : > +klog (00118) <16/05/12> ADV : ADVICE: The FADT table contains > +klog (00119) <16/05/12> ADV : Generic Address Structure that has a > +klog (00120) <16/05/12> ADV : mismatch between the 32 bit and 64 bit > +klog (00121) <16/05/12> ADV : versions of an address. This should be > +klog (00122) <16/05/12> ADV : fixed so there are no mismatches. > +klog (00123) <16/05/12> NLN : > +klog (00124) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiBadAmlCode: Test > +klog (00125) <16/05/12> FAL H: 1, HIGH Kernel message: [ 0.000000] > +klog (00126) <16/05/12> FAL H: ACPI Warning: BIOS XSDT has NULL entry > +klog (00127) <16/05/12> FAL H: , using RSDT (20110112/tbutils-663) > +klog (00128) <16/05/12> NLN : > +klog (00129) <16/05/12> ADV : ADVICE: ACPI AML intepreter has found > +klog (00130) <16/05/12> ADV : some non-conforming AML code. This > +klog (00131) <16/05/12> ADV : should be investigated and fixed. > +klog (00132) <16/05/12> NLN : > +klog (00133) <16/05/12> FAL H: FAILED [HIGH] > +klog (00134) <16/05/12> FAL H: KlogAcpiFadtInvalidLength: Test 1, > +klog (00135) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI > +klog (00136) <16/05/12> FAL H: Warning: Invalid length for > +klog (00137) <16/05/12> FAL H: Pm1aControlBlock: 32, using default 16 > +klog (00138) <16/05/12> FAL H: (20090903/tbfadt-607) > +klog (00139) <16/05/12> NLN : > +klog (00140) <16/05/12> ADV : ADVICE: This item in the FADT is the > +klog (00141) <16/05/12> ADV : incorrect length. Should be corrected. > +klog (00142) <16/05/12> NLN : > +klog (00143) <16/05/12> FAL H: FAILED [HIGH] > +klog (00144) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength > +klog (00145) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ > +klog (00146) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field > +klog (00147) <16/05/12> FAL H: Gpe1Block has zero address or length: > +klog (00148) <16/05/12> FAL H: 000000000000102C/0 20090521 tbfadt-558 > +klog (00149) <16/05/12> NLN : > +klog (00150) <16/05/12> ADV : ADVICE: An ACPI table contains Generic > +klog (00151) <16/05/12> ADV : Address Structure that has an address > +klog (00152) <16/05/12> ADV : that is incorrectly set to zero, or a > +klog (00153) <16/05/12> ADV : zero length. This needs to be fixed. > +klog (00154) <16/05/12> NLN : > +klog (00155) <16/05/12> FAL H: FAILED [HIGH] > +klog (00156) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength > +klog (00157) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ > +klog (00158) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field > +klog (00159) <16/05/12> FAL H: Pm2ControlBlock has zero address or > +klog (00160) <16/05/12> FAL H: length: 0000000000000000/1 20090521 > +klog (00161) <16/05/12> FAL H: tbfadt-558 > +klog (00162) <16/05/12> NLN : > +klog (00163) <16/05/12> ADV : ADVICE: An ACPI table contains Generic > +klog (00164) <16/05/12> ADV : Address Structure that has an address > +klog (00165) <16/05/12> ADV : that is incorrectly set to zero, or a > +klog (00166) <16/05/12> ADV : zero length. This needs to be fixed. > +klog (00167) <16/05/12> NLN : > +klog (00168) <16/05/12> FAL H: FAILED [HIGH] > +klog (00169) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength > +klog (00170) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ > +klog (00171) <16/05/12> FAL H: 0.000000] ACPI Warning (tbfadt-0460): > +klog (00172) <16/05/12> FAL H: Optional field "Gpe1Block" has zero > +klog (00173) <16/05/12> FAL H: address or length: 000000000000102C/0 > +klog (00174) <16/05/12> FAL H: [20080926] > +klog (00175) <16/05/12> NLN : > +klog (00176) <16/05/12> ADV : ADVICE: An ACPI table contains Generic > +klog (00177) <16/05/12> ADV : Address Structure that has an address > +klog (00178) <16/05/12> ADV : that is incorrectly set to zero, or a > +klog (00179) <16/05/12> ADV : zero length. This needs to be fixed. > +klog (00180) <16/05/12> NLN : > +klog (00181) <16/05/12> FAL M: FAILED [MEDIUM] > +klog (00182) <16/05/12> FAL M: KlogBiosMtrrIncorrectMask: Test 1, > +klog (00183) <16/05/12> FAL M: MEDIUM Kernel message: [ 0.000000] > +klog (00184) <16/05/12> FAL M: mtrr: your BIOS has configured an > +klog (00185) <16/05/12> FAL M: incorrect mask, fixing it. > +klog (00186) <16/05/12> NLN : > +klog (00187) <16/05/12> ADV : ADVICE: The Memory Type Range > +klog (00188) <16/05/12> ADV : Registers (MTRRs) which define memory > +klog (00189) <16/05/12> ADV : caching policy are misconfigued by the > +klog (00190) <16/05/12> ADV : BIOS. In this case, the mask is > +klog (00191) <16/05/12> ADV : incorrectly set and the kernel has > +klog (00192) <16/05/12> ADV : detected this and worked around the > +klog (00193) <16/05/12> ADV : firmware bug. > +klog (00194) <16/05/12> NLN : > +klog (00195) <16/05/12> FAL C: FAILED [CRITICAL] > +klog (00196) <16/05/12> FAL C: KlogBiosCpuMtrrMisconfigured: Test 1, > +klog (00197) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000] > +klog (00198) <16/05/12> FAL C: WARNING: BIOS bug: CPU MTRRs don't > +klog (00199) <16/05/12> FAL C: cover all of memory, losing 1408MB of > +klog (00200) <16/05/12> FAL C: RAM. > +klog (00201) <16/05/12> NLN : > +klog (00202) <16/05/12> ADV : ADVICE: The Memory Type Range > +klog (00203) <16/05/12> ADV : Registers (MTRRs) which define memory > +klog (00204) <16/05/12> ADV : caching policy are misconfigued by the > +klog (00205) <16/05/12> ADV : BIOS and don't appear to cover all > +klog (00206) <16/05/12> ADV : available physical memory. The kernel > +klog (00207) <16/05/12> ADV : has detected this and has reduced the > +klog (00208) <16/05/12> ADV : amount of memory available to be safe. > +klog (00209) <16/05/12> ADV : Either check that the BIOS memory > +klog (00210) <16/05/12> ADV : caching options are set correctly or > +klog (00211) <16/05/12> ADV : contact your BIOS vendor to get this > +klog (00212) <16/05/12> ADV : fixed. > +klog (00213) <16/05/12> NLN : > +klog (00214) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiUnknownAmlOpcode > +klog (00215) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ > +klog (00216) <16/05/12> FAL H: 0.022719] ACPI Error: Found unknown > +klog (00217) <16/05/12> FAL H: opcode 0xFD at AML address f7ffe14c > +klog (00218) <16/05/12> FAL H: offset 0xE8, ignoring (20110112 > +klog (00219) <16/05/12> FAL H: /psloop-141) > +klog (00220) <16/05/12> NLN : > +klog (00221) <16/05/12> ADV : ADVICE: ACPI execution run time error: > +klog (00222) <16/05/12> ADV : The ACPI interpreter has reached an > +klog (00223) <16/05/12> ADV : opcode that is unknown, this normally > +klog (00224) <16/05/12> ADV : is a bug in the underlying AML code > +klog (00225) <16/05/12> ADV : either because of badly written AML > +klog (00226) <16/05/12> ADV : code or the compiler has produced code > +klog (00227) <16/05/12> ADV : that is incorrect or the ACPI > +klog (00228) <16/05/12> ADV : interpreter does not support this > +klog (00229) <16/05/12> ADV : valid opcode. > +klog (00230) <16/05/12> NLN : > +klog (00231) <16/05/12> FAL C: FAILED [CRITICAL] > +klog (00232) <16/05/12> FAL C: KlogAcpiDetectedUnsupportedOpCode: > +klog (00233) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [ > +klog (00234) <16/05/12> FAL C: 0.025463] ACPI Warning: Detected an > +klog (00235) <16/05/12> FAL C: unsupported executable opcode at > +klog (00236) <16/05/12> FAL C: module-level: [0x007B] at table offset > +klog (00237) <16/05/12> FAL C: 0x00C3 (20110112/psloop-526) > +klog (00238) <16/05/12> NLN : > +klog (00239) <16/05/12> ADV : ADVICE: An illegal AML opcode has been > +klog (00240) <16/05/12> ADV : found and is ignored. This indicates > +klog (00241) <16/05/12> ADV : either badly compiled code or opcode > +klog (00242) <16/05/12> ADV : corruption in the DSDT or SSDT tables > +klog (00243) <16/05/12> ADV : or a bug in the ACPI execution engine. > +klog (00244) <16/05/12> ADV : Recommend disassembing using iasl to > +klog (00245) <16/05/12> ADV : find any offending code. > +klog (00246) <16/05/12> NLN : > +klog (00247) <16/05/12> FAL H: FAILED [HIGH] > +klog (00248) <16/05/12> FAL H: KlogAcpiObjectAlreadyExists: Test 1, > +klog (00249) <16/05/12> FAL H: HIGH Kernel message: [ 0.034090] ACPI > +klog (00250) <16/05/12> FAL H: Error: Method parse/execution failed > +klog (00251) <16/05/12> FAL H: [_SB_.PCI0._OSC] (Node ee025630), > +klog (00252) <16/05/12> FAL H: AE_ALREADY_EXISTS (20110112 > +klog (00253) <16/05/12> FAL H: /psparse-536) > +klog (00254) <16/05/12> NLN : > +klog (00255) <16/05/12> ADV : ADVICE: This is a bug picked up by the > +klog (00256) <16/05/12> ADV : kernel, but as yet, the firmware test > +klog (00257) <16/05/12> ADV : suite has no diagnostic advice for > +klog (00258) <16/05/12> ADV : this particular problem. > +klog (00259) <16/05/12> NLN : > +klog (00260) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiFirmwareError: > +klog (00261) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ > +klog (00262) <16/05/12> FAL H: 0.040119] [Firmware Bug]: the BIOS has > +klog (00263) <16/05/12> FAL H: corrupted hw-PMU resources (MSR 186 is > +klog (00264) <16/05/12> FAL H: 400000) > klog (00265) <16/05/12> NLN : > -klog (00266) <16/05/12> FAL C: FAILED [CRITICAL] > -klog (00267) <16/05/12> FAL C: KlogACPIWarningDetectedAnUnsupported: > -klog (00268) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [ > -klog (00269) <16/05/12> FAL C: 0.042222] ACPI Warning: Detected an > -klog (00270) <16/05/12> FAL C: unsupported executable opcode at > -klog (00271) <16/05/12> FAL C: module-level: [0x0070] at table offset > -klog (00272) <16/05/12> FAL C: 0x2366 (20100121/psloop-526) > -klog (00273) <16/05/12> NLN : > -klog (00274) <16/05/12> ADV : ADVICE: An illegal AML opcode has been > -klog (00275) <16/05/12> ADV : found and is ignored. This indicates > -klog (00276) <16/05/12> ADV : either badly compiled code or opcode > -klog (00277) <16/05/12> ADV : corruption in the DSDT or SSDT tables > -klog (00278) <16/05/12> ADV : or a bug in the ACPI execution engine. > -klog (00279) <16/05/12> ADV : Recommend disassembing using iasl to > -klog (00280) <16/05/12> ADV : find any offending code. > -klog (00281) <16/05/12> NLN : > -klog (00282) <16/05/12> INF : Found 18 unique errors in kernel log. > -klog (00283) <16/05/12> NLN : > -klog (00284) <16/05/12> SEP : ====================================== > -klog (00285) <16/05/12> SUM : 0 passed, 18 failed, 0 warnings, 0 > -klog (00286) <16/05/12> SUM : aborted, 0 skipped, 0 info only. > -klog (00287) <16/05/12> SEP : ====================================== > +klog (00266) <16/05/12> ADV : ADVICE: The kernel has detected a > +klog (00267) <16/05/12> ADV : Firmware bug in the BIOS or ACPI which > +klog (00268) <16/05/12> ADV : needs investigating and fixing. > +klog (00269) <16/05/12> NLN : > +klog (00270) <16/05/12> FAL C: FAILED [CRITICAL] > +klog (00271) <16/05/12> FAL C: KlogAcpiDetectedUnsupportedOpCode: > +klog (00272) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [ > +klog (00273) <16/05/12> FAL C: 0.042222] ACPI Warning: Detected an > +klog (00274) <16/05/12> FAL C: unsupported executable opcode at > +klog (00275) <16/05/12> FAL C: module-level: [0x0070] at table offset > +klog (00276) <16/05/12> FAL C: 0x2366 (20100121/psloop-526) > +klog (00277) <16/05/12> NLN : > +klog (00278) <16/05/12> ADV : ADVICE: An illegal AML opcode has been > +klog (00279) <16/05/12> ADV : found and is ignored. This indicates > +klog (00280) <16/05/12> ADV : either badly compiled code or opcode > +klog (00281) <16/05/12> ADV : corruption in the DSDT or SSDT tables > +klog (00282) <16/05/12> ADV : or a bug in the ACPI execution engine. > +klog (00283) <16/05/12> ADV : Recommend disassembing using iasl to > +klog (00284) <16/05/12> ADV : find any offending code. > +klog (00285) <16/05/12> NLN : > +klog (00286) <16/05/12> INF : Found 18 unique errors in kernel log. > +klog (00287) <16/05/12> NLN : > +klog (00288) <16/05/12> SEP : ====================================== > +klog (00289) <16/05/12> SUM : 0 passed, 18 failed, 0 warnings, 0 > +klog (00290) <16/05/12> SUM : aborted, 0 skipped, 0 info only. > +klog (00291) <16/05/12> SEP : ====================================== > diff --git a/arg-log-format-0001/klog-0002.log b/arg-log-format-0001/klog-0002.log > index 6942a5b..55723ce 100644 > --- a/arg-log-format-0001/klog-0002.log > +++ b/arg-log-format-0001/klog-0002.log > @@ -1,9 +1,9 @@ > klog : Scan kernel log for errors and warnings. > klog : --------------------------------------------------------------- > klog : Test 1 of 1: Kernel log error check. > -klog : FAILED [HIGH] KlogACPIBIOSBugMultipleAPIC: Test 1, HIGH Kernel > -klog : message: [ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, > -klog : using 0 > +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" > @@ -11,9 +11,9 @@ 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 : > -klog : FAILED [HIGH] KlogACPIError3264XAddress: Test 1, HIGH Kernel > -klog : message: [ 0.000000] ACPI Error: 32/64X address mismatch in > -klog : Gpe0Block: 00008018/0000000000008028, using 32 (20090903 > +klog : FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1, HIGH > +klog : Kernel message: [ 0.000000] ACPI Error: 32/64X address mismatch > +klog : in Gpe0Block: 00008018/0000000000008028, using 32 (20090903 > klog : /tbfadt-427) > klog : > klog : ADVICE: The FADT table contains a mismatch between a 32 bit > @@ -23,18 +23,18 @@ klog : incorrect. If a non-null 32 bit pointer exists, then the kernel > klog : will opt for this in preference to the 64 bit pointer even > klog : though this is not in accordance to the ACPI specification. > klog : > -klog : FAILED [CRITICAL] KlogACPIErrorAValidRSDP: Test 1, CRITICAL > +klog : FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1, CRITICAL > klog : Kernel message: [ 0.000000] ACPI Error: A valid RSDP was not > klog : found (20090903/tbxfroot-219) > klog : > -klog : ADVICE: An ACPI-compatible system must provide an RSDP (Root > -klog : System Description Pointer in the system’s low address space. > -klog : This structure’s only purpose is to provide the physical > -klog : address of the RSDT and XSDT. > +klog : ADVICE: An ACPI compatible system must provide an RSDP (Root > +klog : System Description Pointer). This structure provides the > +klog : physical address of the RSDT and XSDT. Since this could not be > +klog : found, the ACPI driver has had to disable ACPI support. > klog : > -klog : FAILED [HIGH] KlogACPIWarningErrortwoFACS: Test 1, HIGH Kernel > -klog : message: [ 0.000000] ACPI Warning: 32/64 FACS address mismatch > -klog : in FADT - two FACS tables! (20090903/tbfadt-369) > +klog : FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel message: [ > +klog : 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - > +klog : two FACS tables! (20090903/tbfadt-369) > klog : > klog : ADVICE: The FADT table contains a mismatch between the 32 bit > klog : pointer (FIRMWARE_CTRL) and 64 bit pointer (X_FIRMWARE_CTRL) > @@ -49,39 +49,39 @@ klog : FACS tables are present in your system, which is NOT complaint > klog : with the ACPI specification. The kernel has to make a choice > klog : and opts for the 32 bit FIRMWARE_CTRL. > klog : > -klog : FAILED [HIGH] KlogACPIWarningError3264length: Test 1, HIGH > -klog : Kernel message: [ 0.000000] ACPI Warning: 32/64X FACS address > -klog : mismatch in FADT - DEF2DF40/00000000DEF30D40, using 32 > +klog : FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt: Test 1, > +klog : HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64X FACS > +klog : address mismatch in FADT - DEF2DF40/00000000DEF30D40, using 32 > klog : (20090903/tbfadt-486) > klog : > klog : ADVICE: The FADT table contains Generic Address Structure that > klog : has a mismatch between the 32 bit and 64 bit versions of an > klog : address. This should be fixed so there are no mismatches. > klog : > -klog : FAILED [HIGH] KlogACPIWarningError3264length: Test 1, HIGH > -klog : Kernel message: [ 0.000000] ACPI Warning: 32/64X length > +klog : FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt: Test 1, > +klog : HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64X length > klog : mismatch in Gpe1Block: 0/32 20090521 tbfadt-527 > klog : > klog : ADVICE: The FADT table contains Generic Address Structure that > klog : has a mismatch between the 32 bit and 64 bit versions of an > klog : address. This should be fixed so there are no mismatches. > klog : > -klog : FAILED [HIGH] KlogACPIWarning: Test 1, HIGH Kernel message: [ > -klog : 0.000000] ACPI Warning: BIOS XSDT has NULL entry, using RSDT > +klog : FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: > +klog : [ 0.000000] ACPI Warning: BIOS XSDT has NULL entry, using RSDT > klog : (20110112/tbutils-663) > klog : > klog : ADVICE: ACPI AML intepreter has found some non-conforming AML > klog : code. This should be investigated and fixed. > klog : > -klog : FAILED [HIGH] KlogACPIWarningInvalidLengthForfadt: Test 1, HIGH > -klog : Kernel message: [ 0.000000] ACPI Warning: Invalid length for > +klog : FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1, HIGH Kernel > +klog : message: [ 0.000000] ACPI Warning: Invalid length for > klog : Pm1aControlBlock: 32, using default 16 (20090903/tbfadt-607) > klog : > klog : ADVICE: This item in the FADT is the incorrect length. Should > klog : be corrected. > klog : > -klog : FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1, HIGH > -klog : Kernel message: [ 0.000000] ACPI Warning: Optional field > +klog : FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: Test 1, > +klog : HIGH Kernel message: [ 0.000000] ACPI Warning: Optional field > klog : Gpe1Block has zero address or length: 000000000000102C/0 > klog : 20090521 tbfadt-558 > klog : > @@ -89,8 +89,8 @@ klog : ADVICE: An ACPI table contains Generic Address Structure that > klog : has an address that is incorrectly set to zero, or a zero > klog : length. This needs to be fixed. > klog : > -klog : FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1, HIGH > -klog : Kernel message: [ 0.000000] ACPI Warning: Optional field > +klog : FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: Test 1, > +klog : HIGH Kernel message: [ 0.000000] ACPI Warning: Optional field > klog : Pm2ControlBlock has zero address or length: 0000000000000000/1 > klog : 20090521 tbfadt-558 > klog : > @@ -98,8 +98,8 @@ klog : ADVICE: An ACPI table contains Generic Address Structure that > klog : has an address that is incorrectly set to zero, or a zero > klog : length. This needs to be fixed. > klog : > -klog : FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1, HIGH > -klog : Kernel message: [ 0.000000] ACPI Warning (tbfadt-0460): > +klog : FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: Test 1, > +klog : HIGH Kernel message: [ 0.000000] ACPI Warning (tbfadt-0460): > klog : Optional field "Gpe1Block" has zero address or length: > klog : 000000000000102C/0 [20080926] > klog : > @@ -107,7 +107,7 @@ klog : ADVICE: An ACPI table contains Generic Address Structure that > klog : has an address that is incorrectly set to zero, or a zero > klog : length. This needs to be fixed. > klog : > -klog : FAILED [MEDIUM] KlogMtrryourBIOSHasConfigured: Test 1, MEDIUM > +klog : FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1, MEDIUM > klog : Kernel message: [ 0.000000] mtrr: your BIOS has configured an > klog : incorrect mask, fixing it. > klog : > @@ -116,7 +116,7 @@ klog : memory caching policy are misconfigued by the BIOS. In this > klog : case, the mask is incorrectly set and the kernel has detected > klog : this and worked around the firmware bug. > klog : > -klog : FAILED [CRITICAL] KlogWARNINGBIOSBugCPUMTRRsDont: Test 1, > +klog : FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test 1, > klog : CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug: CPU > klog : MTRRs don't cover all of memory, losing 1408MB of RAM. > klog : > @@ -127,18 +127,18 @@ klog : detected this and has reduced the amount of memory available to > klog : be safe. Either check that the BIOS memory caching options are > klog : set correctly or contact your BIOS vendor to get this fixed. > klog : > -klog : FAILED [CRITICAL] KlogACPIErrorFoundUnknownOpcode: Test 1, > -klog : CRITICAL Kernel message: [ 0.022719] ACPI Error: Found unknown > -klog : opcode 0xFD at AML address f7ffe14c offset 0xE8, ignoring > -klog : (20110112/psloop-141) > +klog : FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH Kernel > +klog : message: [ 0.022719] ACPI Error: Found unknown opcode 0xFD at > +klog : AML address f7ffe14c offset 0xE8, ignoring (20110112 > +klog : /psloop-141) > klog : > -klog : ADVICE: An illegal AML opcode has been found and is ignored. > -klog : This indicates either badly compiled code or opcode corruption > -klog : in the DSDT or SSDT tables or a bug in the ACPI execution > -klog : engine. Recommend disassembing using iasl to find any offending > -klog : code. > +klog : ADVICE: ACPI execution run time error: The ACPI interpreter has > +klog : reached an opcode that is unknown, this normally is a bug in > +klog : the underlying AML code either because of badly written AML > +klog : code or the compiler has produced code that is incorrect or the > +klog : ACPI interpreter does not support this valid opcode. > klog : > -klog : FAILED [CRITICAL] KlogACPIWarningDetectedAnUnsupported: Test 1, > +klog : FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test 1, > klog : CRITICAL Kernel message: [ 0.025463] ACPI Warning: Detected an > klog : unsupported executable opcode at module-level: [0x007B] at > klog : table offset 0x00C3 (20110112/psloop-526) > @@ -149,23 +149,23 @@ klog : in the DSDT or SSDT tables or a bug in the ACPI execution > klog : engine. Recommend disassembing using iasl to find any offending > klog : code. > klog : > -klog : FAILED [HIGH] KlogACPIErrorMethodExecutionParse: Test 1, HIGH > -klog : Kernel message: [ 0.034090] ACPI Error: Method parse/execution > -klog : failed [_SB_.PCI0._OSC] (Node ee025630), AE_ALREADY_EXISTS > -klog : (20110112/psparse-536) > +klog : FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1, HIGH Kernel > +klog : message: [ 0.034090] ACPI Error: Method parse/execution failed > +klog : [_SB_.PCI0._OSC] (Node ee025630), AE_ALREADY_EXISTS (20110112 > +klog : /psparse-536) > klog : > klog : ADVICE: This is a bug picked up by the kernel, but as yet, the > klog : firmware test suite has no diagnostic advice for this > klog : particular problem. > klog : > -klog : FAILED [HIGH] KlogFirmwareBug: Test 1, HIGH Kernel message: [ > -klog : 0.040119] [Firmware Bug]: the BIOS has corrupted hw-PMU > -klog : resources (MSR 186 is 400000) > +klog : FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH Kernel > +klog : message: [ 0.040119] [Firmware Bug]: the BIOS has corrupted > +klog : hw-PMU resources (MSR 186 is 400000) > klog : > klog : ADVICE: The kernel has detected a Firmware bug in the BIOS or > klog : ACPI which needs investigating and fixing. > klog : > -klog : FAILED [CRITICAL] KlogACPIWarningDetectedAnUnsupported: Test 1, > +klog : FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test 1, > klog : CRITICAL Kernel message: [ 0.042222] ACPI Warning: Detected an > klog : unsupported executable opcode at module-level: [0x0070] at > klog : table offset 0x2366 (20100121/psloop-526) > diff --git a/arg-log-format-0001/klog-0003.log b/arg-log-format-0001/klog-0003.log > index b0492b9..48f3655 100644 > --- a/arg-log-format-0001/klog-0003.log > +++ b/arg-log-format-0001/klog-0003.log > @@ -1,7 +1,7 @@ > klog 00013: Scan kernel log for errors and warnings. > klog 00014: --------------------------------------------------------- > klog 00015: Test 1 of 1: Kernel log error check. > -klog 00016: FAILED [HIGH] KlogACPIBIOSBugMultipleAPIC: Test 1, HIGH > +klog 00016: FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH > klog 00017: Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC > klog 00018: /MADT found, using 0 > klog 00019: > @@ -12,10 +12,10 @@ klog 00023: the kernel will by default select the first one. However, > klog 00024: one can override this and select the Nth MADT using > klog 00025: acpi_apic_instance=N. > klog 00026: > -klog 00027: FAILED [HIGH] KlogACPIError3264XAddress: Test 1, HIGH > -klog 00028: Kernel message: [ 0.000000] ACPI Error: 32/64X address > -klog 00029: mismatch in Gpe0Block: 00008018/0000000000008028, using > -klog 00030: 32 (20090903/tbfadt-427) > +klog 00027: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1, > +klog 00028: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X > +klog 00029: address mismatch in Gpe0Block: 00008018/0000000000008028, > +klog 00030: using 32 (20090903/tbfadt-427) > klog 00031: > klog 00032: ADVICE: The FADT table contains a mismatch between a 32 > klog 00033: bit pointer and a 64 bit Generic Address pointer. Because > @@ -25,19 +25,19 @@ klog 00036: then the kernel will opt for this in preference to the 64 > klog 00037: bit pointer even though this is not in accordance to the > klog 00038: ACPI specification. > klog 00039: > -klog 00040: FAILED [CRITICAL] KlogACPIErrorAValidRSDP: Test 1, > +klog 00040: FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1, > klog 00041: CRITICAL Kernel message: [ 0.000000] ACPI Error: A valid > klog 00042: RSDP was not found (20090903/tbxfroot-219) > klog 00043: > -klog 00044: ADVICE: An ACPI-compatible system must provide an RSDP > -klog 00045: (Root System Description Pointer in the system’s low > -klog 00046: address space. This structure’s only purpose is to > -klog 00047: provide the physical address of the RSDT and XSDT. > -klog 00048: > -klog 00049: FAILED [HIGH] KlogACPIWarningErrortwoFACS: Test 1, HIGH > -klog 00050: Kernel message: [ 0.000000] ACPI Warning: 32/64 FACS > -klog 00051: address mismatch in FADT - two FACS tables! (20090903 > -klog 00052: /tbfadt-369) > +klog 00044: ADVICE: An ACPI compatible system must provide an RSDP > +klog 00045: (Root System Description Pointer). This structure > +klog 00046: provides the physical address of the RSDT and XSDT. Since > +klog 00047: this could not be found, the ACPI driver has had to > +klog 00048: disable ACPI support. > +klog 00049: > +klog 00050: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel > +klog 00051: message: [ 0.000000] ACPI Warning: 32/64 FACS address > +klog 00052: mismatch in FADT - two FACS tables! (20090903/tbfadt-369) > klog 00053: > klog 00054: ADVICE: The FADT table contains a mismatch between the 32 > klog 00055: bit pointer (FIRMWARE_CTRL) and 64 bit pointer > @@ -54,134 +54,134 @@ klog 00065: which is NOT complaint with the ACPI specification. The > klog 00066: kernel has to make a choice and opts for the 32 bit > klog 00067: FIRMWARE_CTRL. > klog 00068: > -klog 00069: FAILED [HIGH] KlogACPIWarningError3264length: Test 1, > -klog 00070: HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64X > -klog 00071: FACS address mismatch in FADT - DEF2DF40/00000000DEF30D40 > -klog 00072: , using 32 (20090903/tbfadt-486) > +klog 00069: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt: > +klog 00070: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32 > +klog 00071: /64X FACS address mismatch in FADT - DEF2DF40 > +klog 00072: /00000000DEF30D40, using 32 (20090903/tbfadt-486) > klog 00073: > klog 00074: ADVICE: The FADT table contains Generic Address Structure > klog 00075: that has a mismatch between the 32 bit and 64 bit > klog 00076: versions of an address. This should be fixed so there are > klog 00077: no mismatches. > klog 00078: > -klog 00079: FAILED [HIGH] KlogACPIWarningError3264length: Test 1, > -klog 00080: HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64X > -klog 00081: length mismatch in Gpe1Block: 0/32 20090521 tbfadt-527 > -klog 00082: > -klog 00083: ADVICE: The FADT table contains Generic Address Structure > -klog 00084: that has a mismatch between the 32 bit and 64 bit > -klog 00085: versions of an address. This should be fixed so there are > -klog 00086: no mismatches. > -klog 00087: > -klog 00088: FAILED [HIGH] KlogACPIWarning: Test 1, HIGH Kernel > -klog 00089: message: [ 0.000000] ACPI Warning: BIOS XSDT has NULL > -klog 00090: entry, using RSDT (20110112/tbutils-663) > -klog 00091: > -klog 00092: ADVICE: ACPI AML intepreter has found some non-conforming > -klog 00093: AML code. This should be investigated and fixed. > -klog 00094: > -klog 00095: FAILED [HIGH] KlogACPIWarningInvalidLengthForfadt: Test 1 > -klog 00096: , HIGH Kernel message: [ 0.000000] ACPI Warning: Invalid > -klog 00097: length for Pm1aControlBlock: 32, using default 16 > -klog 00098: (20090903/tbfadt-607) > -klog 00099: > -klog 00100: ADVICE: This item in the FADT is the incorrect length. > -klog 00101: Should be corrected. > -klog 00102: > -klog 00103: FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1 > -klog 00104: , HIGH Kernel message: [ 0.000000] ACPI Warning: Optional > -klog 00105: field Gpe1Block has zero address or length: > -klog 00106: 000000000000102C/0 20090521 tbfadt-558 > -klog 00107: > -klog 00108: ADVICE: An ACPI table contains Generic Address Structure > -klog 00109: that has an address that is incorrectly set to zero, or a > -klog 00110: zero length. This needs to be fixed. > -klog 00111: > -klog 00112: FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1 > -klog 00113: , HIGH Kernel message: [ 0.000000] ACPI Warning: Optional > -klog 00114: field Pm2ControlBlock has zero address or length: > -klog 00115: 0000000000000000/1 20090521 tbfadt-558 > -klog 00116: > -klog 00117: ADVICE: An ACPI table contains Generic Address Structure > -klog 00118: that has an address that is incorrectly set to zero, or a > -klog 00119: zero length. This needs to be fixed. > -klog 00120: > -klog 00121: FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1 > -klog 00122: , HIGH Kernel message: [ 0.000000] ACPI Warning > -klog 00123: (tbfadt-0460): Optional field "Gpe1Block" has zero > -klog 00124: address or length: 000000000000102C/0 [20080926] > -klog 00125: > -klog 00126: ADVICE: An ACPI table contains Generic Address Structure > -klog 00127: that has an address that is incorrectly set to zero, or a > -klog 00128: zero length. This needs to be fixed. > -klog 00129: > -klog 00130: FAILED [MEDIUM] KlogMtrryourBIOSHasConfigured: Test 1, > -klog 00131: MEDIUM Kernel message: [ 0.000000] mtrr: your BIOS has > -klog 00132: configured an incorrect mask, fixing it. > -klog 00133: > -klog 00134: ADVICE: The Memory Type Range Registers (MTRRs) which > -klog 00135: define memory caching policy are misconfigued by the > -klog 00136: BIOS. In this case, the mask is incorrectly set and the > -klog 00137: kernel has detected this and worked around the firmware > -klog 00138: bug. > -klog 00139: > -klog 00140: FAILED [CRITICAL] KlogWARNINGBIOSBugCPUMTRRsDont: Test 1, > -klog 00141: CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug: > -klog 00142: CPU MTRRs don't cover all of memory, losing 1408MB of > -klog 00143: RAM. > -klog 00144: > -klog 00145: ADVICE: The Memory Type Range Registers (MTRRs) which > -klog 00146: define memory caching policy are misconfigued by the BIOS > -klog 00147: and don't appear to cover all available physical memory. > -klog 00148: The kernel has detected this and has reduced the amount > -klog 00149: of memory available to be safe. Either check that the > -klog 00150: BIOS memory caching options are set correctly or contact > -klog 00151: your BIOS vendor to get this fixed. > -klog 00152: > -klog 00153: FAILED [CRITICAL] KlogACPIErrorFoundUnknownOpcode: Test 1 > -klog 00154: , CRITICAL Kernel message: [ 0.022719] ACPI Error: Found > -klog 00155: unknown opcode 0xFD at AML address f7ffe14c offset 0xE8, > -klog 00156: ignoring (20110112/psloop-141) > -klog 00157: > -klog 00158: ADVICE: An illegal AML opcode has been found and is > -klog 00159: ignored. This indicates either badly compiled code or > -klog 00160: opcode corruption in the DSDT or SSDT tables or a bug in > -klog 00161: the ACPI execution engine. Recommend disassembing using > -klog 00162: iasl to find any offending code. > -klog 00163: > -klog 00164: FAILED [CRITICAL] KlogACPIWarningDetectedAnUnsupported: > -klog 00165: Test 1, CRITICAL Kernel message: [ 0.025463] ACPI Warning > -klog 00166: : Detected an unsupported executable opcode at > -klog 00167: module-level: [0x007B] at table offset 0x00C3 (20110112 > -klog 00168: /psloop-526) > -klog 00169: > -klog 00170: ADVICE: An illegal AML opcode has been found and is > -klog 00171: ignored. This indicates either badly compiled code or > -klog 00172: opcode corruption in the DSDT or SSDT tables or a bug in > -klog 00173: the ACPI execution engine. Recommend disassembing using > -klog 00174: iasl to find any offending code. > -klog 00175: > -klog 00176: FAILED [HIGH] KlogACPIErrorMethodExecutionParse: Test 1, > -klog 00177: HIGH Kernel message: [ 0.034090] ACPI Error: Method parse > -klog 00178: /execution failed [_SB_.PCI0._OSC] (Node ee025630), > -klog 00179: AE_ALREADY_EXISTS (20110112/psparse-536) > -klog 00180: > -klog 00181: ADVICE: This is a bug picked up by the kernel, but as yet > -klog 00182: , the firmware test suite has no diagnostic advice for > -klog 00183: this particular problem. > -klog 00184: > -klog 00185: FAILED [HIGH] KlogFirmwareBug: Test 1, HIGH Kernel > -klog 00186: message: [ 0.040119] [Firmware Bug]: the BIOS has > -klog 00187: corrupted hw-PMU resources (MSR 186 is 400000) > -klog 00188: > -klog 00189: ADVICE: The kernel has detected a Firmware bug in the > -klog 00190: BIOS or ACPI which needs investigating and fixing. > -klog 00191: > -klog 00192: FAILED [CRITICAL] KlogACPIWarningDetectedAnUnsupported: > -klog 00193: Test 1, CRITICAL Kernel message: [ 0.042222] ACPI Warning > -klog 00194: : Detected an unsupported executable opcode at > -klog 00195: module-level: [0x0070] at table offset 0x2366 (20100121 > -klog 00196: /psloop-526) > +klog 00079: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt: > +klog 00080: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32 > +klog 00081: /64X length mismatch in Gpe1Block: 0/32 20090521 > +klog 00082: tbfadt-527 > +klog 00083: > +klog 00084: ADVICE: The FADT table contains Generic Address Structure > +klog 00085: that has a mismatch between the 32 bit and 64 bit > +klog 00086: versions of an address. This should be fixed so there are > +klog 00087: no mismatches. > +klog 00088: > +klog 00089: FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel > +klog 00090: message: [ 0.000000] ACPI Warning: BIOS XSDT has NULL > +klog 00091: entry, using RSDT (20110112/tbutils-663) > +klog 00092: > +klog 00093: ADVICE: ACPI AML intepreter has found some non-conforming > +klog 00094: AML code. This should be investigated and fixed. > +klog 00095: > +klog 00096: FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1, HIGH > +klog 00097: Kernel message: [ 0.000000] ACPI Warning: Invalid length > +klog 00098: for Pm1aControlBlock: 32, using default 16 (20090903 > +klog 00099: /tbfadt-607) > +klog 00100: > +klog 00101: ADVICE: This item in the FADT is the incorrect length. > +klog 00102: Should be corrected. > +klog 00103: > +klog 00104: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: > +klog 00105: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: > +klog 00106: Optional field Gpe1Block has zero address or length: > +klog 00107: 000000000000102C/0 20090521 tbfadt-558 > +klog 00108: > +klog 00109: ADVICE: An ACPI table contains Generic Address Structure > +klog 00110: that has an address that is incorrectly set to zero, or a > +klog 00111: zero length. This needs to be fixed. > +klog 00112: > +klog 00113: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: > +klog 00114: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: > +klog 00115: Optional field Pm2ControlBlock has zero address or length > +klog 00116: : 0000000000000000/1 20090521 tbfadt-558 > +klog 00117: > +klog 00118: ADVICE: An ACPI table contains Generic Address Structure > +klog 00119: that has an address that is incorrectly set to zero, or a > +klog 00120: zero length. This needs to be fixed. > +klog 00121: > +klog 00122: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: > +klog 00123: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning > +klog 00124: (tbfadt-0460): Optional field "Gpe1Block" has zero > +klog 00125: address or length: 000000000000102C/0 [20080926] > +klog 00126: > +klog 00127: ADVICE: An ACPI table contains Generic Address Structure > +klog 00128: that has an address that is incorrectly set to zero, or a > +klog 00129: zero length. This needs to be fixed. > +klog 00130: > +klog 00131: FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1, MEDIUM > +klog 00132: Kernel message: [ 0.000000] mtrr: your BIOS has > +klog 00133: configured an incorrect mask, fixing it. > +klog 00134: > +klog 00135: ADVICE: The Memory Type Range Registers (MTRRs) which > +klog 00136: define memory caching policy are misconfigued by the > +klog 00137: BIOS. In this case, the mask is incorrectly set and the > +klog 00138: kernel has detected this and worked around the firmware > +klog 00139: bug. > +klog 00140: > +klog 00141: FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test 1, > +klog 00142: CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug: > +klog 00143: CPU MTRRs don't cover all of memory, losing 1408MB of > +klog 00144: RAM. > +klog 00145: > +klog 00146: ADVICE: The Memory Type Range Registers (MTRRs) which > +klog 00147: define memory caching policy are misconfigued by the BIOS > +klog 00148: and don't appear to cover all available physical memory. > +klog 00149: The kernel has detected this and has reduced the amount > +klog 00150: of memory available to be safe. Either check that the > +klog 00151: BIOS memory caching options are set correctly or contact > +klog 00152: your BIOS vendor to get this fixed. > +klog 00153: > +klog 00154: FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH > +klog 00155: Kernel message: [ 0.022719] ACPI Error: Found unknown > +klog 00156: opcode 0xFD at AML address f7ffe14c offset 0xE8, ignoring > +klog 00157: (20110112/psloop-141) > +klog 00158: > +klog 00159: ADVICE: ACPI execution run time error: The ACPI > +klog 00160: interpreter has reached an opcode that is unknown, this > +klog 00161: normally is a bug in the underlying AML code either > +klog 00162: because of badly written AML code or the compiler has > +klog 00163: produced code that is incorrect or the ACPI interpreter > +klog 00164: does not support this valid opcode. > +klog 00165: > +klog 00166: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test > +klog 00167: 1, CRITICAL Kernel message: [ 0.025463] ACPI Warning: > +klog 00168: Detected an unsupported executable opcode at module-level > +klog 00169: : [0x007B] at table offset 0x00C3 (20110112/psloop-526) > +klog 00170: > +klog 00171: ADVICE: An illegal AML opcode has been found and is > +klog 00172: ignored. This indicates either badly compiled code or > +klog 00173: opcode corruption in the DSDT or SSDT tables or a bug in > +klog 00174: the ACPI execution engine. Recommend disassembing using > +klog 00175: iasl to find any offending code. > +klog 00176: > +klog 00177: FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1, HIGH > +klog 00178: Kernel message: [ 0.034090] ACPI Error: Method parse > +klog 00179: /execution failed [_SB_.PCI0._OSC] (Node ee025630), > +klog 00180: AE_ALREADY_EXISTS (20110112/psparse-536) > +klog 00181: > +klog 00182: ADVICE: This is a bug picked up by the kernel, but as yet > +klog 00183: , the firmware test suite has no diagnostic advice for > +klog 00184: this particular problem. > +klog 00185: > +klog 00186: FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH Kernel > +klog 00187: message: [ 0.040119] [Firmware Bug]: the BIOS has > +klog 00188: corrupted hw-PMU resources (MSR 186 is 400000) > +klog 00189: > +klog 00190: ADVICE: The kernel has detected a Firmware bug in the > +klog 00191: BIOS or ACPI which needs investigating and fixing. > +klog 00192: > +klog 00193: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test > +klog 00194: 1, CRITICAL Kernel message: [ 0.042222] ACPI Warning: > +klog 00195: Detected an unsupported executable opcode at module-level > +klog 00196: : [0x0070] at table offset 0x2366 (20100121/psloop-526) > klog 00197: > klog 00198: ADVICE: An illegal AML opcode has been found and is > klog 00199: ignored. This indicates either badly compiled code or > diff --git a/arg-log-format-0001/klog-0004.log b/arg-log-format-0001/klog-0004.log > index 0521c06..7f3048f 100644 > --- a/arg-log-format-0001/klog-0004.log > +++ b/arg-log-format-0001/klog-0004.log > @@ -1,7 +1,7 @@ > klog 10/10/11 : 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] KlogACPIBIOSBugMultipleAPIC: Test 1, > +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 : > @@ -12,9 +12,9 @@ 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] KlogACPIError3264XAddress: Test 1, > -klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X > -klog 10/10/11 H: address mismatch in Gpe0Block: 00008018 > +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 > @@ -25,19 +25,19 @@ 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] KlogACPIErrorAValidRSDP: Test 1, > +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 in the > -klog 10/10/11 : system’s low address space. This structure’s > -klog 10/10/11 : only purpose is to provide the physical address of > -klog 10/10/11 : the RSDT and XSDT. > +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] KlogACPIWarningErrortwoFACS: Test 1, > -klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64 > -klog 10/10/11 H: FACS address mismatch in FADT - two FACS tables! > +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 > @@ -56,8 +56,9 @@ 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] KlogACPIWarningError3264length: Test 1 > -klog 10/10/11 H: , HIGH Kernel message: [ 0.000000] ACPI Warning: 32 > +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 : > @@ -66,8 +67,9 @@ 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] KlogACPIWarningError3264length: Test 1 > -klog 10/10/11 H: , HIGH Kernel message: [ 0.000000] ACPI Warning: 32 > +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 : > @@ -76,57 +78,58 @@ 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] KlogACPIWarning: Test 1, HIGH Kernel > -klog 10/10/11 H: message: [ 0.000000] ACPI Warning: BIOS XSDT has > -klog 10/10/11 H: NULL entry, using RSDT (20110112/tbutils-663) > +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] KlogACPIWarningInvalidLengthForfadt: > -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI > -klog 10/10/11 H: Warning: Invalid length for Pm1aControlBlock: 32, > -klog 10/10/11 H: using default 16 (20090903/tbfadt-607) > +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] KlogACPIWarningOptionalFieldhasZero: > -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI > -klog 10/10/11 H: Warning: Optional field Gpe1Block has zero address > -klog 10/10/11 H: or length: 000000000000102C/0 20090521 tbfadt-558 > +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] KlogACPIWarningOptionalFieldhasZero: > -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI > -klog 10/10/11 H: Warning: Optional field Pm2ControlBlock has zero > -klog 10/10/11 H: address or length: 0000000000000000/1 20090521 > -klog 10/10/11 H: tbfadt-558 > +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] KlogACPIWarningOptionalFieldhasZero: > -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI > -klog 10/10/11 H: Warning (tbfadt-0460): Optional field "Gpe1Block" > -klog 10/10/11 H: has zero address or length: 000000000000102C/0 > -klog 10/10/11 H: [20080926] > +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] KlogMtrryourBIOSHasConfigured: Test > -klog 10/10/11 M: 1, MEDIUM Kernel message: [ 0.000000] mtrr: your > -klog 10/10/11 M: BIOS has configured an incorrect mask, fixing it. > +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 > @@ -134,9 +137,9 @@ 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] KlogWARNINGBIOSBugCPUMTRRsDont: > -klog 10/10/11 C: Test 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: 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) > @@ -148,22 +151,23 @@ 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 C: FAILED [CRITICAL] KlogACPIErrorFoundUnknownOpcode: > -klog 10/10/11 C: Test 1, CRITICAL Kernel message: [ 0.022719] ACPI > -klog 10/10/11 C: Error: Found unknown opcode 0xFD at AML address > -klog 10/10/11 C: f7ffe14c offset 0xE8, ignoring (20110112/psloop-141) > +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 : 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 C: FAILED [CRITICAL] > -klog 10/10/11 C: KlogACPIWarningDetectedAnUnsupported: Test 1, > -klog 10/10/11 C: CRITICAL Kernel message: [ 0.025463] ACPI Warning: > -klog 10/10/11 C: Detected an unsupported executable opcode at > -klog 10/10/11 C: module-level: [0x007B] at table offset 0x00C3 > +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 > @@ -172,28 +176,27 @@ 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] KlogACPIErrorMethodExecutionParse: > -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.034090] ACPI Error: > -klog 10/10/11 H: Method parse/execution failed [_SB_.PCI0._OSC] (Node > +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] KlogFirmwareBug: Test 1, HIGH Kernel > -klog 10/10/11 H: message: [ 0.040119] [Firmware Bug]: the BIOS has > -klog 10/10/11 H: corrupted hw-PMU resources (MSR 186 is 400000) > +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] > -klog 10/10/11 C: KlogACPIWarningDetectedAnUnsupported: Test 1, > -klog 10/10/11 C: CRITICAL Kernel message: [ 0.042222] ACPI Warning: > -klog 10/10/11 C: Detected an unsupported executable opcode at > -klog 10/10/11 C: module-level: [0x0070] at table offset 0x2366 > +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 > -- > 1.8.0 > Acked-by: Keng-Yu Lin <kengyu@canonical.com>
On 11/29/2012 07:05 PM, Colin King wrote: > From: Colin Ian King <colin.king@canonical.com> > > Because of the changes in the way the klog test now generates error > labels we have to update the test results here. > > Signed-off-by: Colin Ian King <colin.king@canonical.com> > --- > arg-log-format-0001/klog-0001.log | 504 +++++++++++++++++++------------------- > arg-log-format-0001/klog-0002.log | 98 ++++---- > arg-log-format-0001/klog-0003.log | 274 ++++++++++----------- > arg-log-format-0001/klog-0004.log | 141 +++++------ > 4 files changed, 512 insertions(+), 505 deletions(-) > > diff --git a/arg-log-format-0001/klog-0001.log b/arg-log-format-0001/klog-0001.log > index 973ff4b..a332bea 100644 > --- a/arg-log-format-0001/klog-0001.log > +++ b/arg-log-format-0001/klog-0001.log > Acked-by: Alex Hung <alex.hung@canonical.com>
diff --git a/arg-log-format-0001/klog-0001.log b/arg-log-format-0001/klog-0001.log index 973ff4b..a332bea 100644 --- a/arg-log-format-0001/klog-0001.log +++ b/arg-log-format-0001/klog-0001.log @@ -3,7 +3,7 @@ klog (00018) <16/05/12> HED : warnings. klog (00019) <16/05/12> SEP : -------------------------------------- klog (00020) <16/05/12> INF : Test 1 of 1: Kernel log error check. klog (00021) <16/05/12> FAL H: FAILED [HIGH] -klog (00022) <16/05/12> FAL H: KlogACPIBIOSBugMultipleAPIC: Test 1, +klog (00022) <16/05/12> FAL H: KlogAcpiMultipleApicMadtFound: Test 1, klog (00023) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI: klog (00024) <16/05/12> FAL H: BIOS bug: multiple APIC/MADT found, klog (00025) <16/05/12> FAL H: using 0 @@ -19,253 +19,257 @@ klog (00034) <16/05/12> ADV : select the Nth MADT using klog (00035) <16/05/12> ADV : acpi_apic_instance=N. klog (00036) <16/05/12> NLN : klog (00037) <16/05/12> FAL H: FAILED [HIGH] -klog (00038) <16/05/12> FAL H: KlogACPIError3264XAddress: Test 1, -klog (00039) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI -klog (00040) <16/05/12> FAL H: Error: 32/64X address mismatch in -klog (00041) <16/05/12> FAL H: Gpe0Block: 00008018/0000000000008028, -klog (00042) <16/05/12> FAL H: using 32 (20090903/tbfadt-427) -klog (00043) <16/05/12> NLN : -klog (00044) <16/05/12> ADV : ADVICE: The FADT table contains a -klog (00045) <16/05/12> ADV : mismatch between a 32 bit pointer and -klog (00046) <16/05/12> ADV : a 64 bit Generic Address pointer. -klog (00047) <16/05/12> ADV : Because these pointers are different, -klog (00048) <16/05/12> ADV : it suggests either one of them is -klog (00049) <16/05/12> ADV : incorrect. If a non-null 32 bit -klog (00050) <16/05/12> ADV : pointer exists, then the kernel will -klog (00051) <16/05/12> ADV : opt for this in preference to the 64 -klog (00052) <16/05/12> ADV : bit pointer even though this is not in -klog (00053) <16/05/12> ADV : accordance to the ACPI specification. -klog (00054) <16/05/12> NLN : -klog (00055) <16/05/12> FAL C: FAILED [CRITICAL] -klog (00056) <16/05/12> FAL C: KlogACPIErrorAValidRSDP: Test 1, -klog (00057) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000] -klog (00058) <16/05/12> FAL C: ACPI Error: A valid RSDP was not found -klog (00059) <16/05/12> FAL C: (20090903/tbxfroot-219) -klog (00060) <16/05/12> NLN : -klog (00061) <16/05/12> ADV : ADVICE: An ACPI-compatible system must -klog (00062) <16/05/12> ADV : provide an RSDP (Root System -klog (00063) <16/05/12> ADV : Description Pointer in the system’s -klog (00064) <16/05/12> ADV : low address space. This structure’s -klog (00065) <16/05/12> ADV : only purpose is to provide the -klog (00066) <16/05/12> ADV : physical address of the RSDT and XSDT. -klog (00067) <16/05/12> NLN : -klog (00068) <16/05/12> FAL H: FAILED [HIGH] -klog (00069) <16/05/12> FAL H: KlogACPIWarningErrortwoFACS: Test 1, -klog (00070) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI -klog (00071) <16/05/12> FAL H: Warning: 32/64 FACS address mismatch -klog (00072) <16/05/12> FAL H: in FADT - two FACS tables! (20090903 -klog (00073) <16/05/12> FAL H: /tbfadt-369) -klog (00074) <16/05/12> NLN : -klog (00075) <16/05/12> ADV : ADVICE: The FADT table contains a -klog (00076) <16/05/12> ADV : mismatch between the 32 bit pointer -klog (00077) <16/05/12> ADV : (FIRMWARE_CTRL) and 64 bit pointer -klog (00078) <16/05/12> ADV : (X_FIRMWARE_CTRL) pointer to the FACS -klog (00079) <16/05/12> ADV : table. Section 5.2.9 of version 4.0a -klog (00080) <16/05/12> ADV : of the ACPI specification states that -klog (00081) <16/05/12> ADV : X_FIRMWARE_CTRL should be zero if -klog (00082) <16/05/12> ADV : FIRMWARE_CTRL is defined, or -klog (00083) <16/05/12> ADV : FIRMWARE_CTRL should be zero if -klog (00084) <16/05/12> ADV : X_FIRMWARE_CTRL is zero. With two -klog (00085) <16/05/12> ADV : different pointers defined, the kernel -klog (00086) <16/05/12> ADV : has to make a choice, and opts for the -klog (00087) <16/05/12> ADV : 32 bit pointer. Because these pointers -klog (00088) <16/05/12> ADV : are different, it suggests either one -klog (00089) <16/05/12> ADV : of them is incorrect, or different 32 -klog (00090) <16/05/12> ADV : bit and 64 bit FACS tables are present -klog (00091) <16/05/12> ADV : in your system, which is NOT complaint -klog (00092) <16/05/12> ADV : with the ACPI specification. The -klog (00093) <16/05/12> ADV : kernel has to make a choice and opts -klog (00094) <16/05/12> ADV : for the 32 bit FIRMWARE_CTRL. -klog (00095) <16/05/12> NLN : -klog (00096) <16/05/12> FAL H: FAILED [HIGH] -klog (00097) <16/05/12> FAL H: KlogACPIWarningError3264length: Test 1 -klog (00098) <16/05/12> FAL H: , HIGH Kernel message: [ 0.000000] -klog (00099) <16/05/12> FAL H: ACPI Warning: 32/64X FACS address -klog (00100) <16/05/12> FAL H: mismatch in FADT - DEF2DF40 -klog (00101) <16/05/12> FAL H: /00000000DEF30D40, using 32 (20090903 -klog (00102) <16/05/12> FAL H: /tbfadt-486) -klog (00103) <16/05/12> NLN : -klog (00104) <16/05/12> ADV : ADVICE: The FADT table contains -klog (00105) <16/05/12> ADV : Generic Address Structure that has a -klog (00106) <16/05/12> ADV : mismatch between the 32 bit and 64 bit -klog (00107) <16/05/12> ADV : versions of an address. This should be -klog (00108) <16/05/12> ADV : fixed so there are no mismatches. -klog (00109) <16/05/12> NLN : -klog (00110) <16/05/12> FAL H: FAILED [HIGH] -klog (00111) <16/05/12> FAL H: KlogACPIWarningError3264length: Test 1 -klog (00112) <16/05/12> FAL H: , HIGH Kernel message: [ 0.000000] -klog (00113) <16/05/12> FAL H: ACPI Warning: 32/64X length mismatch -klog (00114) <16/05/12> FAL H: in Gpe1Block: 0/32 20090521 tbfadt-527 -klog (00115) <16/05/12> NLN : -klog (00116) <16/05/12> ADV : ADVICE: The FADT table contains -klog (00117) <16/05/12> ADV : Generic Address Structure that has a -klog (00118) <16/05/12> ADV : mismatch between the 32 bit and 64 bit -klog (00119) <16/05/12> ADV : versions of an address. This should be -klog (00120) <16/05/12> ADV : fixed so there are no mismatches. -klog (00121) <16/05/12> NLN : -klog (00122) <16/05/12> FAL H: FAILED [HIGH] KlogACPIWarning: Test 1, -klog (00123) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI -klog (00124) <16/05/12> FAL H: Warning: BIOS XSDT has NULL entry, -klog (00125) <16/05/12> FAL H: using RSDT (20110112/tbutils-663) -klog (00126) <16/05/12> NLN : -klog (00127) <16/05/12> ADV : ADVICE: ACPI AML intepreter has found -klog (00128) <16/05/12> ADV : some non-conforming AML code. This -klog (00129) <16/05/12> ADV : should be investigated and fixed. -klog (00130) <16/05/12> NLN : -klog (00131) <16/05/12> FAL H: FAILED [HIGH] -klog (00132) <16/05/12> FAL H: KlogACPIWarningInvalidLengthForfadt: -klog (00133) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ -klog (00134) <16/05/12> FAL H: 0.000000] ACPI Warning: Invalid length -klog (00135) <16/05/12> FAL H: for Pm1aControlBlock: 32, using -klog (00136) <16/05/12> FAL H: default 16 (20090903/tbfadt-607) -klog (00137) <16/05/12> NLN : -klog (00138) <16/05/12> ADV : ADVICE: This item in the FADT is the -klog (00139) <16/05/12> ADV : incorrect length. Should be corrected. -klog (00140) <16/05/12> NLN : -klog (00141) <16/05/12> FAL H: FAILED [HIGH] -klog (00142) <16/05/12> FAL H: KlogACPIWarningOptionalFieldhasZero: -klog (00143) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ -klog (00144) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field -klog (00145) <16/05/12> FAL H: Gpe1Block has zero address or length: -klog (00146) <16/05/12> FAL H: 000000000000102C/0 20090521 tbfadt-558 -klog (00147) <16/05/12> NLN : -klog (00148) <16/05/12> ADV : ADVICE: An ACPI table contains Generic -klog (00149) <16/05/12> ADV : Address Structure that has an address -klog (00150) <16/05/12> ADV : that is incorrectly set to zero, or a -klog (00151) <16/05/12> ADV : zero length. This needs to be fixed. -klog (00152) <16/05/12> NLN : -klog (00153) <16/05/12> FAL H: FAILED [HIGH] -klog (00154) <16/05/12> FAL H: KlogACPIWarningOptionalFieldhasZero: -klog (00155) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ -klog (00156) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field -klog (00157) <16/05/12> FAL H: Pm2ControlBlock has zero address or -klog (00158) <16/05/12> FAL H: length: 0000000000000000/1 20090521 -klog (00159) <16/05/12> FAL H: tbfadt-558 -klog (00160) <16/05/12> NLN : -klog (00161) <16/05/12> ADV : ADVICE: An ACPI table contains Generic -klog (00162) <16/05/12> ADV : Address Structure that has an address -klog (00163) <16/05/12> ADV : that is incorrectly set to zero, or a -klog (00164) <16/05/12> ADV : zero length. This needs to be fixed. -klog (00165) <16/05/12> NLN : -klog (00166) <16/05/12> FAL H: FAILED [HIGH] -klog (00167) <16/05/12> FAL H: KlogACPIWarningOptionalFieldhasZero: -klog (00168) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ -klog (00169) <16/05/12> FAL H: 0.000000] ACPI Warning (tbfadt-0460): -klog (00170) <16/05/12> FAL H: Optional field "Gpe1Block" has zero -klog (00171) <16/05/12> FAL H: address or length: 000000000000102C/0 -klog (00172) <16/05/12> FAL H: [20080926] -klog (00173) <16/05/12> NLN : -klog (00174) <16/05/12> ADV : ADVICE: An ACPI table contains Generic -klog (00175) <16/05/12> ADV : Address Structure that has an address -klog (00176) <16/05/12> ADV : that is incorrectly set to zero, or a -klog (00177) <16/05/12> ADV : zero length. This needs to be fixed. -klog (00178) <16/05/12> NLN : -klog (00179) <16/05/12> FAL M: FAILED [MEDIUM] -klog (00180) <16/05/12> FAL M: KlogMtrryourBIOSHasConfigured: Test 1, -klog (00181) <16/05/12> FAL M: MEDIUM Kernel message: [ 0.000000] -klog (00182) <16/05/12> FAL M: mtrr: your BIOS has configured an -klog (00183) <16/05/12> FAL M: incorrect mask, fixing it. -klog (00184) <16/05/12> NLN : -klog (00185) <16/05/12> ADV : ADVICE: The Memory Type Range -klog (00186) <16/05/12> ADV : Registers (MTRRs) which define memory -klog (00187) <16/05/12> ADV : caching policy are misconfigued by the -klog (00188) <16/05/12> ADV : BIOS. In this case, the mask is -klog (00189) <16/05/12> ADV : incorrectly set and the kernel has -klog (00190) <16/05/12> ADV : detected this and worked around the -klog (00191) <16/05/12> ADV : firmware bug. -klog (00192) <16/05/12> NLN : -klog (00193) <16/05/12> FAL C: FAILED [CRITICAL] -klog (00194) <16/05/12> FAL C: KlogWARNINGBIOSBugCPUMTRRsDont: Test 1 -klog (00195) <16/05/12> FAL C: , CRITICAL Kernel message: [ 0.000000] -klog (00196) <16/05/12> FAL C: WARNING: BIOS bug: CPU MTRRs don't -klog (00197) <16/05/12> FAL C: cover all of memory, losing 1408MB of -klog (00198) <16/05/12> FAL C: RAM. -klog (00199) <16/05/12> NLN : -klog (00200) <16/05/12> ADV : ADVICE: The Memory Type Range -klog (00201) <16/05/12> ADV : Registers (MTRRs) which define memory -klog (00202) <16/05/12> ADV : caching policy are misconfigued by the -klog (00203) <16/05/12> ADV : BIOS and don't appear to cover all -klog (00204) <16/05/12> ADV : available physical memory. The kernel -klog (00205) <16/05/12> ADV : has detected this and has reduced the -klog (00206) <16/05/12> ADV : amount of memory available to be safe. -klog (00207) <16/05/12> ADV : Either check that the BIOS memory -klog (00208) <16/05/12> ADV : caching options are set correctly or -klog (00209) <16/05/12> ADV : contact your BIOS vendor to get this -klog (00210) <16/05/12> ADV : fixed. -klog (00211) <16/05/12> NLN : -klog (00212) <16/05/12> FAL C: FAILED [CRITICAL] -klog (00213) <16/05/12> FAL C: KlogACPIErrorFoundUnknownOpcode: Test -klog (00214) <16/05/12> FAL C: 1, CRITICAL Kernel message: [ -klog (00215) <16/05/12> FAL C: 0.022719] ACPI Error: Found unknown -klog (00216) <16/05/12> FAL C: opcode 0xFD at AML address f7ffe14c -klog (00217) <16/05/12> FAL C: offset 0xE8, ignoring (20110112 -klog (00218) <16/05/12> FAL C: /psloop-141) -klog (00219) <16/05/12> NLN : -klog (00220) <16/05/12> ADV : ADVICE: An illegal AML opcode has been -klog (00221) <16/05/12> ADV : found and is ignored. This indicates -klog (00222) <16/05/12> ADV : either badly compiled code or opcode -klog (00223) <16/05/12> ADV : corruption in the DSDT or SSDT tables -klog (00224) <16/05/12> ADV : or a bug in the ACPI execution engine. -klog (00225) <16/05/12> ADV : Recommend disassembing using iasl to -klog (00226) <16/05/12> ADV : find any offending code. -klog (00227) <16/05/12> NLN : -klog (00228) <16/05/12> FAL C: FAILED [CRITICAL] -klog (00229) <16/05/12> FAL C: KlogACPIWarningDetectedAnUnsupported: -klog (00230) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [ -klog (00231) <16/05/12> FAL C: 0.025463] ACPI Warning: Detected an -klog (00232) <16/05/12> FAL C: unsupported executable opcode at -klog (00233) <16/05/12> FAL C: module-level: [0x007B] at table offset -klog (00234) <16/05/12> FAL C: 0x00C3 (20110112/psloop-526) -klog (00235) <16/05/12> NLN : -klog (00236) <16/05/12> ADV : ADVICE: An illegal AML opcode has been -klog (00237) <16/05/12> ADV : found and is ignored. This indicates -klog (00238) <16/05/12> ADV : either badly compiled code or opcode -klog (00239) <16/05/12> ADV : corruption in the DSDT or SSDT tables -klog (00240) <16/05/12> ADV : or a bug in the ACPI execution engine. -klog (00241) <16/05/12> ADV : Recommend disassembing using iasl to -klog (00242) <16/05/12> ADV : find any offending code. -klog (00243) <16/05/12> NLN : -klog (00244) <16/05/12> FAL H: FAILED [HIGH] -klog (00245) <16/05/12> FAL H: KlogACPIErrorMethodExecutionParse: -klog (00246) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ -klog (00247) <16/05/12> FAL H: 0.034090] ACPI Error: Method parse -klog (00248) <16/05/12> FAL H: /execution failed [_SB_.PCI0._OSC] -klog (00249) <16/05/12> FAL H: (Node ee025630), AE_ALREADY_EXISTS -klog (00250) <16/05/12> FAL H: (20110112/psparse-536) -klog (00251) <16/05/12> NLN : -klog (00252) <16/05/12> ADV : ADVICE: This is a bug picked up by the -klog (00253) <16/05/12> ADV : kernel, but as yet, the firmware test -klog (00254) <16/05/12> ADV : suite has no diagnostic advice for -klog (00255) <16/05/12> ADV : this particular problem. -klog (00256) <16/05/12> NLN : -klog (00257) <16/05/12> FAL H: FAILED [HIGH] KlogFirmwareBug: Test 1, -klog (00258) <16/05/12> FAL H: HIGH Kernel message: [ 0.040119] -klog (00259) <16/05/12> FAL H: [Firmware Bug]: the BIOS has corrupted -klog (00260) <16/05/12> FAL H: hw-PMU resources (MSR 186 is 400000) -klog (00261) <16/05/12> NLN : -klog (00262) <16/05/12> ADV : ADVICE: The kernel has detected a -klog (00263) <16/05/12> ADV : Firmware bug in the BIOS or ACPI which -klog (00264) <16/05/12> ADV : needs investigating and fixing. +klog (00038) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatch: +klog (00039) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ +klog (00040) <16/05/12> FAL H: 0.000000] ACPI Error: 32/64X address +klog (00041) <16/05/12> FAL H: mismatch in Gpe0Block: 00008018 +klog (00042) <16/05/12> FAL H: /0000000000008028, using 32 (20090903 +klog (00043) <16/05/12> FAL H: /tbfadt-427) +klog (00044) <16/05/12> NLN : +klog (00045) <16/05/12> ADV : ADVICE: The FADT table contains a +klog (00046) <16/05/12> ADV : mismatch between a 32 bit pointer and +klog (00047) <16/05/12> ADV : a 64 bit Generic Address pointer. +klog (00048) <16/05/12> ADV : Because these pointers are different, +klog (00049) <16/05/12> ADV : it suggests either one of them is +klog (00050) <16/05/12> ADV : incorrect. If a non-null 32 bit +klog (00051) <16/05/12> ADV : pointer exists, then the kernel will +klog (00052) <16/05/12> ADV : opt for this in preference to the 64 +klog (00053) <16/05/12> ADV : bit pointer even though this is not in +klog (00054) <16/05/12> ADV : accordance to the ACPI specification. +klog (00055) <16/05/12> NLN : +klog (00056) <16/05/12> FAL C: FAILED [CRITICAL] +klog (00057) <16/05/12> FAL C: KlogAcpiValidRsdpNotFound: Test 1, +klog (00058) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000] +klog (00059) <16/05/12> FAL C: ACPI Error: A valid RSDP was not found +klog (00060) <16/05/12> FAL C: (20090903/tbxfroot-219) +klog (00061) <16/05/12> NLN : +klog (00062) <16/05/12> ADV : ADVICE: An ACPI compatible system must +klog (00063) <16/05/12> ADV : provide an RSDP (Root System +klog (00064) <16/05/12> ADV : Description Pointer). This structure +klog (00065) <16/05/12> ADV : provides the physical address of the +klog (00066) <16/05/12> ADV : RSDT and XSDT. Since this could not be +klog (00067) <16/05/12> ADV : found, the ACPI driver has had to +klog (00068) <16/05/12> ADV : disable ACPI support. +klog (00069) <16/05/12> NLN : +klog (00070) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, +klog (00071) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI +klog (00072) <16/05/12> FAL H: Warning: 32/64 FACS address mismatch +klog (00073) <16/05/12> FAL H: in FADT - two FACS tables! (20090903 +klog (00074) <16/05/12> FAL H: /tbfadt-369) +klog (00075) <16/05/12> NLN : +klog (00076) <16/05/12> ADV : ADVICE: The FADT table contains a +klog (00077) <16/05/12> ADV : mismatch between the 32 bit pointer +klog (00078) <16/05/12> ADV : (FIRMWARE_CTRL) and 64 bit pointer +klog (00079) <16/05/12> ADV : (X_FIRMWARE_CTRL) pointer to the FACS +klog (00080) <16/05/12> ADV : table. Section 5.2.9 of version 4.0a +klog (00081) <16/05/12> ADV : of the ACPI specification states that +klog (00082) <16/05/12> ADV : X_FIRMWARE_CTRL should be zero if +klog (00083) <16/05/12> ADV : FIRMWARE_CTRL is defined, or +klog (00084) <16/05/12> ADV : FIRMWARE_CTRL should be zero if +klog (00085) <16/05/12> ADV : X_FIRMWARE_CTRL is zero. With two +klog (00086) <16/05/12> ADV : different pointers defined, the kernel +klog (00087) <16/05/12> ADV : has to make a choice, and opts for the +klog (00088) <16/05/12> ADV : 32 bit pointer. Because these pointers +klog (00089) <16/05/12> ADV : are different, it suggests either one +klog (00090) <16/05/12> ADV : of them is incorrect, or different 32 +klog (00091) <16/05/12> ADV : bit and 64 bit FACS tables are present +klog (00092) <16/05/12> ADV : in your system, which is NOT complaint +klog (00093) <16/05/12> ADV : with the ACPI specification. The +klog (00094) <16/05/12> ADV : kernel has to make a choice and opts +klog (00095) <16/05/12> ADV : for the 32 bit FIRMWARE_CTRL. +klog (00096) <16/05/12> NLN : +klog (00097) <16/05/12> FAL H: FAILED [HIGH] +klog (00098) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt +klog (00099) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ +klog (00100) <16/05/12> FAL H: 0.000000] ACPI Warning: 32/64X FACS +klog (00101) <16/05/12> FAL H: address mismatch in FADT - DEF2DF40 +klog (00102) <16/05/12> FAL H: /00000000DEF30D40, using 32 (20090903 +klog (00103) <16/05/12> FAL H: /tbfadt-486) +klog (00104) <16/05/12> NLN : +klog (00105) <16/05/12> ADV : ADVICE: The FADT table contains +klog (00106) <16/05/12> ADV : Generic Address Structure that has a +klog (00107) <16/05/12> ADV : mismatch between the 32 bit and 64 bit +klog (00108) <16/05/12> ADV : versions of an address. This should be +klog (00109) <16/05/12> ADV : fixed so there are no mismatches. +klog (00110) <16/05/12> NLN : +klog (00111) <16/05/12> FAL H: FAILED [HIGH] +klog (00112) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt +klog (00113) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ +klog (00114) <16/05/12> FAL H: 0.000000] ACPI Warning: 32/64X length +klog (00115) <16/05/12> FAL H: mismatch in Gpe1Block: 0/32 20090521 +klog (00116) <16/05/12> FAL H: tbfadt-527 +klog (00117) <16/05/12> NLN : +klog (00118) <16/05/12> ADV : ADVICE: The FADT table contains +klog (00119) <16/05/12> ADV : Generic Address Structure that has a +klog (00120) <16/05/12> ADV : mismatch between the 32 bit and 64 bit +klog (00121) <16/05/12> ADV : versions of an address. This should be +klog (00122) <16/05/12> ADV : fixed so there are no mismatches. +klog (00123) <16/05/12> NLN : +klog (00124) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiBadAmlCode: Test +klog (00125) <16/05/12> FAL H: 1, HIGH Kernel message: [ 0.000000] +klog (00126) <16/05/12> FAL H: ACPI Warning: BIOS XSDT has NULL entry +klog (00127) <16/05/12> FAL H: , using RSDT (20110112/tbutils-663) +klog (00128) <16/05/12> NLN : +klog (00129) <16/05/12> ADV : ADVICE: ACPI AML intepreter has found +klog (00130) <16/05/12> ADV : some non-conforming AML code. This +klog (00131) <16/05/12> ADV : should be investigated and fixed. +klog (00132) <16/05/12> NLN : +klog (00133) <16/05/12> FAL H: FAILED [HIGH] +klog (00134) <16/05/12> FAL H: KlogAcpiFadtInvalidLength: Test 1, +klog (00135) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI +klog (00136) <16/05/12> FAL H: Warning: Invalid length for +klog (00137) <16/05/12> FAL H: Pm1aControlBlock: 32, using default 16 +klog (00138) <16/05/12> FAL H: (20090903/tbfadt-607) +klog (00139) <16/05/12> NLN : +klog (00140) <16/05/12> ADV : ADVICE: This item in the FADT is the +klog (00141) <16/05/12> ADV : incorrect length. Should be corrected. +klog (00142) <16/05/12> NLN : +klog (00143) <16/05/12> FAL H: FAILED [HIGH] +klog (00144) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength +klog (00145) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ +klog (00146) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field +klog (00147) <16/05/12> FAL H: Gpe1Block has zero address or length: +klog (00148) <16/05/12> FAL H: 000000000000102C/0 20090521 tbfadt-558 +klog (00149) <16/05/12> NLN : +klog (00150) <16/05/12> ADV : ADVICE: An ACPI table contains Generic +klog (00151) <16/05/12> ADV : Address Structure that has an address +klog (00152) <16/05/12> ADV : that is incorrectly set to zero, or a +klog (00153) <16/05/12> ADV : zero length. This needs to be fixed. +klog (00154) <16/05/12> NLN : +klog (00155) <16/05/12> FAL H: FAILED [HIGH] +klog (00156) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength +klog (00157) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ +klog (00158) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field +klog (00159) <16/05/12> FAL H: Pm2ControlBlock has zero address or +klog (00160) <16/05/12> FAL H: length: 0000000000000000/1 20090521 +klog (00161) <16/05/12> FAL H: tbfadt-558 +klog (00162) <16/05/12> NLN : +klog (00163) <16/05/12> ADV : ADVICE: An ACPI table contains Generic +klog (00164) <16/05/12> ADV : Address Structure that has an address +klog (00165) <16/05/12> ADV : that is incorrectly set to zero, or a +klog (00166) <16/05/12> ADV : zero length. This needs to be fixed. +klog (00167) <16/05/12> NLN : +klog (00168) <16/05/12> FAL H: FAILED [HIGH] +klog (00169) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength +klog (00170) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ +klog (00171) <16/05/12> FAL H: 0.000000] ACPI Warning (tbfadt-0460): +klog (00172) <16/05/12> FAL H: Optional field "Gpe1Block" has zero +klog (00173) <16/05/12> FAL H: address or length: 000000000000102C/0 +klog (00174) <16/05/12> FAL H: [20080926] +klog (00175) <16/05/12> NLN : +klog (00176) <16/05/12> ADV : ADVICE: An ACPI table contains Generic +klog (00177) <16/05/12> ADV : Address Structure that has an address +klog (00178) <16/05/12> ADV : that is incorrectly set to zero, or a +klog (00179) <16/05/12> ADV : zero length. This needs to be fixed. +klog (00180) <16/05/12> NLN : +klog (00181) <16/05/12> FAL M: FAILED [MEDIUM] +klog (00182) <16/05/12> FAL M: KlogBiosMtrrIncorrectMask: Test 1, +klog (00183) <16/05/12> FAL M: MEDIUM Kernel message: [ 0.000000] +klog (00184) <16/05/12> FAL M: mtrr: your BIOS has configured an +klog (00185) <16/05/12> FAL M: incorrect mask, fixing it. +klog (00186) <16/05/12> NLN : +klog (00187) <16/05/12> ADV : ADVICE: The Memory Type Range +klog (00188) <16/05/12> ADV : Registers (MTRRs) which define memory +klog (00189) <16/05/12> ADV : caching policy are misconfigued by the +klog (00190) <16/05/12> ADV : BIOS. In this case, the mask is +klog (00191) <16/05/12> ADV : incorrectly set and the kernel has +klog (00192) <16/05/12> ADV : detected this and worked around the +klog (00193) <16/05/12> ADV : firmware bug. +klog (00194) <16/05/12> NLN : +klog (00195) <16/05/12> FAL C: FAILED [CRITICAL] +klog (00196) <16/05/12> FAL C: KlogBiosCpuMtrrMisconfigured: Test 1, +klog (00197) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000] +klog (00198) <16/05/12> FAL C: WARNING: BIOS bug: CPU MTRRs don't +klog (00199) <16/05/12> FAL C: cover all of memory, losing 1408MB of +klog (00200) <16/05/12> FAL C: RAM. +klog (00201) <16/05/12> NLN : +klog (00202) <16/05/12> ADV : ADVICE: The Memory Type Range +klog (00203) <16/05/12> ADV : Registers (MTRRs) which define memory +klog (00204) <16/05/12> ADV : caching policy are misconfigued by the +klog (00205) <16/05/12> ADV : BIOS and don't appear to cover all +klog (00206) <16/05/12> ADV : available physical memory. The kernel +klog (00207) <16/05/12> ADV : has detected this and has reduced the +klog (00208) <16/05/12> ADV : amount of memory available to be safe. +klog (00209) <16/05/12> ADV : Either check that the BIOS memory +klog (00210) <16/05/12> ADV : caching options are set correctly or +klog (00211) <16/05/12> ADV : contact your BIOS vendor to get this +klog (00212) <16/05/12> ADV : fixed. +klog (00213) <16/05/12> NLN : +klog (00214) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiUnknownAmlOpcode +klog (00215) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [ +klog (00216) <16/05/12> FAL H: 0.022719] ACPI Error: Found unknown +klog (00217) <16/05/12> FAL H: opcode 0xFD at AML address f7ffe14c +klog (00218) <16/05/12> FAL H: offset 0xE8, ignoring (20110112 +klog (00219) <16/05/12> FAL H: /psloop-141) +klog (00220) <16/05/12> NLN : +klog (00221) <16/05/12> ADV : ADVICE: ACPI execution run time error: +klog (00222) <16/05/12> ADV : The ACPI interpreter has reached an +klog (00223) <16/05/12> ADV : opcode that is unknown, this normally +klog (00224) <16/05/12> ADV : is a bug in the underlying AML code +klog (00225) <16/05/12> ADV : either because of badly written AML +klog (00226) <16/05/12> ADV : code or the compiler has produced code +klog (00227) <16/05/12> ADV : that is incorrect or the ACPI +klog (00228) <16/05/12> ADV : interpreter does not support this +klog (00229) <16/05/12> ADV : valid opcode. +klog (00230) <16/05/12> NLN : +klog (00231) <16/05/12> FAL C: FAILED [CRITICAL] +klog (00232) <16/05/12> FAL C: KlogAcpiDetectedUnsupportedOpCode: +klog (00233) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [ +klog (00234) <16/05/12> FAL C: 0.025463] ACPI Warning: Detected an +klog (00235) <16/05/12> FAL C: unsupported executable opcode at +klog (00236) <16/05/12> FAL C: module-level: [0x007B] at table offset +klog (00237) <16/05/12> FAL C: 0x00C3 (20110112/psloop-526) +klog (00238) <16/05/12> NLN : +klog (00239) <16/05/12> ADV : ADVICE: An illegal AML opcode has been +klog (00240) <16/05/12> ADV : found and is ignored. This indicates +klog (00241) <16/05/12> ADV : either badly compiled code or opcode +klog (00242) <16/05/12> ADV : corruption in the DSDT or SSDT tables +klog (00243) <16/05/12> ADV : or a bug in the ACPI execution engine. +klog (00244) <16/05/12> ADV : Recommend disassembing using iasl to +klog (00245) <16/05/12> ADV : find any offending code. +klog (00246) <16/05/12> NLN : +klog (00247) <16/05/12> FAL H: FAILED [HIGH] +klog (00248) <16/05/12> FAL H: KlogAcpiObjectAlreadyExists: Test 1, +klog (00249) <16/05/12> FAL H: HIGH Kernel message: [ 0.034090] ACPI +klog (00250) <16/05/12> FAL H: Error: Method parse/execution failed +klog (00251) <16/05/12> FAL H: [_SB_.PCI0._OSC] (Node ee025630), +klog (00252) <16/05/12> FAL H: AE_ALREADY_EXISTS (20110112 +klog (00253) <16/05/12> FAL H: /psparse-536) +klog (00254) <16/05/12> NLN : +klog (00255) <16/05/12> ADV : ADVICE: This is a bug picked up by the +klog (00256) <16/05/12> ADV : kernel, but as yet, the firmware test +klog (00257) <16/05/12> ADV : suite has no diagnostic advice for +klog (00258) <16/05/12> ADV : this particular problem. +klog (00259) <16/05/12> NLN : +klog (00260) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiFirmwareError: +klog (00261) <16/05/12> FAL H: Test 1, HIGH Kernel message: [ +klog (00262) <16/05/12> FAL H: 0.040119] [Firmware Bug]: the BIOS has +klog (00263) <16/05/12> FAL H: corrupted hw-PMU resources (MSR 186 is +klog (00264) <16/05/12> FAL H: 400000) klog (00265) <16/05/12> NLN : -klog (00266) <16/05/12> FAL C: FAILED [CRITICAL] -klog (00267) <16/05/12> FAL C: KlogACPIWarningDetectedAnUnsupported: -klog (00268) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [ -klog (00269) <16/05/12> FAL C: 0.042222] ACPI Warning: Detected an -klog (00270) <16/05/12> FAL C: unsupported executable opcode at -klog (00271) <16/05/12> FAL C: module-level: [0x0070] at table offset -klog (00272) <16/05/12> FAL C: 0x2366 (20100121/psloop-526) -klog (00273) <16/05/12> NLN : -klog (00274) <16/05/12> ADV : ADVICE: An illegal AML opcode has been -klog (00275) <16/05/12> ADV : found and is ignored. This indicates -klog (00276) <16/05/12> ADV : either badly compiled code or opcode -klog (00277) <16/05/12> ADV : corruption in the DSDT or SSDT tables -klog (00278) <16/05/12> ADV : or a bug in the ACPI execution engine. -klog (00279) <16/05/12> ADV : Recommend disassembing using iasl to -klog (00280) <16/05/12> ADV : find any offending code. -klog (00281) <16/05/12> NLN : -klog (00282) <16/05/12> INF : Found 18 unique errors in kernel log. -klog (00283) <16/05/12> NLN : -klog (00284) <16/05/12> SEP : ====================================== -klog (00285) <16/05/12> SUM : 0 passed, 18 failed, 0 warnings, 0 -klog (00286) <16/05/12> SUM : aborted, 0 skipped, 0 info only. -klog (00287) <16/05/12> SEP : ====================================== +klog (00266) <16/05/12> ADV : ADVICE: The kernel has detected a +klog (00267) <16/05/12> ADV : Firmware bug in the BIOS or ACPI which +klog (00268) <16/05/12> ADV : needs investigating and fixing. +klog (00269) <16/05/12> NLN : +klog (00270) <16/05/12> FAL C: FAILED [CRITICAL] +klog (00271) <16/05/12> FAL C: KlogAcpiDetectedUnsupportedOpCode: +klog (00272) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [ +klog (00273) <16/05/12> FAL C: 0.042222] ACPI Warning: Detected an +klog (00274) <16/05/12> FAL C: unsupported executable opcode at +klog (00275) <16/05/12> FAL C: module-level: [0x0070] at table offset +klog (00276) <16/05/12> FAL C: 0x2366 (20100121/psloop-526) +klog (00277) <16/05/12> NLN : +klog (00278) <16/05/12> ADV : ADVICE: An illegal AML opcode has been +klog (00279) <16/05/12> ADV : found and is ignored. This indicates +klog (00280) <16/05/12> ADV : either badly compiled code or opcode +klog (00281) <16/05/12> ADV : corruption in the DSDT or SSDT tables +klog (00282) <16/05/12> ADV : or a bug in the ACPI execution engine. +klog (00283) <16/05/12> ADV : Recommend disassembing using iasl to +klog (00284) <16/05/12> ADV : find any offending code. +klog (00285) <16/05/12> NLN : +klog (00286) <16/05/12> INF : Found 18 unique errors in kernel log. +klog (00287) <16/05/12> NLN : +klog (00288) <16/05/12> SEP : ====================================== +klog (00289) <16/05/12> SUM : 0 passed, 18 failed, 0 warnings, 0 +klog (00290) <16/05/12> SUM : aborted, 0 skipped, 0 info only. +klog (00291) <16/05/12> SEP : ====================================== diff --git a/arg-log-format-0001/klog-0002.log b/arg-log-format-0001/klog-0002.log index 6942a5b..55723ce 100644 --- a/arg-log-format-0001/klog-0002.log +++ b/arg-log-format-0001/klog-0002.log @@ -1,9 +1,9 @@ klog : Scan kernel log for errors and warnings. klog : --------------------------------------------------------------- klog : Test 1 of 1: Kernel log error check. -klog : FAILED [HIGH] KlogACPIBIOSBugMultipleAPIC: Test 1, HIGH Kernel -klog : message: [ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, -klog : using 0 +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" @@ -11,9 +11,9 @@ 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 : -klog : FAILED [HIGH] KlogACPIError3264XAddress: Test 1, HIGH Kernel -klog : message: [ 0.000000] ACPI Error: 32/64X address mismatch in -klog : Gpe0Block: 00008018/0000000000008028, using 32 (20090903 +klog : FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1, HIGH +klog : Kernel message: [ 0.000000] ACPI Error: 32/64X address mismatch +klog : in Gpe0Block: 00008018/0000000000008028, using 32 (20090903 klog : /tbfadt-427) klog : klog : ADVICE: The FADT table contains a mismatch between a 32 bit @@ -23,18 +23,18 @@ klog : incorrect. If a non-null 32 bit pointer exists, then the kernel klog : will opt for this in preference to the 64 bit pointer even klog : though this is not in accordance to the ACPI specification. klog : -klog : FAILED [CRITICAL] KlogACPIErrorAValidRSDP: Test 1, CRITICAL +klog : FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1, CRITICAL klog : Kernel message: [ 0.000000] ACPI Error: A valid RSDP was not klog : found (20090903/tbxfroot-219) klog : -klog : ADVICE: An ACPI-compatible system must provide an RSDP (Root -klog : System Description Pointer in the system’s low address space. -klog : This structure’s only purpose is to provide the physical -klog : address of the RSDT and XSDT. +klog : ADVICE: An ACPI compatible system must provide an RSDP (Root +klog : System Description Pointer). This structure provides the +klog : physical address of the RSDT and XSDT. Since this could not be +klog : found, the ACPI driver has had to disable ACPI support. klog : -klog : FAILED [HIGH] KlogACPIWarningErrortwoFACS: Test 1, HIGH Kernel -klog : message: [ 0.000000] ACPI Warning: 32/64 FACS address mismatch -klog : in FADT - two FACS tables! (20090903/tbfadt-369) +klog : FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel message: [ +klog : 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - +klog : two FACS tables! (20090903/tbfadt-369) klog : klog : ADVICE: The FADT table contains a mismatch between the 32 bit klog : pointer (FIRMWARE_CTRL) and 64 bit pointer (X_FIRMWARE_CTRL) @@ -49,39 +49,39 @@ klog : FACS tables are present in your system, which is NOT complaint klog : with the ACPI specification. The kernel has to make a choice klog : and opts for the 32 bit FIRMWARE_CTRL. klog : -klog : FAILED [HIGH] KlogACPIWarningError3264length: Test 1, HIGH -klog : Kernel message: [ 0.000000] ACPI Warning: 32/64X FACS address -klog : mismatch in FADT - DEF2DF40/00000000DEF30D40, using 32 +klog : FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt: Test 1, +klog : HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64X FACS +klog : address mismatch in FADT - DEF2DF40/00000000DEF30D40, using 32 klog : (20090903/tbfadt-486) klog : klog : ADVICE: The FADT table contains Generic Address Structure that klog : has a mismatch between the 32 bit and 64 bit versions of an klog : address. This should be fixed so there are no mismatches. klog : -klog : FAILED [HIGH] KlogACPIWarningError3264length: Test 1, HIGH -klog : Kernel message: [ 0.000000] ACPI Warning: 32/64X length +klog : FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt: Test 1, +klog : HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64X length klog : mismatch in Gpe1Block: 0/32 20090521 tbfadt-527 klog : klog : ADVICE: The FADT table contains Generic Address Structure that klog : has a mismatch between the 32 bit and 64 bit versions of an klog : address. This should be fixed so there are no mismatches. klog : -klog : FAILED [HIGH] KlogACPIWarning: Test 1, HIGH Kernel message: [ -klog : 0.000000] ACPI Warning: BIOS XSDT has NULL entry, using RSDT +klog : FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: +klog : [ 0.000000] ACPI Warning: BIOS XSDT has NULL entry, using RSDT klog : (20110112/tbutils-663) klog : klog : ADVICE: ACPI AML intepreter has found some non-conforming AML klog : code. This should be investigated and fixed. klog : -klog : FAILED [HIGH] KlogACPIWarningInvalidLengthForfadt: Test 1, HIGH -klog : Kernel message: [ 0.000000] ACPI Warning: Invalid length for +klog : FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1, HIGH Kernel +klog : message: [ 0.000000] ACPI Warning: Invalid length for klog : Pm1aControlBlock: 32, using default 16 (20090903/tbfadt-607) klog : klog : ADVICE: This item in the FADT is the incorrect length. Should klog : be corrected. klog : -klog : FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1, HIGH -klog : Kernel message: [ 0.000000] ACPI Warning: Optional field +klog : FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: Test 1, +klog : HIGH Kernel message: [ 0.000000] ACPI Warning: Optional field klog : Gpe1Block has zero address or length: 000000000000102C/0 klog : 20090521 tbfadt-558 klog : @@ -89,8 +89,8 @@ klog : ADVICE: An ACPI table contains Generic Address Structure that klog : has an address that is incorrectly set to zero, or a zero klog : length. This needs to be fixed. klog : -klog : FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1, HIGH -klog : Kernel message: [ 0.000000] ACPI Warning: Optional field +klog : FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: Test 1, +klog : HIGH Kernel message: [ 0.000000] ACPI Warning: Optional field klog : Pm2ControlBlock has zero address or length: 0000000000000000/1 klog : 20090521 tbfadt-558 klog : @@ -98,8 +98,8 @@ klog : ADVICE: An ACPI table contains Generic Address Structure that klog : has an address that is incorrectly set to zero, or a zero klog : length. This needs to be fixed. klog : -klog : FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1, HIGH -klog : Kernel message: [ 0.000000] ACPI Warning (tbfadt-0460): +klog : FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: Test 1, +klog : HIGH Kernel message: [ 0.000000] ACPI Warning (tbfadt-0460): klog : Optional field "Gpe1Block" has zero address or length: klog : 000000000000102C/0 [20080926] klog : @@ -107,7 +107,7 @@ klog : ADVICE: An ACPI table contains Generic Address Structure that klog : has an address that is incorrectly set to zero, or a zero klog : length. This needs to be fixed. klog : -klog : FAILED [MEDIUM] KlogMtrryourBIOSHasConfigured: Test 1, MEDIUM +klog : FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1, MEDIUM klog : Kernel message: [ 0.000000] mtrr: your BIOS has configured an klog : incorrect mask, fixing it. klog : @@ -116,7 +116,7 @@ klog : memory caching policy are misconfigued by the BIOS. In this klog : case, the mask is incorrectly set and the kernel has detected klog : this and worked around the firmware bug. klog : -klog : FAILED [CRITICAL] KlogWARNINGBIOSBugCPUMTRRsDont: Test 1, +klog : FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test 1, klog : CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug: CPU klog : MTRRs don't cover all of memory, losing 1408MB of RAM. klog : @@ -127,18 +127,18 @@ klog : detected this and has reduced the amount of memory available to klog : be safe. Either check that the BIOS memory caching options are klog : set correctly or contact your BIOS vendor to get this fixed. klog : -klog : FAILED [CRITICAL] KlogACPIErrorFoundUnknownOpcode: Test 1, -klog : CRITICAL Kernel message: [ 0.022719] ACPI Error: Found unknown -klog : opcode 0xFD at AML address f7ffe14c offset 0xE8, ignoring -klog : (20110112/psloop-141) +klog : FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH Kernel +klog : message: [ 0.022719] ACPI Error: Found unknown opcode 0xFD at +klog : AML address f7ffe14c offset 0xE8, ignoring (20110112 +klog : /psloop-141) klog : -klog : ADVICE: An illegal AML opcode has been found and is ignored. -klog : This indicates either badly compiled code or opcode corruption -klog : in the DSDT or SSDT tables or a bug in the ACPI execution -klog : engine. Recommend disassembing using iasl to find any offending -klog : code. +klog : ADVICE: ACPI execution run time error: The ACPI interpreter has +klog : reached an opcode that is unknown, this normally is a bug in +klog : the underlying AML code either because of badly written AML +klog : code or the compiler has produced code that is incorrect or the +klog : ACPI interpreter does not support this valid opcode. klog : -klog : FAILED [CRITICAL] KlogACPIWarningDetectedAnUnsupported: Test 1, +klog : FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test 1, klog : CRITICAL Kernel message: [ 0.025463] ACPI Warning: Detected an klog : unsupported executable opcode at module-level: [0x007B] at klog : table offset 0x00C3 (20110112/psloop-526) @@ -149,23 +149,23 @@ klog : in the DSDT or SSDT tables or a bug in the ACPI execution klog : engine. Recommend disassembing using iasl to find any offending klog : code. klog : -klog : FAILED [HIGH] KlogACPIErrorMethodExecutionParse: Test 1, HIGH -klog : Kernel message: [ 0.034090] ACPI Error: Method parse/execution -klog : failed [_SB_.PCI0._OSC] (Node ee025630), AE_ALREADY_EXISTS -klog : (20110112/psparse-536) +klog : FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1, HIGH Kernel +klog : message: [ 0.034090] ACPI Error: Method parse/execution failed +klog : [_SB_.PCI0._OSC] (Node ee025630), AE_ALREADY_EXISTS (20110112 +klog : /psparse-536) klog : klog : ADVICE: This is a bug picked up by the kernel, but as yet, the klog : firmware test suite has no diagnostic advice for this klog : particular problem. klog : -klog : FAILED [HIGH] KlogFirmwareBug: Test 1, HIGH Kernel message: [ -klog : 0.040119] [Firmware Bug]: the BIOS has corrupted hw-PMU -klog : resources (MSR 186 is 400000) +klog : FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH Kernel +klog : message: [ 0.040119] [Firmware Bug]: the BIOS has corrupted +klog : hw-PMU resources (MSR 186 is 400000) klog : klog : ADVICE: The kernel has detected a Firmware bug in the BIOS or klog : ACPI which needs investigating and fixing. klog : -klog : FAILED [CRITICAL] KlogACPIWarningDetectedAnUnsupported: Test 1, +klog : FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test 1, klog : CRITICAL Kernel message: [ 0.042222] ACPI Warning: Detected an klog : unsupported executable opcode at module-level: [0x0070] at klog : table offset 0x2366 (20100121/psloop-526) diff --git a/arg-log-format-0001/klog-0003.log b/arg-log-format-0001/klog-0003.log index b0492b9..48f3655 100644 --- a/arg-log-format-0001/klog-0003.log +++ b/arg-log-format-0001/klog-0003.log @@ -1,7 +1,7 @@ klog 00013: Scan kernel log for errors and warnings. klog 00014: --------------------------------------------------------- klog 00015: Test 1 of 1: Kernel log error check. -klog 00016: FAILED [HIGH] KlogACPIBIOSBugMultipleAPIC: Test 1, HIGH +klog 00016: FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH klog 00017: Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC klog 00018: /MADT found, using 0 klog 00019: @@ -12,10 +12,10 @@ klog 00023: the kernel will by default select the first one. However, klog 00024: one can override this and select the Nth MADT using klog 00025: acpi_apic_instance=N. klog 00026: -klog 00027: FAILED [HIGH] KlogACPIError3264XAddress: Test 1, HIGH -klog 00028: Kernel message: [ 0.000000] ACPI Error: 32/64X address -klog 00029: mismatch in Gpe0Block: 00008018/0000000000008028, using -klog 00030: 32 (20090903/tbfadt-427) +klog 00027: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1, +klog 00028: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X +klog 00029: address mismatch in Gpe0Block: 00008018/0000000000008028, +klog 00030: using 32 (20090903/tbfadt-427) klog 00031: klog 00032: ADVICE: The FADT table contains a mismatch between a 32 klog 00033: bit pointer and a 64 bit Generic Address pointer. Because @@ -25,19 +25,19 @@ klog 00036: then the kernel will opt for this in preference to the 64 klog 00037: bit pointer even though this is not in accordance to the klog 00038: ACPI specification. klog 00039: -klog 00040: FAILED [CRITICAL] KlogACPIErrorAValidRSDP: Test 1, +klog 00040: FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1, klog 00041: CRITICAL Kernel message: [ 0.000000] ACPI Error: A valid klog 00042: RSDP was not found (20090903/tbxfroot-219) klog 00043: -klog 00044: ADVICE: An ACPI-compatible system must provide an RSDP -klog 00045: (Root System Description Pointer in the system’s low -klog 00046: address space. This structure’s only purpose is to -klog 00047: provide the physical address of the RSDT and XSDT. -klog 00048: -klog 00049: FAILED [HIGH] KlogACPIWarningErrortwoFACS: Test 1, HIGH -klog 00050: Kernel message: [ 0.000000] ACPI Warning: 32/64 FACS -klog 00051: address mismatch in FADT - two FACS tables! (20090903 -klog 00052: /tbfadt-369) +klog 00044: ADVICE: An ACPI compatible system must provide an RSDP +klog 00045: (Root System Description Pointer). This structure +klog 00046: provides the physical address of the RSDT and XSDT. Since +klog 00047: this could not be found, the ACPI driver has had to +klog 00048: disable ACPI support. +klog 00049: +klog 00050: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel +klog 00051: message: [ 0.000000] ACPI Warning: 32/64 FACS address +klog 00052: mismatch in FADT - two FACS tables! (20090903/tbfadt-369) klog 00053: klog 00054: ADVICE: The FADT table contains a mismatch between the 32 klog 00055: bit pointer (FIRMWARE_CTRL) and 64 bit pointer @@ -54,134 +54,134 @@ klog 00065: which is NOT complaint with the ACPI specification. The klog 00066: kernel has to make a choice and opts for the 32 bit klog 00067: FIRMWARE_CTRL. klog 00068: -klog 00069: FAILED [HIGH] KlogACPIWarningError3264length: Test 1, -klog 00070: HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64X -klog 00071: FACS address mismatch in FADT - DEF2DF40/00000000DEF30D40 -klog 00072: , using 32 (20090903/tbfadt-486) +klog 00069: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt: +klog 00070: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32 +klog 00071: /64X FACS address mismatch in FADT - DEF2DF40 +klog 00072: /00000000DEF30D40, using 32 (20090903/tbfadt-486) klog 00073: klog 00074: ADVICE: The FADT table contains Generic Address Structure klog 00075: that has a mismatch between the 32 bit and 64 bit klog 00076: versions of an address. This should be fixed so there are klog 00077: no mismatches. klog 00078: -klog 00079: FAILED [HIGH] KlogACPIWarningError3264length: Test 1, -klog 00080: HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64X -klog 00081: length mismatch in Gpe1Block: 0/32 20090521 tbfadt-527 -klog 00082: -klog 00083: ADVICE: The FADT table contains Generic Address Structure -klog 00084: that has a mismatch between the 32 bit and 64 bit -klog 00085: versions of an address. This should be fixed so there are -klog 00086: no mismatches. -klog 00087: -klog 00088: FAILED [HIGH] KlogACPIWarning: Test 1, HIGH Kernel -klog 00089: message: [ 0.000000] ACPI Warning: BIOS XSDT has NULL -klog 00090: entry, using RSDT (20110112/tbutils-663) -klog 00091: -klog 00092: ADVICE: ACPI AML intepreter has found some non-conforming -klog 00093: AML code. This should be investigated and fixed. -klog 00094: -klog 00095: FAILED [HIGH] KlogACPIWarningInvalidLengthForfadt: Test 1 -klog 00096: , HIGH Kernel message: [ 0.000000] ACPI Warning: Invalid -klog 00097: length for Pm1aControlBlock: 32, using default 16 -klog 00098: (20090903/tbfadt-607) -klog 00099: -klog 00100: ADVICE: This item in the FADT is the incorrect length. -klog 00101: Should be corrected. -klog 00102: -klog 00103: FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1 -klog 00104: , HIGH Kernel message: [ 0.000000] ACPI Warning: Optional -klog 00105: field Gpe1Block has zero address or length: -klog 00106: 000000000000102C/0 20090521 tbfadt-558 -klog 00107: -klog 00108: ADVICE: An ACPI table contains Generic Address Structure -klog 00109: that has an address that is incorrectly set to zero, or a -klog 00110: zero length. This needs to be fixed. -klog 00111: -klog 00112: FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1 -klog 00113: , HIGH Kernel message: [ 0.000000] ACPI Warning: Optional -klog 00114: field Pm2ControlBlock has zero address or length: -klog 00115: 0000000000000000/1 20090521 tbfadt-558 -klog 00116: -klog 00117: ADVICE: An ACPI table contains Generic Address Structure -klog 00118: that has an address that is incorrectly set to zero, or a -klog 00119: zero length. This needs to be fixed. -klog 00120: -klog 00121: FAILED [HIGH] KlogACPIWarningOptionalFieldhasZero: Test 1 -klog 00122: , HIGH Kernel message: [ 0.000000] ACPI Warning -klog 00123: (tbfadt-0460): Optional field "Gpe1Block" has zero -klog 00124: address or length: 000000000000102C/0 [20080926] -klog 00125: -klog 00126: ADVICE: An ACPI table contains Generic Address Structure -klog 00127: that has an address that is incorrectly set to zero, or a -klog 00128: zero length. This needs to be fixed. -klog 00129: -klog 00130: FAILED [MEDIUM] KlogMtrryourBIOSHasConfigured: Test 1, -klog 00131: MEDIUM Kernel message: [ 0.000000] mtrr: your BIOS has -klog 00132: configured an incorrect mask, fixing it. -klog 00133: -klog 00134: ADVICE: The Memory Type Range Registers (MTRRs) which -klog 00135: define memory caching policy are misconfigued by the -klog 00136: BIOS. In this case, the mask is incorrectly set and the -klog 00137: kernel has detected this and worked around the firmware -klog 00138: bug. -klog 00139: -klog 00140: FAILED [CRITICAL] KlogWARNINGBIOSBugCPUMTRRsDont: Test 1, -klog 00141: CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug: -klog 00142: CPU MTRRs don't cover all of memory, losing 1408MB of -klog 00143: RAM. -klog 00144: -klog 00145: ADVICE: The Memory Type Range Registers (MTRRs) which -klog 00146: define memory caching policy are misconfigued by the BIOS -klog 00147: and don't appear to cover all available physical memory. -klog 00148: The kernel has detected this and has reduced the amount -klog 00149: of memory available to be safe. Either check that the -klog 00150: BIOS memory caching options are set correctly or contact -klog 00151: your BIOS vendor to get this fixed. -klog 00152: -klog 00153: FAILED [CRITICAL] KlogACPIErrorFoundUnknownOpcode: Test 1 -klog 00154: , CRITICAL Kernel message: [ 0.022719] ACPI Error: Found -klog 00155: unknown opcode 0xFD at AML address f7ffe14c offset 0xE8, -klog 00156: ignoring (20110112/psloop-141) -klog 00157: -klog 00158: ADVICE: An illegal AML opcode has been found and is -klog 00159: ignored. This indicates either badly compiled code or -klog 00160: opcode corruption in the DSDT or SSDT tables or a bug in -klog 00161: the ACPI execution engine. Recommend disassembing using -klog 00162: iasl to find any offending code. -klog 00163: -klog 00164: FAILED [CRITICAL] KlogACPIWarningDetectedAnUnsupported: -klog 00165: Test 1, CRITICAL Kernel message: [ 0.025463] ACPI Warning -klog 00166: : Detected an unsupported executable opcode at -klog 00167: module-level: [0x007B] at table offset 0x00C3 (20110112 -klog 00168: /psloop-526) -klog 00169: -klog 00170: ADVICE: An illegal AML opcode has been found and is -klog 00171: ignored. This indicates either badly compiled code or -klog 00172: opcode corruption in the DSDT or SSDT tables or a bug in -klog 00173: the ACPI execution engine. Recommend disassembing using -klog 00174: iasl to find any offending code. -klog 00175: -klog 00176: FAILED [HIGH] KlogACPIErrorMethodExecutionParse: Test 1, -klog 00177: HIGH Kernel message: [ 0.034090] ACPI Error: Method parse -klog 00178: /execution failed [_SB_.PCI0._OSC] (Node ee025630), -klog 00179: AE_ALREADY_EXISTS (20110112/psparse-536) -klog 00180: -klog 00181: ADVICE: This is a bug picked up by the kernel, but as yet -klog 00182: , the firmware test suite has no diagnostic advice for -klog 00183: this particular problem. -klog 00184: -klog 00185: FAILED [HIGH] KlogFirmwareBug: Test 1, HIGH Kernel -klog 00186: message: [ 0.040119] [Firmware Bug]: the BIOS has -klog 00187: corrupted hw-PMU resources (MSR 186 is 400000) -klog 00188: -klog 00189: ADVICE: The kernel has detected a Firmware bug in the -klog 00190: BIOS or ACPI which needs investigating and fixing. -klog 00191: -klog 00192: FAILED [CRITICAL] KlogACPIWarningDetectedAnUnsupported: -klog 00193: Test 1, CRITICAL Kernel message: [ 0.042222] ACPI Warning -klog 00194: : Detected an unsupported executable opcode at -klog 00195: module-level: [0x0070] at table offset 0x2366 (20100121 -klog 00196: /psloop-526) +klog 00079: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt: +klog 00080: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32 +klog 00081: /64X length mismatch in Gpe1Block: 0/32 20090521 +klog 00082: tbfadt-527 +klog 00083: +klog 00084: ADVICE: The FADT table contains Generic Address Structure +klog 00085: that has a mismatch between the 32 bit and 64 bit +klog 00086: versions of an address. This should be fixed so there are +klog 00087: no mismatches. +klog 00088: +klog 00089: FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel +klog 00090: message: [ 0.000000] ACPI Warning: BIOS XSDT has NULL +klog 00091: entry, using RSDT (20110112/tbutils-663) +klog 00092: +klog 00093: ADVICE: ACPI AML intepreter has found some non-conforming +klog 00094: AML code. This should be investigated and fixed. +klog 00095: +klog 00096: FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1, HIGH +klog 00097: Kernel message: [ 0.000000] ACPI Warning: Invalid length +klog 00098: for Pm1aControlBlock: 32, using default 16 (20090903 +klog 00099: /tbfadt-607) +klog 00100: +klog 00101: ADVICE: This item in the FADT is the incorrect length. +klog 00102: Should be corrected. +klog 00103: +klog 00104: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: +klog 00105: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: +klog 00106: Optional field Gpe1Block has zero address or length: +klog 00107: 000000000000102C/0 20090521 tbfadt-558 +klog 00108: +klog 00109: ADVICE: An ACPI table contains Generic Address Structure +klog 00110: that has an address that is incorrectly set to zero, or a +klog 00111: zero length. This needs to be fixed. +klog 00112: +klog 00113: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: +klog 00114: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: +klog 00115: Optional field Pm2ControlBlock has zero address or length +klog 00116: : 0000000000000000/1 20090521 tbfadt-558 +klog 00117: +klog 00118: ADVICE: An ACPI table contains Generic Address Structure +klog 00119: that has an address that is incorrectly set to zero, or a +klog 00120: zero length. This needs to be fixed. +klog 00121: +klog 00122: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength: +klog 00123: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning +klog 00124: (tbfadt-0460): Optional field "Gpe1Block" has zero +klog 00125: address or length: 000000000000102C/0 [20080926] +klog 00126: +klog 00127: ADVICE: An ACPI table contains Generic Address Structure +klog 00128: that has an address that is incorrectly set to zero, or a +klog 00129: zero length. This needs to be fixed. +klog 00130: +klog 00131: FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1, MEDIUM +klog 00132: Kernel message: [ 0.000000] mtrr: your BIOS has +klog 00133: configured an incorrect mask, fixing it. +klog 00134: +klog 00135: ADVICE: The Memory Type Range Registers (MTRRs) which +klog 00136: define memory caching policy are misconfigued by the +klog 00137: BIOS. In this case, the mask is incorrectly set and the +klog 00138: kernel has detected this and worked around the firmware +klog 00139: bug. +klog 00140: +klog 00141: FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test 1, +klog 00142: CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug: +klog 00143: CPU MTRRs don't cover all of memory, losing 1408MB of +klog 00144: RAM. +klog 00145: +klog 00146: ADVICE: The Memory Type Range Registers (MTRRs) which +klog 00147: define memory caching policy are misconfigued by the BIOS +klog 00148: and don't appear to cover all available physical memory. +klog 00149: The kernel has detected this and has reduced the amount +klog 00150: of memory available to be safe. Either check that the +klog 00151: BIOS memory caching options are set correctly or contact +klog 00152: your BIOS vendor to get this fixed. +klog 00153: +klog 00154: FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH +klog 00155: Kernel message: [ 0.022719] ACPI Error: Found unknown +klog 00156: opcode 0xFD at AML address f7ffe14c offset 0xE8, ignoring +klog 00157: (20110112/psloop-141) +klog 00158: +klog 00159: ADVICE: ACPI execution run time error: The ACPI +klog 00160: interpreter has reached an opcode that is unknown, this +klog 00161: normally is a bug in the underlying AML code either +klog 00162: because of badly written AML code or the compiler has +klog 00163: produced code that is incorrect or the ACPI interpreter +klog 00164: does not support this valid opcode. +klog 00165: +klog 00166: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test +klog 00167: 1, CRITICAL Kernel message: [ 0.025463] ACPI Warning: +klog 00168: Detected an unsupported executable opcode at module-level +klog 00169: : [0x007B] at table offset 0x00C3 (20110112/psloop-526) +klog 00170: +klog 00171: ADVICE: An illegal AML opcode has been found and is +klog 00172: ignored. This indicates either badly compiled code or +klog 00173: opcode corruption in the DSDT or SSDT tables or a bug in +klog 00174: the ACPI execution engine. Recommend disassembing using +klog 00175: iasl to find any offending code. +klog 00176: +klog 00177: FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1, HIGH +klog 00178: Kernel message: [ 0.034090] ACPI Error: Method parse +klog 00179: /execution failed [_SB_.PCI0._OSC] (Node ee025630), +klog 00180: AE_ALREADY_EXISTS (20110112/psparse-536) +klog 00181: +klog 00182: ADVICE: This is a bug picked up by the kernel, but as yet +klog 00183: , the firmware test suite has no diagnostic advice for +klog 00184: this particular problem. +klog 00185: +klog 00186: FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH Kernel +klog 00187: message: [ 0.040119] [Firmware Bug]: the BIOS has +klog 00188: corrupted hw-PMU resources (MSR 186 is 400000) +klog 00189: +klog 00190: ADVICE: The kernel has detected a Firmware bug in the +klog 00191: BIOS or ACPI which needs investigating and fixing. +klog 00192: +klog 00193: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test +klog 00194: 1, CRITICAL Kernel message: [ 0.042222] ACPI Warning: +klog 00195: Detected an unsupported executable opcode at module-level +klog 00196: : [0x0070] at table offset 0x2366 (20100121/psloop-526) klog 00197: klog 00198: ADVICE: An illegal AML opcode has been found and is klog 00199: ignored. This indicates either badly compiled code or diff --git a/arg-log-format-0001/klog-0004.log b/arg-log-format-0001/klog-0004.log index 0521c06..7f3048f 100644 --- a/arg-log-format-0001/klog-0004.log +++ b/arg-log-format-0001/klog-0004.log @@ -1,7 +1,7 @@ klog 10/10/11 : 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] KlogACPIBIOSBugMultipleAPIC: Test 1, +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 : @@ -12,9 +12,9 @@ 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] KlogACPIError3264XAddress: Test 1, -klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X -klog 10/10/11 H: address mismatch in Gpe0Block: 00008018 +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 @@ -25,19 +25,19 @@ 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] KlogACPIErrorAValidRSDP: Test 1, +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 in the -klog 10/10/11 : system’s low address space. This structure’s -klog 10/10/11 : only purpose is to provide the physical address of -klog 10/10/11 : the RSDT and XSDT. +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] KlogACPIWarningErrortwoFACS: Test 1, -klog 10/10/11 H: HIGH Kernel message: [ 0.000000] ACPI Warning: 32/64 -klog 10/10/11 H: FACS address mismatch in FADT - two FACS tables! +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 @@ -56,8 +56,9 @@ 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] KlogACPIWarningError3264length: Test 1 -klog 10/10/11 H: , HIGH Kernel message: [ 0.000000] ACPI Warning: 32 +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 : @@ -66,8 +67,9 @@ 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] KlogACPIWarningError3264length: Test 1 -klog 10/10/11 H: , HIGH Kernel message: [ 0.000000] ACPI Warning: 32 +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 : @@ -76,57 +78,58 @@ 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] KlogACPIWarning: Test 1, HIGH Kernel -klog 10/10/11 H: message: [ 0.000000] ACPI Warning: BIOS XSDT has -klog 10/10/11 H: NULL entry, using RSDT (20110112/tbutils-663) +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] KlogACPIWarningInvalidLengthForfadt: -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI -klog 10/10/11 H: Warning: Invalid length for Pm1aControlBlock: 32, -klog 10/10/11 H: using default 16 (20090903/tbfadt-607) +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] KlogACPIWarningOptionalFieldhasZero: -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI -klog 10/10/11 H: Warning: Optional field Gpe1Block has zero address -klog 10/10/11 H: or length: 000000000000102C/0 20090521 tbfadt-558 +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] KlogACPIWarningOptionalFieldhasZero: -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI -klog 10/10/11 H: Warning: Optional field Pm2ControlBlock has zero -klog 10/10/11 H: address or length: 0000000000000000/1 20090521 -klog 10/10/11 H: tbfadt-558 +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] KlogACPIWarningOptionalFieldhasZero: -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.000000] ACPI -klog 10/10/11 H: Warning (tbfadt-0460): Optional field "Gpe1Block" -klog 10/10/11 H: has zero address or length: 000000000000102C/0 -klog 10/10/11 H: [20080926] +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] KlogMtrryourBIOSHasConfigured: Test -klog 10/10/11 M: 1, MEDIUM Kernel message: [ 0.000000] mtrr: your -klog 10/10/11 M: BIOS has configured an incorrect mask, fixing it. +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 @@ -134,9 +137,9 @@ 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] KlogWARNINGBIOSBugCPUMTRRsDont: -klog 10/10/11 C: Test 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: 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) @@ -148,22 +151,23 @@ 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 C: FAILED [CRITICAL] KlogACPIErrorFoundUnknownOpcode: -klog 10/10/11 C: Test 1, CRITICAL Kernel message: [ 0.022719] ACPI -klog 10/10/11 C: Error: Found unknown opcode 0xFD at AML address -klog 10/10/11 C: f7ffe14c offset 0xE8, ignoring (20110112/psloop-141) +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 : 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 C: FAILED [CRITICAL] -klog 10/10/11 C: KlogACPIWarningDetectedAnUnsupported: Test 1, -klog 10/10/11 C: CRITICAL Kernel message: [ 0.025463] ACPI Warning: -klog 10/10/11 C: Detected an unsupported executable opcode at -klog 10/10/11 C: module-level: [0x007B] at table offset 0x00C3 +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 @@ -172,28 +176,27 @@ 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] KlogACPIErrorMethodExecutionParse: -klog 10/10/11 H: Test 1, HIGH Kernel message: [ 0.034090] ACPI Error: -klog 10/10/11 H: Method parse/execution failed [_SB_.PCI0._OSC] (Node +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] KlogFirmwareBug: Test 1, HIGH Kernel -klog 10/10/11 H: message: [ 0.040119] [Firmware Bug]: the BIOS has -klog 10/10/11 H: corrupted hw-PMU resources (MSR 186 is 400000) +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] -klog 10/10/11 C: KlogACPIWarningDetectedAnUnsupported: Test 1, -klog 10/10/11 C: CRITICAL Kernel message: [ 0.042222] ACPI Warning: -klog 10/10/11 C: Detected an unsupported executable opcode at -klog 10/10/11 C: module-level: [0x0070] at table offset 0x2366 +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