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.

Description of problem: lshw does not provide cpu information easily obtainable from /proc/cpuinfo. It should provide:

- cpu family
- cpu model
- cpu stepping
- cpu NUMA information (in the style of 'lscpu' NUMA data)


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


How reproducible: 100%


Steps to Reproduce:
1. Run 'lshw' and it lacks the requested data.


Actual results:
Missing cpu data.

Expected results:
Provide additional cpu data.


Additional info:

Here is the justification offered by the customer:

"Since lshw has decided to pull in things like all the cpu flags, which are also present in /proc/cpuinfo, then they should also pull in stepping, family, etc. Why should we need to pull from multiple sources when one will do?"

Merged in upstream: f914f225975b ("report CPU family/model/stepping"). Please refer to the comment#3 in the bz1794049. Thanks.

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 (lshw bug fix and enhancement update), 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-2020:4018