Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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
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
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
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