[OMPI devel] FD leak in Altix timer code?

2007-10-23 Thread Paul H. Hargrove
I was just looking at the Altix timer code in the OMPI trunk and unless I am missing something, the fd opened in opal_timer_altix_open() is never closed. It can be safely closed right after the mmap(). -Paul -- Paul H. Hargrove phhargr...@lbl.gov Future Technologies G

Re: [OMPI devel] PathScale 3.0 problems with Open MPI 1.2.[34]

2007-10-23 Thread Brian Barrett
On Oct 23, 2007, at 10:58 AM, Patrick Geoffray wrote: Bogdan Costescu wrote: I made some progress: if I configure with "--without-memory-manager" (along with all other options that I mentioned before), then it works. This was inspired by the fact that the segmentation fault occured in ptmall

Re: [OMPI devel] PathScale 3.0 problems with Open MPI 1.2.[34]

2007-10-23 Thread Patrick Geoffray
Hi Bogdan, Bogdan Costescu wrote: I made some progress: if I configure with "--without-memory-manager" (along with all other options that I mentioned before), then it works. This was inspired by the fact that the segmentation fault occured in ptmalloc2. I have previously tried to remove the MX

Re: [OMPI devel] PathScale 3.0 problems with Open MPI 1.2.[34]

2007-10-23 Thread Scott Atchley
On Oct 23, 2007, at 10:36 AM, Bogdan Costescu wrote: I don't get to that point... I am not even able to use the wrapper compilers (f.e. mpif90) to obtain an executable to run. The segmentation fault happens when Open MPI utilities are being run, even ompi_info. Ahh, I thought you were getting

Re: [OMPI devel] PathScale 3.0 problems with Open MPI 1.2.[34]

2007-10-23 Thread Bogdan Costescu
On Tue, 23 Oct 2007, Scott Atchley wrote: Which version of MX are you using? Are you enabling the MX registration cache (regcache)? Can you try two runs, one exporting MX_RCACHE=1 and one exporting MX_RCACHE=0 to all processes? I don't get to that point... I am not even able to use the wrappe

Re: [OMPI devel] PathScale 3.0 problems with Open MPI 1.2.[34]

2007-10-23 Thread Scott Atchley
On Oct 23, 2007, at 6:33 AM, Bogdan Costescu wrote: I made some progress: if I configure with "--without-memory-manager" (along with all other options that I mentioned before), then it works. This was inspired by the fact that the segmentation fault occured in ptmalloc2. I have previously tried

Re: [OMPI devel] collective problems

2007-10-23 Thread Gleb Natapov
On Tue, Oct 23, 2007 at 09:40:45AM -0400, Shipman, Galen M. wrote: > So this problem goes WAY back.. > > The problem here is that the PML marks MPI completion just prior to calling > btl_send and then returns to the user. This wouldn't be a problem if the BTL > then did something, but in the case

Re: [OMPI devel] collective problems

2007-10-23 Thread Shipman, Galen M.
So this problem goes WAY back.. The problem here is that the PML marks MPI completion just prior to calling btl_send and then returns to the user. This wouldn't be a problem if the BTL then did something, but in the case of OpenIB this fragment may not actually be on the wire (the joys of user lev

Re: [OMPI devel] PathScale 3.0 problems with Open MPI 1.2.[34]

2007-10-23 Thread Jeff Squyres
On Oct 23, 2007, at 6:33 AM, Bogdan Costescu wrote: There is in the openib BTL. The bug #1025 has in one the answers the following phrase: "It looks like this will affect many threading issues with the pathscale compiler -- the openib BTL is simply the first place we tripped it." which along

Re: [OMPI devel] PathScale 3.0 problems with Open MPI 1.2.[34]

2007-10-23 Thread Bogdan Costescu
On Mon, 22 Oct 2007, Jeff Squyres wrote: There is in the openib BTL. The bug #1025 has in one the answers the following phrase: "It looks like this will affect many threading issues with the pathscale compiler -- the openib BTL is simply the first place we tripped it." which along with th