[OMPI devel] 1.8.3 and PSM errors

Running Open MPI 1.8.3 with PSM does not seem to work right now at all. I am getting the same errors also on trunk from my newly set up MTT. Before trying to debug this I just wanted to make sure this is not a configuration error. I have following PSM packages installed:

[OMPI devel] errno and reentrance

Folks, While investigating an issue started at http://www.open-mpi.org/community/lists/users/2014/10/25562.php i found that it is mandatory to compile with -D_REENTRANT on Solaris (10 and 11) (otherwise errno is not per thread specific, and the pmix thread silently misinterpret EAGAIN or

Re: [OMPI devel] errno and reentrance

On Mon, Oct 27, 2014 at 2:42 AM, Gilles Gouaillardet < gilles.gouaillar...@iferc.org> wrote: [...] > Paul, since you have access to many platforms, could you please run this > test with and without -D_REENTRANT / -D_THREAD_SAFE > and tell me where the program produces incorrect behaviour (output

Re: [OMPI devel] errno and reentrance

Thanks Paul ! Gilles On 2014/10/27 18:47, Paul Hargrove wrote: > On Mon, Oct 27, 2014 at 2:42 AM, Gilles Gouaillardet < > gilles.gouaillar...@iferc.org> wrote: > [...] > >> Paul, since you have access to many platforms, could you please run this >> test with and without -D_REENTRANT /

Re: [OMPI devel] errno and reentrance

Gilles, I responded too quickly, not thinking that this test is pretty quick and doesn't require that I try sparc, ppc, ia64, etc. So my results: Solaris-{10,11}: With "cc" I agree with your findings (need -D_REENTRANT for correct behavior). With gcc either "-pthread" or "-D_REENTRANT" gave

Re: [OMPI devel] errno and reentrance

Thanks Paul, so the simplest way is to force -D_REENTRANT on Solaris, i will do that ! Cheers, Gilles On 2014/10/27 19:36, Paul Hargrove wrote: > Gilles, > > I responded too quickly, not thinking that this test is pretty quick and > doesn't require that I try sparc, ppc, ia64, etc. > So my

Re: [OMPI devel] 1.8.3 and PSM errors

I’m afraid I can’t quite decipher from all this what actually fails. Of course, PSM doesn’t support dynamic operations like comm_spawn or connect_accept, so if you are running those tests that just won’t work. Is that the heart of the problem here? > On Oct 27, 2014, at 1:40 AM, Adrian Reber

Re: [OMPI devel] 1.8.3 and PSM errors

This is a simpler test setup: On 8 core machines this works: $ mpirun -np 8 mpi_test_suite -t "environment" [...] Number of failed tests:0 Using 9 or more cores it fails: $ mpirun -np 9 mpi_test_suite -t "environment" mpi_test_suite:20293 terminated with signal 11 at PC=2b6d107fa9a4

Re: [OMPI devel] 1.8.3 and PSM errors

Andrew@Intel is looking into it - he has some PSM patches coming that may resolve this already. > On Oct 27, 2014, at 9:10 AM, Adrian Reber wrote: > > This is a simpler test setup: > > On 8 core machines this works: > > $ mpirun -np 8 mpi_test_suite -t "environment" >

[OMPI devel] Interesting warning in openib...

Saw this in CentOS7 using gcc 4.8.2: btl_openib_component.c: In function 'init_one_device': btl_openib_component.c:2019:54: warning: comparison between 'enum ' and 'mca_base_var_source_t' [-Wenum-compare] else if (BTL_OPENIB_RQ_SOURCE_DEVICE_INI == Ralph

Re: [OMPI devel] 1.8.3 and PSM errors

Hi Adrian, I'm unable to reproduce here with OMPI v1.8.3 (I assume you're doing this with one 8-core node): $ mpirun -np 32 -mca pml cm -mca mtl psm ./mpi_test_suite -t "environment" (Rank:0) tst_test_array[0]:Status (Rank:0) tst_test_array[1]:Request_Null (Rank:0) tst_test_array[2]:Type_dup

[OMPI devel] fixing a bug in 1.8 that's not in master

Hi Folks, A cut and past error seems to have happened with plm_alps_modules.c in 1.8 which causes a compile failure when building for cray. So right now, there's no building ompi 1.8 for crays. The problem is not present in master. For these kinds of problems, are we suppose to bypass all the

Re: [OMPI devel] fixing a bug in 1.8 that's not in master

Just create a topic branch from v1.8 in a local clone of ompi-release, make the change there, and then file a PR on the ompi-release repo Obviously, if it is a bug solely confined to v1.8, you can’t put it in master first :-) > On Oct 27, 2014, at 3:22 PM, Howard Pritchard