On Tue, 16 Aug 2016 20:41:42 +0300 Kevin Wilson <wkevils at gmail.com> wrote:
> Thanks Metthew. > Indeed, something seems broken in that machine, > > Running > dmidecode > gives: > ..... > Invalid entry length (0). DMI table is broken! Stop > > Kevin > > > On Mon, Jul 18, 2016 at 10:13 PM, Matthew Hall <mhall at mhcomputing.net> > wrote: > > On Fri, Jul 15, 2016 at 09:51:42AM +0300, Kevin Wilson wrote: > >> Hello, > >> I have a machine on which there is a bit non common setup: I have only > >> "node1" (no node0) under /sys/devices/system/node: > >> ls /sys/devices/system/node/ > >> ... > >> node1 > >> ... > > > > If I had to guess then either the BIOS is busted or the CPU is in the wrong > > socket or the RAM is in the wrong socket. > > > > Either way all bets are off how this is going to pan out. Probably badly > > when > > it comes to getting the top performance. > > > > Some exploration of the dmidecode output on the machine could be valuable. > > > > Matthew. What if you have a two socket machine, and node 0 is not populated? Also does the kernel have NUMA support enabled? Long ago there was a bug in DPDK where it got NUMA socket info from /proc/cpuinfo. On some machines, the 'physical id' starts at 1 because value comes from BIOS.
