I'm losing it today, I just now noticed I sent mx_info for the wrong nodes ...
// node-1 $ mx_info MX Version: 1.1.6 MX Build: ggrobe@juggernaut:/home/ggrobe/Tools/mx-1.1.6 Thu Nov 30 14:17:44 GMT 2006 1 Myrinet board installed. The MX driver is configured to support up to 4 instances and 1024 nodes. =================================================================== Instance #0: 224.9 MHz LANai, 133.3 MHz PCI bus, 2 MB SRAM Status: Running, P0: Link up MAC Address: 00:60:dd:47:ab:c9 Product code: M3F-PCIXD-2 V2.2 Part number: 09-03034 Serial number: 299207 Mapper: 46:4d:53:4d:41:50, version = 0x0000000c, configured Mapped hosts: 16 ROUTE COUNT INDEX MAC ADDRESS HOST NAME P0 ----- ----------- --------- --- 0) 00:60:dd:47:ab:c9 node-1:0 1,1 1) 00:60:dd:47:c2:a7 juggernaut:0 5,3 2) 00:60:dd:47:ab:c8 node-2:0 6,3 3) 00:60:dd:47:ab:ca node-3:0 7,3 4) 00:60:dd:47:bf:65 node-7:0 7,3 5) 00:60:dd:47:c2:e1 node-8:0 7,3 6) 00:60:dd:47:c0:c1 node-9:0 6,3 7) 00:60:dd:47:c0:e5 node-13:0 1,1 8) 00:60:dd:47:c2:91 node-14:0 7,3 9) 00:60:dd:47:c0:b2 node-15:0 7,3 10) 00:60:dd:47:bf:f5 node-19:0 6,3 11) 00:60:dd:47:c0:b1 node-20:0 8,3 12) 00:60:dd:47:c0:f8 node-21:0 5,3 13) 00:60:dd:47:c0:8a node-25:0 6,3 14) 00:60:dd:47:c0:c2 node-27:0 7,3 15) 00:60:dd:47:c2:e0 node-26:0 6,3 // node-2 $ mx_info MX Version: 1.1.6 MX Build: ggrobe@juggernaut:/home/ggrobe/Tools/mx-1.1.6 Thu Nov 30 14:17:44 GMT 2006 1 Myrinet board installed. The MX driver is configured to support up to 4 instances and 1024 nodes. =================================================================== Instance #0: 224.9 MHz LANai, 133.0 MHz PCI bus, 2 MB SRAM Status: Running, P0: Link up MAC Address: 00:60:dd:47:ab:c8 Product code: M3F-PCIXD-2 V2.2 Part number: 09-03034 Serial number: 299208 Mapper: 46:4d:53:4d:41:50, version = 0x0000000c, configured Mapped hosts: 16 ROUTE COUNT INDEX MAC ADDRESS HOST NAME P0 ----- ----------- --------- --- 0) 00:60:dd:47:ab:c8 node-2:0 1,1 1) 00:60:dd:47:ab:c9 node-1:0 6,3 2) 00:60:dd:47:c2:a7 juggernaut:0 5,3 3) 00:60:dd:47:ab:ca node-3:0 6,3 4) 00:60:dd:47:bf:65 node-7:0 5,3 5) 00:60:dd:47:c2:e1 node-8:0 6,3 6) 00:60:dd:47:c0:c1 node-9:0 5,3 7) 00:60:dd:47:c0:e5 node-13:0 6,3 8) 00:60:dd:47:c2:91 node-14:0 8,3 9) 00:60:dd:47:c0:b2 node-15:0 1,1 10) 00:60:dd:47:bf:f5 node-19:0 5,3 11) 00:60:dd:47:c0:f8 node-21:0 5,3 12) 00:60:dd:47:c0:8a node-25:0 5,3 13) 00:60:dd:47:c0:c2 node-27:0 6,3 14) 00:60:dd:47:c2:e0 node-26:0 5,3 15) 00:60:dd:47:c0:b1 node-20:0 6,3 -----Original Message----- From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] On Behalf Of Reese Faucette Sent: Tuesday, January 02, 2007 4:08 PM To: Open MPI Users Subject: Re: [OMPI users] Ompi failing on mx only Ompi failing on mx only> I've attached the ompi_info from node-1 and node-2. thanks, but i need "mx_info", not "ompi_info" ;-) > But now that you mention mapper, I take it that's what SEGV_MAPERR > might be referring to. this is an ompi red herring; it has nothing to do with Myrinet mapping, even though it kinda looks like it. > $ mpirun --prefix /usr/local/openmpi-1.2b2 -x > LD_LIBRARY_PATH=${LD_LIBRARY_PATH} --hostfile ./h1-3 -np 5 --mca mtl > mx,self ./cpi > Signal:11 info.si_errno:0(Success) si_code:1(SEGV_MAPERR) A gdb traceback would be interesting on this one. thanks, -reese _______________________________________________ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users