** No longer affects: util-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1427995
Title:
lscpu -p is showing wrong values for Node component
Status in
For reference, the deployed fix shows correct result on an Intel i7 processor:
Prior to update:
…
# CPU,Core,Socket,Node,,L1d,L1i,L2,L3
0,0,0,0,,0,0,0,0
1,1,0,0,,1,1,1,0
2,2,0,0,,2,2,2,0
3,3,0,0,,3,3,3,0
4,0,0,0,,0,0,0,0
5,1,0,0,,1,1,1,0
6,2,0,65,,2,2,2,0
7,3,0,0,,3,3,3,0
After update:
…
#
This bug was fixed in the package util-linux - 2.20.1-5.1ubuntu20.7
---
util-linux (2.20.1-5.1ubuntu20.7) trusty; urgency=medium
* Use the correct parameter to index node names. (LP: #1427995)
-- Mathieu Trudel-Lapierre Wed, 02 Sep 2015
11:06:26 -0400
**
** Changed in: util-linux (Ubuntu)
Importance: High => Medium
** Changed in: util-linux (Ubuntu Trusty)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
Verified this on a fully-enabled POWER8 system; confirming that without
the patch, multiple CPUs show incorrect node values (random garbage):
144,18,3,0,,18,18,18,18
145,18,3,0,,18,18,18,18
146,18,3,436483456,,18,18,18,18
147,18,3,256,,18,18,18,18
148,18,3,436482464,,18,18,18,18
Fixed up to correctly target this at Trusty; this bug doesn't exist in
later releases. I uploaded the SRU to the trusty queue.
** Also affects: util-linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Trusty)
Status: New => In Progress
**
** Description changed:
+ [Impact]
+ Any user of lscpu on systems with multiple NUMA nodes.
+
+ [Test case]
+ On a POWER8 system:
+ 1) Run 'lscpu'; take note of the values for "NUMA node# CPU(s)".
+ 2) Run 'lscpu -p'.
+
+ The values on the fourth column in lscpu -p output should match the node
** Changed in: util-linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1427995
Title:
lscpu -p is showing wrong values
** Changed in: util-linux (Ubuntu Trusty)
Milestone: None => ubuntu-14.04.4
** Changed in: util-linux (Ubuntu)
Milestone: ubuntu-14.04.4 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
** Tags removed: targetmilestone-inin14042
** Tags added: targetmilestone-inin14043
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1427995
Title:
lscpu -p is showing
Hello bugproxy, or anyone else affected,
Accepted util-linux into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.20.1-5.1ubuntu20.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Steve, what exactly did you test?
This issue looks a lot like what should have been fixed by
2.20.1-5.1ubuntu20.4; discontinuous NUMA nodes, but it's already the
version that would have been used.
I have access to a system which appears to show the issue, so I'll see
if I can find which other
** Changed in: util-linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) = Mathieu Trudel-Lapierre
(mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
** Tags removed: severity-high
** Tags added: severity-medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1427995
Title:
lscpu -p is showing wrong values for Node
I've just done a test here with both Ubuntu 14.04 and Ubuntu 15.04
versions of util-linux (2.20.1-5.1ubuntu20.4 vs. 2.25.2-4ubuntu2), and I
can confirm that the older version of lscpu gives different output on
the same kernel. So yes, this is a bug in util-linux's parsing of /sys.
** Changed in:
Thanks for this additional information. This still doesn't answer the
question of whether the bug is in lscpu, or in the kernel's /sys
interfaces. Have you checked whether old util-linux with new kernel, or
new util-linux with old kernel, works?
--
You received this bug notification because
** Changed in: util-linux (Ubuntu)
Assignee: (unassigned) = Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1427995
Title:
Please note that bugs in launchpad should be assigned to taco-screen-
team if you are looking for Canonical to take action on them.
This bug has been assigned to the util-linux package, and says that the
output in the 'node' column is incorrect. What are the correct values
for the 'node' field,
** Package changed: ubuntu = util-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1427995
Title:
lscpu -p is showing wrong values for Node component
19 matches
Mail list logo