-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-9.3.0
-
None
-
None
-
rhel-sst-kernel-debug
-
ssg_core_kernel
-
None
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
-
aarch64
-
None
What were you trying to do that didn't work?
run dmidecode on NXP I.MX8 system
Please provide the package NVR for which bug is seen:
How reproducible:
100%
Steps to reproduce
- run dmidecode and observe failure
Expected results
dmidecode completes
Actual results
Invalid entry length (0). DMI table is broken! Stop.
I am trying to run redhat-certification tests on some ARM Edge systems including NXP I.MX8 and Nvidia systems
Please see https://issues.redhat.com/browse/CERTPX-11489 for details
We use dmidecode to plan the proper tests and it is also a subtest to determine supportability.
On NXP I.MX8 I am seeing this for dmidecode
[root@imx8 ~]# dmidecode
dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.0 present.
7 structures occupying 233 bytes.
Table at 0xFA6E2020.
Wrong DMI structures length: 233 bytes announced, only 152 bytes available.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: U-Boot
Version: 2021.04-lf_v2021.04+g263b27e076
Release Date: 11/22/2021
ROM Size: 64 kB
Characteristics:
PCI is supported
BIOS is upgradeable
Selectable boot is supported
I2O boot is supported
Targeted content distribution is supported
BIOS Revision: 21.4
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Not Specified
Product Name: Not Specified
Version: Not Specified
Serial Number: 0c1da1d6f6c99ef5
UUID: 64316330-3161-3664-6636-633939656635
Wake-up Type: Reserved
SKU Number: Not Specified
Family: Not Specified
Handle 0x0002, DMI type 2, 14 bytes
Base Board Information
Manufacturer: Not Specified
Product Name: Not Specified
Version: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Features:
Board is a hosting board
Location In Chassis: Not Specified
Chassis Handle: 0x0000
Type: Motherboard
Invalid entry length (0). DMI table is broken! Stop.
It has been suggested in the above Jira that dmidecode should not crash on a single broken table. It has also been suggested that this is a firmware issue and the hardware partner has to fix their bad firmware tables so that the tables are valid and not change dmidecode
I am filing this Jira to keep track of the issue and the fix if one is deemed necessary