[Bug 1638515] Comment bridged from LTC Bugzilla
--- Comment From vipar...@in.ibm.com 2016-11-15 03:55 EDT--- Thanks!! for explanation. Since things are working as per numactl code design, thus i am closing this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1638515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638515] Comment bridged from LTC Bugzilla
--- Comment From vipar...@in.ibm.com 2016-11-08 08:03 EDT--- # ls -l /sys/class/net/enP32770p1s0f0 .. /sys/class/net/enP32770p1s0f0 -> ../../devices/pci8002:01/8002:01:00.0/net/enP32770p1s0f0 # cat /sys/class/net/enP32770p1s0f0/device/numa_node -1 # cat /sys/devices/pci8002\:01/8002:01:00.0/numa_node -1 # numactl -a --cpubind=netdev:enP32770p1s0f0 echo hi libnuma: Warning: Kernel does not know node mask for device `/devices/pci8002:01/8002:01:00.0/' is invalid For enP32770p1s0f0 device numa_code contains -1 and thus "numactl --cpubind" fails with "Kernel does not know node mask" Hello Canonical, Thanks!! for your findings with numactl --cpubind option. Here enP28p96s0fX devices fall under numa_node 1, which doesn't have CPUs and thus cpubind fails with "Cannot read node mask". This is expected behaviour as per numactl code working. enP32770p1s0f0 fails numactl --cpubind option with "Kernel does not know node mask". This fail is likely due to numa_node for this device having -1 as value. Any suggestions why enP32770p1s0f0 device is having numa_node value of -1 ? Is this some kernel issue here ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1638515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638515] Comment bridged from LTC Bugzilla
--- Comment From vipar...@in.ibm.com 2016-11-08 07:08 EDT--- # for i in `ifconfig -a | awk -F : '/^e/ {print $1}'`; do echo -n "$i - " ; ethtool -i $i | grep bus; done enP28p96s0f0 - bus-info: 001c:60:00.0 enP28p96s0f1 - bus-info: 001c:60:00.1 enP28p96s0f2 - bus-info: 001c:60:00.2 enP28p96s0f3 - bus-info: 001c:60:00.3 enP32770p1s0f0 - bus-info: 8002:01:00.0 # lspci 0018:01:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre Channel Host Adapter (rev 30) 0018:01:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre Channel Host Adapter (rev 30) 001c:60:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 001c:60:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 001c:60:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 001c:60:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 001c:60:00.4 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator (Lancer) (rev 10) 001c:60:00.5 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator (Lancer) (rev 10) 8002:01:00.0 Ethernet controller: Emulex Corporation Device e228 (rev 10) # numactl -H available: 2 nodes (0-1) node 0 cpus: 0 - 159 node 0 size: 0 MB node 0 free: 0 MB node 1 cpus: node 1 size: 17826 MB node 1 free: 13171 MB node distances: # ls -l /sys/class/net | cut -d ' ' -f 10- enP28p96s0f0 -> ../../devices/pci001c:60/001c:60:00.0/net/enP28p96s0f0 enP28p96s0f1 -> ../../devices/pci001c:60/001c:60:00.1/net/enP28p96s0f1 enP28p96s0f2 -> ../../devices/pci001c:60/001c:60:00.2/net/enP28p96s0f2 enP28p96s0f3 -> ../../devices/pci001c:60/001c:60:00.3/net/enP28p96s0f3 enP32770p1s0f0 -> ../../devices/pci8002:01/8002:01:00.0/net/enP32770p1s0f0 lo -> ../../devices/virtual/net/lo # cat /sys/class/net/enP28p96s0f0/device/numa_node 1 # cat /sys/class/net/enP28p96s0f1/device/numa_node 1 # # numactl -a --cpunodebind=netdev:enP28p96s0f0 libnuma: Warning: Cannot read node mask for device `/devices/pci001c:60/001c:60:00.0/' is invalid .. .. # numactl -a --cpunodebind=netdev:enP28p96s0f1 libnuma: Warning: Cannot read node mask for device `/devices/pci001c:60/001c:60:00.1/' is invalid There are 5 Ethernet controllers onto this box. enP28p96s0fX devices fall under numa_node 1, and since node 1 doesn't have any cpus assigned thus numactl with --cpunodebind fails with "Cannot read node mask" error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1638515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638515] Comment bridged from LTC Bugzilla
--- Comment From pt...@cn.ibm.com 2016-11-07 00:49 EDT--- (In reply to comment #18) > On Nov 6, 2016 17:45, "bugproxy"wrote: > > > > (In reply to comment #15) > > > From the affected systems, can you provide: > > > > > > ls -ahl /sys/class/net/ (which should be a symlink) > > > cat /sys/devices//numa_node > > > [ I believe in your case, that would be: > > > cat /sys//devices/pci0002:01/0002:01:00.3/numa_node > > > ] > > > cat /sys/class/net//device/numa_node > > > > > > > The original system which I found this bug with 16.04.1 cannot reproduce > > it with 16.10 anymore. I found another system roselp3 and adding a NIC > > adapter(U78C9.001.WZS02T4-P1-C8) by DLPAR. Then, > > > > % numactl -a --cpunodebind=netdev:enP28p96s0f3 numactl --show > > libnuma: Warning: Cannot read node mask for device > `/devices/pci001c:60/001c:60:00.3/' > > is invalid > > ... ... > > > > % ls -ahl /sys/class/net/enP28p96s0f3 > > lrwxrwxrwx 1 root root 0 Nov 6 19:18 /sys/class/net/enP28p96s0f3 -> > ../../devices/pci001c:60/001c:60:00.3/net/enP28p96s0f3 > > % cat /sys/devices/pci001c:60/001c:60:00.3/numa_node > > 1 > > % cat /sys/class/net/enP28p96s0f3/device/numa_node > > 1 > > Can you please provide numactl -H output from the affected system? % sudo numactl -H available: 2 nodes (0-1) 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 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 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 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 0 size: 0 MB node 0 free: 0 MB node 1 cpus: node 1 size: 17826 MB node 1 free: 13472 MB node distances: node 0 1 0: 10 20 1: 20 10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1638515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1638515] Comment bridged from LTC Bugzilla
On Nov 6, 2016 17:45, "bugproxy"wrote: > > --- Comment From pt...@cn.ibm.com 2016-11-06 20:30 EDT--- > (In reply to comment #15) > > From the affected systems, can you provide: > > > > ls -ahl /sys/class/net/ (which should be a symlink) > > cat /sys/devices//numa_node > > [ I believe in your case, that would be: > > cat /sys//devices/pci0002:01/0002:01:00.3/numa_node > > ] > > cat /sys/class/net//device/numa_node > > > > The original system which I found this bug with 16.04.1 cannot reproduce > it with 16.10 anymore. I found another system roselp3 and adding a NIC > adapter(U78C9.001.WZS02T4-P1-C8) by DLPAR. Then, > > % numactl -a --cpunodebind=netdev:enP28p96s0f3 numactl --show > libnuma: Warning: Cannot read node mask for device `/devices/pci001c:60/001c:60:00.3/' > is invalid > ... ... > > % ls -ahl /sys/class/net/enP28p96s0f3 > lrwxrwxrwx 1 root root 0 Nov 6 19:18 /sys/class/net/enP28p96s0f3 -> ../../devices/pci001c:60/001c:60:00.3/net/enP28p96s0f3 > % cat /sys/devices/pci001c:60/001c:60:00.3/numa_node > 1 > % cat /sys/class/net/enP28p96s0f3/device/numa_node > 1 Can you please provide numactl -H output from the affected system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1638515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638515] Comment bridged from LTC Bugzilla
--- Comment From pt...@cn.ibm.com 2016-11-06 20:30 EDT--- (In reply to comment #15) > From the affected systems, can you provide: > > ls -ahl /sys/class/net/ (which should be a symlink) > cat /sys/devices//numa_node > [ I believe in your case, that would be: > cat /sys//devices/pci0002:01/0002:01:00.3/numa_node > ] > cat /sys/class/net//device/numa_node > The original system which I found this bug with 16.04.1 cannot reproduce it with 16.10 anymore. I found another system roselp3 and adding a NIC adapter(U78C9.001.WZS02T4-P1-C8) by DLPAR. Then, % numactl -a --cpunodebind=netdev:enP28p96s0f3 numactl --show libnuma: Warning: Cannot read node mask for device `/devices/pci001c:60/001c:60:00.3/' is invalid ... ... % ls -ahl /sys/class/net/enP28p96s0f3 lrwxrwxrwx 1 root root 0 Nov 6 19:18 /sys/class/net/enP28p96s0f3 -> ../../devices/pci001c:60/001c:60:00.3/net/enP28p96s0f3 % cat /sys/devices/pci001c:60/001c:60:00.3/numa_node 1 % cat /sys/class/net/enP28p96s0f3/device/numa_node 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1638515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638515] Comment bridged from LTC Bugzilla
--- Comment From vipar...@in.ibm.com 2016-11-02 07:11 EDT--- Hello Canonical, Can you please have a look and advise at numactl command failures being seen with '--cpubind' option. We could recreate it on ppc and x86 platforms running 16.10 and 16.04.1. Refer previous comments about detailed description and findings on the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1638515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs