- discuss - mailman3.cels.anl.gov

[PATCH] test: add attrdeleteget, MPI_Attr_get called from delete_fn
by Jed Brown 17 May '13

17 May '13

MS-MPI 64-bit from HPC Pack 2008 and 2012 errors when MPI_Attr_get is called from delete_fn on a communicator obtained from MPI_Comm_split. Signed-off-by: Jed Brown <jedbrown(a)mcs.anl.gov> Signed-off-by: Satish Balay <balay(a)mcs.anl.gov> --- This represents a reduced test case from a reported PETSc error when using split communicators on MS-MPI. PETSc uses a reference-counted "inner" communicator to manage tags between objects. When the user destroys the outer communicator, the inner communicator must be detached to avoid holding a dangling reference. I'm submitting this bug report as a patch to MPICH in hopes that it makes it downstream to Microsoft and other vendors so that this problem does not occur again. test/mpi/.gitignore | 1 + test/mpi/attr/Makefile.am | 1 + test/mpi/attr/attrdeleteget.c | 37 +++++++++++++++++++++++++++++++++++++ test/mpi/attr/testlist | 1 + 4 files changed, 40 insertions(+) create mode 100644 test/mpi/attr/attrdeleteget.c diff --git a/test/mpi/.gitignore b/test/mpi/.gitignore index 3aadba2..0bdcd15 100644 --- a/test/mpi/.gitignore +++ b/test/mpi/.gitignore @@ -51,6 +51,7 @@ /attr/attrerr /attr/attrerrcomm /attr/attrerrtype +/attr/attrdeleteget /attr/attric /attr/attrorder /attr/attrordercomm diff --git a/test/mpi/attr/Makefile.am b/test/mpi/attr/Makefile.am index a672192..e1d788b 100644 --- a/test/mpi/attr/Makefile.am +++ b/test/mpi/attr/Makefile.am @@ -18,6 +18,7 @@ noinst_PROGRAMS = \ attrerr \ attrerrcomm \ attrerrtype \ + attrdeleteget \ attr2type \ attrorder \ attrordercomm \ diff --git a/test/mpi/attr/attrdeleteget.c b/test/mpi/attr/attrdeleteget.c new file mode 100644 index 0000000..7ed66d0 --- /dev/null +++ b/test/mpi/attr/attrdeleteget.c @@ -0,0 +1,37 @@ +/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */ +/* + * + * (C) 2013 by Argonne National Laboratory. + * See COPYRIGHT in top-level directory. + */ + +#include <stdio.h> +#include "mpi.h" +#include "mpitest.h" + +int key = MPI_KEYVAL_INVALID; +char a[100]; + +int delete_fn (MPI_Comm, int, void *, void *); + +int main(int argc,char **argv) +{ + MPI_Comm scomm; + + MTest_Init(&argc,&argv); + MPI_Comm_split(MPI_COMM_WORLD,1,0,&scomm); + MPI_Keyval_create(MPI_NULL_COPY_FN,delete_fn,&key,(void*)0); + MPI_Attr_put(scomm,key,a); + MPI_Comm_free(&scomm); + MPI_Finalize(); + return 0; +} + +int delete_fn(MPI_Comm comm,int keyval,void *attr_val,void *extra_state) +{ + int flg; + void *ptr; + + MPI_Attr_get(comm,key,&ptr,&flg); + return MPI_SUCCESS; +} diff --git a/test/mpi/attr/testlist b/test/mpi/attr/testlist index 61bd613..4db94df 100644 --- a/test/mpi/attr/testlist +++ b/test/mpi/attr/testlist @@ -7,6 +7,7 @@ attrend2 1 attrend2 5 attrerrcomm 1 attrerrtype 1 +attrdeleteget 1 attr2type 1 attrorder 1 attrordercomm 1 -- 1.8.2.3

1 0

[PATCH] config: change PAC_FUNC_NEEDS_DECL to check by assignment
by Jed Brown 17 May '13

17 May '13

The old method attempts to create a failed compile when the function *is* already declared, by creating an incompatible declaration. That is insufficient with clang-3.2, which only warns in case of incompatible redeclaration of a library function: conftest.c:44:5: warning: incompatible redeclaration of library function 'strncmp' int strncmp(double, int, double, const char *); ^ /usr/include/string.h:143:12: note: 'strncmp' is a builtin with type 'int (const char *, const char *, size_t)' extern int strncmp (const char *__s1, const char *__s2, size_t __n) ^ 1 warning generated. Instead, we take the opposite approach, generating a failed compile when the library function has *not* been declared in the header. void (*fptr)(void) = (void(*)(void))strncmp; Signed-off-by: Jed Brown <jedbrown(a)mcs.anl.gov> --- confdb/aclocal_cc.m4 | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/confdb/aclocal_cc.m4 b/confdb/aclocal_cc.m4 index 7a92a8a..10964e1 100644 --- a/confdb/aclocal_cc.m4 +++ b/confdb/aclocal_cc.m4 @@ -1205,25 +1205,22 @@ dnl Sets 'NEEDS_<funcname>_DECL' if 'funcname' is not declared by the dnl headerfiles. dnl dnl Approach: -dnl Try to compile a program with the function, but passed with an incorrect -dnl calling sequence. If the compilation fails, then the declaration -dnl is provided within the header files. If the compilation succeeds, -dnl the declaration is required. +dnl Attempt to assign library function to function pointer. If the function +dnl is not declared in a header, this will fail. Use a non-static global so +dnl the compiler does not warn about an unused variable. dnl -dnl We use a 'double' as the first argument to try and catch varargs -dnl routines that may use an int or pointer as the first argument. +dnl Simply calling the function is not enough because C89 compilers allow +dnl calls to implicitly-defined functions. Re-declaring a library function +dnl with an incompatible prototype is also not sufficient because some +dnl compilers (notably clang-3.2) only produce a warning in this case. dnl -dnl There is one difficulty - if the compiler has been instructed to -dnl fail on implicitly defined functions, then this test will always -dnl fail. -dnl dnl D*/ AC_DEFUN([PAC_FUNC_NEEDS_DECL],[ AC_CACHE_CHECK([whether $2 needs a declaration], pac_cv_func_decl_$2,[ AC_TRY_COMPILE([$1 -int $2(double, int, double, const char *);],[int a=$2(1.0,27,1.0,"foo");], -pac_cv_func_decl_$2=yes,pac_cv_func_decl_$2=no)]) +void (*fptr)(void) = (void(*)(void))$2;],[], +pac_cv_func_decl_$2=no,pac_cv_func_decl_$2=yes)]) if test "$pac_cv_func_decl_$2" = "yes" ; then changequote(<<,>>)dnl define(<<PAC_FUNC_NAME>>, translit(NEEDS_$2_DECL, [a-z *], [A-Z__]))dnl -- 1.8.2.3

1 0

Re: [mpich-discuss] mpich 3.0.4 build fails on OS X Mountain lion
by Jeff Hammond 15 May '13

15 May '13

Well, assuming that the problem you see is the same as is discussed on that website, you can: (1) --disable-shared (2) use llvm-gcc instead of clang (3) upgrade to Xcode 4.5.2+ Jeff On Wed, May 15, 2013 at 11:42 AM, Mathieu MORLIGHEM <Mathieu.Morlighem(a)uci.edu> wrote: > Hi Jeff, > > thanks for the link, I will try it. Does this mean that I cannot build shared libs? > Also, this workaround is for mpich2, and the compilation with --enable-shared of mpich2 (version 1.5) works well on my machine, I tried it again this morning… > > Thanks > Mathieu > > On May 15, 2013, at 9:33 AM, Jeff Hammond <jhammond(a)alcf.anl.gov> wrote: > >> I recall that this was addressed a month or two ago on this list but I >> can't find the direct reference. I can, however, point you to >> https://github.com/mxcl/homebrew/pull/16299, which explains the >> details and how you can work around it. >> >> Jeff >> >> On Wed, May 15, 2013 at 11:28 AM, Mathieu MORLIGHEM >> <Mathieu.Morlighem(a)uci.edu> wrote: >>> Hello, >>> >>> I am trying to compile mpich 3.0.4 on my machine: >>> >>> uname -a >>> Darwin shackleton.ess.uci.edu 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan >>> 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64 >>> >>> I successfully installed mpich 1.5 several times with the following options: >>> ./configure --prefix="$ISSM_DIR/externalpackages/mpich2/install" >>> --enable-shared >>> >>> However, with the same options, the build of mpich 3.0.4 at linking with a >>> segmentation fault: >>> >>> Making all in . >>> make[3]: Nothing to be done for `all-am'. >>> Making all in . >>> GEN lib/libmpich.la >>> collect2: ld terminated with signal 11 [Segmentation fault: 11] >>> make[2]: *** [lib/libmpich.la] Error 1 >>> make[1]: *** [all-recursive] Error 1 >>> make: *** [all] Error 2 >>> >>> with VERBOSE=1: >>> /bin/sh ./libtool --tag=F77 --mode=link gfortran -O2 -L./src/mpl >>> -L./src/openpa/src -version-info 10:4:0 -Wl,-flat_namespace -o >>> lib/libmpich.la -rpath >>> /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/install/lib >>> src/mpi/attr/attrutil.lo src/mpi/attr/dup_fn.lo src/mpi/coll/allred_group.lo >>> src/mpi/coll/barrier_group.lo ………… src/mpi_t/.libs/pvar_stop.o >>> src/mpi_t/.libs/pvar_write.o src/binding/f77/.libs/setbot.o >>> src/binding/f77/.libs/setbotf.o >>> -Wl,-force_load,src/mpi/romio/.libs/libromio.a >>> -Wl,-force_load,src/mpi/romio/.libs/libpromio.a -L./src/mpl >>> -L./src/openpa/src >>> /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/src/src/mpl/.libs/libmpl.dylib >>> /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/src/src/openpa/src/.libs/libopa.dylib >>> -lpthread -O2 -Wl,-flat_namespace -install_name >>> /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/install/lib/libmpich.10.dylib >>> -compatibility_version 11 -current_version 11.4 -Wl,-single_module >>> collect2: ld terminated with signal 11 [Segmentation fault: 11] >>> make[2]: *** [lib/libmpich.la] Error 1 >>> make[1]: *** [all-recursive] Error 1 >>> make: *** [all] Error 2 >>> >>> Has anybody reported a similar issue? Do you think this is a problem with >>> libtool? >>> Thanks a lot for your help >>> >>> -- >>> Mathieu Morlighem >>> >>> Assistant Project Scientist >>> Department of Earth System Science >>> University of California, Irvine >>> >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> -- >> Jeff Hammond >> Argonne Leadership Computing Facility >> University of Chicago Computation Institute >> jhammond(a)alcf.anl.gov / (630) 252-5381 >> http://www.linkedin.com/in/jeffhammond >> https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond >> ALCF docs: http://www.alcf.anl.gov/user-guides >> _______________________________________________ >> 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 -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

Re: [mpich-discuss] mpich 3.0.4 build fails on OS X Mountain lion
by Mathieu MORLIGHEM 15 May '13

15 May '13

Hi Jeff, thanks for the link, I will try it. Does this mean that I cannot build shared libs? Also, this workaround is for mpich2, and the compilation with --enable-shared of mpich2 (version 1.5) works well on my machine, I tried it again this morning… Thanks Mathieu On May 15, 2013, at 9:33 AM, Jeff Hammond <jhammond(a)alcf.anl.gov> wrote: > I recall that this was addressed a month or two ago on this list but I > can't find the direct reference. I can, however, point you to > https://github.com/mxcl/homebrew/pull/16299, which explains the > details and how you can work around it. > > Jeff > > On Wed, May 15, 2013 at 11:28 AM, Mathieu MORLIGHEM > <Mathieu.Morlighem(a)uci.edu> wrote: >> Hello, >> >> I am trying to compile mpich 3.0.4 on my machine: >> >> uname -a >> Darwin shackleton.ess.uci.edu 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan >> 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64 >> >> I successfully installed mpich 1.5 several times with the following options: >> ./configure --prefix="$ISSM_DIR/externalpackages/mpich2/install" >> --enable-shared >> >> However, with the same options, the build of mpich 3.0.4 at linking with a >> segmentation fault: >> >> Making all in . >> make[3]: Nothing to be done for `all-am'. >> Making all in . >> GEN lib/libmpich.la >> collect2: ld terminated with signal 11 [Segmentation fault: 11] >> make[2]: *** [lib/libmpich.la] Error 1 >> make[1]: *** [all-recursive] Error 1 >> make: *** [all] Error 2 >> >> with VERBOSE=1: >> /bin/sh ./libtool --tag=F77 --mode=link gfortran -O2 -L./src/mpl >> -L./src/openpa/src -version-info 10:4:0 -Wl,-flat_namespace -o >> lib/libmpich.la -rpath >> /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/install/lib >> src/mpi/attr/attrutil.lo src/mpi/attr/dup_fn.lo src/mpi/coll/allred_group.lo >> src/mpi/coll/barrier_group.lo ………… src/mpi_t/.libs/pvar_stop.o >> src/mpi_t/.libs/pvar_write.o src/binding/f77/.libs/setbot.o >> src/binding/f77/.libs/setbotf.o >> -Wl,-force_load,src/mpi/romio/.libs/libromio.a >> -Wl,-force_load,src/mpi/romio/.libs/libpromio.a -L./src/mpl >> -L./src/openpa/src >> /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/src/src/mpl/.libs/libmpl.dylib >> /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/src/src/openpa/src/.libs/libopa.dylib >> -lpthread -O2 -Wl,-flat_namespace -install_name >> /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/install/lib/libmpich.10.dylib >> -compatibility_version 11 -current_version 11.4 -Wl,-single_module >> collect2: ld terminated with signal 11 [Segmentation fault: 11] >> make[2]: *** [lib/libmpich.la] Error 1 >> make[1]: *** [all-recursive] Error 1 >> make: *** [all] Error 2 >> >> Has anybody reported a similar issue? Do you think this is a problem with >> libtool? >> Thanks a lot for your help >> >> -- >> Mathieu Morlighem >> >> Assistant Project Scientist >> Department of Earth System Science >> University of California, Irvine >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > Argonne Leadership Computing Facility > University of Chicago Computation Institute > jhammond(a)alcf.anl.gov / (630) 252-5381 > http://www.linkedin.com/in/jeffhammond > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > ALCF docs: http://www.alcf.anl.gov/user-guides > _______________________________________________ > 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] mpich 3.0.4 build fails on OS X Mountain lion
by Jeff Hammond 15 May '13

15 May '13

I recall that this was addressed a month or two ago on this list but I can't find the direct reference. I can, however, point you to https://github.com/mxcl/homebrew/pull/16299, which explains the details and how you can work around it. Jeff On Wed, May 15, 2013 at 11:28 AM, Mathieu MORLIGHEM <Mathieu.Morlighem(a)uci.edu> wrote: > Hello, > > I am trying to compile mpich 3.0.4 on my machine: > > uname -a > Darwin shackleton.ess.uci.edu 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan > 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64 > > I successfully installed mpich 1.5 several times with the following options: > ./configure --prefix="$ISSM_DIR/externalpackages/mpich2/install" > --enable-shared > > However, with the same options, the build of mpich 3.0.4 at linking with a > segmentation fault: > > Making all in . > make[3]: Nothing to be done for `all-am'. > Making all in . > GEN lib/libmpich.la > collect2: ld terminated with signal 11 [Segmentation fault: 11] > make[2]: *** [lib/libmpich.la] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > > with VERBOSE=1: > /bin/sh ./libtool --tag=F77 --mode=link gfortran -O2 -L./src/mpl > -L./src/openpa/src -version-info 10:4:0 -Wl,-flat_namespace -o > lib/libmpich.la -rpath > /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/install/lib > src/mpi/attr/attrutil.lo src/mpi/attr/dup_fn.lo src/mpi/coll/allred_group.lo > src/mpi/coll/barrier_group.lo ………… src/mpi_t/.libs/pvar_stop.o > src/mpi_t/.libs/pvar_write.o src/binding/f77/.libs/setbot.o > src/binding/f77/.libs/setbotf.o > -Wl,-force_load,src/mpi/romio/.libs/libromio.a > -Wl,-force_load,src/mpi/romio/.libs/libpromio.a -L./src/mpl > -L./src/openpa/src > /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/src/src/mpl/.libs/libmpl.dylib > /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/src/src/openpa/src/.libs/libopa.dylib > -lpthread -O2 -Wl,-flat_namespace -install_name > /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/install/lib/libmpich.10.dylib > -compatibility_version 11 -current_version 11.4 -Wl,-single_module > collect2: ld terminated with signal 11 [Segmentation fault: 11] > make[2]: *** [lib/libmpich.la] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > > Has anybody reported a similar issue? Do you think this is a problem with > libtool? > Thanks a lot for your help > > -- > Mathieu Morlighem > > Assistant Project Scientist > Department of Earth System Science > University of California, Irvine > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

mpich 3.0.4 build fails on OS X Mountain lion
by Mathieu MORLIGHEM 15 May '13

15 May '13

Hello, I am trying to compile mpich 3.0.4 on my machine: uname -a Darwin shackleton.ess.uci.edu 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64 I successfully installed mpich 1.5 several times with the following options: ./configure --prefix="$ISSM_DIR/externalpackages/mpich2/install" --enable-shared However, with the same options, the build of mpich 3.0.4 at linking with a segmentation fault: Making all in . make[3]: Nothing to be done for `all-am'. Making all in . GEN lib/libmpich.la collect2: ld terminated with signal 11 [Segmentation fault: 11] make[2]: *** [lib/libmpich.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 with VERBOSE=1: /bin/sh ./libtool --tag=F77 --mode=link gfortran -O2 -L./src/mpl -L./src/openpa/src -version-info 10:4:0 -Wl,-flat_namespace -o lib/libmpich.la -rpath /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/install/lib src/mpi/attr/attrutil.lo src/mpi/attr/dup_fn.lo src/mpi/coll/allred_group.lo src/mpi/coll/barrier_group.lo ………… src/mpi_t/.libs/pvar_stop.o src/mpi_t/.libs/pvar_write.o src/binding/f77/.libs/setbot.o src/binding/f77/.libs/setbotf.o -Wl,-force_load,src/mpi/romio/.libs/libromio.a -Wl,-force_load,src/mpi/romio/.libs/libpromio.a -L./src/mpl -L./src/openpa/src /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/src/src/mpl/.libs/libmpl.dylib /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/src/src/openpa/src/.libs/libopa.dylib -lpthread -O2 -Wl,-flat_namespace -install_name /Users/mmorligh/Desktop/issmuci/trunk-jpl/externalpackages/mpich/install/lib/libmpich.10.dylib -compatibility_version 11 -current_version 11.4 -Wl,-single_module collect2: ld terminated with signal 11 [Segmentation fault: 11] make[2]: *** [lib/libmpich.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Has anybody reported a similar issue? Do you think this is a problem with libtool? Thanks a lot for your help -- Mathieu Morlighem Assistant Project Scientist Department of Earth System Science University of California, Irvine

1 0

Re: [mpich-discuss] Error in dynamically spawned processes
by Antonio J. Peña 15 May '13

15 May '13

Hi, We would need more information to determine if this error is caused by an MPICH bug. Could you please post the code which is failing along with some sample input for both failing and non-failing cases? Thanks, Antonio On Wednesday, May 15, 2013 07:19:59 PM Mahesh Doijade wrote: Hi, I am dynamic creating process using MPI_Comm_spawn_multiple(), the code runs for several inputs without any error but for some larger input size it is throwing this error as given below. Fatal error in PMPI_Barrier: A process has failed, error stack: PMPI_Barrier(426).........: MPI_Barrier(comm=0x84000002) failed MPIR_Barrier_impl(333)....: Failure during collective MPIR_Barrier_impl(315)....: MPIR_Barrier_intra(83)....: dequeue_and_set_error(823): Communication error with rank 0 =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = EXIT CODE: 1 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES =================================================================================== [proxy:1:0@clusterslave3] HYD_pmcd_pmip_control_cmd_cb (./pm/pmiserv/pmip_cb.c:883): assert (!closed) failed [proxy:1:0@clusterslave3] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status [proxy:1:0@clusterslave3] main (./pm/pmiserv/pmip.c:210): demux engine error waiting for event [mpiexec@clusterslave3] HYDT_bscu_wait_for_completion (./tools/bootstrap/utils/bscu_wait.c:76): one of the processes terminated badly; aborting [mpiexec@clusterslave3] HYDT_bsci_wait_for_completion (./tools/bootstrap/src/bsci_wait.c:23): launcher returned error waiting for completion [mpiexec@clusterslave3] HYD_pmci_wait_for_completion (./pm/pmiserv/pmiserv_pmci.c:216): launcher returned error waiting for completion [mpiexec@clusterslave3] main (./ui/mpich/mpiexec.c:325): process manager error waiting for completion -- Regards, -- Mahesh Doijade

1 0

Error in dynamically spawned processes
by Mahesh Doijade 15 May '13

15 May '13

Hi, I am dynamic creating process using MPI_Comm_spawn_multiple(), the code runs for several inputs without any error but for some larger input size it is throwing this error as given below. Fatal error in PMPI_Barrier: A process has failed, error stack: PMPI_Barrier(426).........: MPI_Barrier(comm=0x84000002) failed MPIR_Barrier_impl(333)....: Failure during collective MPIR_Barrier_impl(315)....: MPIR_Barrier_intra(83)....: dequeue_and_set_error(823): Communication error with rank 0 =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = EXIT CODE: 1 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES =================================================================================== [proxy:1:0@clusterslave3] HYD_pmcd_pmip_control_cmd_cb (./pm/pmiserv/pmip_cb.c:883): assert (!closed) failed [proxy:1:0@clusterslave3] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status [proxy:1:0@clusterslave3] main (./pm/pmiserv/pmip.c:210): demux engine error waiting for event [mpiexec@clusterslave3] HYDT_bscu_wait_for_completion (./tools/bootstrap/utils/bscu_wait.c:76): one of the processes terminated badly; aborting [mpiexec@clusterslave3] HYDT_bsci_wait_for_completion (./tools/bootstrap/src/bsci_wait.c:23): launcher returned error waiting for completion [mpiexec@clusterslave3] HYD_pmci_wait_for_completion (./pm/pmiserv/pmiserv_pmci.c:216): launcher returned error waiting for completion [mpiexec@clusterslave3] main (./ui/mpich/mpiexec.c:325): process manager error waiting for completion -- Regards, -- Mahesh Doijade

1 0

Re: [mpich-discuss] sizeof() usage inconsistencies in pm/hydra/utils/sock/sock.c
by Yauheni Zelenko 14 May '13

14 May '13

Thank you for taking care! Sure, it's not error, so I was in doubt :-) Eugene. ________________________________________ From: Pavan Balaji [balaji(a)mcs.anl.gov] Sent: Tuesday, May 14, 2013 6:09 PM To: discuss(a)mpich.org Cc: Yauheni Zelenko Subject: Re: [mpich-discuss] sizeof() usage inconsistencies in pm/hydra/utils/sock/sock.c Yup, thanks. I've created a ticket for it. https://trac.mpich.org/projects/mpich/ticket/1851 Btw, I've created an account for you on our trac page. For parts that are clearly errors, please feel free to create tickets directly. When in doubt, discuss(a)mpich.org is the right list to send questions to. -- Pavan On 05/14/2013 07:56 PM US Central Time, Yauheni Zelenko wrote: > Hi! > > sizeof() is used inconsistently in pm/hydra/utils/sock/sock.c. In some places this is size of type, in some - size of variable. > > Sure, it's not major problem, but I think will be good idea to improve code. > > Eugene. > _______________________________________________ > 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

1 0

Re: [mpich-discuss] sizeof() usage inconsistencies in pm/hydra/utils/sock/sock.c
by Pavan Balaji 14 May '13

14 May '13

Yup, thanks. I've created a ticket for it. https://trac.mpich.org/projects/mpich/ticket/1851 Btw, I've created an account for you on our trac page. For parts that are clearly errors, please feel free to create tickets directly. When in doubt, discuss(a)mpich.org is the right list to send questions to. -- Pavan On 05/14/2013 07:56 PM US Central Time, Yauheni Zelenko wrote: > Hi! > > sizeof() is used inconsistently in pm/hydra/utils/sock/sock.c. In some places this is size of type, in some - size of variable. > > Sure, it's not major problem, but I think will be good idea to improve code. > > Eugene. > _______________________________________________ > 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

1 0