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:

is below really true?

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                32
On-line CPU(s) list:   0-31
Thread(s) per core:    2 ---- here?
Core(s) per socket:    8 ---- here?
Socket(s):             2
NUMA node(s):          4
Vendor ID:             AuthenticAMD
CPU family:            21
Model:                 2
Model name:            AMD Opteron(tm) Processor 6366 HE
Stepping:              0
CPU MHz:               1000.000
BogoMIPS:              3599.50
Virtualization:        AMD-V
L1d cache:             16K
L1i cache:             64K
L2 cache:              2048K
L3 cache:              6144K
NUMA node0 CPU(s):     0-7
NUMA node1 CPU(s):     8-15
NUMA node2 CPU(s):     16-23
NUMA node3 CPU(s):     24-31


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

util-linux-2.23.2-16.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

The processor 6366 HE has 16 cores (at least according to info on amd.com). What output from lscpu do you expect?


If there is really problem, than please, create a dump from /proc and /sys by script:

https://raw.githubusercontent.com/karelzak/util-linux/master/tests/ts/lscpu/mk-input.sh

and add the tarball generated by the script to bugzilla. Thanks.

I mask bits that make me dubious as --- here ?
I can be wrong, any Opteron does hyperthreading ?

Created attachment 945536 [details]
mk-input.sh diag

The numbers are based on how kernel see the CPU topology:

$ cat opteron-6366.txt/sys/devices/system/cpu/cpu0/topology/thread_siblings_list 
0-1
$ cat opteron-6366.txt/sys/devices/system/cpu/cpu0/topology/core_siblings_list 
0-15
$ cat opteron-6366.txt/sys/devices/system/cpu/online 
0-31

It means 32 CPUs, 16 cores, so 2 threads per core. 

NOTABUG from lscpu point of view, if this wrong then we need to fix kernel.