Re: [OMPI users] OpenMPI 1.8 and PGI compilers

2014-04-28 Thread Jeff Squyres (jsquyres)
Brian: Can you report this bug to PGI and see what they say? On Apr 27, 2014, at 2:15 PM, "Hjelm, Nathan T" wrote: > I see nothing invalid about that line. It is setting a struct scif_portID > from another struct scif_portID which is allowed in C99. The error might be > misleading or a compil

Re: [OMPI users] Connection timed out on TCP

2014-04-28 Thread Jeff Squyres (jsquyres)
In principle, there's nothing wrong with using ib0 interfaces for TCP MPI communication, but it does raise the question of why you're using TCP when you have InfiniBand available...? Aside from that, can you send all the info listed here: http://www.open-mpi.org/community/help/ On Apr 28,

Re: [OMPI users] Deadlocks and warnings from libevent when using MPI_THREAD_MULTIPLE

2014-04-28 Thread Ralph Castain
It isn't that simple. In some cases, THREAD_MULTIPLE works just fine. In some, it doesn't. Trying to devise logic that accurately detects when it does and doesn't work would be extremely difficult, and in many cases application-dependent. If we disable it for everyone, then those who can make i

Re: [OMPI users] Connection timed out on TCP

2014-04-28 Thread Vince Grimes
After barring the ib0 interfaces, I still get "Connection timed out" errors even over the Ethernet interfaces. At the end of the output I not get the following messages in addition to the one above: -- Sorry! You were su

Re: [OMPI users] Deadlocks and warnings from libevent when using MPI_THREAD_MULTIPLE

2014-04-28 Thread Jeffrey A Cummings
Wouldn't you save yourself work and your users confusion if you disabled options that don't currently work? Jeffrey A. Cummings Engineering Specialist Performance Modeling and Analysis Department Systems Analysis and Simulation Subdivision Systems Engineering Division Engineering and Technology