DMI not present or invalid in R35.5.0

[854053437]

Hi, I’m using our custom board with jetson xavier nx (L4T version: R35.5.0). And I met a error when use dmidecode tool to get the hardware info.

I see this similar question, but it’s not helpful

Jetson Orin NX SOC Serial Number

I would like to read the serial number that is unique to each SOC from the Jetson Orin NX. I am aware that the Jetson Nano carrier board contains a serial number in the EEPROM which can be read from /proc/device-tree/serial-number. I do not want that number. I need something to uniquely identify each Jetson module. In the 35.4.1 release I could read this info at /sys/class/dmi/id/product_serial, but this no longer works in release 35.5.0.

I can see this message in dmesg

[    0.318784] DMI not present or invalid.

So I check the source code, find that it’s in \kernel\kernel-5.10\drivers\firmware\dmi_scan.c, and I added some pr_info in it, find that it’s wrong in this section.

		if (efi.smbios3 != EFI_INVALID_TABLE_ADDR) {
			p = dmi_early_remap(efi.smbios3, 32);
			if (p == NULL) {
				pr_info("DMI invalid: efi.smbios3 invalid.\n");
				goto error;
			}
			memcpy_fromio(buf, p, 32);
			dmi_early_unmap(p, 32);

			if (!dmi_smbios3_present(buf)) {
				dmi_available = 1;
				return;
			}
		}
		if (efi.smbios == EFI_INVALID_TABLE_ADDR) {
				pr_info("DMI invalid: efi.smbios invalid.\n");
				goto error;
		}

the smbios3 and smbios are both invalid, so it print those err message.
I wonder is this related to our custom board or it’s a bug in this kernel version?

[WayneWWW]

Invoking dmidecode 3.2 on BSP 35.5.0 freezes the system and then reboot - #5 by KevinFFF

Why did this not help? You applied but not effect?

[854053437]

Yes, I used custom defconfig file and set CONFIG_DMI to y. Should I just remove it rather than set it to y?

[KevinFFF]

You can remove it and run the following command on your board after boot up to check its status.

$ zcat /proc/config.gz | grep CONFIG_DMI