Hi Samuel, I have attached the output of tests/linux/gather-topology.sh `uname --kernel-release`_`uname -- nodename`_gather-topology
I'm sorry for the long delay - systems has been used by somebody else, I had to wait for it to be free. System is running kernel 2.6.18-227.el5 (RHEL 5.6). ia64 is not supported on RHEL 6.0 so I cannot really test it on the new kernel. It would be really interesting if you can recognize if it's a kernel bug or hwloc problem. Thanks a lot! Jirka On Wednesday, October 27, 2010 02:59:30 pm Samuel Thibault wrote: > Hello, > > Jirka Hladky, le Wed 27 Oct 2010 14:53:01 +0200, a écrit : > > I have attached a tar file with full information. > > Could you also post the result of test/linux/gather-topology.sh ? > > Samuel > _______________________________________________ > hwloc-devel mailing list > hwloc-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
2.6.18-227.el5_hp-bl870c-01.rhts.eng.bos.redhat.com_gather-topology.tar.gz
Description: application/compressed-tar
Machine (phys=0 local=16591312KB total=16591312KB)
Socket #0 (phys=0)
L2Cache #0 (256KB)
L1Cache #0 (16KB)
Core #0 (phys=0)
L3Cache #0 (9216KB)
PU #0 (phys=0)
L3Cache #1 (9216KB)
PU #1 (phys=1)
L2Cache #1 (256KB)
L1Cache #1 (16KB)
Core #1 (phys=1)
L3Cache #2 (9216KB)
PU #2 (phys=2)
L3Cache #3 (9216KB)
PU #3 (phys=3)
Socket #1 (phys=1)
L2Cache #2 (256KB)
L1Cache #2 (16KB)
Core #2 (phys=0)
L3Cache #4 (9216KB)
PU #4 (phys=4)
L3Cache #5 (9216KB)
PU #5 (phys=5)
L2Cache #3 (256KB)
L1Cache #3 (16KB)
Core #3 (phys=1)
L3Cache #6 (9216KB)
PU #6 (phys=6)
L3Cache #7 (9216KB)
PU #7 (phys=7)
depth 0: 1 Machine (type #1)
depth 1: 2 Sockets (type #3)
depth 2: 4 Caches (type #4)
depth 3: 4 Caches (type #4)
depth 4: 4 Cores (type #5)
depth 5: 8 Caches (type #4)
depth 6: 8 PUs (type #6)
Topology not from this system
