Re: [OMPI devel] Open MPI 1.6.5 opal_paffinity_base_get_physical_socket_id

2014-05-31 Thread Jeff Squyres (jsquyres)
The super short answer is: 1.6.x is old and deprecated; can you upgrade to the 1.8.x series? The short answer is "no" -- paffinity calls should never block, but it depends on how and what you're measuring. The more detailed answer is: your trace below looks like it includes a call to MPI_Abort

Re: [OMPI devel] [External] Re: Open MPI 1.6.5 opal_paffinity_base_get_physical_socket_id

2014-05-31 Thread Lecrenski, Stephen K PW
This case was a very simple 6 process test on a single node which ran to completion. I'm installing mpi 1.8.1 now to see if I see the same issue. I just installed and ran hwloc. What am I looking for? I see basic information PCI (ib0, ib1, mix4_0) PCI(eth0) PCI(eth1) PCI() PCI(sda) and othe

Re: [OMPI devel] [External] Re: Open MPI 1.6.5 opal_paffinity_base_get_physical_socket_id

2014-05-31 Thread Jeff Squyres (jsquyres)
On May 31, 2014, at 10:32 AM, "Lecrenski, Stephen K PW" wrote: > This case was a very simple 6 process test on a single node which ran to > completion. > > I'm installing mpi 1.8.1 now to see if I see the same issue. > > I just installed and ran hwloc. What am I looking for? I see bas