Re: [OMPI users] Address not mapped segmentation fault with1.4.2 ...

2010-06-10 Thread Richard Walsh
Jeff, OK ... I rebuilt without --with-tm= and as predicted my test case runs (I left the IB flags in). I then ran a job with just: pbsdsh hostname on 16 nodes and that also worked. I know that 1.4.1 works although it was build pointing into the old PBS Pro version tree explicitly. I have

Re: [OMPI users] Address not mapped segmentation fault with1.4.2 ...

2010-06-10 Thread Jeff Squyres
On Jun 10, 2010, at 5:49 PM, Richard Walsh wrote: > OK ... so if I follow your lead and build a version without PBS --tm= > integration > and it works, I should be able to report this as an incompatibility bug > between > the latest version of PBS Pro (10.2.0.93147) and the latest version of

Re: [OMPI users] Address not mapped segmentation fault with1.4.2 ...

2010-06-10 Thread Richard Walsh
Jeff/All, OK ... so if I follow your lead and build a version without PBS --tm= integration and it works, I should be able to report this as an incompatibility bug between the latest version of PBS Pro (10.2.0.93147) and the latest version of OpenMPI (1.4.2). right? Do I report that you to my

Re: [OMPI users] Specifying slots in rankfile

2010-06-10 Thread Terry Dontje
Sorry, there was a miscommunications between Ethan and I. The "*" nomenclature never worked in OMPI, it is the specification of "n:*" that works and we believe still works. --td Terry Dontje wrote: It looks like the rankfile "*" syntax was broke between version r22761 and r23214. So, it

[OMPI users] MPI_GET beyond 2 GB displacement

2010-06-10 Thread Price, Brian M (N-KCI)
OpenMPI version: 1.3.3 Platform: IBM P5 Built OpenMPI 64-bit (i.e., CFLAGS=-q64, CXXFLAGS=-q64, -FFLAGS=-q64, -FCFLAGS=-q64) FORTRAN 90 test program: - Create a large array (3.6 GB of 32-bit INTs) - Initialize MPI - Create a large window to encompass large array

Re: [OMPI users] Specifying slots in rankfile

2010-06-10 Thread Terry Dontje
It looks like the rankfile "*" syntax was broke between version r22761 and r23214. So, it looks like a regression to me. Ethan is looking into trying to narrow this down more. --td Ralph Castain wrote: I would have to look at the code, but I suspect it doesn't handle "*". Could be

Re: [OMPI users] Address not mapped segmentation fault with1.4.2 ...

2010-06-10 Thread Jeff Squyres
Not offhand, but just to close the loop on a question from your first mail: this should not be a memory manager issue (i.e., not related to IB). As Ralph noted, this is a segv in the launcher (mpirun, in this case) -- in the tm_init() function call (TM is the launcher helper library in

Re: [OMPI users] Address not mapped segmentation fault with 1.4.2 ...

2010-06-10 Thread Richard Walsh
Ralph/Jeff, Yes, the change was intentional. I have upgraded PBS as well and built 1.4.2 pointing to the new PBS via a symbolic link to 'default' which allows one to control the actual default without changing the path. I did the same thing on the non-IB system which seems to be working fine

Re: [OMPI users] Address not mapped segmentation fault with 1.4.2 ...

2010-06-10 Thread Jeff Squyres
On Jun 10, 2010, at 10:57 AM, Ralph Castain wrote: > That error would indicate something wrong with the pbs connection - it is > tm_init that is crashing. I note that you did --with-tm pointing to a > different location - was that intentional? Could be something wrong with that > pbs build

Re: [OMPI users] Address not mapped segmentation fault with 1.4.2 ...

2010-06-10 Thread Ralph Castain
That error would indicate something wrong with the pbs connection - it is tm_init that is crashing. I note that you did --with-tm pointing to a different location - was that intentional? Could be something wrong with that pbs build On Jun 10, 2010, at 8:44 AM, Richard Walsh wrote: > > All, >

Re: [OMPI users] Address not mapped segmentation fault with 1.4.2 ...

2010-06-10 Thread Jed Brown
Just a guess, but you could try the updated patch here https://svn.open-mpi.org/trac/ompi/ticket/2431 Jed

[OMPI users] Address not mapped segmentation fault with 1.4.2 ...

2010-06-10 Thread Richard Walsh
All, I am upgrading from 1.4.1 to 1.4.2 on both a cluster with IB and one without. I have no problem on the GE cluster without IB which requires no special configure options for the IB. 1.4.2 works perfectly there with both the latest Intel and PGI compiler. On the IB system 1.4.1 has worked

Re: [OMPI users] mpi_iprobe not behaving as expect

2010-06-10 Thread David Zhang
Thanks for the reply. I've somewhat figured it out the reason. It seems that when a non-blocking send is posted, mpi doesn't spawn another process that takes care the sending. The sending occurs only when the processor is idle. Since the data I sent was immense (2) elements, there wasn't