Hello Johannes I think there are two bugs here.
First one is that each "dual-core compute unit" is reported as a single core with two hardware threads. That's a kernel bug that appeared in 4.6. There's a fix at https://lkml.org/lkml/2016/11/29/852 but I don't think it has been applied yet. The second bug is a conflict between dual-core compute unit sharing and L1i. I am not sure which one is actually buggy. Can you run "HWLOC_COMPONENTS=x86 lstopo foo.xml" and send the generated foo.xml? (this is our raw detection that works around the kernel detection). Trying a Linux kernel <= 4.5 may help in the meantime. thanks Brice Le 03/01/2017 05:29, Johannes Goller a écrit : > As requested on > https://www.open-mpi.org/projects/hwloc/doc/v1.10.1/a00028.php ("What > should I do when hwloc reports 'operating system' warnings?"), I am > reporting the warning/error I received as follows > > **************************************************************************** > * hwloc 1.11.0 has encountered what looks like an error from the > operating system. > * > * L1i (cpuset 0x00000003) intersects with Core (P#0 cpuset 0x00000081) > without inclusion! > * Error occurred in topology.c line 983 > * > * The following FAQ entry in the hwloc documentation may help: > * What should I do when hwloc reports "operating system" warnings? > * Otherwise please report this error message to the hwloc user's > mailing list, > * along with the output+tarball generated by the hwloc-gather-topology > script. > **************************************************************************** > > Please find the tarball attached. > > > > regards, > > Johannes Goller. > > > > _______________________________________________ > hwloc-users mailing list > hwloc-users@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/hwloc-users
_______________________________________________ hwloc-users mailing list hwloc-users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/hwloc-users
