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:

The qdrive3 boards are systems with multiple CPU modules.

$ grep "CPU part" /proc/cpuinfo | sort -u
CPU part    : 0xd4b
CPU part    : 0xd4c

The hex code is converted by lscpu to human readable name. Unfortunately, lscpu in RHEL9 is too old and it has no clue about 0xd4c aka "Cortex-X1C", so it prints "-" instead of the name.

This issue will impact many scripts that uses lscpu from collecting accurate information about the test environment.
 
Version-Release number of selected component (if applicable):
util-linux 2.37.4

How reproducible:
100%

Steps to Reproduce:
1. Run Linux on a qdrive3 board.
2. Install util-linux in the Linux.
3. Run and check the result of `lscpu`.

Actual results:
lscpu cannot convert 0xd4c to Cortex-X1C and include that information in the outputs. So the output looks confusing.

Expected results:
lscpu can display all CPU modules in its output.

Additional info:
1. The initial discuss about this issue can be found at https://issues.redhat.com/browse/AUTOBUG-230

Thanks to Jiri Hladky for bringing this up, and to Karel and Radka for debugging!

I guess we can backport all human-readable ARM names from upstream. The number of new CPU identifiers (the hex) is huge:

$ git diff HEAD^ upstream -- sys-utils/lscpu-arm.c | grep -c '+.*0x'
76

https://issues.redhat.com/browse/AUTOBUG-230?focusedId=22855921&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-22855921

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 (util-linux 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-2023:6706