Understood. Thanks for investigating the possibility. On Fri, May 20, 2016 at 10:43 AM, Colin Ian King <1578...@bugs.launchpad.net> wrote: > @Jeff, the backport to the much older 2.x version of smbios is just too > intrusive and risky for me to deem this worthwhile; this is more like > adding a feature to the older version 2 of the code, which is outside of > the remit of a SRU, so for Trusty, I'm not going to SRU this. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1578022 > > Title: > dmidecode fails to output smibios 3.0 info > > Status in dmidecode package in Ubuntu: > Fix Released > Status in dmidecode source package in Xenial: > Fix Committed > Status in dmidecode source package in Yakkety: > Fix Released > > Bug description: > [SRU JUSTIFICATION][XENIAL] > > Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios > 3.0. Rhel 7.2 can display smibios 3.0 on the same system without a > problem. > > [FIX] > Let read_file return the actual data size > > http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=de9a74e1c60210bee229fcf55b1678a99d1b44dd > > dmidecode: Use read_file() to read the DMI table from sysfs > > http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=364055211b1956539c6a6268e111e244e1292c8c > > There's also a couple other SMBIOS 3.0 related fixes that is listed as > recomended for 3.0 on http://dmidecode.nongnu.org/ > > Fix 'No SMBIOS nor DMI entry point found' on SMBIOS3 > > http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=bf7bad24ce141dab5b5acc3ffb98ce5fe4a8e0f9 > > Use DWORD for Structure table maximum size in SMBIOS3 > > http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=ab02b117511230e46bbef7febbd854b9c832c13c > > Without the fix, dmidecode fails to display SMBIOS 3.0 tables. With > the fix the headers can be decoded correctly. > > [REGRESSION POTENTIAL] > Could break existing dmi table decoding. However, this has been tested on > pre 3.0 and 3.0 SMBIOS tables, so the risk seems minimal as it works on a > range of DMI table versions. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=dmidecode; component=main; > status=Fix Released; importance=Medium; assignee=colin.k...@ubuntu.com; > Launchpad-Bug: distribution=ubuntu; distroseries=xenial; > sourcepackage=dmidecode; component=main; status=Fix Committed; > importance=Medium; assignee=colin.k...@ubuntu.com; > Launchpad-Bug: distribution=ubuntu; distroseries=yakkety; > sourcepackage=dmidecode; component=main; status=Fix Released; > importance=Medium; assignee=colin.k...@ubuntu.com; > Launchpad-Bug-Tags: hwcert-server verification-needed > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: adconrad andre-tomt bladernr colin-king janitor > jefleung samantha-jian > Launchpad-Bug-Reporter: Samantha Jian-Pielak (samantha-jian) > Launchpad-Bug-Modifier: Colin Ian King (colin-king) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr
-- "Entropy isn't what it used to be." Jeff Lane - Server Certification Lead, Warrior Poet, Biker, Lover of Pie Phone: 919-442-8649 Ubuntu Ham: W4KDH Freenode IRC: bladernr or bladernr_ gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417 C466 4ABD 3635 3A14 B2DD -- 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/1578022 Title: dmidecode fails to output smibios 3.0 info Status in dmidecode package in Ubuntu: Fix Released Status in dmidecode source package in Xenial: Fix Committed Status in dmidecode source package in Yakkety: Fix Released Bug description: [SRU JUSTIFICATION][XENIAL] Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios 3.0. Rhel 7.2 can display smibios 3.0 on the same system without a problem. [FIX] Let read_file return the actual data size http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=de9a74e1c60210bee229fcf55b1678a99d1b44dd dmidecode: Use read_file() to read the DMI table from sysfs http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=364055211b1956539c6a6268e111e244e1292c8c There's also a couple other SMBIOS 3.0 related fixes that is listed as recomended for 3.0 on http://dmidecode.nongnu.org/ Fix 'No SMBIOS nor DMI entry point found' on SMBIOS3 http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=bf7bad24ce141dab5b5acc3ffb98ce5fe4a8e0f9 Use DWORD for Structure table maximum size in SMBIOS3 http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=ab02b117511230e46bbef7febbd854b9c832c13c Without the fix, dmidecode fails to display SMBIOS 3.0 tables. With the fix the headers can be decoded correctly. [REGRESSION POTENTIAL] Could break existing dmi table decoding. However, this has been tested on pre 3.0 and 3.0 SMBIOS tables, so the risk seems minimal as it works on a range of DMI table versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+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