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