Unfortunately numactl/libnuma is historically quite bad at making it easy to debug these kind of issues.
Algorithmically, numactl does the following: If a /sys/class/net/<device> symlink is found and the target matches '/devices/pci[0-9a-fA-F:/]+\\.[0-9]+)/', it then tries to parse /sys/<part that matches the above regex>/numa_node If the above symlink is not found, it tries to parse /sys/class/net/<device>/device/numa_node My initial suspicion would be the non-continuous NUMA numbering, but if it also happens on x86 then that seems like not an issue. >From the affected systems, can you provide: ls -ahl /sys/class/net/<device> (which should be a symlink) cat /sys/devices/<pci path to device>/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>/device/numa_node Thanks, Nish -- 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
