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 1947352 - Crash coredump dmidecode also with manually downloaded verson dmidecod 3.3 but also with latest rpm verson 3.2
Summary: Crash coredump dmidecode also with manually downloaded verson dmidecod 3.3 bu...
Keywords:
Status: CLOSED DUPLICATE of bug 1885823
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dmidecode
Version: 8.3
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: beta
: ---
Assignee: lijiang
QA Contact: Jeff Bastian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-08 09:36 UTC by Remke
Modified: 2021-04-19 01:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-19 01:16:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Remke 2021-04-08 09:36:44 UTC 
Description of problem:
When using dmidecode with the installed (latest) version on RHEL8.3 dmidecode -u always will result in a coredump /  crash.

According GIT the latest patch will resolve the problem but this is not the case !
 - tried with the rpm from RHEL8.3:  dmidecode-3.2-6.el8.x86_64
(spec info:

Summary:        Tool to analyse BIOS DMI data
Name:           dmidecode
Version:        3.2
Release:        6%{?dist}
Epoch:          1
License:        GPLv2+
Source0:        http://download.savannah.gnu.org/releases/%{name}/%{name}-%{version}.tar.xz
)

- tried with the installed version removed from rpm and downloaded the latest tgz from git: http://git.savannah.nongnu.org/cgit/dmidecode.git
.. which should have solved the problem ?
-> 2021-01-19	dmidecode: Fix crash with -u option


Version-Release number of selected component (if applicable):
dmidecode-3.2-6.el8.x86_64

How reproducible:
-always-

Steps to Reproduce:
1. run dmidecode -u
2. =/= 1
3. =/= 1

Actual results:
systemd-coredump[3468427]: Process 3468425 (dmidecode) of user 0 dumped core.

 

                                                                       Stack trace of thread 3468425:
                                                                       #0  0x0000561859084edf dmi_table (dmidecode)
                                                                       #1  0x000056185908b581 smbios_decode (dmidecode)
                                                                       #2  0x00005618590834f4 main (dmidecode)
                                                                       #3  0x00007f0e7745c803 __libc_start_main (libc.so.6)
                                                                       #4  0x000056185908356e _start (dmidecode)

Expected results:
Copmplet dump from dmidecode (BIOS)
...
...
Handle 0x00A2, DMI type 33, 31 bytes
64-bit Memory Error Information
        Type: OK
        Granularity: Unknown
        Operation: Unknown
        Vendor Syndrome: Unknown
        Memory Array Address: Unknown
        Device Address: Unknown
        Resolution: Unknown

Handle 0x00A3, DMI type 126, 4 bytes
Inactive

Handle 0x00A4, DMI type 127, 4 bytes
End Of Table


Additional info:
Same has been seen by AlmaLinux:
https://bugs.almalinux.org/view.php?id=45
Comment 1 Coiby 2021-04-09 07:44:12 UTC 
(In reply to Remke from comment #0)
> Description of problem:
> When using dmidecode with the installed (latest) version on RHEL8.3
> dmidecode -u always will result in a coredump /  crash.
> 
> According GIT the latest patch will resolve the problem but this is not the
> case !
>  - tried with the rpm from RHEL8.3:  dmidecode-3.2-6.el8.x86_64
> (spec info:
> 
> Summary:        Tool to analyse BIOS DMI data
> Name:           dmidecode
> Version:        3.2
> Release:        6%{?dist}
> Epoch:          1
> License:        GPLv2+
> Source0:       
> http://download.savannah.gnu.org/releases/%{name}/%{name}-%{version}.tar.xz
> )
> 
> - tried with the installed version removed from rpm and downloaded the
> latest tgz from git: http://git.savannah.nongnu.org/cgit/dmidecode.git
> .. which should have solved the problem ?
> -> 2021-01-19	dmidecode: Fix crash with -u option
> 
> 
> Version-Release number of selected component (if applicable):
> dmidecode-3.2-6.el8.x86_64
> 
> How reproducible:
> -always-
> 
> Steps to Reproduce:
> 1. run dmidecode -u
> 2. =/= 1
> 3. =/= 1
> 
> Actual results:
> systemd-coredump[3468427]: Process 3468425 (dmidecode) of user 0 dumped core.
> 
>  
> 
>                                                                        Stack
> trace of thread 3468425:
>                                                                        #0 
> 0x0000561859084edf dmi_table (dmidecode)
>                                                                        #1 
> 0x000056185908b581 smbios_decode (dmidecode)
>                                                                        #2 
> 0x00005618590834f4 main (dmidecode)
>                                                                        #3 
> 0x00007f0e7745c803 __libc_start_main (libc.so.6)
>                                                                        #4 
> 0x000056185908356e _start (dmidecode)
> 
> Expected results:
> Copmplet dump from dmidecode (BIOS)
> ...
> ...
> Handle 0x00A2, DMI type 33, 31 bytes
> 64-bit Memory Error Information
>         Type: OK
>         Granularity: Unknown
>         Operation: Unknown
>         Vendor Syndrome: Unknown
>         Memory Array Address: Unknown
>         Device Address: Unknown
>         Resolution: Unknown
> 
> Handle 0x00A3, DMI type 126, 4 bytes
> Inactive
> 
> Handle 0x00A4, DMI type 127, 4 bytes
> End Of Table
> 
> 
> Additional info:
> Same has been seen by AlmaLinux:
> https://bugs.almalinux.org/view.php?id=45

Hi Remke,

As pointed out by Martin Poole [1], commit 11e134e54d15e67a64c39a623f492a28df922517 has fixed this issue. But http://git.savannah.nongnu.org/cgit/dmidecode.git/snapshot/dmidecode-3-3.tar.gz doesn't contain the fix. I'll backport 11e134e54d15e67a64c39a623f492a28df922517 to 8.5.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1885823#c2
Comment 2 Coiby 2021-04-19 01:16:57 UTC 

*** This bug has been marked as a duplicate of bug 1885823 ***
Note You need to log in before you can comment on or make changes to this bug.