Check if a system is affected by bad dmi data and a systemd passing on the error.
$ sudo SYSTEMD_LOG_LEVEL=debug /usr/bin/udevadm monitor &
$ sudo udevadm trigger --action=add --subsystem-match dmi
KERNEL[669861.508604] add /devices/virtual/dmi/id (dmi)
sd-device-monitor: Invalid message length.
While the system I found the issue was upgraded and no more has the issue I found that the sister system is affected by the same. Some re-setup and I should be able to verify there.
Check if a system is affected by bad dmi data and a systemd passing on the error. LOG_LEVEL= debug /usr/bin/udevadm monitor & 669861. 508604] add /devices/ virtual/ dmi/id (dmi)
$ sudo SYSTEMD_
$ sudo udevadm trigger --action=add --subsystem-match dmi
KERNEL[
sd-device-monitor: Invalid message length.
While the system I found the issue was upgraded and no more has the issue I found that the sister system is affected by the same. Some re-setup and I should be able to verify there.