[PATCH 5/5][FWTS-TEST] arg-log-format-0001: fixup klog logs due to changes in fwts klog test
IvanHu
ivan.hu at canonical.com
Wed Jan 16 08:33:32 UTC 2013
On 01/15/2013 06:45 PM, Colin King wrote:
> From: Colin Ian King <colin.king at canonical.com>
>
> fwts klog test has made quite a few changes, so fix up these tests
>
> Signed-off-by: Colin Ian King <colin.king at canonical.com>
> ---
> arg-log-format-0001/klog-0001.log | 485 +++++++++++++++++++-------------------
> arg-log-format-0001/klog-0002.log | 10 +-
> arg-log-format-0001/klog-0003.log | 346 ++++++++++++++-------------
> arg-log-format-0001/klog-0004.log | 11 +-
> 4 files changed, 421 insertions(+), 431 deletions(-)
>
> diff --git a/arg-log-format-0001/klog-0001.log b/arg-log-format-0001/klog-0001.log
> index 40e77fa..c12a88e 100644
> --- a/arg-log-format-0001/klog-0001.log
> +++ b/arg-log-format-0001/klog-0001.log
> @@ -1,248 +1,245 @@
> -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> FAL H: FAILED [HIGH]
> -klog (00022) <16/05/12> FAL H: KlogAcpiMultipleApicMadtFound: Test 1,
> -klog (00023) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI:
> -klog (00024) <16/05/12> FAL H: BIOS bug: multiple APIC/MADT found,
> -klog (00025) <16/05/12> FAL H: using 0
> -klog (00026) <16/05/12> NLN :
> -klog (00027) <16/05/12> ADV : ADVICE: The kernel has detected more
> -klog (00028) <16/05/12> ADV : than one ACPI Multiple APIC
> -klog (00029) <16/05/12> ADV : Description Table (MADT) (these tables
> -klog (00030) <16/05/12> ADV : have the "APIC" signature). There
> -klog (00031) <16/05/12> ADV : should only be one MADT and the kernel
> -klog (00032) <16/05/12> ADV : will by default select the first one.
> -klog (00033) <16/05/12> ADV : However, one can override this and
> -klog (00034) <16/05/12> ADV : select the Nth MADT using
> -klog (00035) <16/05/12> ADV : acpi_apic_instance=N.
> -klog (00036) <16/05/12> NLN :
> -klog (00037) <16/05/12> FAL H: FAILED [HIGH]
> -klog (00038) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatch:
> -klog (00039) <16/05/12> FAL H: Test 1, HIGH Kernel message: [
> -klog (00040) <16/05/12> FAL H: 0.000000] ACPI Error: 32/64X address
> -klog (00041) <16/05/12> FAL H: mismatch in Gpe0Block: 00008018
> -klog (00042) <16/05/12> FAL H: /0000000000008028, using 32 (20090903
> -klog (00043) <16/05/12> FAL H: /tbfadt-427)
> -klog (00044) <16/05/12> NLN :
> -klog (00045) <16/05/12> ADV : ADVICE: The FADT table contains a
> -klog (00046) <16/05/12> ADV : mismatch between a 32 bit pointer and
> -klog (00047) <16/05/12> ADV : a 64 bit Generic Address pointer.
> -klog (00048) <16/05/12> ADV : Because these pointers are different,
> -klog (00049) <16/05/12> ADV : it suggests either one of them is
> -klog (00050) <16/05/12> ADV : incorrect. If a non-null 32 bit
> -klog (00051) <16/05/12> ADV : pointer exists, then the kernel will
> -klog (00052) <16/05/12> ADV : opt for this in preference to the 64
> -klog (00053) <16/05/12> ADV : bit pointer even though this is not in
> -klog (00054) <16/05/12> ADV : accordance to the ACPI specification.
> -klog (00055) <16/05/12> NLN :
> -klog (00056) <16/05/12> FAL C: FAILED [CRITICAL]
> -klog (00057) <16/05/12> FAL C: KlogAcpiValidRsdpNotFound: Test 1,
> -klog (00058) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000]
> -klog (00059) <16/05/12> FAL C: ACPI Error: A valid RSDP was not found
> -klog (00060) <16/05/12> FAL C: (20090903/tbxfroot-219)
> -klog (00061) <16/05/12> NLN :
> -klog (00062) <16/05/12> ADV : ADVICE: An ACPI compatible system must
> -klog (00063) <16/05/12> ADV : provide an RSDP (Root System
> -klog (00064) <16/05/12> ADV : Description Pointer). This structure
> -klog (00065) <16/05/12> ADV : provides the physical address of the
> -klog (00066) <16/05/12> ADV : RSDT and XSDT. Since this could not be
> -klog (00067) <16/05/12> ADV : found, the ACPI driver has had to
> -klog (00068) <16/05/12> ADV : disable ACPI support.
> -klog (00069) <16/05/12> NLN :
> -klog (00070) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiTwoFacs: Test 1,
> -klog (00071) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI
> -klog (00072) <16/05/12> FAL H: Warning: 32/64 FACS address mismatch
> -klog (00073) <16/05/12> FAL H: in FADT - two FACS tables! (20090903
> -klog (00074) <16/05/12> FAL H: /tbfadt-369)
> -klog (00075) <16/05/12> NLN :
> -klog (00076) <16/05/12> ADV : ADVICE: The FADT table contains a
> -klog (00077) <16/05/12> ADV : mismatch between the 32 bit pointer
> -klog (00078) <16/05/12> ADV : (FIRMWARE_CTRL) and 64 bit pointer
> -klog (00079) <16/05/12> ADV : (X_FIRMWARE_CTRL) pointer to the FACS
> -klog (00080) <16/05/12> ADV : table. Section 5.2.9 of version 4.0a
> -klog (00081) <16/05/12> ADV : of the ACPI specification states that
> -klog (00082) <16/05/12> ADV : X_FIRMWARE_CTRL should be zero if
> -klog (00083) <16/05/12> ADV : FIRMWARE_CTRL is defined, or
> -klog (00084) <16/05/12> ADV : FIRMWARE_CTRL should be zero if
> -klog (00085) <16/05/12> ADV : X_FIRMWARE_CTRL is zero. With two
> -klog (00086) <16/05/12> ADV : different pointers defined, the kernel
> -klog (00087) <16/05/12> ADV : has to make a choice, and opts for the
> -klog (00088) <16/05/12> ADV : 32 bit pointer. Because these pointers
> -klog (00089) <16/05/12> ADV : are different, it suggests either one
> -klog (00090) <16/05/12> ADV : of them is incorrect, or different 32
> -klog (00091) <16/05/12> ADV : bit and 64 bit FACS tables are present
> -klog (00092) <16/05/12> ADV : in your system, which is NOT complaint
> -klog (00093) <16/05/12> ADV : with the ACPI specification. The
> -klog (00094) <16/05/12> ADV : kernel has to make a choice and opts
> -klog (00095) <16/05/12> ADV : for the 32 bit FIRMWARE_CTRL.
> -klog (00096) <16/05/12> NLN :
> -klog (00097) <16/05/12> FAL H: FAILED [HIGH]
> -klog (00098) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt
> -klog (00099) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> -klog (00100) <16/05/12> FAL H: 0.000000] ACPI Warning: 32/64X FACS
> -klog (00101) <16/05/12> FAL H: address mismatch in FADT - DEF2DF40
> -klog (00102) <16/05/12> FAL H: /00000000DEF30D40, using 32 (20090903
> -klog (00103) <16/05/12> FAL H: /tbfadt-486)
> -klog (00104) <16/05/12> NLN :
> -klog (00105) <16/05/12> ADV : ADVICE: The FADT table contains
> -klog (00106) <16/05/12> ADV : Generic Address Structure that has a
> -klog (00107) <16/05/12> ADV : mismatch between the 32 bit and 64 bit
> -klog (00108) <16/05/12> ADV : versions of an address. This should be
> -klog (00109) <16/05/12> ADV : fixed so there are no mismatches.
> -klog (00110) <16/05/12> NLN :
> -klog (00111) <16/05/12> FAL H: FAILED [HIGH]
> -klog (00112) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt
> -klog (00113) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> -klog (00114) <16/05/12> FAL H: 0.000000] ACPI Warning: 32/64X length
> -klog (00115) <16/05/12> FAL H: mismatch in Gpe1Block: 0/32 20090521
> -klog (00116) <16/05/12> FAL H: tbfadt-527
> -klog (00117) <16/05/12> NLN :
> -klog (00118) <16/05/12> ADV : ADVICE: The FADT table contains
> -klog (00119) <16/05/12> ADV : Generic Address Structure that has a
> -klog (00120) <16/05/12> ADV : mismatch between the 32 bit and 64 bit
> -klog (00121) <16/05/12> ADV : versions of an address. This should be
> -klog (00122) <16/05/12> ADV : fixed so there are no mismatches.
> -klog (00123) <16/05/12> NLN :
> -klog (00124) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiBadAmlCode: Test
> -klog (00125) <16/05/12> FAL H: 1, HIGH Kernel message: [ 0.000000]
> -klog (00126) <16/05/12> FAL H: ACPI Warning: BIOS XSDT has NULL entry
> -klog (00127) <16/05/12> FAL H: , using RSDT (20110112/tbutils-663)
> -klog (00128) <16/05/12> NLN :
> -klog (00129) <16/05/12> ADV : ADVICE: ACPI AML intepreter has found
> -klog (00130) <16/05/12> ADV : some non-conforming AML code. This
> -klog (00131) <16/05/12> ADV : should be investigated and fixed.
> -klog (00132) <16/05/12> NLN :
> -klog (00133) <16/05/12> FAL H: FAILED [HIGH]
> -klog (00134) <16/05/12> FAL H: KlogAcpiFadtInvalidLength: Test 1,
> -klog (00135) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI
> -klog (00136) <16/05/12> FAL H: Warning: Invalid length for
> -klog (00137) <16/05/12> FAL H: Pm1aControlBlock: 32, using default 16
> -klog (00138) <16/05/12> FAL H: (20090903/tbfadt-607)
> -klog (00139) <16/05/12> NLN :
> -klog (00140) <16/05/12> ADV : ADVICE: This item in the FADT is the
> -klog (00141) <16/05/12> ADV : incorrect length. Should be corrected.
> +klog (00020) <16/05/12> HED : Scan kernel log for errors and
> +klog (00021) <16/05/12> HED : warnings.
> +klog (00022) <16/05/12> SEP : --------------------------------------
> +klog (00023) <16/05/12> INF : Test 1 of 1: Kernel log error check.
> +klog (00024) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00025) <16/05/12> FAL H: KlogAcpiMultipleApicMadtFound: Test 1,
> +klog (00026) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI:
> +klog (00027) <16/05/12> FAL H: BIOS bug: multiple APIC/MADT found,
> +klog (00028) <16/05/12> FAL H: using 0
> +klog (00029) <16/05/12> NLN :
> +klog (00030) <16/05/12> ADV : ADVICE: The kernel has detected more
> +klog (00031) <16/05/12> ADV : than one ACPI Multiple APIC
> +klog (00032) <16/05/12> ADV : Description Table (MADT) (these tables
> +klog (00033) <16/05/12> ADV : have the "APIC" signature). There
> +klog (00034) <16/05/12> ADV : should only be one MADT and the kernel
> +klog (00035) <16/05/12> ADV : will by default select the first one.
> +klog (00036) <16/05/12> ADV : However, one can override this and
> +klog (00037) <16/05/12> ADV : select the Nth MADT using
> +klog (00038) <16/05/12> ADV : acpi_apic_instance=N.
> +klog (00039) <16/05/12> NLN :
> +klog (00040) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00041) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatch:
> +klog (00042) <16/05/12> FAL H: Test 1, HIGH Kernel message: [
> +klog (00043) <16/05/12> FAL H: 0.000000] ACPI Error: 32/64X address
> +klog (00044) <16/05/12> FAL H: mismatch in Gpe0Block: 00008018
> +klog (00045) <16/05/12> FAL H: /0000000000008028, using 32 (20090903
> +klog (00046) <16/05/12> FAL H: /tbfadt-427)
> +klog (00047) <16/05/12> NLN :
> +klog (00048) <16/05/12> ADV : ADVICE: The FADT table contains a
> +klog (00049) <16/05/12> ADV : mismatch between a 32 bit pointer and
> +klog (00050) <16/05/12> ADV : a 64 bit Generic Address pointer.
> +klog (00051) <16/05/12> ADV : Because these pointers are different,
> +klog (00052) <16/05/12> ADV : it suggests either one of them is
> +klog (00053) <16/05/12> ADV : incorrect. If a non-null 32 bit
> +klog (00054) <16/05/12> ADV : pointer exists, then the kernel will
> +klog (00055) <16/05/12> ADV : opt for this in preference to the 64
> +klog (00056) <16/05/12> ADV : bit pointer even though this is not in
> +klog (00057) <16/05/12> ADV : accordance to the ACPI specification.
> +klog (00058) <16/05/12> NLN :
> +klog (00059) <16/05/12> FAL C: FAILED [CRITICAL]
> +klog (00060) <16/05/12> FAL C: KlogAcpiValidRsdpNotFound: Test 1,
> +klog (00061) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000]
> +klog (00062) <16/05/12> FAL C: ACPI Error: A valid RSDP was not found
> +klog (00063) <16/05/12> FAL C: (20090903/tbxfroot-219)
> +klog (00064) <16/05/12> NLN :
> +klog (00065) <16/05/12> ADV : ADVICE: An ACPI compatible system must
> +klog (00066) <16/05/12> ADV : provide an RSDP (Root System
> +klog (00067) <16/05/12> ADV : Description Pointer). This structure
> +klog (00068) <16/05/12> ADV : provides the physical address of the
> +klog (00069) <16/05/12> ADV : RSDT and XSDT. Since this could not be
> +klog (00070) <16/05/12> ADV : found, the ACPI driver has had to
> +klog (00071) <16/05/12> ADV : disable ACPI support.
> +klog (00072) <16/05/12> NLN :
> +klog (00073) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiTwoFacs: Test 1,
> +klog (00074) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI
> +klog (00075) <16/05/12> FAL H: Warning: 32/64 FACS address mismatch
> +klog (00076) <16/05/12> FAL H: in FADT - two FACS tables! (20090903
> +klog (00077) <16/05/12> FAL H: /tbfadt-369)
> +klog (00078) <16/05/12> NLN :
> +klog (00079) <16/05/12> ADV : ADVICE: The FADT table contains a
> +klog (00080) <16/05/12> ADV : mismatch between the 32 bit pointer
> +klog (00081) <16/05/12> ADV : (FIRMWARE_CTRL) and 64 bit pointer
> +klog (00082) <16/05/12> ADV : (X_FIRMWARE_CTRL) pointer to the FACS
> +klog (00083) <16/05/12> ADV : table. Section 5.2.9 of version 4.0a
> +klog (00084) <16/05/12> ADV : of the ACPI specification states that
> +klog (00085) <16/05/12> ADV : X_FIRMWARE_CTRL should be zero if
> +klog (00086) <16/05/12> ADV : FIRMWARE_CTRL is defined, or
> +klog (00087) <16/05/12> ADV : FIRMWARE_CTRL should be zero if
> +klog (00088) <16/05/12> ADV : X_FIRMWARE_CTRL is zero. With two
> +klog (00089) <16/05/12> ADV : different pointers defined, the kernel
> +klog (00090) <16/05/12> ADV : has to make a choice, and opts for the
> +klog (00091) <16/05/12> ADV : 32 bit pointer. Because these pointers
> +klog (00092) <16/05/12> ADV : are different, it suggests either one
> +klog (00093) <16/05/12> ADV : of them is incorrect, or different 32
> +klog (00094) <16/05/12> ADV : bit and 64 bit FACS tables are present
> +klog (00095) <16/05/12> ADV : in your system, which is NOT complaint
> +klog (00096) <16/05/12> ADV : with the ACPI specification. The
> +klog (00097) <16/05/12> ADV : kernel has to make a choice and opts
> +klog (00098) <16/05/12> ADV : for the 32 bit FIRMWARE_CTRL.
> +klog (00099) <16/05/12> NLN :
> +klog (00100) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00101) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt
> +klog (00102) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> +klog (00103) <16/05/12> FAL H: 0.000000] ACPI Warning: 32/64X FACS
> +klog (00104) <16/05/12> FAL H: address mismatch in FADT - DEF2DF40
> +klog (00105) <16/05/12> FAL H: /00000000DEF30D40, using 32 (20090903
> +klog (00106) <16/05/12> FAL H: /tbfadt-486)
> +klog (00107) <16/05/12> NLN :
> +klog (00108) <16/05/12> ADV : ADVICE: The FADT table contains
> +klog (00109) <16/05/12> ADV : Generic Address Structure that has a
> +klog (00110) <16/05/12> ADV : mismatch between the 32 bit and 64 bit
> +klog (00111) <16/05/12> ADV : versions of an address. This should be
> +klog (00112) <16/05/12> ADV : fixed so there are no mismatches.
> +klog (00113) <16/05/12> NLN :
> +klog (00114) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00115) <16/05/12> FAL H: KlogAcpi32Bit64BitAddressMismatchInFadt
> +klog (00116) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> +klog (00117) <16/05/12> FAL H: 0.000000] ACPI Warning: 32/64X length
> +klog (00118) <16/05/12> FAL H: mismatch in Gpe1Block: 0/32 20090521
> +klog (00119) <16/05/12> FAL H: tbfadt-527
> +klog (00120) <16/05/12> NLN :
> +klog (00121) <16/05/12> ADV : ADVICE: The FADT table contains
> +klog (00122) <16/05/12> ADV : Generic Address Structure that has a
> +klog (00123) <16/05/12> ADV : mismatch between the 32 bit and 64 bit
> +klog (00124) <16/05/12> ADV : versions of an address. This should be
> +klog (00125) <16/05/12> ADV : fixed so there are no mismatches.
> +klog (00126) <16/05/12> NLN :
> +klog (00127) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiBadAmlCode: Test
> +klog (00128) <16/05/12> FAL H: 1, HIGH Kernel message: [ 0.000000]
> +klog (00129) <16/05/12> FAL H: ACPI Warning: BIOS XSDT has NULL entry
> +klog (00130) <16/05/12> FAL H: , using RSDT (20110112/tbutils-663)
> +klog (00131) <16/05/12> NLN :
> +klog (00132) <16/05/12> ADV : ADVICE: ACPI AML intepreter has found
> +klog (00133) <16/05/12> ADV : some non-conforming AML code. This
> +klog (00134) <16/05/12> ADV : should be investigated and fixed.
> +klog (00135) <16/05/12> NLN :
> +klog (00136) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00137) <16/05/12> FAL H: KlogAcpiFadtInvalidLength: Test 1,
> +klog (00138) <16/05/12> FAL H: HIGH Kernel message: [ 0.000000] ACPI
> +klog (00139) <16/05/12> FAL H: Warning: Invalid length for
> +klog (00140) <16/05/12> FAL H: Pm1aControlBlock: 32, using default 16
> +klog (00141) <16/05/12> FAL H: (20090903/tbfadt-607)
> klog (00142) <16/05/12> NLN :
> -klog (00143) <16/05/12> FAL H: FAILED [HIGH]
> -klog (00144) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
> -klog (00145) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> -klog (00146) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field
> -klog (00147) <16/05/12> FAL H: Gpe1Block has zero address or length:
> -klog (00148) <16/05/12> FAL H: 000000000000102C/0 20090521 tbfadt-558
> -klog (00149) <16/05/12> NLN :
> -klog (00150) <16/05/12> ADV : ADVICE: An ACPI table contains Generic
> -klog (00151) <16/05/12> ADV : Address Structure that has an address
> -klog (00152) <16/05/12> ADV : that is incorrectly set to zero, or a
> -klog (00153) <16/05/12> ADV : zero length. This needs to be fixed.
> -klog (00154) <16/05/12> NLN :
> -klog (00155) <16/05/12> FAL H: FAILED [HIGH]
> -klog (00156) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
> -klog (00157) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> -klog (00158) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field
> -klog (00159) <16/05/12> FAL H: Pm2ControlBlock has zero address or
> -klog (00160) <16/05/12> FAL H: length: 0000000000000000/1 20090521
> -klog (00161) <16/05/12> FAL H: tbfadt-558
> -klog (00162) <16/05/12> NLN :
> -klog (00163) <16/05/12> ADV : ADVICE: An ACPI table contains Generic
> -klog (00164) <16/05/12> ADV : Address Structure that has an address
> -klog (00165) <16/05/12> ADV : that is incorrectly set to zero, or a
> -klog (00166) <16/05/12> ADV : zero length. This needs to be fixed.
> -klog (00167) <16/05/12> NLN :
> -klog (00168) <16/05/12> FAL H: FAILED [HIGH]
> -klog (00169) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
> -klog (00170) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> -klog (00171) <16/05/12> FAL H: 0.000000] ACPI Warning (tbfadt-0460):
> -klog (00172) <16/05/12> FAL H: Optional field "Gpe1Block" has zero
> -klog (00173) <16/05/12> FAL H: address or length: 000000000000102C/0
> -klog (00174) <16/05/12> FAL H: [20080926]
> -klog (00175) <16/05/12> NLN :
> -klog (00176) <16/05/12> ADV : ADVICE: An ACPI table contains Generic
> -klog (00177) <16/05/12> ADV : Address Structure that has an address
> -klog (00178) <16/05/12> ADV : that is incorrectly set to zero, or a
> -klog (00179) <16/05/12> ADV : zero length. This needs to be fixed.
> -klog (00180) <16/05/12> NLN :
> -klog (00181) <16/05/12> FAL M: FAILED [MEDIUM]
> -klog (00182) <16/05/12> FAL M: KlogBiosMtrrIncorrectMask: Test 1,
> -klog (00183) <16/05/12> FAL M: MEDIUM Kernel message: [ 0.000000]
> -klog (00184) <16/05/12> FAL M: mtrr: your BIOS has configured an
> -klog (00185) <16/05/12> FAL M: incorrect mask, fixing it.
> -klog (00186) <16/05/12> NLN :
> -klog (00187) <16/05/12> ADV : ADVICE: The Memory Type Range
> -klog (00188) <16/05/12> ADV : Registers (MTRRs) which define memory
> -klog (00189) <16/05/12> ADV : caching policy are misconfigued by the
> -klog (00190) <16/05/12> ADV : BIOS. In this case, the mask is
> -klog (00191) <16/05/12> ADV : incorrectly set and the kernel has
> -klog (00192) <16/05/12> ADV : detected this and worked around the
> -klog (00193) <16/05/12> ADV : firmware bug.
> -klog (00194) <16/05/12> NLN :
> -klog (00195) <16/05/12> FAL C: FAILED [CRITICAL]
> -klog (00196) <16/05/12> FAL C: KlogBiosCpuMtrrMisconfigured: Test 1,
> -klog (00197) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000]
> -klog (00198) <16/05/12> FAL C: WARNING: BIOS bug: CPU MTRRs don't
> -klog (00199) <16/05/12> FAL C: cover all of memory, losing 1408MB of
> -klog (00200) <16/05/12> FAL C: RAM.
> -klog (00201) <16/05/12> NLN :
> -klog (00202) <16/05/12> ADV : ADVICE: The Memory Type Range
> -klog (00203) <16/05/12> ADV : Registers (MTRRs) which define memory
> -klog (00204) <16/05/12> ADV : caching policy are misconfigued by the
> -klog (00205) <16/05/12> ADV : BIOS and don't appear to cover all
> -klog (00206) <16/05/12> ADV : available physical memory. The kernel
> -klog (00207) <16/05/12> ADV : has detected this and has reduced the
> -klog (00208) <16/05/12> ADV : amount of memory available to be safe.
> -klog (00209) <16/05/12> ADV : Either check that the BIOS memory
> -klog (00210) <16/05/12> ADV : caching options are set correctly or
> -klog (00211) <16/05/12> ADV : contact your BIOS vendor to get this
> -klog (00212) <16/05/12> ADV : fixed.
> -klog (00213) <16/05/12> NLN :
> -klog (00214) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiUnknownAmlOpcode
> -klog (00215) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> -klog (00216) <16/05/12> FAL H: 0.022719] ACPI Error: Found unknown
> -klog (00217) <16/05/12> FAL H: opcode 0xFD at AML address f7ffe14c
> -klog (00218) <16/05/12> FAL H: offset 0xE8, ignoring (20110112
> -klog (00219) <16/05/12> FAL H: /psloop-141)
> -klog (00220) <16/05/12> NLN :
> -klog (00221) <16/05/12> ADV : ADVICE: ACPI execution run time error:
> -klog (00222) <16/05/12> ADV : The ACPI interpreter has reached an
> -klog (00223) <16/05/12> ADV : opcode that is unknown, this normally
> -klog (00224) <16/05/12> ADV : is a bug in the underlying AML code
> -klog (00225) <16/05/12> ADV : either because of badly written AML
> -klog (00226) <16/05/12> ADV : code or the compiler has produced code
> -klog (00227) <16/05/12> ADV : that is incorrect or the ACPI
> -klog (00228) <16/05/12> ADV : interpreter does not support this
> -klog (00229) <16/05/12> ADV : valid opcode.
> -klog (00230) <16/05/12> NLN :
> -klog (00231) <16/05/12> FAL C: FAILED [CRITICAL]
> -klog (00232) <16/05/12> FAL C: KlogAcpiDetectedUnsupportedOpCode:
> -klog (00233) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [
> -klog (00234) <16/05/12> FAL C: 0.025463] ACPI Warning: Detected an
> -klog (00235) <16/05/12> FAL C: unsupported executable opcode at
> -klog (00236) <16/05/12> FAL C: module-level: [0x007B] at table offset
> -klog (00237) <16/05/12> FAL C: 0x00C3 (20110112/psloop-526)
> -klog (00238) <16/05/12> NLN :
> -klog (00239) <16/05/12> ADV : ADVICE: An illegal AML opcode has been
> -klog (00240) <16/05/12> ADV : found and is ignored. This indicates
> -klog (00241) <16/05/12> ADV : either badly compiled code or opcode
> -klog (00242) <16/05/12> ADV : corruption in the DSDT or SSDT tables
> -klog (00243) <16/05/12> ADV : or a bug in the ACPI execution engine.
> -klog (00244) <16/05/12> ADV : Recommend disassembing using iasl to
> -klog (00245) <16/05/12> ADV : find any offending code.
> -klog (00246) <16/05/12> NLN :
> -klog (00247) <16/05/12> FAL H: FAILED [HIGH]
> -klog (00248) <16/05/12> FAL H: KlogAcpiParseExecAmlFailed: Test 1,
> -klog (00249) <16/05/12> FAL H: HIGH Kernel message: [ 0.034090] ACPI
> -klog (00250) <16/05/12> FAL H: Error: Method parse/execution failed
> -klog (00251) <16/05/12> FAL H: [_SB_.PCI0._OSC] (Node ee025630),
> -klog (00252) <16/05/12> FAL H: AE_ALREADY_EXISTS (20110112
> -klog (00253) <16/05/12> FAL H: /psparse-536)
> -klog (00254) <16/05/12> NLN :
> -klog (00255) <16/05/12> ADV : ADVICE: The ACPI driver encounter a
> -klog (00256) <16/05/12> ADV : parse or execution error on some ACPI
> -klog (00257) <16/05/12> ADV : AML code. This is unexepcted and
> -klog (00258) <16/05/12> ADV : normally indicates that there is a bug
> -klog (00259) <16/05/12> ADV : in the compiled AML code. It could be
> -klog (00260) <16/05/12> ADV : a programming fault or an AML compiler
> -klog (00261) <16/05/12> ADV : issue. See acpi_ps_parse_aml().
> +klog (00143) <16/05/12> ADV : ADVICE: This item in the FADT is the
> +klog (00144) <16/05/12> ADV : incorrect length. Should be corrected.
> +klog (00145) <16/05/12> NLN :
> +klog (00146) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00147) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
> +klog (00148) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> +klog (00149) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field
> +klog (00150) <16/05/12> FAL H: Gpe1Block has zero address or length:
> +klog (00151) <16/05/12> FAL H: 000000000000102C/0 20090521 tbfadt-558
> +klog (00152) <16/05/12> NLN :
> +klog (00153) <16/05/12> ADV : ADVICE: An ACPI table contains Generic
> +klog (00154) <16/05/12> ADV : Address Structure that has an address
> +klog (00155) <16/05/12> ADV : that is incorrectly set to zero, or a
> +klog (00156) <16/05/12> ADV : zero length. This needs to be fixed.
> +klog (00157) <16/05/12> NLN :
> +klog (00158) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00159) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
> +klog (00160) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> +klog (00161) <16/05/12> FAL H: 0.000000] ACPI Warning: Optional field
> +klog (00162) <16/05/12> FAL H: Pm2ControlBlock has zero address or
> +klog (00163) <16/05/12> FAL H: length: 0000000000000000/1 20090521
> +klog (00164) <16/05/12> FAL H: tbfadt-558
> +klog (00165) <16/05/12> NLN :
> +klog (00166) <16/05/12> ADV : ADVICE: An ACPI table contains Generic
> +klog (00167) <16/05/12> ADV : Address Structure that has an address
> +klog (00168) <16/05/12> ADV : that is incorrectly set to zero, or a
> +klog (00169) <16/05/12> ADV : zero length. This needs to be fixed.
> +klog (00170) <16/05/12> NLN :
> +klog (00171) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00172) <16/05/12> FAL H: KlogAcpiOptionalFieldZeroAddressOrLength
> +klog (00173) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> +klog (00174) <16/05/12> FAL H: 0.000000] ACPI Warning (tbfadt-0460):
> +klog (00175) <16/05/12> FAL H: Optional field "Gpe1Block" has zero
> +klog (00176) <16/05/12> FAL H: address or length: 000000000000102C/0
> +klog (00177) <16/05/12> FAL H: [20080926]
> +klog (00178) <16/05/12> NLN :
> +klog (00179) <16/05/12> ADV : ADVICE: An ACPI table contains Generic
> +klog (00180) <16/05/12> ADV : Address Structure that has an address
> +klog (00181) <16/05/12> ADV : that is incorrectly set to zero, or a
> +klog (00182) <16/05/12> ADV : zero length. This needs to be fixed.
> +klog (00183) <16/05/12> NLN :
> +klog (00184) <16/05/12> FAL M: FAILED [MEDIUM]
> +klog (00185) <16/05/12> FAL M: KlogBiosMtrrIncorrectMask: Test 1,
> +klog (00186) <16/05/12> FAL M: MEDIUM Kernel message: [ 0.000000]
> +klog (00187) <16/05/12> FAL M: mtrr: your BIOS has configured an
> +klog (00188) <16/05/12> FAL M: incorrect mask, fixing it.
> +klog (00189) <16/05/12> NLN :
> +klog (00190) <16/05/12> ADV : ADVICE: The Memory Type Range
> +klog (00191) <16/05/12> ADV : Registers (MTRRs) which define memory
> +klog (00192) <16/05/12> ADV : caching policy are misconfigued by the
> +klog (00193) <16/05/12> ADV : BIOS. In this case, the mask is
> +klog (00194) <16/05/12> ADV : incorrectly set and the kernel has
> +klog (00195) <16/05/12> ADV : detected this and worked around the
> +klog (00196) <16/05/12> ADV : firmware bug.
> +klog (00197) <16/05/12> NLN :
> +klog (00198) <16/05/12> FAL C: FAILED [CRITICAL]
> +klog (00199) <16/05/12> FAL C: KlogBiosCpuMtrrMisconfigured: Test 1,
> +klog (00200) <16/05/12> FAL C: CRITICAL Kernel message: [ 0.000000]
> +klog (00201) <16/05/12> FAL C: WARNING: BIOS bug: CPU MTRRs don't
> +klog (00202) <16/05/12> FAL C: cover all of memory, losing 1408MB of
> +klog (00203) <16/05/12> FAL C: RAM.
> +klog (00204) <16/05/12> NLN :
> +klog (00205) <16/05/12> ADV : ADVICE: The Memory Type Range
> +klog (00206) <16/05/12> ADV : Registers (MTRRs) which define memory
> +klog (00207) <16/05/12> ADV : caching policy are misconfigued by the
> +klog (00208) <16/05/12> ADV : BIOS and don't appear to cover all
> +klog (00209) <16/05/12> ADV : available physical memory. The kernel
> +klog (00210) <16/05/12> ADV : has detected this and has reduced the
> +klog (00211) <16/05/12> ADV : amount of memory available to be safe.
> +klog (00212) <16/05/12> ADV : Either check that the BIOS memory
> +klog (00213) <16/05/12> ADV : caching options are set correctly or
> +klog (00214) <16/05/12> ADV : contact your BIOS vendor to get this
> +klog (00215) <16/05/12> ADV : fixed.
> +klog (00216) <16/05/12> NLN :
> +klog (00217) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiUnknownAmlOpcode
> +klog (00218) <16/05/12> FAL H: : Test 1, HIGH Kernel message: [
> +klog (00219) <16/05/12> FAL H: 0.022719] ACPI Error: Found unknown
> +klog (00220) <16/05/12> FAL H: opcode 0xFD at AML address f7ffe14c
> +klog (00221) <16/05/12> FAL H: offset 0xE8, ignoring (20110112
> +klog (00222) <16/05/12> FAL H: /psloop-141)
> +klog (00223) <16/05/12> NLN :
> +klog (00224) <16/05/12> ADV : ADVICE: ACPI execution run time error:
> +klog (00225) <16/05/12> ADV : The ACPI interpreter has reached an
> +klog (00226) <16/05/12> ADV : opcode that is unknown, this normally
> +klog (00227) <16/05/12> ADV : is a bug in the underlying AML code
> +klog (00228) <16/05/12> ADV : either because of badly written AML
> +klog (00229) <16/05/12> ADV : code or the compiler has produced code
> +klog (00230) <16/05/12> ADV : that is incorrect or the ACPI
> +klog (00231) <16/05/12> ADV : interpreter does not support this
> +klog (00232) <16/05/12> ADV : valid opcode.
> +klog (00233) <16/05/12> NLN :
> +klog (00234) <16/05/12> FAL C: FAILED [CRITICAL]
> +klog (00235) <16/05/12> FAL C: KlogAcpiDetectedUnsupportedOpCode:
> +klog (00236) <16/05/12> FAL C: Test 1, CRITICAL Kernel message: [
> +klog (00237) <16/05/12> FAL C: 0.025463] ACPI Warning: Detected an
> +klog (00238) <16/05/12> FAL C: unsupported executable opcode at
> +klog (00239) <16/05/12> FAL C: module-level: [0x007B] at table offset
> +klog (00240) <16/05/12> FAL C: 0x00C3 (20110112/psloop-526)
> +klog (00241) <16/05/12> NLN :
> +klog (00242) <16/05/12> ADV : ADVICE: An illegal AML opcode has been
> +klog (00243) <16/05/12> ADV : found and is ignored. This indicates
> +klog (00244) <16/05/12> ADV : either badly compiled code or opcode
> +klog (00245) <16/05/12> ADV : corruption in the DSDT or SSDT tables
> +klog (00246) <16/05/12> ADV : or a bug in the ACPI execution engine.
> +klog (00247) <16/05/12> ADV : Recommend disassembing using iasl to
> +klog (00248) <16/05/12> ADV : find any offending code.
> +klog (00249) <16/05/12> NLN :
> +klog (00250) <16/05/12> FAL H: FAILED [HIGH]
> +klog (00251) <16/05/12> FAL H: KlogAcpiObjectAlreadyExists: Test 1,
> +klog (00252) <16/05/12> FAL H: HIGH Kernel message: [ 0.034090] ACPI
> +klog (00253) <16/05/12> FAL H: Error: Method parse/execution failed
> +klog (00254) <16/05/12> FAL H: [_SB_.PCI0._OSC] (Node ee025630),
> +klog (00255) <16/05/12> FAL H: AE_ALREADY_EXISTS (20110112
> +klog (00256) <16/05/12> FAL H: /psparse-536)
> +klog (00257) <16/05/12> NLN :
> +klog (00258) <16/05/12> ADV : ADVICE: This is a bug picked up by the
> +klog (00259) <16/05/12> ADV : kernel, but as yet, the firmware test
> +klog (00260) <16/05/12> ADV : suite has no diagnostic advice for
> +klog (00261) <16/05/12> ADV : this particular problem.
> klog (00262) <16/05/12> NLN :
> klog (00263) <16/05/12> FAL H: FAILED [HIGH] KlogAcpiFirmwareError:
> klog (00264) <16/05/12> FAL H: Test 1, HIGH Kernel message: [
> diff --git a/arg-log-format-0001/klog-0002.log b/arg-log-format-0001/klog-0002.log
> index 1be475c..55723ce 100644
> --- a/arg-log-format-0001/klog-0002.log
> +++ b/arg-log-format-0001/klog-0002.log
> @@ -149,16 +149,14 @@ klog : in the DSDT or SSDT tables or a bug in the ACPI execution
> klog : engine. Recommend disassembing using iasl to find any offending
> klog : code.
> klog :
> -klog : FAILED [HIGH] KlogAcpiParseExecAmlFailed: Test 1, HIGH Kernel
> +klog : FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1, HIGH Kernel
> klog : message: [ 0.034090] ACPI Error: Method parse/execution failed
> klog : [_SB_.PCI0._OSC] (Node ee025630), AE_ALREADY_EXISTS (20110112
> klog : /psparse-536)
> klog :
> -klog : ADVICE: The ACPI driver encounter a parse or execution error on
> -klog : some ACPI AML code. This is unexepcted and normally indicates
> -klog : that there is a bug in the compiled AML code. It could be a
> -klog : programming fault or an AML compiler issue. See
> -klog : acpi_ps_parse_aml().
> +klog : ADVICE: This is a bug picked up by the kernel, but as yet, the
> +klog : firmware test suite has no diagnostic advice for this
> +klog : particular problem.
> klog :
> klog : FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH Kernel
> klog : message: [ 0.040119] [Firmware Bug]: the BIOS has corrupted
> diff --git a/arg-log-format-0001/klog-0003.log b/arg-log-format-0001/klog-0003.log
> index 673a52b..496669d 100644
> --- a/arg-log-format-0001/klog-0003.log
> +++ b/arg-log-format-0001/klog-0003.log
> @@ -1,177 +1,175 @@
> -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] KlogAcpiMultipleApicMadtFound: 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] KlogAcpi32Bit64BitAddressMismatch: Test 1,
> -klog 00028: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X
> -klog 00029: address mismatch in Gpe0Block: 00008018/0000000000008028,
> -klog 00030: using 32 (20090903/tbfadt-427)
> -klog 00031:
> -klog 00032: ADVICE: The FADT table contains a mismatch between a 32
> -klog 00033: bit pointer and a 64 bit Generic Address pointer. Because
> -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] KlogAcpiValidRsdpNotFound: Test 1,
> -klog 00041: CRITICAL Kernel message: [ 0.000000] ACPI Error: A valid
> -klog 00042: RSDP was not found (20090903/tbxfroot-219)
> -klog 00043:
> -klog 00044: ADVICE: An ACPI compatible system must provide an RSDP
> -klog 00045: (Root System Description Pointer). This structure
> -klog 00046: provides the physical address of the RSDT and XSDT. Since
> -klog 00047: this could not be found, the ACPI driver has had to
> -klog 00048: disable ACPI support.
> -klog 00049:
> -klog 00050: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel
> -klog 00051: message: [ 0.000000] ACPI Warning: 32/64 FACS address
> -klog 00052: mismatch in FADT - two FACS tables! (20090903/tbfadt-369)
> -klog 00053:
> -klog 00054: ADVICE: The FADT table contains a mismatch between the 32
> -klog 00055: bit pointer (FIRMWARE_CTRL) and 64 bit pointer
> -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] KlogAcpi32Bit64BitAddressMismatchInFadt:
> -klog 00070: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32
> -klog 00071: /64X FACS address mismatch in FADT - DEF2DF40
> -klog 00072: /00000000DEF30D40, using 32 (20090903/tbfadt-486)
> -klog 00073:
> -klog 00074: ADVICE: The FADT table contains Generic Address Structure
> -klog 00075: that has a mismatch between the 32 bit and 64 bit
> -klog 00076: versions of an address. This should be fixed so there are
> -klog 00077: no mismatches.
> -klog 00078:
> -klog 00079: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt:
> -klog 00080: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32
> -klog 00081: /64X length mismatch in Gpe1Block: 0/32 20090521
> -klog 00082: tbfadt-527
> -klog 00083:
> -klog 00084: ADVICE: The FADT table contains Generic Address Structure
> -klog 00085: that has a mismatch between the 32 bit and 64 bit
> -klog 00086: versions of an address. This should be fixed so there are
> -klog 00087: no mismatches.
> -klog 00088:
> -klog 00089: FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel
> -klog 00090: message: [ 0.000000] ACPI Warning: BIOS XSDT has NULL
> -klog 00091: entry, using RSDT (20110112/tbutils-663)
> -klog 00092:
> -klog 00093: ADVICE: ACPI AML intepreter has found some non-conforming
> -klog 00094: AML code. This should be investigated and fixed.
> -klog 00095:
> -klog 00096: FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1, HIGH
> -klog 00097: Kernel message: [ 0.000000] ACPI Warning: Invalid length
> -klog 00098: for Pm1aControlBlock: 32, using default 16 (20090903
> -klog 00099: /tbfadt-607)
> -klog 00100:
> -klog 00101: ADVICE: This item in the FADT is the incorrect length.
> -klog 00102: Should be corrected.
> -klog 00103:
> -klog 00104: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
> -klog 00105: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning:
> -klog 00106: Optional field Gpe1Block has zero address or length:
> -klog 00107: 000000000000102C/0 20090521 tbfadt-558
> -klog 00108:
> -klog 00109: ADVICE: An ACPI table contains Generic Address Structure
> -klog 00110: that has an address that is incorrectly set to zero, or a
> -klog 00111: zero length. This needs to be fixed.
> -klog 00112:
> -klog 00113: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
> -klog 00114: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning:
> -klog 00115: Optional field Pm2ControlBlock has zero address or length
> -klog 00116: : 0000000000000000/1 20090521 tbfadt-558
> -klog 00117:
> -klog 00118: ADVICE: An ACPI table contains Generic Address Structure
> -klog 00119: that has an address that is incorrectly set to zero, or a
> -klog 00120: zero length. This needs to be fixed.
> -klog 00121:
> -klog 00122: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
> -klog 00123: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning
> -klog 00124: (tbfadt-0460): Optional field "Gpe1Block" has zero
> -klog 00125: address or length: 000000000000102C/0 [20080926]
> -klog 00126:
> -klog 00127: ADVICE: An ACPI table contains Generic Address Structure
> -klog 00128: that has an address that is incorrectly set to zero, or a
> -klog 00129: zero length. This needs to be fixed.
> -klog 00130:
> -klog 00131: FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1, MEDIUM
> -klog 00132: Kernel message: [ 0.000000] mtrr: your BIOS has
> -klog 00133: configured an incorrect mask, fixing it.
> -klog 00134:
> -klog 00135: ADVICE: The Memory Type Range Registers (MTRRs) which
> -klog 00136: define memory caching policy are misconfigued by the
> -klog 00137: BIOS. In this case, the mask is incorrectly set and the
> -klog 00138: kernel has detected this and worked around the firmware
> -klog 00139: bug.
> -klog 00140:
> -klog 00141: FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test 1,
> -klog 00142: CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug:
> -klog 00143: CPU MTRRs don't cover all of memory, losing 1408MB of
> -klog 00144: RAM.
> -klog 00145:
> -klog 00146: ADVICE: The Memory Type Range Registers (MTRRs) which
> -klog 00147: define memory caching policy are misconfigued by the BIOS
> -klog 00148: and don't appear to cover all available physical memory.
> -klog 00149: The kernel has detected this and has reduced the amount
> -klog 00150: of memory available to be safe. Either check that the
> -klog 00151: BIOS memory caching options are set correctly or contact
> -klog 00152: your BIOS vendor to get this fixed.
> -klog 00153:
> -klog 00154: FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH
> -klog 00155: Kernel message: [ 0.022719] ACPI Error: Found unknown
> -klog 00156: opcode 0xFD at AML address f7ffe14c offset 0xE8, ignoring
> -klog 00157: (20110112/psloop-141)
> -klog 00158:
> -klog 00159: ADVICE: ACPI execution run time error: The ACPI
> -klog 00160: interpreter has reached an opcode that is unknown, this
> -klog 00161: normally is a bug in the underlying AML code either
> -klog 00162: because of badly written AML code or the compiler has
> -klog 00163: produced code that is incorrect or the ACPI interpreter
> -klog 00164: does not support this valid opcode.
> -klog 00165:
> -klog 00166: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test
> -klog 00167: 1, CRITICAL Kernel message: [ 0.025463] ACPI Warning:
> -klog 00168: Detected an unsupported executable opcode at module-level
> -klog 00169: : [0x007B] at table offset 0x00C3 (20110112/psloop-526)
> -klog 00170:
> -klog 00171: ADVICE: An illegal AML opcode has been found and is
> -klog 00172: ignored. This indicates either badly compiled code or
> -klog 00173: opcode corruption in the DSDT or SSDT tables or a bug in
> -klog 00174: the ACPI execution engine. Recommend disassembing using
> -klog 00175: iasl to find any offending code.
> -klog 00176:
> -klog 00177: FAILED [HIGH] KlogAcpiParseExecAmlFailed: Test 1, HIGH
> -klog 00178: Kernel message: [ 0.034090] ACPI Error: Method parse
> -klog 00179: /execution failed [_SB_.PCI0._OSC] (Node ee025630),
> -klog 00180: AE_ALREADY_EXISTS (20110112/psparse-536)
> -klog 00181:
> -klog 00182: ADVICE: The ACPI driver encounter a parse or execution
> -klog 00183: error on some ACPI AML code. This is unexepcted and
> -klog 00184: normally indicates that there is a bug in the compiled
> -klog 00185: AML code. It could be a programming fault or an AML
> -klog 00186: compiler issue. See acpi_ps_parse_aml().
> +klog 00015: Scan kernel log for errors and warnings.
> +klog 00016: ---------------------------------------------------------
> +klog 00017: Test 1 of 1: Kernel log error check.
> +klog 00018: FAILED [HIGH] KlogAcpiMultipleApicMadtFound: Test 1, HIGH
> +klog 00019: Kernel message: [ 0.000000] ACPI: BIOS bug: multiple APIC
> +klog 00020: /MADT found, using 0
> +klog 00021:
> +klog 00022: ADVICE: The kernel has detected more than one ACPI
> +klog 00023: Multiple APIC Description Table (MADT) (these tables have
> +klog 00024: the "APIC" signature). There should only be one MADT and
> +klog 00025: the kernel will by default select the first one. However,
> +klog 00026: one can override this and select the Nth MADT using
> +klog 00027: acpi_apic_instance=N.
> +klog 00028:
> +klog 00029: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatch: Test 1,
> +klog 00030: HIGH Kernel message: [ 0.000000] ACPI Error: 32/64X
> +klog 00031: address mismatch in Gpe0Block: 00008018/0000000000008028,
> +klog 00032: using 32 (20090903/tbfadt-427)
> +klog 00033:
> +klog 00034: ADVICE: The FADT table contains a mismatch between a 32
> +klog 00035: bit pointer and a 64 bit Generic Address pointer. Because
> +klog 00036: these pointers are different, it suggests either one of
> +klog 00037: them is incorrect. If a non-null 32 bit pointer exists,
> +klog 00038: then the kernel will opt for this in preference to the 64
> +klog 00039: bit pointer even though this is not in accordance to the
> +klog 00040: ACPI specification.
> +klog 00041:
> +klog 00042: FAILED [CRITICAL] KlogAcpiValidRsdpNotFound: Test 1,
> +klog 00043: CRITICAL Kernel message: [ 0.000000] ACPI Error: A valid
> +klog 00044: RSDP was not found (20090903/tbxfroot-219)
> +klog 00045:
> +klog 00046: ADVICE: An ACPI compatible system must provide an RSDP
> +klog 00047: (Root System Description Pointer). This structure
> +klog 00048: provides the physical address of the RSDT and XSDT. Since
> +klog 00049: this could not be found, the ACPI driver has had to
> +klog 00050: disable ACPI support.
> +klog 00051:
> +klog 00052: FAILED [HIGH] KlogAcpiTwoFacs: Test 1, HIGH Kernel
> +klog 00053: message: [ 0.000000] ACPI Warning: 32/64 FACS address
> +klog 00054: mismatch in FADT - two FACS tables! (20090903/tbfadt-369)
> +klog 00055:
> +klog 00056: ADVICE: The FADT table contains a mismatch between the 32
> +klog 00057: bit pointer (FIRMWARE_CTRL) and 64 bit pointer
> +klog 00058: (X_FIRMWARE_CTRL) pointer to the FACS table. Section
> +klog 00059: 5.2.9 of version 4.0a of the ACPI specification states
> +klog 00060: that X_FIRMWARE_CTRL should be zero if FIRMWARE_CTRL is
> +klog 00061: defined, or FIRMWARE_CTRL should be zero if
> +klog 00062: X_FIRMWARE_CTRL is zero. With two different pointers
> +klog 00063: defined, the kernel has to make a choice, and opts for
> +klog 00064: the 32 bit pointer. Because these pointers are different,
> +klog 00065: it suggests either one of them is incorrect, or different
> +klog 00066: 32 bit and 64 bit FACS tables are present in your system,
> +klog 00067: which is NOT complaint with the ACPI specification. The
> +klog 00068: kernel has to make a choice and opts for the 32 bit
> +klog 00069: FIRMWARE_CTRL.
> +klog 00070:
> +klog 00071: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt:
> +klog 00072: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32
> +klog 00073: /64X FACS address mismatch in FADT - DEF2DF40
> +klog 00074: /00000000DEF30D40, using 32 (20090903/tbfadt-486)
> +klog 00075:
> +klog 00076: ADVICE: The FADT table contains Generic Address Structure
> +klog 00077: that has a mismatch between the 32 bit and 64 bit
> +klog 00078: versions of an address. This should be fixed so there are
> +klog 00079: no mismatches.
> +klog 00080:
> +klog 00081: FAILED [HIGH] KlogAcpi32Bit64BitAddressMismatchInFadt:
> +klog 00082: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning: 32
> +klog 00083: /64X length mismatch in Gpe1Block: 0/32 20090521
> +klog 00084: tbfadt-527
> +klog 00085:
> +klog 00086: ADVICE: The FADT table contains Generic Address Structure
> +klog 00087: that has a mismatch between the 32 bit and 64 bit
> +klog 00088: versions of an address. This should be fixed so there are
> +klog 00089: no mismatches.
> +klog 00090:
> +klog 00091: FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel
> +klog 00092: message: [ 0.000000] ACPI Warning: BIOS XSDT has NULL
> +klog 00093: entry, using RSDT (20110112/tbutils-663)
> +klog 00094:
> +klog 00095: ADVICE: ACPI AML intepreter has found some non-conforming
> +klog 00096: AML code. This should be investigated and fixed.
> +klog 00097:
> +klog 00098: FAILED [HIGH] KlogAcpiFadtInvalidLength: Test 1, HIGH
> +klog 00099: Kernel message: [ 0.000000] ACPI Warning: Invalid length
> +klog 00100: for Pm1aControlBlock: 32, using default 16 (20090903
> +klog 00101: /tbfadt-607)
> +klog 00102:
> +klog 00103: ADVICE: This item in the FADT is the incorrect length.
> +klog 00104: Should be corrected.
> +klog 00105:
> +klog 00106: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
> +klog 00107: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning:
> +klog 00108: Optional field Gpe1Block has zero address or length:
> +klog 00109: 000000000000102C/0 20090521 tbfadt-558
> +klog 00110:
> +klog 00111: ADVICE: An ACPI table contains Generic Address Structure
> +klog 00112: that has an address that is incorrectly set to zero, or a
> +klog 00113: zero length. This needs to be fixed.
> +klog 00114:
> +klog 00115: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
> +klog 00116: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning:
> +klog 00117: Optional field Pm2ControlBlock has zero address or length
> +klog 00118: : 0000000000000000/1 20090521 tbfadt-558
> +klog 00119:
> +klog 00120: ADVICE: An ACPI table contains Generic Address Structure
> +klog 00121: that has an address that is incorrectly set to zero, or a
> +klog 00122: zero length. This needs to be fixed.
> +klog 00123:
> +klog 00124: FAILED [HIGH] KlogAcpiOptionalFieldZeroAddressOrLength:
> +klog 00125: Test 1, HIGH Kernel message: [ 0.000000] ACPI Warning
> +klog 00126: (tbfadt-0460): Optional field "Gpe1Block" has zero
> +klog 00127: address or length: 000000000000102C/0 [20080926]
> +klog 00128:
> +klog 00129: ADVICE: An ACPI table contains Generic Address Structure
> +klog 00130: that has an address that is incorrectly set to zero, or a
> +klog 00131: zero length. This needs to be fixed.
> +klog 00132:
> +klog 00133: FAILED [MEDIUM] KlogBiosMtrrIncorrectMask: Test 1, MEDIUM
> +klog 00134: Kernel message: [ 0.000000] mtrr: your BIOS has
> +klog 00135: configured an incorrect mask, fixing it.
> +klog 00136:
> +klog 00137: ADVICE: The Memory Type Range Registers (MTRRs) which
> +klog 00138: define memory caching policy are misconfigued by the
> +klog 00139: BIOS. In this case, the mask is incorrectly set and the
> +klog 00140: kernel has detected this and worked around the firmware
> +klog 00141: bug.
> +klog 00142:
> +klog 00143: FAILED [CRITICAL] KlogBiosCpuMtrrMisconfigured: Test 1,
> +klog 00144: CRITICAL Kernel message: [ 0.000000] WARNING: BIOS bug:
> +klog 00145: CPU MTRRs don't cover all of memory, losing 1408MB of
> +klog 00146: RAM.
> +klog 00147:
> +klog 00148: ADVICE: The Memory Type Range Registers (MTRRs) which
> +klog 00149: define memory caching policy are misconfigued by the BIOS
> +klog 00150: and don't appear to cover all available physical memory.
> +klog 00151: The kernel has detected this and has reduced the amount
> +klog 00152: of memory available to be safe. Either check that the
> +klog 00153: BIOS memory caching options are set correctly or contact
> +klog 00154: your BIOS vendor to get this fixed.
> +klog 00155:
> +klog 00156: FAILED [HIGH] KlogAcpiUnknownAmlOpcode: Test 1, HIGH
> +klog 00157: Kernel message: [ 0.022719] ACPI Error: Found unknown
> +klog 00158: opcode 0xFD at AML address f7ffe14c offset 0xE8, ignoring
> +klog 00159: (20110112/psloop-141)
> +klog 00160:
> +klog 00161: ADVICE: ACPI execution run time error: The ACPI
> +klog 00162: interpreter has reached an opcode that is unknown, this
> +klog 00163: normally is a bug in the underlying AML code either
> +klog 00164: because of badly written AML code or the compiler has
> +klog 00165: produced code that is incorrect or the ACPI interpreter
> +klog 00166: does not support this valid opcode.
> +klog 00167:
> +klog 00168: FAILED [CRITICAL] KlogAcpiDetectedUnsupportedOpCode: Test
> +klog 00169: 1, CRITICAL Kernel message: [ 0.025463] ACPI Warning:
> +klog 00170: Detected an unsupported executable opcode at module-level
> +klog 00171: : [0x007B] at table offset 0x00C3 (20110112/psloop-526)
> +klog 00172:
> +klog 00173: ADVICE: An illegal AML opcode has been found and is
> +klog 00174: ignored. This indicates either badly compiled code or
> +klog 00175: opcode corruption in the DSDT or SSDT tables or a bug in
> +klog 00176: the ACPI execution engine. Recommend disassembing using
> +klog 00177: iasl to find any offending code.
> +klog 00178:
> +klog 00179: FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1, HIGH
> +klog 00180: Kernel message: [ 0.034090] ACPI Error: Method parse
> +klog 00181: /execution failed [_SB_.PCI0._OSC] (Node ee025630),
> +klog 00182: AE_ALREADY_EXISTS (20110112/psparse-536)
> +klog 00183:
> +klog 00184: ADVICE: This is a bug picked up by the kernel, but as yet
> +klog 00185: , the firmware test suite has no diagnostic advice for
> +klog 00186: this particular problem.
> klog 00187:
> klog 00188: FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH Kernel
> klog 00189: message: [ 0.040119] [Firmware Bug]: the BIOS has
> diff --git a/arg-log-format-0001/klog-0004.log b/arg-log-format-0001/klog-0004.log
> index 149409b..7f3048f 100644
> --- a/arg-log-format-0001/klog-0004.log
> +++ b/arg-log-format-0001/klog-0004.log
> @@ -176,17 +176,14 @@ klog 10/10/11 : or opcode corruption in the DSDT or SSDT tables or a
> klog 10/10/11 : bug in the ACPI execution engine. Recommend
> klog 10/10/11 : disassembing using iasl to find any offending code.
> klog 10/10/11 :
> -klog 10/10/11 H: FAILED [HIGH] KlogAcpiParseExecAmlFailed: Test 1,
> +klog 10/10/11 H: FAILED [HIGH] KlogAcpiObjectAlreadyExists: Test 1,
> klog 10/10/11 H: HIGH Kernel message: [ 0.034090] ACPI Error: Method
> klog 10/10/11 H: parse/execution failed [_SB_.PCI0._OSC] (Node
> klog 10/10/11 H: ee025630), AE_ALREADY_EXISTS (20110112/psparse-536)
> klog 10/10/11 :
> -klog 10/10/11 : ADVICE: The ACPI driver encounter a parse or
> -klog 10/10/11 : execution error on some ACPI AML code. This is
> -klog 10/10/11 : unexepcted and normally indicates that there is a
> -klog 10/10/11 : bug in the compiled AML code. It could be a
> -klog 10/10/11 : programming fault or an AML compiler issue. See
> -klog 10/10/11 : acpi_ps_parse_aml().
> +klog 10/10/11 : ADVICE: This is a bug picked up by the kernel, but
> +klog 10/10/11 : as yet, the firmware test suite has no diagnostic
> +klog 10/10/11 : advice for this particular problem.
> klog 10/10/11 :
> klog 10/10/11 H: FAILED [HIGH] KlogAcpiFirmwareError: Test 1, HIGH
> klog 10/10/11 H: Kernel message: [ 0.040119] [Firmware Bug]: the BIOS
>
Acked-by: Ivan Hu <ivan.hu at canonical.com>
More information about the fwts-devel
mailing list