This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4 --------------- freeipmi (1.4.11-1.1ubuntu4) artful; urgency=medium
* Use kernel DMI table interface, when available, instead of trolling /dev/mem to avoid a crash on ARM. LP: #1699933. -- dann frazier <dann.fraz...@canonical.com> Wed, 28 Jun 2017 13:26:09 -0600 ** Changed in: freeipmi (Ubuntu Artful) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1699933 Title: ipmi-locate crash on arm64 Status in freeipmi package in Ubuntu: Fix Released Status in freeipmi source package in Xenial: Triaged Status in freeipmi source package in Yakkety: Triaged Status in freeipmi source package in Zesty: Triaged Status in freeipmi source package in Artful: Fix Released Status in freeipmi package in Debian: Confirmed Bug description: [Impact] * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is not stable to read, it will cause ipmi-locate crash. [Test Case] * `sudo ipmi-locate` shall not crash [Regression Potential] * Reading from DMI tables is sysfs is more stable then reading from /dev/mem and if DMI tables is not available ipmi-locate will use the old way to search in /dev/mem. I believe its low regression risk ---- Similiar to bug 1499838 but not 100% same. ipmi-locate looks into /dev/mem for DMI tables and crash when DMI tables are not in accessible memory region. Kernel > v4.2 provides /sys/firmware/DMI/tables/DMI which is a much safer place to read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1699933/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp