diff mbox

fwts-test: arg-log-format-0001: update to sync with fwts

Message ID 1394181758-22511-1-git-send-email-ivan.hu@canonical.com
State Rejected
Headers show

Commit Message

Ivan Hu March 7, 2014, 8:42 a.m. UTC 
Signed-off-by: Ivan Hu <ivan.hu@canonical.com>
---
 fwts-test/arg-log-format-0001/klog-0001.log |  550 +++++++++++++--------------
 1 file changed, 275 insertions(+), 275 deletions(-)

Comments

Colin Ian King March 7, 2014, 9:10 a.m. UTC | #1 
On 07/03/14 08:42, Ivan Hu wrote:
> Signed-off-by: Ivan Hu <ivan.hu@canonical.com>
> ---
>  fwts-test/arg-log-format-0001/klog-0001.log |  550 +++++++++++++--------------
>  1 file changed, 275 insertions(+), 275 deletions(-)
> 
> diff --git a/fwts-test/arg-log-format-0001/klog-0001.log b/fwts-test/arg-log-format-0001/klog-0001.log
> index db134e0..6ce5b40 100644
> --- a/fwts-test/arg-log-format-0001/klog-0001.log
> +++ b/fwts-test/arg-log-format-0001/klog-0001.log
> @@ -1,275 +1,275 @@
> -klog            (00021) <10/02/14> HED  : klog: Scan kernel log for errors and
> -klog            (00022) <10/02/14> HED  : warnings.
> -klog            (00023) <10/02/14> SEP  : --------------------------------------
<text deleted>

NACK.

Unfortunately because the test is rather stupid one has to ensure the
date matches the original reference date hard coded in the test as this
is then replaced using sed to match the date one runs the test. It's
lame and I need to fix that. Until I fix that test, the klog-0001.log
date needs to be always <10/02/14>

..I can guarantee if you don't set the date the test will only work
today ;-)

Colin
Colin Ian King March 7, 2014, 10:38 a.m. UTC | #2 
On 07/03/14 09:10, Colin Ian King wrote:
> On 07/03/14 08:42, Ivan Hu wrote:
>> Signed-off-by: Ivan Hu <ivan.hu@canonical.com>
>> ---
>>  fwts-test/arg-log-format-0001/klog-0001.log |  550 +++++++++++++--------------
>>  1 file changed, 275 insertions(+), 275 deletions(-)
>>
>> diff --git a/fwts-test/arg-log-format-0001/klog-0001.log b/fwts-test/arg-log-format-0001/klog-0001.log
>> index db134e0..6ce5b40 100644
>> --- a/fwts-test/arg-log-format-0001/klog-0001.log
>> +++ b/fwts-test/arg-log-format-0001/klog-0001.log
>> @@ -1,275 +1,275 @@
>> -klog            (00021) <10/02/14> HED  : klog: Scan kernel log for errors and
>> -klog            (00022) <10/02/14> HED  : warnings.
>> -klog            (00023) <10/02/14> SEP  : --------------------------------------
> <text deleted>
> 
> NACK.
> 
> Unfortunately because the test is rather stupid one has to ensure the
> date matches the original reference date hard coded in the test as this
> is then replaced using sed to match the date one runs the test. It's
> lame and I need to fix that. Until I fix that test, the klog-0001.log
> date needs to be always <10/02/14>
> 
> ..I can guarantee if you don't set the date the test will only work
> today ;-)
> 
> Colin
> 
OK, Ignore my NACK, I've sent a fix to the mailing list that should
address this issue in a generic way so we don't have to keep on tweaking
the date.

I'm ACK'ing this patch as long as my fix for LP:#1289225 is accepted as
it will make this test work on any day.

Colin
diff mbox

Patch

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