help review the fwts-test failure

Keng-Yu Lin kengyu at canonical.com
Fri Apr 20 03:17:55 UTC 2012


Hi all:
  We have more failures from fwts-test this time likely due to the new
version of ACPICA.

  I made some obvious ones fixed but still got some left. This may
need more time investigating.

  It will be great if you can spot any cause of the failures please
reply with a comment will be very appreciated.

  --- Below is the failure.log ---

TEST: acpidump-0001, subtest test-0001.sh

TEST: acpitables-0001, subtest test-0001.sh

TEST: acpitables-0002, subtest test-0001.sh

TEST: acpitables-0002, subtest test-0002.sh

TEST: acpitables-0003, subtest test-0001.sh

TEST: acpitables-0004, subtest test-0001.sh

TEST: acpitables-0005, subtest test-0001.sh

TEST: acpitables-0006, subtest test-0001.sh

TEST: acpitables-0007, subtest test-0001.sh

TEST: acpitables-0008, subtest test-0001.sh
10c10,22
< acpitables      PASSED: Test 1, Table RSDP passed.
---
> acpitables      FAILED [MEDIUM] RSDPBadOEMId: Test 1, RSDP: oem_id does
> acpitables      not contain any alpha numeric characters.
> acpitables
> acpitables      ADVICE: The RSDP OEM Id is non-conforming, but this will
> acpitables      not affect the system behaviour. However this should be
> acpitables      fixed if possible to make the firmware ACPI complaint.
> acpitables
> acpitables      FAILED [MEDIUM] RSDPBadRevisionId: Test 1, RSDP: revision
> acpitables      is 3, expected value less than 2.
> acpitables
> acpitables      ADVICE: A RSDP revision number greater than 2 probably
> acpitables      won't cause any system problems.
> acpitables
15c27
< acpitables      3 passed, 0 failed, 0 warnings, 0 aborted, 0 skipped, 0
---
> acpitables      2 passed, 2 failed, 0 warnings, 0 aborted, 0 skipped, 0

TEST: apicinstance-0001, subtest test-0001.sh

TEST: apicinstance-0001, subtest test-0002.sh

TEST: arg-help-0001, subtest test-0001.sh

TEST: arg-help-0001, subtest test-0002.sh

TEST: arg-json-0001, subtest test-0001.sh

TEST: arg-json-0001, subtest test-0002.sh

TEST: arg-json-0001, subtest test-0003.sh

TEST: arg-json-0001, subtest test-0004.sh

TEST: arg-klog-0001, subtest test-0001.sh

TEST: arg-klog-0001, subtest test-0002.sh

TEST: arg-log-fields-0001, subtest test-0001.sh

TEST: arg-log-format-0001, subtest test-0001.sh

TEST: arg-log-format-0001, subtest test-0002.sh

TEST: arg-log-format-0001, subtest test-0003.sh

TEST: arg-log-format-0001, subtest test-0004.sh

TEST: arg-quiet-0001, subtest test-0001.sh

TEST: arg-quiet-0001, subtest test-0002.sh

TEST: arg-results-0001, subtest test-0001.sh

TEST: arg-results-0001, subtest test-0002.sh

TEST: arg-results-0001, subtest test-0003.sh

TEST: arg-results-0001, subtest test-0004.sh

TEST: arg-results-0001, subtest test-0005.sh

TEST: arg-results-0001, subtest test-0006.sh

TEST: arg-results-no-separators-0001, subtest test-0001.sh

TEST: arg-show-progress-dialog-0001, subtest test-0001.sh

TEST: arg-show-progress-dialog-0001, subtest test-0002.sh

TEST: arg-show-tests-0001, subtest test-0001.sh

TEST: arg-show-tests-0001, subtest test-0002.sh

TEST: arg-show-tests-full-0001, subtest test-0001.sh

TEST: arg-table-path-0001, subtest test-0001.sh

TEST: arg-table-path-0001, subtest test-0002.sh

TEST: arg-width-0001, subtest test-0001.sh

TEST: arg-width-0001, subtest test-0002.sh

TEST: arg-width-0001, subtest test-0003.sh

TEST: arg-width-0001, subtest test-0004.sh

TEST: arg-width-0001, subtest test-0005.sh

TEST: arg-width-0001, subtest test-0006.sh

TEST: arg-width-0001, subtest test-0007.sh

TEST: arg-width-0001, subtest test-0008.sh

TEST: checksum-0001, subtest test-0001.sh
20,21c20
< checksum        PASSED: Test 1, Table RSDT has correct checksum 0xd.
< checksum        PASSED: Test 1, Table RSDP has correct checksum 0x93.
---
> checksum        PASSED: Test 1, Table RSDP has correct checksum 0xc5.
23c22,23
< checksum        0xf8.
---
> checksum        0x39.
> checksum        PASSED: Test 1, Table RSDT has correct checksum 0x48.

TEST: checksum-0001, subtest test-0002.sh
20,23c20,34
< checksum        PASSED: Test 1, Table RSDT has correct checksum 0xd.
< checksum        PASSED: Test 1, Table RSDP has correct checksum 0x2f.
< checksum        PASSED: Test 1, Table RSDP has correct extended checksum
< checksum        0xba.
---
> checksum        FAILED [CRITICAL] ACPITableChecksumRSDP: Test 1, RSDP has
> checksum        incorrect checksum, expected 0xc5, got 0xff.
> checksum
> checksum        ADVICE: The kernel will not load the RSDP with an invalid
> checksum        checksum and hence all other ACPI tables will also fail to
> checksum        load.
> checksum
> checksum        FAILED [CRITICAL] ACPITableChecksumRSDP: Test 1, RSDP has
> checksum        incorrect extended checksum, expected 0xff, got 0x39.
> checksum
> checksum        ADVICE: The kernel will not load the RSDP with an invalid
> checksum        extended checksum and hence all other ACPI tables will
> checksum        also fail to load.
> checksum
> checksum        PASSED: Test 1, Table RSDT has correct checksum 0x48.
26c37
< checksum        19 passed, 0 failed, 0 warnings, 0 aborted, 0 skipped, 0
---
> checksum        17 passed, 2 failed, 0 warnings, 0 aborted, 0 skipped, 0

TEST: checksum-0001, subtest test-0003.sh
27,28c27
< checksum        PASSED: Test 1, Table RSDT has correct checksum 0xd.
< checksum        PASSED: Test 1, Table RSDP has correct checksum 0x3d.
---
> checksum        PASSED: Test 1, Table RSDP has correct checksum 0xc5.
30c29,30
< checksum        0x2c.
---
> checksum        0x39.
> checksum        PASSED: Test 1, Table RSDT has correct checksum 0x48.

TEST: checksum-0001, subtest test-0004.sh
124,125c124
< checksum        PASSED: Test 1, Table RSDT has correct checksum 0xd.
< checksum        PASSED: Test 1, Table RSDP has correct checksum 0x32.
---
> checksum        PASSED: Test 1, Table RSDP has correct checksum 0xc5.
127c126,127
< checksum        0x85.
---
> checksum        0x39.
> checksum        PASSED: Test 1, Table RSDT has correct checksum 0x48.

TEST: disassemble-0001, subtest test-0001.sh

TEST: dmesg_common-0001, subtest test-0001.sh

TEST: dmesg_common-0001, subtest test-0002.sh

TEST: dmesg_common-0001, subtest test-0003.sh

TEST: klog-0001, subtest test-0001.sh

TEST: klog-0001, subtest test-0002.sh

TEST: klog-0001, subtest test-0003.sh

TEST: method-0001, subtest test-0001.sh
3d2
< method          Failed to install global event handler.
139,160c138,139
< method          FAILED [MEDIUM] MethodBadTemp: Test 27, AC0 returned a
< method          dubious value below 0 degrees C: 0x00000000 ( 0.0 degrees
< method          K)
< method
< method          ADVICE: An incorrect value could be because the method
< method          requires interaction with I/O ports or the embedded
< method          controller and this test frame work is spoofing these
< method          operations. However, it is worth sanity checking these
< method          values in /sys/class/thermal/thermal_zone*.
< method
< method          PASSED: Test 27, \_SB_.PCI0.LPCB.EC0_.BAC0 correctly
< method          acquired and released locks 6 times.
< method
< method          FAILED [MEDIUM] MethodBadTemp: Test 27, AC1 returned a
< method          dubious value below 0 degrees C: 0x00000000 ( 0.0 degrees
< method          K)
< method
< method          ADVICE: An incorrect value could be because the method
< method          requires interaction with I/O ports or the embedded
< method          controller and this test frame work is spoofing these
< method          operations. However, it is worth sanity checking these
< method          values in /sys/class/thermal/thermal_zone*.
---
> method          SKIPPED: Test 27, Skipping test for non-existant object
> method          AC0.
162,163c141,142
< method          PASSED: Test 27, \_SB_.PCI0.LPCB.EC0_.BAC1 correctly
< method          acquired and released locks 6 times.
---
> method          SKIPPED: Test 27, Skipping test for non-existant object
> method          AC1.
1176c1155
< method          312 passed, 2 failed, 5 warnings, 0 aborted, 75 skipped, 0
---
> method          166 passed, 0 failed, 5 warnings, 0 aborted, 79 skipped, 0

TEST: oops-0001, subtest test-0001.sh

TEST: oops-0001, subtest test-0002.sh

TEST: oops-0001, subtest test-0003.sh

TEST: osilinux-0001, subtest test-0001.sh

TEST: osilinux-0001, subtest test-0002.sh

TEST: syntaxcheck-0001, subtest test-0001.sh
4,5c4,50
< syntaxcheck     PASSED: Test 1, DSDT (0) reassembly, Found 0 errors, 0
< syntaxcheck     warnings.
---
> syntaxcheck     FAILED [HIGH] AMLAssemblerError4122: Test 1, Assembler
> syntaxcheck     error in line 1070
> syntaxcheck     Line | AML source
> syntaxcheck     ---------------------------------------------------------
> syntaxcheck     01067|                     0x00000000,         // Range Minimum
> syntaxcheck     01068|                     0xDFFFFFFF,         // Range Maximum
> syntaxcheck     01069|                     0x00000000,         // Translation Offset
> syntaxcheck     01070|                     0x00000000,         // Length
> syntaxcheck          |                              ^
> syntaxcheck          | error 4122: Invalid combination of Length and Min/Max fixed flags
> syntaxcheck     01071|                     ,, _Y0D, AddressRangeMemory, TypeStatic)
> syntaxcheck     01072|                 DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite,
> syntaxcheck     01073|                     0x00000000,         // Granularity
> syntaxcheck     =========================================================
> syntaxcheck
> syntaxcheck     ADVICE: (for error #4122): This occurs if the length is
> syntaxcheck     zero and just one of the resource MIF/MAF flags are set,
> syntaxcheck     or the length is non-zero and resource MIF/MAF flags are
> syntaxcheck     both set. These are illegal combinations and need to be
> syntaxcheck     fixed. See section 6.4.3.5 Address Space Resource
> syntaxcheck     Descriptors of version 4.0a of the ACPI specification for
> syntaxcheck     more details.
> syntaxcheck
> syntaxcheck     FAILED [HIGH] AMLAssemblerError4122: Test 1, Assembler
> syntaxcheck     error in line 1084
> syntaxcheck     Line | AML source
> syntaxcheck     ---------------------------------------------------------
> syntaxcheck     01081|                     0xFED40000,         // Range Minimum
> syntaxcheck     01082|                     0xFED44FFF,         // Range Maximum
> syntaxcheck     01083|                     0x00000000,         // Translation Offset
> syntaxcheck     01084|                     0x00000000,         // Length
> syntaxcheck          |                              ^
> syntaxcheck          | error 4122: Invalid combination of Length and Min/Max fixed flags
> syntaxcheck     01085|                     ,, , AddressRangeMemory, TypeStatic)
> syntaxcheck     01086|             })
> syntaxcheck     01087|             Method (_CRS, 0, Serialized)
> syntaxcheck     =========================================================
> syntaxcheck
> syntaxcheck     ADVICE: (for error #4122): This occurs if the length is
> syntaxcheck     zero and just one of the resource MIF/MAF flags are set,
> syntaxcheck     or the length is non-zero and resource MIF/MAF flags are
> syntaxcheck     both set. These are illegal combinations and need to be
> syntaxcheck     fixed. See section 6.4.3.5 Address Space Resource
> syntaxcheck     Descriptors of version 4.0a of the ACPI specification for
> syntaxcheck     more details.
> syntaxcheck
> syntaxcheck     Table DSDT (0) reassembly: Found 2 errors, 0 warnings.
20c65
< syntaxcheck     6 passed, 0 failed, 0 warnings, 0 aborted, 0 skipped, 0
---
> syntaxcheck     5 passed, 2 failed, 0 warnings, 0 aborted, 0 skipped, 0

TEST: wmi-0001, subtest test-0001.sh
6,24c6,14
< wmi             Found WMI Event, Notifier ID: 0x01, GUID:
< wmi             2E851DA7-D053-9D5F-FA1A-4AD62E6A4143, Instance 0x3b
< wmi             FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID
< wmi             2E851DA7-D053-9D5F-FA1A-4AD62E6A4143 is unknown to the
< wmi             kernel, a driver may need to be implemented for this GUID.
< wmi
< wmi             ADVICE: A WMI driver probably needs to be written for this
< wmi             event.
< wmi             It can checked for using:
< wmi             wmi_has_guid("2E851DA7-D053-9D5F-FA1A-4AD62E6A4143").
< wmi             One can install a notify handler using
< wmi
wmi_install_notify_handler("2E851DA7-D053-9D5F-FA1A-4AD62E6A4143"
< wmi             , handler, NULL).
< wmi             http://lwn.net/Articles/391230 describes how to write an
< wmi             appropriate driver.
< wmi
< wmi             Found WMI Method WM \90 with GUID:
< wmi             72FBDD43-BC4C-43B8-FE0D-64F942430121, Instance 0x05
< wmi             Found WMI Object, Object ID
---
> wmi             Found WMI Object, Object ID AC, GUID:
> wmi             2E851DA7-D053-495F-9DFA-1A4AD62E6A86, Instance 0x01, Flags
> wmi             : 00
> wmi             Found WMI Object, Object ID BC, GUID:
> wmi             71436D3B-FBDD-4C72-BCB8-435BFE0D64F9, Instance 0x01, Flags
> wmi             : 00
> wmi             Found WMI Object, Object ID BA, GUID:
> wmi             05901221-D566-11D1-B2F0-00A0C9062910, Instance 0x01, Flags
> wmi             : 00
30c20
< wmi             0 passed, 1 failed, 0 warnings, 0 aborted, 0 skipped, 1
---
> wmi             0 passed, 0 failed, 0 warnings, 0 aborted, 0 skipped, 2

TEST: wmi-0001, subtest test-0002.sh
6,13c6,19
< wmi             Found WMI Method WM
< wmi             Found WMI Method WMY\BB with GUID:
< wmi             DAA99705-B011-B612-A1EF-549242410194, Instance 0x9d
< wmi             Found WMI Object, Object ID \88 , GUID:
< wmi             12B0DAA9-22B6-EFA1-54D0-000108E06C77, Instance 0xdb, Flags
< wmi             : 11 WMI_EXPENSIVE
< wmi             Found WMI Object, Object ID Ѳ, GUID:
< wmi             20088BA9-9A0C-4266-4301-2112900566D5, Instance 0xf0, Flags
---
> wmi             Found WMI Object, Object ID AA, GUID:
> wmi             8D9DDCBC-A997-11DA-B012-B622A1EF5492, Instance 0x01, Flags
> wmi             : 00
> wmi             Found WMI Method WMBA with GUID:
> wmi             A80593CE-A997-11DA-B012-B622A1EF5492, Instance 0x01
> wmi             Found WMI Event, Notifier ID: 0xd0, GUID:
> wmi             9DBB5994-A997-11DA-B012-B622A1EF5492, Instance 0x01
> wmi             PASSED: Test 1, GUID 9DBB5994-A997-11DA-B012-B622A1EF5492
> wmi             is handled by driver dell-wmi (Vendor: Dell).
> wmi             Found WMI Object, Object ID BC, GUID:
> wmi             A3776CE0-1E88-11DB-A98B-0800200C9A66, Instance 0x01, Flags
> wmi             : 00
> wmi             Found WMI Object, Object ID MO, GUID:
> wmi             05901221-D566-11D1-B2F0-00A0C9062910, Instance 0x01, Flags
15d20
< wmi             Found WMI Object, Object ID
21c26
< wmi             0 passed, 0 failed, 0 warnings, 0 aborted, 0 skipped, 2
---
> wmi             1 passed, 0 failed, 0 warnings, 0 aborted, 0 skipped, 1

TEST: wmi-0001, subtest test-0003.sh
6,13c6,31
< wmi             Found WMI Method WM
< wmi             Found WMI Method WMY\FF with GUID:
< wmi             DAA99705-B011-B612-A1EF-549242410194, Instance 0x9d
< wmi             Found WMI Object, Object ID \88 , GUID:
< wmi             12B0DAA9-22B6-EFA1-54D0-000108E06C77, Instance 0xdb, Flags
< wmi             : 11 WMI_EXPENSIVE
< wmi             Found WMI Object, Object ID Ѳ, GUID:
< wmi             20088BA9-9A0C-4266-4301-2112900566D5, Instance 0xf0, Flags
---
> wmi             Found WMI Object, Object ID AA, GUID:
> wmi             8D9DDCBC-A997-11DA-B012-B622A1EF5492, Instance 0x01, Flags
> wmi             : 00
> wmi             Found WMI Method WMBA with GUID:
> wmi             A80593CE-A997-11DA-B012-B622A1EF5492, Instance 0x01
> wmi             Found WMI Event, Notifier ID: 0xd0, GUID:
> wmi             9DFF5994-A997-11DA-B012-B622A1EF5492, Instance 0x01
> wmi             FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID
> wmi             9DFF5994-A997-11DA-B012-B622A1EF5492 is unknown to the
> wmi             kernel, a driver may need to be implemented for this GUID.
> wmi
> wmi             ADVICE: A WMI driver probably needs to be written for this
> wmi             event.
> wmi             It can checked for using:
> wmi             wmi_has_guid("9DFF5994-A997-11DA-B012-B622A1EF5492").
> wmi             One can install a notify handler using
> wmi             wmi_install_notify_handler("9DFF5994-A997-11DA-B012-B622A1EF5492"
> wmi             , handler, NULL).
> wmi             http://lwn.net/Articles/391230 describes how to write an
> wmi             appropriate driver.
> wmi
> wmi             Found WMI Object, Object ID BC, GUID:
> wmi             A3776CE0-1E88-11DB-A98B-0800200C9A66, Instance 0x01, Flags
> wmi             : 00
> wmi             Found WMI Object, Object ID MO, GUID:
> wmi             05901221-D566-11D1-B2F0-00A0C9062910, Instance 0x01, Flags
15d32
< wmi             Found WMI Object, Object ID
21c38
< wmi             0 passed, 0 failed, 0 warnings, 0 aborted, 0 skipped, 2
---
> wmi             0 passed, 1 failed, 0 warnings, 0 aborted, 0 skipped, 1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: failure.log
Type: application/octet-stream
Size: 16964 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20120420/5cb05469/attachment.obj>


More information about the fwts-devel mailing list