Re: [hwloc-devel] hwloc on PPC64

2010-07-12 Thread Brice Goglin
Le 12/07/2010 00:08, Jirka Hladky a écrit : > $./lstopo --xml /tmp/2010-Jul-10_22h14m_results/2.6.32-44.el6.ppc64_OS- > indexing.xml a.txt > Segmentation fault (core dumped) > This was a crash in a drawing code (in the merge() function) that Samuel fixed in trunk r2234 (and backported in

Re: [hwloc-devel] hwloc on PPC64

2010-07-11 Thread Jirka Hladky
On Sunday, July 11, 2010 07:57:48 pm Brice Goglin wrote: > Le 11/07/2010 19:48, Jirka Hladky a écrit : > > Hi all, > > > > I have run into two bugs on PPC64 on 2.6.32 kernel. > > > > Version: > > > > lt-lstopo 1.0.1 > > > > BUG #1: No Socket information in lstopo output: > > > > ./lstopo > >

Re: [hwloc-devel] hwloc on PPC64

2010-07-11 Thread Brice Goglin
Le 11/07/2010 19:48, Jirka Hladky a écrit : > > Hi all, > > I have run into two bugs on PPC64 on 2.6.32 kernel. > > Version: > > lt-lstopo 1.0.1 > > BUG #1: No Socket information in lstopo output: > > ./lstopo > > Machine (3654MB) + L2 #0 (4096KB) > > L1 #0 (64KB) + Core #0 > > PU #0 (phys=0) > >

[hwloc-devel] hwloc on PPC64

2010-07-11 Thread Jirka Hladky
Hi all, I have run into two bugs on PPC64 on 2.6.32 kernel. Version: lt-lstopo 1.0.1 BUG #1: No Socket information in lstopo output: ./lstopo Machine (3654MB) + L2 #0 (4096KB) L1 #0 (64KB) + Core #0 PU #0 (phys=0) PU #1 (phys=1) L1 #1 (64KB) + Core #1 PU #2 (phys=2) PU #3