Upstream has a fix like the one I was hinting at in comment #9, I'll SRU
this fix.
commit e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
Author: Jean Delvare <jdelv...@suse.de>
Date: Mon Aug 26 14:20:15 2019 +0200
dmidecode: Only scan /dev/mem for entry point on x86
x86 is the only architecture which can have a DMI entry point scanned
from /dev/mem. Do not attempt it on other architectures, because not
only it can't work, but it can even cause the system to reboot.
This fixes support request #109697:
https://savannah.nongnu.org/support/?109697
** Changed in: dmidecode (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: dmidecode (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858615
Title:
dmidecode triggers system reboot on Inforce 6640
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1858615/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
