dmidecode fails to output smibios 3.0 info
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dmidecode (Ubuntu) |
Fix Released
|
Medium
|
Colin Ian King | ||
Xenial |
Fix Released
|
Medium
|
Colin Ian King | ||
Yakkety |
Fix Released
|
Medium
|
Colin Ian King |
Bug Description
[SRU JUSTIFICATION]
Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios 3.0. Rhel 7.2 can display smibios 3.0 on the same system without a problem.
[FIX]
Let read_file return the actual data size
http://
dmidecode: Use read_file() to read the DMI table from sysfs
http://
There's also a couple other SMBIOS 3.0 related fixes that is listed as recomended for 3.0 on http://
Fix 'No SMBIOS nor DMI entry point found' on SMBIOS3
http://
Use DWORD for Structure table maximum size in SMBIOS3
http://
Without the fix, dmidecode fails to display SMBIOS 3.0 tables. With the fix the headers can be decoded correctly.
[REGRESSION POTENTIAL]
Could break existing dmi table decoding. However, this has been tested on pre 3.0 and 3.0 SMBIOS tables, so the risk seems minimal as it works on a range of DMI table versions.
Changed in dmidecode (Ubuntu): | |
status: | In Progress → Incomplete |
Changed in dmidecode (Ubuntu Yakkety): | |
status: | Incomplete → Fix Committed |
Changed in dmidecode (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Colin Ian King (colin-king) |
tags: |
added: verification-done removed: verification-needed |
We found this during certification testing of a couple models from one OEM that apparently use SMIBIOS 3.0.
The failed test shows this in the output:
mmap: Can't map beyond end of file /sys/firmware/ dmi/tables/ DMI
Table is unreachable, sorry.
*** Incorrect or unknown server chassis type!
Failed 1 test (see above)
We also capture output of dmidecode in the test logs, on the 3.0 system this is all we get in output:
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x7BB4E000.