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 if it's a broken firmware DMI table
or a kernel issue.

** Changed in: dmidecode (Ubuntu)
       Status: New => Triaged

** Changed in: dmidecode (Ubuntu)
     Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: dmidecode (Ubuntu)
   Importance: Undecided => Medium

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.

  dmidecode triggers system reboot on Inforce 6640

Status in cloud-init:
Status in dmidecode package in Ubuntu:

Bug description:
  Device: Inforce 6640
  SoC: Snapdragon 820

  version='#76-Ubuntu SMP Tue Nov 26 16:10:14 UTC 2019', 

  The issue is caused by following commit.
  Inforce 6640 doesn't have functional demidecode.
  System will reboot when executing dmidecode.

  commit 3416e2ee7f65defdb15aab861a85767d13e8c34c
  Author: Robert Schweikert <>
  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

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to