[Bug 1419503] Re: [SRU] lscpu reports incorrect number of NUMA nodes on systems with discontinuous NUMA nodes
Matt Ezell
ezellma at ornl.gov
Fri Feb 13 19:35:00 UTC 2015
Verified that the update package produces the expected results on
Trusty:
root at crest4:~# dpkg -l util-linux
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==================================-======================-======================-=========================================================================
ii util-linux 2.20.1-5.1ubuntu20.3 ppc64el Miscellaneous system utilities
root at crest4:~# lscpu|grep NUMA
NUMA node(s): 2
NUMA node0 CPU(s): 0-39
NUMA node1 CPU(s): 40-79
root at crest4:~# apt-get install util-linux=2.20.1-5.1ubuntu20.4
...
root at crest4:~# lscpu|grep NUMA
NUMA node(s): 4
NUMA node0 CPU(s): 0-39
NUMA node1 CPU(s): 40-79
NUMA node16 CPU(s): 80-119
NUMA node17 CPU(s): 120-159
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1419503
Title:
[SRU] lscpu reports incorrect number of NUMA nodes on systems with
discontinuous NUMA nodes
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Trusty:
Fix Committed
Bug description:
[Impact]
Running 'lscpu' on a system with discontinuous NUMA nodes (such as some IBM Power 8 hardware) will only display the continuous NUMA nodes. Users may be confused due to incorrect information.
[Test Case]
On a system with discontinuous NUMA nodes, just run the lscpu command
# ls -d /sys/devices/system/node/node*
/sys/devices/system/node/node0 /sys/devices/system/node/node1 /sys/devices/system/node/node16 /sys/devices/system/node/node17
# lscpu|grep NUMA
NUMA node(s): 2
NUMA node0 CPU(s): 0-39
NUMA node1 CPU(s): 40-79
[Regression Potential]
Since this is an informational command, anything relying on its output may experience new behavior.
This affects Trusty, but Utopic and Vivid are based on newer upstream
releases that don't include this error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1419503/+subscriptions
More information about the foundations-bugs
mailing list