Re: [OMPI users] Bug in OpenMPI-1.8.3: storage limition in shared memory allocation (MPI_WIN_ALLOCATE_SHARED) in Ftn-code

2014-10-24 Thread Jeff Squyres (jsquyres)
Nathan tells me that this may well be related to a fix that was literally just pulled into the v1.8 branch today: https://github.com/open-mpi/ompi-release/pull/56 Would you mind testing any nightly tarball after tonight? (i.e., the v1.8 tarballs generated tonight will be the first ones to

Re: [OMPI users] Problem with Yosemite

2014-10-24 Thread Ralph Castain
Found that you do have to use the Apple version of libtool, however, to build - the Darwin ports “glibtool” version will fail. Tested the 1.8.3 tarball and it again worked fine. > On Oct 24, 2014, at 10:46 AM, Ralph Castain wrote: > > Will do - just taking forever to update my Darwin ports so

Re: [OMPI users] Problem with Yosemite

2014-10-24 Thread Ralph Castain
Will do - just taking forever to update my Darwin ports so I can try with their libtool version Guillaume - did you remember to update your ports before building? Major changes to support Yosemite. > On Oct 24, 2014, at 10:01 AM, Jeff Squyres (jsquyres) > wrote: > > Ralph -- > > Can you tr

Re: [OMPI users] Problem with Yosemite

2014-10-24 Thread Jeff Squyres (jsquyres)
Ralph -- Can you try a 1.8 nightly tarball build on Y? On Oct 24, 2014, at 12:32 PM, Ralph Castain wrote: > Could well be - I’m using the libtool from Apple > > Apple Inc. version cctools-855 > > Just verified that 1.8 is working fine as well. > Ralph > > >> On Oct 24, 2014, at 9:23 AM,

Re: [OMPI users] Problem with Yosemite

2014-10-24 Thread Ralph Castain
Could well be - I’m using the libtool from Apple Apple Inc. version cctools-855 Just verified that 1.8 is working fine as well. Ralph > On Oct 24, 2014, at 9:23 AM, Bert Wesarg wrote: > > This is maybe related to a problem in libtool: > > http://lists.gnu.org/archive/html/libtool-patches/20

Re: [OMPI users] which info is needed for SIGSEGV in Java foropenmpi-dev-124-g91e9686on Solaris

2014-10-24 Thread Siegmar Gross
Hi Gilles, thank you very much for your help. > how did you configure openmpi ? which java version did you use ? > > i just found a regression and you currently have to explicitly add > CFLAGS=-D_REENTRANT CPPFLAGS=-D_REENTRANT > to your configure command line I added "-D_REENTRANT" to my comma

Re: [OMPI users] Problem with Yosemite

2014-10-24 Thread Bert Wesarg
This is maybe related to a problem in libtool: http://lists.gnu.org/archive/html/libtool-patches/2014-09/msg2.html On Fri, Oct 24, 2014 at 6:09 PM, Ralph Castain wrote: > I was able to build and run the trunk without problem on Yosemite with: > > gcc (MacPorts gcc49 4.9.1_0) 4.9.1 > GNU Fort

Re: [OMPI users] Problem with Yosemite

2014-10-24 Thread Ralph Castain
I was able to build and run the trunk without problem on Yosemite with: gcc (MacPorts gcc49 4.9.1_0) 4.9.1 GNU Fortran (MacPorts gcc49 4.9.1_0) 4.9.1 Will test 1.8 branch now, though I believe the fortran support in 1.8 is up-to-date > On Oct 24, 2014, at 6:46 AM, Guillaume Houzeaux > wrote:

[OMPI users] Bug in OpenMPI-1.8.3: storage limition in shared memory allocation (MPI_WIN_ALLOCATE_SHARED) in Ftn-code

2014-10-24 Thread Michael.Rachner
Dear developers of OPENMPI, I am running a small downsized Fortran-testprogram for shared memory allocation (using MPI_WIN_ALLOCATE_SHARED and MPI_WIN_SHARED_QUERY) ) on only 1 node of 2 different Linux-clusters with OPENMPI-1.8.3 and Intel-14.0.4 /Intel-13.0.1, respectively. The program sim

Re: [OMPI users] OMPI users] low CPU utilization with OpenMPI

2014-10-24 Thread Gilles Gouaillardet
Can you also check there is no cpu binding issue (several mpi tasks and/or OpenMP threads if any, bound to the same core and doing time sharing ? A simple way to check that is to log into a compute node, run top and then press 1 f j If some cores have higher usage than others, you are likely doin

[OMPI users] Problem with Yosemite

2014-10-24 Thread Guillaume Houzeaux
Good morning/afternoon/night, I actualized my OS two days ago from Maverick to Yosemite (Xcode6.1). I recompiled openmpi-1.4.1, openmpi-1.6.3, openmpi-1.8.3 and get the same problem. What I did: 1. mpif90 test_openmpi.f90 -o test_openmpi.x 2. ./test_openmpi.x and get BEFORE [bsccs456.int.b

Re: [OMPI users] New ib locked pages behavior?

2014-10-24 Thread Jeff Squyres (jsquyres)
On Oct 22, 2014, at 3:37 AM, r...@q-leap.de wrote: > I've commented in detail on this (non-)issue on 2014-08-20: > > http://www.open-mpi.org/community/lists/users/2014/08/25090.php > > A change in the FAQ and a fix in the code would really be nice > at this stage. Thanks for the reminder; I've

Re: [OMPI users] low CPU utilization with OpenMPI

2014-10-24 Thread Jeff Squyres (jsquyres)
- Is /tmp on that machine on NFS or local? - Have you looked at the text of the help message that came out before the "9 more processes have sent help message help-opal-shmem-mmap.txt / mmap on nfs" message? It should contain details about what the problematic NFS directory is. - Do you know t

Re: [OMPI users] which info is needed for SIGSEGV in Java foropenmpi-dev-124-g91e9686 on Solaris

2014-10-24 Thread Gilles Gouaillardet
Siegmar, how did you configure openmpi ? which java version did you use ? i just found a regression and you currently have to explicitly add CFLAGS=-D_REENTRANT CPPFLAGS=-D_REENTRANT to your configure command line if you want to debug this issue (i cannot reproduce it on a solaris 11 x86 virtual