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 747324 - Error message being printed to stdout and not stderr 'SMBIOS implementations newer than version 2.6 are not fully supported by this version of dmidecode.'
Summary: Error message being printed to stdout and not stderr 'SMBIOS implementations ...
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dmidecode
Version: 6.1
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Anton Arapov
QA Contact: qe-baseos-daemons
Depends On:
Blocks: 806845
TreeView+ depends on / blocked
Reported: 2011-10-19 13:52 UTC by Lee Yarwood
Modified: 2018-11-27 21:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 806845 (view as bug list)
Last Closed: 2011-10-20 12:02:11 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Lee Yarwood 2011-10-19 13:52:38 UTC
Description of problem:

When dmidecode encounters an issue with the SMBIOS version it prints the following error out to stdout. While this error is obviously correct it does play havoc with scripts attempting to parse it's output. A number of customers that have hit this issue have suggested that these errors are printed to stderr to allow for an easier work around in scripts etc.

# /usr/sbin/dmidecode -s system-uuid
# SMBIOS implementations newer than version 2.6 are not
# fully supported by this version of dmidecode.

Version-Release number of selected component (if applicable):

How reproducible:
Attempt to access parse dmidecode output when SMBIOS is newer than version 2.6.

Steps to Reproduce:
1. Run any command when SMBIOS is newer than version 2.6.
Actual results:
Error message printed to stdout.

Expected results:
Error message printed to stderr.

Additional info:

Comment 2 Anton Arapov 2011-10-20 11:48:15 UTC
  it's not an error message, it's INFO message. All the error messages are already routed to stderr. This very message is intentionally left to stdout because it IS important. And it can be easily filtered out in a shell scripts.
  We are not going to fix it.

Let me know if you have any concerns. Otherwise I close it.

Comment 5 Anton Arapov 2012-03-23 10:06:50 UTC
  The message is important because we can't guarantee the output is correct in that case. If we suppress it we might be getting reports of the wrong information interpretation. IOW users will complaint about all kind of weirdness dmidecode might show them when use new hardware.
  I will update the documentation and man page to define this behaviour.

Comment 6 Ken Booth 2012-03-23 21:37:55 UTC
Hi Anton,

Thanks for the detailed explanation. The customer is now happy, especially after I told him we will change the documentation.


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