** Description changed: - Device: Inforce 6640 - https://www.inforcecomputing.com/products/single-board-computers-sbc/qualcomm-snapdragon-820-inforce-6640-sbc - SoC: Snapdragon 820 + [Impact] + Running 'sudo dmidecode' on non-UEFI ARM systems can cause them to crash/reboot. cloud-init apparently runs dmidecode as root, so it breaks any cloud-init based installation. - sysname='Linux', - nodename='ubuntu', - release='4.15.0-1069-snapdragon', - version='#76-Ubuntu SMP Tue Nov 26 16:10:14 UTC 2019', - machine='aarch64' + [Test Case] + sudo dmidecode - The issue is caused by following commit. - Inforce 6640 doesn't have functional demidecode. - System will reboot when executing dmidecode. + [Fix] + Upstream has the following fix: - commit 3416e2ee7f65defdb15aab861a85767d13e8c34c - Author: Robert Schweikert <rjsch...@suse.com> - Date: Sat Oct 29 09:29:53 2016 -0400 - dmidecode: Allow dmidecode to be used on aarch64 - aarch64 systems have functional dmidecode, so allow that to be used. - - aarch64 has support for dmidecode as well + 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 + + [Regression Risk] + In Ubuntu, dmidecode only builds on amd64, arm64, armhf & i386. + The fix is to disable code on !x86, so the regression risk is restricted to ARM platforms, where we know /dev/mem trolling is bad news.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1858615 Title: dmidecode triggers system reboot on Inforce 6640 Status in cloud-init: Invalid Status in dmidecode package in Ubuntu: Fix Released Status in dmidecode source package in Bionic: In Progress Status in dmidecode source package in Eoan: In Progress Status in dmidecode source package in Focal: Fix Released Status in dmidecode package in Debian: Unknown Bug description: [Impact] Running 'sudo dmidecode' on non-UEFI ARM systems can cause them to crash/reboot. cloud-init apparently runs dmidecode as root, so it breaks any cloud-init based installation. [Test Case] sudo dmidecode [Fix] Upstream has the following 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 [Regression Risk] In Ubuntu, dmidecode only builds on amd64, arm64, armhf & i386. The fix is to disable code on !x86, so the regression risk is restricted to ARM platforms, where we know /dev/mem trolling is bad news. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1858615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
