[Bug 1419503] Re: [SRU] lscpu reports incorrect number of NUMA nodes on systems with discontinuous NUMA nodes

[Launchpad Bug Tracker]

This bug was fixed in the package util-linux - 2.20.1-5.1ubuntu20.4

---------------
util-linux (2.20.1-5.1ubuntu20.4) trusty; urgency=medium

  * Backport from util-linux upstream commit e9074a16 to support discontinuous
    NUMA nodes. This also pulls in code from upstream 416c43a9 and dd3bc51a to
    support the backport. (LP: #1419503)
 -- Matt Ezell <ezellma at ornl.gov>   Tue, 10 Feb 2015 08:56:56 -0600

** Changed in: util-linux (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
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 Released

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