DMIInvalidHardwareEntry - Unmatched Chassis Type

[Brendan Donegan]

We're encountering this error when running fwts on a variety of different servers - only the numbers vary:

== HP Proliant ML110 G5 ==

FAILED [HIGH] DMIInvalidHardwareEntry: Test 1, Unmatched Chassis Type SMBIOS Type 3 reports 11 ACPI
FACP reports 0

== HP DL385 G7 ==

FAILED [HIGH] DMIInvalidHardwareEntry: Test 1, Unmatched Chassis Type SMBIOS Type 3 reports 17 ACPI
FACP reports 0

== Intel Server System SR1600UR ==

FAILED [HIGH] DMIInvalidHardwareEntry: Test 1, Unmatched Chassis Type SMBIOS Type 3 reports 17 ACPI
FACP reports 4

== Lenevo ThinkServer RD240 ==

FAILED [HIGH] DMIInvalidHardwareEntry: Test 1, Unmatched Chassis Type SMBIOS Type 3 reports 11 ACPI
FACP reports 1

[Colin Ian King (colin-king)]

OK, I'm just adding a little more context to this bug report. We're seeing these errors quite frequently on a range of machines.

Case 1:
FAILED [HIGH] DMIInvalidHardwareEntry: Test 1, Unmatched Chassis Type SMBIOS Type 3 reports 11 ACPI
FACP reports 0

--> SMBIOS thinks it's a "Main Server Chassis" device, The ACPI FACP states it's "unknown"

..so I think for this, since it's "unknown" in the FACP, this is probably a false positive from fwts. We need to fix this case.

Case 2:
FAILED [HIGH] DMIInvalidHardwareEntry: Test 1, Unmatched Chassis Type SMBIOS Type 3 reports 17 ACPI
FACP reports 0

--> SMBIOS thinks it's a "Rack Mounted Chassis" device, The ACPI FACP states it's "unknown"
..so I think for this, since it's "unknown" in the FACP, this is probably a false positive from fwts. We need to fix this case.

Case 3:
FAILED [HIGH] DMIInvalidHardwareEntry: Test 1, Unmatched Chassis Type SMBIOS Type 3 reports 17 ACPI
FACP reports 4

--> SMBIOS thinks it's a "Rack Mounted Chassis" device, The ACPI FACP states it's "Enterprise Server", so this looks OK to me and fwts is being overly pedantic. This is a fwts bug.

Case 4:
FAILED [HIGH] DMIInvalidHardwareEntry: Test 1, Unmatched Chassis Type SMBIOS Type 3 reports 11 ACPI
FACP reports 1

 SMBIOS thinks it's a "Desktop" device, The ACPI FACP states it's "Desktop", so this is OK, and fwts is wrong.

So, fwts is wrong on most counts. This needs fixing

[Colin Ian King (colin-king)]

These errors should be fixed with a bunch of patches I've sent to the fwts-devel mailing list. Hopefully they will land in fwts 0.25.05

[Colin Ian King (colin-king)]

Fixed in commit a45f2d80c21228fee60f3feb705ed0a5b8ca0147

Released in V0.25.05, see https://launchpad.net/~firmware-testing-team/+archive/ppa-fwts-devel

[Keng-Yu Lin (lexical)]

There is the need for package upload sponsoring:

https://launchpad.net/~firmware-testing-team/+archive/ppa-fwts-devel/+files/fwts_0.25.05.dsc

The diff: https://launchpad.net/~firmware-testing-team/+archive/ppa-fwts-devel/+files/fwts_0.25.04_0.25.05.diff.gz

[Launchpad Janitor (janitor)]

This bug was fixed in the package fwts - 0.25.05

---------------
fwts (0.25.05) quantal; urgency=low

  [Chris Van Hoof]
  * live-image/fwts-frontend-text: use mv versus ln as symbolic links are not
    supported on fat file systems

  [Colin Ian King]
  * dmi_decode: Add some more advice text
  * dmi_decode: Only be pedantic if we are sure about the board type
    (LP: #1021674)
  * dmi_decode: report chassis types with 0x prefix since they are in hex
  * lib: tidy up source, remove trailing whitespaces and empty lines
  * acpi: method: update table of implemented tests
  * acpi: method: add new _AEI check
  * acpi: method: Add stub for ACPI 5.0 _CPC
  * acpi: method: Add new ACPI 5.0 _PRE
  * acpi: method: Add new ACPI 5.0 _PSE check
  * acpi: acpidump: Add ACPI 5.0 GTDT support.
  * acpi: acpidump: Add ACPI 5.0 BGRT support.
  * lib: fwts_log_json: do more json object out of memory checking
  * acpi: acpidump: dump out ACPI UEFI tables
  * acpi: acpidump: Add SLIC table dump
  * acpi: acpidump: dump out the DMAR table
  * acpi: acpidump: dump out the ASF! table
  * acpi: acpidump: Add dump of TCPA
  * acpi: s4: hibernate/resume failures should be HIGH failures
  * acpi: s3: suspend/resume failures should be HIGH failures
  * Add empty m4 directory so autoreconf does not fail
  * Remove the autotool generated files
  * lib: fwts_hwinfo: sort device info before comparing (LP: #1018288)

  [Keng-Yu Lin]
  * Install the libraries in pkglib
  * debian: Add autoreconf parameters -ivf
 -- Keng-Yu Lin <email address hidden> Wed, 11 Jul 2012 13:58:43 +0800