numa_node_of_cpu() returns warning when cpu_index > 79
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
numactl (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned | ||
Utopic |
Fix Released
|
High
|
Unassigned | ||
Vivid |
Fix Released
|
High
|
Unassigned |
Bug Description
=======
SRU Justification
1. Impact: numactl fails on systems with > 79 cpus
2. Test case: see 'steps to reproduce' below in the description.
3. Regression potential: this is a straight cherrypick of an upstream commit and should be safe. It changes core code so if there were regressions we can't say they'd be contained in any way, but they should not affect other packages
=======
== Comment: #0 - TSAI-YANG JEA <email address hidden> - 2014-08-12 14:52:38 ==
---Problem Description---
In a ppc64le P8 node with SMT 8 mode, numa_node_of_cpu (80) returns following warning:
libnuma: Warning: /sys not mounted or invalid. Assuming one node: No such file or directory
---uname output---
Linux c656f2n01 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:29:58 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuletta P8 22L
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Problem can be created with following test case on a P8 LE machine with SMT=8.
#include <dlfcn.h>
#include <stdio.h>
int main(int argc, char *argv[])
{
int dlopen_flags = RTLD_NOW|
int(
int node = 0;
int cpu;
if(argc != 2) {
return -1;
}
cpu = atoi(argv[1]);
printf("%d\n", cpu);
void *handle = dlopen(
if(handle) {
node_of_cpu = (__typeof_
node = node_of_cpu(cpu);
}
}
return 0;
}
To compile the test: gcc test.c -ldl -o test
To run: ./test 80
Other information:
$ numactl -H
available: 4 nodes (0-1,16-17)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
node 0 size: 65115 MB
node 0 free: 2955 MB
node 1 cpus: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
node 1 size: 65473 MB
node 1 free: 3313 MB
node 16 cpus: 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119
node 16 size: 65457 MB
node 16 free: 9310 MB
node 17 cpus: 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
node 17 size: 65209 MB
node 17 free: 10999 MB
node distances:
node 0 1 16 17
0: 10 20 40 40
1: 20 10 40 40
16: 40 40 10 20
17: 40 40 20 10
Userspace tool common name: libnuma
The userspace tool has the following bit modes: 64-bit
== Comment: #4 - Kamalesh Babulal <email address hidden> - 2014-08-19 12:29:15 ==
numa_node_of_cpu
|
|_numa_
and tries to read /sys/devices/
That's the reason why your seeing the warning and wrong information about node. We should be skipping the nodes which are not set in the numa_nodes_ptr
tags: | added: architecture-ppc64le bugnameltc-114573 severity-medium targetmilestone-inin1404 |
affects: | ubuntu → numactl (Ubuntu) |
tags: |
added: severity-high removed: severity-medium |
Changed in numactl (Ubuntu): | |
status: | New → Confirmed |
Changed in numactl (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Serge Hallyn (serge-hallyn) |
Changed in numactl (Ubuntu): | |
importance: | Undecided → High |
status: | Confirmed → Incomplete |
Changed in numactl (Ubuntu): | |
status: | Incomplete → In Progress |
Changed in numactl (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in numactl (Ubuntu Trusty): | |
importance: | Undecided → High |
description: | updated |
Changed in numactl (Ubuntu Trusty): | |
status: | New → Fix Committed |
tags: | added: verification-needed |
Changed in numactl (Ubuntu Utopic): | |
status: | New → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
tags: |
added: verification-done-trusty verification-done-vivid removed: verification-done |
tags: | added: verification-needed-utopic |
Changed in numactl (Ubuntu Trusty): | |
status: | Fix Committed → Fix Released |
tags: | removed: verification-done-trusty verification-done-vivid verification-needed-utopic |
Changed in numactl (Ubuntu Utopic): | |
status: | Fix Committed → Fix Released |
Changed in numactl (Ubuntu Trusty): | |
status: | Fix Released → Confirmed |
Changed in numactl (Ubuntu Utopic): | |
status: | Fix Released → Confirmed |
importance: | Undecided → High |
Changed in numactl (Ubuntu Vivid): | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: |
added: verification-done removed: verification-needed |
Changed in numactl (Ubuntu): | |
assignee: | Serge Hallyn (serge-hallyn) → nobody |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1358835/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]