This bug was fixed in the package dmidecode - 3.0-2ubuntu0.2
---
dmidecode (3.0-2ubuntu0.2) xenial; urgency=medium
* Restrict /dev/mem scanning for entry point to x86, fixing crashes
on certain ARM platforms (LP: #1858615):
- New
This bug was fixed in the package dmidecode - 3.1-1ubuntu0.1
---
dmidecode (3.1-1ubuntu0.1) bionic; urgency=medium
* Restrict /dev/mem scanning for entry point to x86, fixing crashes
on certain ARM platforms (LP: #1858615):
- New
This bug was fixed in the package dmidecode - 3.2-2ubuntu0.1
---
dmidecode (3.2-2ubuntu0.1) eoan; urgency=medium
* Restrict /dev/mem scanning for entry point to x86, fixing crashes
on certain ARM platforms (LP: #1858615):
- New debian/patches/0140-Fix_scan_entry_point.patch
Verified dmidecode_(3.1-1ubuntu0.1_amd64.deb) on my x86 laptop (Ubuntu 18.04.3
LTS, Desktop).
It works well.
--
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
@Colin @dann @Timo
I have verified the following packages on my inforce 6640.
eoan-proposed: dmidecode_3.2-2ubuntu0.1_arm64.deb
bionic-proposed: dmidecode_3.1-1ubuntu0.1_arm64.deb
xenial-proposed: dmidecode_3.0-2ubuntu0.2_arm64.deb
They look good.
When I run dmidecode, I get the following
Both crmsh autopkgtest failures could be explained by a flaky network
connection. The eoan one is certainly that - it's unable to connect to
the archive. The error from the bionic case is masked - but the test is
trying to apt install vim. That could obviously also be an archive
connectivity
e/b/x all verified on a dragonboard 410c
** Tags removed: verification-needed verification-needed-bionic
verification-needed-eoan
** Tags added: verification-done verification-done-bionic verification-done-eoan
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
Hello ethan.hsieh, or anyone else affected,
Accepted dmidecode into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/dmidecode/3.1-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello ethan.hsieh, or anyone else affected,
Accepted dmidecode into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dmidecode/3.2-2ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: dmidecode (Debian)
Status: Unknown => Fix Released
--
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
** Also affects: dmidecode (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: dmidecode (Ubuntu Xenial)
Status: New => In Progress
** Changed in: dmidecode (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification
** 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
Dann, tested on my 6640 on an older kernel, now get:
sudo dmidecode
# dmidecode 3.1
# No SMBIOS nor DMI entry point found, sorry.
I guess that's expected.
I'd like to see what Ethan gets on his H/W as I'm not running a cloud
installation on my dev board.
--
You received this bug notification
Actually, I realized I can reproduce this on a dragonboard I have here.
I've verified the PPA fix myself, so I'll go ahead and SRU.
--
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:
On Mon, Jan 27, 2020 at 05:07:06PM -, Colin Ian King wrote:
> I guess the next question is why dmidecode being run as root is required
> on a cloud init?
cloud-init uses DMI data to identify that it is running on certain
platforms. It will use /sys/class/dmi/... if available, but falls back
Sure Colin, I'll take it from here - thanks for your analysis so far. As
a next step, I'll wait for Ethan - or someone else w/ hw access - to
verify the PPA build in Comment #12.
** Bug watch added: Debian Bug tracker #946911
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946911
** Also
It needs backporting to eoan, disco bionic, I was just about to upload a
fix to my ppa so I could get it sponsored. Do you want to take it from
here Dann?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We carry this patch in focal - do we just need to backport it to bionic?
http://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
I uploaded a test fix to ppa:dannf/test. Could someone w/ hw access
verify that?
--
You received this bug notification
Upstream has a fix like the one I was hinting at in comment #9, I'll SRU
this fix.
commit e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
Author: Jean Delvare
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
I guess the next question is why dmidecode being run as root is required
on a cloud init? What happens when arches don't have DMI data?
--
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:
dmidocode.c directly accesses memory and assumes it's an x86 without any
checking that the arch is x86.. Randomly scanning arbitrary hunks of
memory on non-x86 as root will lead to all sorts of woe:
memory_scan:
if (!(opt.flags & FLAG_QUIET))
printf("Scanning %s for entry
So, dmidecode directly mmap's to /dev/mem and does some probing based on
the belief that the system is a x86 architecture even on arm
architectures.
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3, {st_mode=S_IFCHR|0640, st_rdev=makedev(0x1, 0x1), ...}) = 0
mmap(NULL, 65536, PROT_READ,
Hi, can you provide me instructions on how to get and install the image
for this board? I'd like to reproduce this issue and get a suitable fix
for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Dan
Got it. Thanks~
--
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:
Oh, stupid me, I've just read the info in comment #1
--
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
Does the kernel expose the DMI tables via the sysfs following sysfs
file: /sys/firmware/dmi/tables/DMI ?
If so, can you do the following:
sudo cat /sys/firmware/dmi/tables/DMI > dmi.raw
and attach it to the bug report. Also a dump of the kernel dmesg log
after it boots may be useful to see
Ethan, cloud-init isn't the right level to handle hardware issues with
DMI (which is why we've added the dmidecode task). I've pinged kernel
folks to see if we can get eyes on this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Ryan
Not all aarch64 platforms can support demidecode well.
How about revert the patch? or create a black list?
--
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
28 matches
Mail list logo
