December 2014 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] MPICH 3 Problem
by Lu, Huiwei 03 Dec '14

03 Dec '14

Hi, Vipan, Looks like the MPI runtime is fine since you can run the cpi correctly. The error may be caused by your mpi_hello code. Could you attach the smallest code that can reproduce your error? Best, — Huiwei > On Dec 3, 2014, at 7:07 AM, vipan sharma <vipan.badyal(a)gmail.com> wrote: > > Dear Sir/Madam > Greetings of the day !! > I have installed the MPICH3 on RHEL5 with the steps give in the installation manual > inside the tar file of Mpich3 . > I am using a cluster of 3 systems with all the settings done as suggested by the manual , > and successfully able to run the example given inside the package i.e. Pi value calculation (cpi) > using the command > > $mpiexec -n 6 -f machinefile ./cpi > > Now when I am running some other process or some other examples the following error > is getting generated about which I have no clues how to get rid of the error > > Here I am listing the programm and the command I am using and error generating > > NANO35 if my master node > > [user@NANO35 test]$ mpiexec -n 6 -f /home/user/machinefile ./mpi_hello > [mpiexec@NANO35] control_cb (pm/pmiserv/pmiserv_cb.c:200): assert (!closed) failed > [mpiexec@NANO35] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status > [mpiexec@NANO35] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:198): error waiting for event > [mpiexec@NANO35] main (ui/mpich/mpiexec.c:344): process manager error waiting for completion > > Machinefile looks like > NANO35:2 > NANO36:2 > NANO37:2 > NANO38:2 > > PFA : LOG Files > > regards > Vipan SHARMA > <mpich3log.tar.gz>_______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] f77 bindings and profiling
by Jan Bierbaum 03 Dec '14

03 Dec '14

On 28.11.2014 18:07, Jan Bierbaum wrote: > Is this a bug or are we missing something here? Any new insights? Did anybody manage to properly use the PMPI interface with a Fortran application and MPICH 3.1.3? As a workaround I just use the Fortran wrapper from MPICH 3.1 now which still works fine with MPICH 3.1.3. But a proper fix would be better of course. Regards, Jan _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH 3 Problem
by vipan sharma 03 Dec '14

03 Dec '14

Dear Sir/Madam Greetings of the day !! I have installed the MPICH3 on RHEL5 with the steps give in the installation manual inside the tar file of Mpich3 . I am using a cluster of 3 systems with all the settings done as suggested by the manual , and successfully able to run the example given inside the package i.e. Pi value calculation (cpi) using the command $mpiexec -n 6 -f machinefile ./cpi Now when I am running some other process or some other examples the following error is getting generated about which I have no clues how to get rid of the error Here I am listing the programm and the command I am using and error generating NANO35 if my master node [user@NANO35 test]$ mpiexec -n 6 -f /home/user/machinefile ./mpi_hello [mpiexec@NANO35] control_cb (pm/pmiserv/pmiserv_cb.c:200): assert (!closed) failed [mpiexec@NANO35] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status [mpiexec@NANO35] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:198): error waiting for event [mpiexec@NANO35] main (ui/mpich/mpiexec.c:344): process manager error waiting for completion Machinefile looks like NANO35:2 NANO36:2 NANO37:2 NANO38:2 *PFA* : LOG Files regards Vipan SHARMA _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH Run Time error
by vipan sharma 03 Dec '14

03 Dec '14

Dear Sir/Madam Greetings of the day !! I have installed the MPICH3 on RHEL5 with the steps give in the installation manual inside the tar file of Mpich3 . I am using a cluster of 3 systems with all the settings done as suggested by the manual , and successfully able to run the example given inside the package i.e. Pi value calculation (cpi) using the command $mpiexec -n 6 -f machinefile ./cpi Now when I am running some other process or some other examples the following error is getting generated about which I have no clues how to get rid of the error Here I am listing the programm and the command I am using and error generating NANO35 if my master node [user@NANO35 test]$ mpiexec -n 6 -f /home/user/machinefile ./mpi_hello [mpiexec@NANO35] control_cb (pm/pmiserv/pmiserv_cb.c:200): assert (!closed) failed [mpiexec@NANO35] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status [mpiexec@NANO35] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:198): error waiting for event [mpiexec@NANO35] main (ui/mpich/mpiexec.c:344): process manager error waiting for completion Machinefile looks like NANO35:2 NANO36:2 NANO37:2 NANO38:2 regards vipan Sharma _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] [patch] fix bug in NEWMAD and MXM netmods
by Seo, Sangmin 02 Dec '14

02 Dec '14

Hi Kuleshov, Thanks for reporting this bug and patch. I have pushed your patch to mpich/master. You can find it from http://git.mpich.org/mpich.git/commit/8bdfaf741104f88c27b8a845d4ca325ad5005…. Best regards, Sangmin On Nov 29, 2014, at 2:14 PM, Kuleshov Aleksey <rndfax(a)yandex.ru<mailto:[email protected]>> wrote: diff --git a/src/mpid/ch3/channels/nemesis/netmod/mxm/mxm_poll.c b/src/mpid/ch3/channels/nemesis/netmod/mxm/mxm_poll.c index e8bddc3..752a1f9 100644 --- a/src/mpid/ch3/channels/nemesis/netmod/mxm/mxm_poll.c +++ b/src/mpid/ch3/channels/nemesis/netmod/mxm/mxm_poll.c @@ -482,8 +482,8 @@ static int _mxm_process_rdtype(MPID_Request ** rreq_p, MPI_Datatype datatype, *iov_count = n_iov; } else { - int packsize = 0; - MPIR_Pack_size_impl(rreq->dev.user_count, rreq->dev.datatype, (MPI_Aint *) & packsize); + MPI_Aint packsize = 0; + MPIR_Pack_size_impl(rreq->dev.user_count, rreq->dev.datatype, &packsize); rreq->dev.tmpbuf = MPIU_Malloc((size_t) packsize); MPIU_Assert(rreq->dev.tmpbuf); rreq->dev.tmpbuf_sz = packsize; diff --git a/src/mpid/ch3/channels/nemesis/netmod/newmad/newmad_poll.c b/src/mpid/ch3/channels/nemesis/netmod/newmad/newmad_poll.c index 2dba872..5a32515 100644 --- a/src/mpid/ch3/channels/nemesis/netmod/newmad/newmad_poll.c +++ b/src/mpid/ch3/channels/nemesis/netmod/newmad/newmad_poll.c @@ -575,7 +575,7 @@ int MPID_nem_newmad_process_rdtype(MPID_Request **rreq_p, MPID_Datatype * dt_ptr } else { - int packsize = 0; + MPI_Aint packsize = 0; MPIR_Pack_size_impl(rreq->dev.user_count, rreq->dev.datatype, &packsize); rreq->dev.tmpbuf = MPIU_Malloc((size_t) packsize); MPIU_Assert(rreq->dev.tmpbuf); _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-ibm] [mpich-discuss] Problem with MPICH3/OpenPA on IBM P755
by Rob Latham 02 Dec '14

02 Dec '14

On 12/02/2014 05:11 PM, Sameh S Sharkawi wrote: > I am not familiar with OPA but I can point out couple of issues here: > > 1 - PAMI installed on the system which seems to be 1.2, "may not" be > compatible with MPICH3 code. MPICH3 is only supported on 1.4 and above > and only for Linux > 2 - --with-file-system=bg+bglockless is definitely the wrong option for > this machine. I would try nfs+ufs > If this machine has GPFS, then use the new 3.x style: --with-file-system=gpfs:PE ==rob _______________________________________________ ibm mailing list ibm(a)lists.mpich.org https://lists.mpich.org/mailman/listinfo/ibm

1 0

Re: [mpich-ibm] [mpich-discuss] Problem with MPICH3/OpenPA on IBM P755
by Sameh S Sharkawi 02 Dec '14

02 Dec '14

I am not familiar with OPA but I can point out couple of issues here: 1 - PAMI installed on the system which seems to be 1.2, "may not" be compatible with MPICH3 code. MPICH3 is only supported on 1.4 and above and only for Linux 2 - --with-file-system=bg+bglockless is definitely the wrong option for this machine. I would try nfs+ufs Thanks Sameh |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Balaji, Pavan" <balaji(a)anl.gov> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"discuss(a)mpich.org" <discuss(a)mpich.org> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Cc: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"ibm(a)lists.mpich.org" <ibm(a)lists.mpich.org> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |11/27/2014 09:12 AM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Re: [mpich-ibm] [mpich-discuss] Problem with MPICH3/OpenPA on IBM P755 | >--------------------------------------------------------------------------------------------------------------------------------------------------| Hmm. That's not a good sign. OPA's configure seems to think that it can use some inbuilt atomic capability while the compiler/hardware is clearly not supporting it. Can you send us the OPA config.log (src/openpa/config.log) so we can look into it? Also cc'ed the IBM folks. IBM folks, any thoughts? -- Pavan > On Nov 27, 2014, at 6:11 AM, Victor Vysotskiy <victor.vysotskiy(a)teokem.lu.se> wrote: > > Hi, > > I am trying to compile the latest ('v3.2a2-24-g4ad367d0') nightly snapshot on the IBM P775 machine. The MPICH3 is configured with the following options: > > export OBJECT_MODE=64 > ./configure --enable-f77 --enable-fc --enable-cxx --enable-smpcoll --with-thread-package=pthreads --with-pami=/opt/ibmhpc/pecurrent/ppe.pami --with-pami-lib=/opt/ibmhpc/pecurrent/ppe.pami/lib --with-pami-include=/opt/ibmhpc/pecurrent/ppe.pami/include64 --enable-mpe --enable-error-messages=all CC="xlc_r -q64 -qmaxmem=-1" CPP=/usr/ccs/lib/cpp CXX="xlC_r -q64 -qmaxmem=-1" F77="xlf_r -q64 -qmaxmem=-1" FC="xlf90_r -q64 -qmaxmem=-1" CFLAGS="-q64 -qmaxmem=-1" CXXFLAGS="-q64 -qmaxmem=-1" FCFLAGS="-qmaxmem=-1 -q64" FFLAGS="-q64 -qmaxmem=-1" OBJECT_MODE=64 AR="ar -X 64" --with-file-system=bg +bglockless > > No problem with compiling it, but there is a problem with running OpenPA tests: > > Testing simple integer load-linked/store-conditional functionality -SKIP- > LL/SC not available > Testing simple pointer load-linked/store-conditional functionality -SKIP- > LL/SC not available > Testing integer LL/SC ABA -SKIP- > LL/SC not available > Testing pointer LL/SC ABA -SKIP- > LL/SC not available > Testing integer load/store with 1 thread *FAILED* > at test_primitives.c:371 in test_threaded_loadstore_int()... > Testing pointer load/store with 1 thread *FAILED* > at test_primitives.c:556 in test_threaded_loadstore_ptr()... > Testing add with 1 thread *FAILED* > at test_primitives.c:750 in test_threaded_add()... > Testing incr and decr with 1 thread PASSED > Testing decr and test with 1 thread *FAILED* > at test_primitives.c:1093 in test_threaded_decr_and_test()... > Testing fetch and add with 1 thread *FAILED* > at test_primitives.c:1344 in test_threaded_faa()... > Testing fetch and add return values with 1 thread *FAILED* > at test_primitives.c:1490 in test_threaded_faa_ret()... > Testing fetch and incr/decr with 1 thread PASSED > Testing fetch and incr return values with 1 thread *FAILED* > at test_primitives.c:1796 in test_threaded_fai_ret()... > Testing fetch and decr return values with 1 thread *FAILED* > at test_primitives.c:1953 in test_threaded_fad_ret()... > Testing integer compare-and-swap with 1 thread *FAILED* > at test_primitives.c:2191 in test_threaded_cas_int()... > Testing pointer compare-and-swap with 1 thread *FAILED* > at test_primitives.c:2346 in test_threaded_cas_ptr()... > Testing grouped integer compare-and-swap with 1 thread *FAILED* > at test_primitives.c:2506 in test_grouped_cas_int()... > Testing grouped pointer compare-and-swap with 1 thread *FAILED* > at test_primitives.c:2683 in test_grouped_cas_ptr()... > Testing integer compare-and-swap fairness with 1 thread *FAILED* > at test_primitives.c:2890 in test_threaded_cas_int_fairness()... > Testing pointer compare-and-swap fairness with 1 thread *FAILED* > at test_primitives.c:3087 in test_threaded_cas_ptr_fairness()... > Testing integer swap with 1 thread *FAILED* > at test_primitives.c:3341 in test_threaded_swap_int()... > Testing pointer swap with 1 thread *FAILED* > at test_primitives.c:3496 in test_threaded_swap_ptr()... > Testing integer LL/SC stack -SKIP- > LL/SC not available > Testing pointer LL/SC stack -SKIP- > LL/SC not available > Testing integer LL/SC stack -SKIP- > LL/SC not available > Testing pointer LL/SC stack -SKIP- > LL/SC not available > Testing integer LL/SC stack -SKIP- > LL/SC not available > Testing pointer LL/SC stack -SKIP- > LL/SC not available > Testing integer LL/SC stack -SKIP- > LL/SC not available > Testing pointer LL/SC stack -SKIP- > LL/SC not available > ***** 16 PRIMITIVES TESTS FAILED! ***** > > Apparently, a bunch of tests failed. Is there anything to worry about? Or, I can simply skip these failed test and can use the compiled MPICH3 for production? > > The software stack used: > AIX v7.1.0.0 > XLC/XLF compiler v14.01.0000.0008 > POE v1-1.2.0.3 > > Best, > Victor. > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji _______________________________________________ ibm mailing list ibm(a)lists.mpich.org https://lists.mpich.org/mailman/listinfo/ibm _______________________________________________ ibm mailing list ibm(a)lists.mpich.org https://lists.mpich.org/mailman/listinfo/ibm

1 0

Re: [mpich-discuss] mpich run error
by Bland, Wesley B. 01 Dec '14

01 Dec '14

It appears that you need to start at the beginning to get some of the basics of MPI. This mailing isn’t a good forum to teach you everything you need to know, but there are great tutorials all over the web to help you out. One of my favorites for some of the most beginner topics is: http://mpitutorial.com Check that out and see if it helps with your problems. I’d also recommend the “Using MPI” series of books. Thanks, Wesley On Nov 29, 2014, at 10:00 PM, نازنین <nazanin.mirshokraei(a)gmail.com<mailto:[email protected]>> wrote: please give me more detail . you mean to compile mpich-3.0.4 with what flags? ./configure --prefix=/home/nazanin/program_install/mpich-3.0.4 make make install do u mean to add another flag to the command ? thanks nazi On Sat, Nov 29, 2014 at 8:53 AM, Junchao Zhang <jczhang(a)mcs.anl.gov<mailto:[email protected]>> wrote: Try to compile your program with mpicc or mpicxx On Nov 29, 2014 8:15 AM, "نازنین" <nazanin.mirshokraei(a)gmail.com<mailto:[email protected]>> wrote: thank u for your reply .... can you please tell me what is the reason? it is my first time running a mpi .... i compiled a program with cpp which tells to use : export USE_MPI=on # distributed-memory parallelism export USE_MPIF90=on # compile with mpif90 script export which_MPI=mpich # compile with MPICH library #export which_MPI=mpich2 # compile with MPICH2 library # export which_MPI=openmpi # compile with OpenMPI library #export USE_OpenMP=on # shared-memory parallelism # export FORT=ifort export FORT=gfortran #export FORT=pgi #export USE_DEBUG= # use Fortran debugging flags export USE_LARGE=on # activate 64-bit compilation #export USE_NETCDF4=on # compile with NetCDF-4 library #export USE_PARALLEL_IO=on # Parallel I/O with Netcdf-4/HDF5 #export USE_MY_LIBS=on # use my library paths below and then it gives me a file(coawstM) and the manual tells me to run that file in this way : mpirun -np 2 ./coawstM swan_only.in<http://swan_only.in/> what will be the reason? is it because mpich was not compiled truely or the coawstM is not working for a reason? thank you On Sat, Nov 29, 2014 at 6:07 AM, Junchao Zhang <jczhang(a)mcs.anl.gov<mailto:[email protected]>> wrote: As indicated by the message, you passed an invalid communicator to MPI_Comm_rank() in your program. --Junchao Zhang On Sat, Nov 29, 2014 at 4:32 AM, نازنین <nazanin.mirshokraei(a)gmail.com<mailto:[email protected]>> wrote: hi does any one know about this error : Fatal error in PMPI_Comm_rank: Invalid communicator, error stack: PMPI_Comm_rank(108): MPI_Comm_rank(comm=0x0, rank=0x7fff24a405bc) failed PMPI_Comm_rank(66).: Invalid communicator Fatal error in PMPI_Comm_rank: Invalid communicator, error stack: PMPI_Comm_rank(108): MPI_Comm_rank(comm=0x0, rank=0x7fff63e1598c) failed PMPI_Comm_rank(66).: Invalid communicator it is when i run mpich like : mpirun -np 2 ./coawstM swan_only.in<http://swan_only.in/> i don't know if this is a problem in my executable file (coawstM) or this is from mpich or any other hardware issues or anything else thank you for your help nazi _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0