Em 30-06-2017 17:28, Brice Goglin escreveu: Le 30/06/2017 22:08, fabricio a écrit : Em 30-06-2017 16:21, Brice Goglin escreveu: Yes, it's possible but very easy. Before we go that way: Can you also pass HWLOC_COMPONENTS_VERBOSE=1 in the environment and send the verbose output?
Hello We have seen _many_ reports like these. But there are different kinds of errors. As far as I understand: * Julio's error is caused by the Linux kernel improperly reporting L3 cache affinities. It's specific to multi-socket 12-core processors because the kernel makes invalid assumptions
Le 30/06/2017 22:08, fabricio a écrit : > Em 30-06-2017 16:21, Brice Goglin escreveu: >> Yes, it's possible but very easy. Before we go that way: >> Can you also pass HWLOC_COMPONENTS_VERBOSE=1 in the environment and send >> the verbose output? > >
We (Georgia Tech) too have been observing this on 16-core AMD AbuDhabi machines (6378). We weren’t aware of HWLOC_COMPONENTS workaround, which seems to mitigate the issue. Before: # ./lstopo * hwloc has encountered
Em 29-06-2017 02:24, Brice Goglin escreveu: Hello Brice I'm still seeing this error message even when passing the HWLOC_COMPONENTS=x86 variable. Is it possible to generate a xml file that can silence this error? TIA, Fabricio ___ hwloc-users
Hello We've seen this issue many times (it's specific to 12-core opterons), but I am surprised it still occurs with such a recent kernel. AMD was supposed to fix the kernel in early 2016 but I forgot checking whether something was actually pushed. Anyway, you can likely ignore the issue as