RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1421971 - dmidecode has 2 SMBIOS 3.0 entries
Summary: dmidecode has 2 SMBIOS 3.0 entries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dmidecode
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Petr Oros
QA Contact: Mike Gahagan
URL:
Whiteboard:
Depends On:
Blocks: 1369100 1446211
TreeView+ depends on / blocked
 
Reported: 2017-02-14 08:58 UTC by wangsy30
Modified: 2021-03-11 14:57 UTC (History)
8 users (show)

Fixed In Version: dmidecode-3.0-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 17:53:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
dmidecode -17 (4.44 KB, text/plain)
2017-02-14 08:58 UTC, wangsy30
no flags Details
0001 patch (2.26 KB, application/mbox)
2017-02-15 02:17 UTC, wangsy30
no flags Details
002 patch (2.64 KB, application/mbox)
2017-02-15 02:18 UTC, wangsy30
no flags Details
dmidecode.spec (8.33 KB, text/x-rpm-spec)
2017-02-15 02:21 UTC, wangsy30
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3108991 0 None None None 2017-07-10 08:40:32 UTC
Red Hat Product Errata RHBA-2017:1858 0 normal SHIPPED_LIVE dmidecode bug fix and enhancement update 2017-08-01 18:04:08 UTC

Description wangsy30 2017-02-14 08:58:14 UTC
Created attachment 1250149 [details]
dmidecode -17

Description of problem:
dmidecode has 2 SMBIOS 3.0 entries

Version-Release number of selected component (if applicable):
dmidecode-3.0-2.el7.x86_64

How reproducible:
dmidecode

Steps to Reproduce:
Take type 17 as an example.
1. 4 dimms on board 
2. dmidecode -t 17

Actual results:
Display 4 dimms in SMBIOS 3.0 and 4 dimms in SMBIOS 3.0.0


Expected results:
Display 4 dimms in SMBIOS 3.0

Comment 1 wangsy30 2017-02-14 08:59:17 UTC
Upstream has fixed this issue:

commit 12fbde92a26da61eda9f2ff0ba3c316779163f10
Author: Jean Delvare <jdelvare>
Date:   Fri Jan 20 10:57:12 2017 +0100

    Only decode one DMI table

    Since version 3.0.0 of the SMBIOS specification, there can be
    multiple entry points in memory, pointing to one or two DMI tables.
    If both a 32-bit ("_SM_") entry point and a 64-bit ("_SM3_") entry
    point are present, the specification requires that the latter points
    to a table which is a super-set of the table pointed to by the
    former. Therefore it makes no sense to decode both.

    Per specification, look for a 64-bit ("_SM3_") entry point first, and
    if we can't find any, look for a 32-bit ("_SM_" or "_DMI_") entry
    point.

    This fixes bug #50022:
    https://savannah.nongnu.org/bugs/?50022

Comment 3 wangsy30 2017-02-15 02:17:44 UTC
Created attachment 1250465 [details]
0001 patch

Comment 4 wangsy30 2017-02-15 02:18:29 UTC
Created attachment 1250466 [details]
002 patch

Comment 5 wangsy30 2017-02-15 02:21:21 UTC
Created attachment 1250467 [details]
dmidecode.spec

I uploaded 2 patches and dmidecode.spec. Test is passed on board which has SMBIOS 3.0.

Comment 6 wangsy30 2017-02-15 08:10:20 UTC
Petr Oros,
According CHANGELOG, it seems there is no update after 2015-11-02 , 
I advise add all upstream patches besides the 2 patches I attached.

Comment 7 Petr Oros 2017-02-15 09:42:49 UTC
Hi,
I agree with you. Will do.

Thanks,
-Petr

Comment 10 Mike Gahagan 2017-05-03 19:46:06 UTC
The SMBIOS 3 based system I have access to doesn't seem to reproduce the bug however I can confirm the fix is in dmidecode-3.0-4.el7.

Comment 11 errata-xmlrpc 2017-08-01 17:53:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1858


Note You need to log in before you can comment on or make changes to this bug.