January 2015 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Threaded Listener
by Jeff Hammond 17 Jan '15

17 Jan '15

How do you create processes on this system? If you are using an MPI implementation that has a 1:1 mapping between MPI processes and OS processes, you've got to be able to create multiple processes somehow. Do you have any platform details you can share? Jeff On Sat, Jan 17, 2015 at 11:46 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: > I tried to use a newer MPICH, but, as you said, Hydra forks as part of > mpiexec. Is it possible to launch a job without mpiexec/mpirun ? That should > probably work in my environment (assuming that there is no listener as a > heavy process as it is the case in the default mpich-1.2.7p1). > > The problem is not that the fork symbol is missing. The problem is that it > is been called. My environment actually has a dummy fork, but that only > causes the program to abort if it is called. > > So in summary, the problem is that I cannot use mpiexec to launch a program, > because it calls fork. In mpich-1.2.7p1 , I can launch myself the program as > if I was launching a debug (as in section 3.5.6 of the CH_P4 manual). In > addition, the mpich cannot issue a fork for a listener like task, only > threads. > > Eduardo > > On Sat, Jan 17, 2015 at 4:23 PM, Jeff Hammond <jeff.science(a)gmail.com> > wrote: >> >> MPICH shouldn't fork. Hydra probably uses fork to launch processes as part >> of mpiexec. >> >> Blue Gene doesn't support fork either and MPICH runs there, but the >> process launcher is not Hydra. Same for Cray last time I checked. So I'm >> sure that fork isn't required to use MPICH, at least if dynamic processes >> are not used. >> >> Is the issue that you cannot link an MPI program because the fork symbol >> is missing or that you cannot launch jobs with a Hydra? >> >> All mainstream MPI implementations use OS processes to implement MPI >> processes, but the standard doesn't require this. FG-MPI uses threads to >> implement MPI processes, but as it still uses Hydra (AFAIK), it may or may >> not work for you. >> >> Can you describe in detail what happens when you try to build and run >> MPICH-latest on your system? >> >> Jeff >> >> Sent from my iPhone >> >> On Jan 17, 2015, at 9:41 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: >> >> I would use a newer version if I could. However, I cannot issue a fork in >> my embedded environment. I can create threads though. >> >> So, is there any newer versions of mpich that does not create heavy >> processes? I can live without MPI_Spawn and the like. >> >> Regards, >> >> Eduardo >> >> On Jan 16, 2015 5:42 PM, "Wesley Bland" <wbland(a)anl.gov> wrote: >>> >>> Can you try using a more recent version of MPICH. The version you are >>> using is years old and we don't support it anymore. Our latest version is >>> 3.1.3. You might see if the issue is still present there. >>> >>> Thanks, >>> Wesley >>> >>> On Fri, Jan 16, 2015 at 10:54 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: >>>> >>>> Hi, >>>> >>>> I am trying to compile and use mpich-1.2.7p1 with threaded listener >>>> (i.e. configured with --enable-threaded-listener). However, I cannot even >>>> run a simple mpi example with the resulting mpich. >>>> >>>> I need to use threaded listener because the environment I am compiling >>>> for (kind of embedded environment) does not have fork (no heavy processes). >>>> >>>> The error I get with the mpich with threaded listener is: >>>> >>>> rm_2889: 1103279872: p4_error: listener select: -1 >>>> p4_error: latest msg from perror: Bad file descriptor >>>> p0_2710: (2.097656) net_recv failed for fd = 5 >>>> p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 >>>> >>>> Has anyone experienced a similar problem? >>>> >>>> Thanks in advance, >>>> Eduardo >>> >>> >>> >>> _______________________________________________ >>> 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 >> >> >> _______________________________________________ >> 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 jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ 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] Threaded Listener
by Eduardo 17 Jan '15

17 Jan '15

I tried to use a newer MPICH, but, as you said, Hydra forks as part of mpiexec. Is it possible to launch a job without mpiexec/mpirun ? That should probably work in my environment (assuming that there is no listener as a heavy process as it is the case in the default mpich-1.2.7p1). The problem is not that the fork symbol is missing. The problem is that it is been called. My environment actually has a dummy fork, but that only causes the program to abort if it is called. So in summary, the problem is that I cannot use mpiexec to launch a program, because it calls fork. In mpich-1.2.7p1 , I can launch myself the program as if I was launching a debug (as in section 3.5.6 of the CH_P4 manual). In addition, the mpich cannot issue a fork for a listener like task, only threads. Eduardo On Sat, Jan 17, 2015 at 4:23 PM, Jeff Hammond <jeff.science(a)gmail.com> wrote: > MPICH shouldn't fork. Hydra probably uses fork to launch processes as part > of mpiexec. > > Blue Gene doesn't support fork either and MPICH runs there, but the > process launcher is not Hydra. Same for Cray last time I checked. So I'm > sure that fork isn't required to use MPICH, at least if dynamic processes > are not used. > > Is the issue that you cannot link an MPI program because the fork symbol > is missing or that you cannot launch jobs with a Hydra? > > All mainstream MPI implementations use OS processes to implement MPI > processes, but the standard doesn't require this. FG-MPI uses threads to > implement MPI processes, but as it still uses Hydra (AFAIK), it may or may > not work for you. > > Can you describe in detail what happens when you try to build and run > MPICH-latest on your system? > > Jeff > > Sent from my iPhone > > On Jan 17, 2015, at 9:41 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: > > I would use a newer version if I could. However, I cannot issue a fork in > my embedded environment. I can create threads though. > > So, is there any newer versions of mpich that does not create heavy > processes? I can live without MPI_Spawn and the like. > > Regards, > > Eduardo > On Jan 16, 2015 5:42 PM, "Wesley Bland" <wbland(a)anl.gov> wrote: > >> Can you try using a more recent version of MPICH. The version you are >> using is years old and we don't support it anymore. Our latest version is >> 3.1.3. You might see if the issue is still present there. >> >> Thanks, >> Wesley >> >> On Fri, Jan 16, 2015 at 10:54 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: >> >>> Hi, >>> >>> I am trying to compile and use mpich-1.2.7p1 with threaded listener >>> (i.e. configured with --enable-threaded-listener). However, I cannot even >>> run a simple mpi example with the resulting mpich. >>> >>> I need to use threaded listener because the environment I am compiling >>> for (kind of embedded environment) does not have fork (no heavy processes). >>> >>> The error I get with the mpich with threaded listener is: >>> >>> rm_2889: 1103279872: p4_error: listener select: -1 >>> p4_error: latest msg from perror: Bad file descriptor >>> p0_2710: (2.097656) net_recv failed for fd = 5 >>> p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 >>> >>> Has anyone experienced a similar problem? >>> >>> Thanks in advance, >>> Eduardo >>> >> >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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] Threaded Listener
by Jeff Hammond 17 Jan '15

17 Jan '15

MPICH shouldn't fork. Hydra probably uses fork to launch processes as part of mpiexec. Blue Gene doesn't support fork either and MPICH runs there, but the process launcher is not Hydra. Same for Cray last time I checked. So I'm sure that fork isn't required to use MPICH, at least if dynamic processes are not used. Is the issue that you cannot link an MPI program because the fork symbol is missing or that you cannot launch jobs with a Hydra? All mainstream MPI implementations use OS processes to implement MPI processes, but the standard doesn't require this. FG-MPI uses threads to implement MPI processes, but as it still uses Hydra (AFAIK), it may or may not work for you. Can you describe in detail what happens when you try to build and run MPICH-latest on your system? Jeff Sent from my iPhone > On Jan 17, 2015, at 9:41 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: > > I would use a newer version if I could. However, I cannot issue a fork in my embedded environment. I can create threads though. > > So, is there any newer versions of mpich that does not create heavy processes? I can live without MPI_Spawn and the like. > > Regards, > > Eduardo > >> On Jan 16, 2015 5:42 PM, "Wesley Bland" <wbland(a)anl.gov> wrote: >> Can you try using a more recent version of MPICH. The version you are using is years old and we don't support it anymore. Our latest version is 3.1.3. You might see if the issue is still present there. >> >> Thanks, >> Wesley >> >>> On Fri, Jan 16, 2015 at 10:54 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: >>> Hi, >>> >>> I am trying to compile and use mpich-1.2.7p1 with threaded listener (i.e. configured with --enable-threaded-listener). However, I cannot even run a simple mpi example with the resulting mpich. >>> >>> I need to use threaded listener because the environment I am compiling for (kind of embedded environment) does not have fork (no heavy processes). >>> >>> The error I get with the mpich with threaded listener is: >>> >>> rm_2889: 1103279872: p4_error: listener select: -1 >>> p4_error: latest msg from perror: Bad file descriptor >>> p0_2710: (2.097656) net_recv failed for fd = 5 >>> p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 >>> >>> Has anyone experienced a similar problem? >>> >>> Thanks in advance, >>> Eduardo >> >> >> _______________________________________________ >> 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 _______________________________________________ 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] Threaded Listener
by Eduardo 17 Jan '15

17 Jan '15

I would use a newer version if I could. However, I cannot issue a fork in my embedded environment. I can create threads though. So, is there any newer versions of mpich that does not create heavy processes? I can live without MPI_Spawn and the like. Regards, Eduardo On Jan 16, 2015 5:42 PM, "Wesley Bland" <wbland(a)anl.gov> wrote: > Can you try using a more recent version of MPICH. The version you are > using is years old and we don't support it anymore. Our latest version is > 3.1.3. You might see if the issue is still present there. > > Thanks, > Wesley > > On Fri, Jan 16, 2015 at 10:54 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: > >> Hi, >> >> I am trying to compile and use mpich-1.2.7p1 with threaded listener >> (i.e. configured with --enable-threaded-listener). However, I cannot even >> run a simple mpi example with the resulting mpich. >> >> I need to use threaded listener because the environment I am compiling >> for (kind of embedded environment) does not have fork (no heavy processes). >> >> The error I get with the mpich with threaded listener is: >> >> rm_2889: 1103279872: p4_error: listener select: -1 >> p4_error: latest msg from perror: Bad file descriptor >> p0_2710: (2.097656) net_recv failed for fd = 5 >> p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 >> >> Has anyone experienced a similar problem? >> >> Thanks in advance, >> Eduardo >> > > > _______________________________________________ > 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] bug report: MPI_LB and MPI_UB used in MPI_Type_create_subarray
by Thakur, Rajeev 16 Jan '15

16 Jan '15

I have created a ticket for this. http://trac.mpich.org/projects/mpich/ticket/2220 Rajeev On Jan 15, 2015, at 5:32 PM, Wei-keng Liao <wkliao(a)eecs.northwestern.edu> wrote: > After a discussion with Rajeev and Rob, we found that the deprecated MPI_LB and MPI_UB > markers are still being used in the implementation of MPI_Type_create_subarray() and/or darray. > These markers were mistakenly carried over in MPI_Type_create_struct() causing an incorrect > lower bound for the newly created datatype. A test program that can reproduce the error is > attached. Below is its description. > > The test program tries to concatenate two data types. > The first datatype is a contiguous space of 16 bytes at displacement 0. > The second is a subarray type at displacement 32, named bodytype created by MPI_Type_create_subarray(). > The global array is 5*nprocs integers and subarray is of size 5 integers. > > The two types were concatenated by MPI_Type_create_struct() to create > a new datatype named ftype. Here is the stdout for running it on 1 process. > > --- the stdout from both mpich and openmpi ---- > HEADER_EXTENT = 16 VAR_BEGIN = 32 > bodytype lb= 0 ub=20 extent=20 size=20 > ftype lb=32 ub=52 extent=20 size=36 true_lb= 0 true_extent=52 > > [ 0]: 0 1 2 3 8 9 10 11 12 5 > [10]: 6 7 8 13 14 15 16 17 10 11 > [20]: 12 13 18 19 20 21 22 > > Problems: > 1. ftype's lower bound should be 0. (mpich shows 32) > 2. ftype's extent should be 52. (mpich shows 20) > 3. packing 3 of ftypes to a contiguous array (27 integers) and its contents are incorrect. > ps. explicitly resizing ftype with lb=0 and extent=52 produces correct packed results, though. > > Wei-keng > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > <struct2.c> _______________________________________________ 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] Threaded Listener
by Lu, Huiwei 16 Jan '15

16 Jan '15

Looks like it is a very old feature of MPICH1. http://www.mcs.anl.gov/research/projects/mpi/mpich1-old/docs/mpichman-chp4/… I don’t think the recent version of MPICH support it anymore. — Huiwei > On Jan 16, 2015, at 1:41 PM, Wesley Bland <wbland(a)anl.gov> wrote: > > Can you try using a more recent version of MPICH. The version you are using is years old and we don't support it anymore. Our latest version is 3.1.3. You might see if the issue is still present there. > > Thanks, > Wesley > > On Fri, Jan 16, 2015 at 10:54 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: > Hi, > > I am trying to compile and use mpich-1.2.7p1 with threaded listener (i.e. configured with --enable-threaded-listener). However, I cannot even run a simple mpi example with the resulting mpich. > > I need to use threaded listener because the environment I am compiling for (kind of embedded environment) does not have fork (no heavy processes). > > The error I get with the mpich with threaded listener is: > > rm_2889: 1103279872: p4_error: listener select: -1 > p4_error: latest msg from perror: Bad file descriptor > p0_2710: (2.097656) net_recv failed for fd = 5 > p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 > > Has anyone experienced a similar problem? > > Thanks in advance, > Eduardo > > _______________________________________________ > 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] Threaded Listener
by Wesley Bland 16 Jan '15

16 Jan '15

Can you try using a more recent version of MPICH. The version you are using is years old and we don't support it anymore. Our latest version is 3.1.3. You might see if the issue is still present there. Thanks, Wesley On Fri, Jan 16, 2015 at 10:54 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: > Hi, > > I am trying to compile and use mpich-1.2.7p1 with threaded listener > (i.e. configured with --enable-threaded-listener). However, I cannot even > run a simple mpi example with the resulting mpich. > > I need to use threaded listener because the environment I am compiling > for (kind of embedded environment) does not have fork (no heavy processes). > > The error I get with the mpich with threaded listener is: > > rm_2889: 1103279872: p4_error: listener select: -1 > p4_error: latest msg from perror: Bad file descriptor > p0_2710: (2.097656) net_recv failed for fd = 5 > p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 > > Has anyone experienced a similar problem? > > Thanks in advance, > Eduardo > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Threaded Listener
by Eduardo 16 Jan '15

16 Jan '15

Hi, I am trying to compile and use mpich-1.2.7p1 with threaded listener (i.e. configured with --enable-threaded-listener). However, I cannot even run a simple mpi example with the resulting mpich. I need to use threaded listener because the environment I am compiling for (kind of embedded environment) does not have fork (no heavy processes). The error I get with the mpich with threaded listener is: rm_2889: 1103279872: p4_error: listener select: -1 p4_error: latest msg from perror: Bad file descriptor p0_2710: (2.097656) net_recv failed for fd = 5 p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 Has anyone experienced a similar problem? Thanks in advance, Eduardo _______________________________________________ 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] [OMPI users] OpenMPI 1.8.4rc3, 1.6.5 and 1.6.3: segmentation violation in mca_io_romio_dist_MPI_File_close
by Eric Chamberland 16 Jan '15

16 Jan '15

On 01/14/2015 05:57 PM, Rob Latham wrote: > > > On 12/17/2014 07:04 PM, Eric Chamberland wrote: >> Hi! >> >> Here is a "poor man's fix" that works for me (the idea is not from me, >> thanks to Thomas H.): >> >> #1- char* lCwd = getcwd(0,0); >> #2- chdir(lPathToFile); >> #3- MPI_File_open(...,lFileNameWithoutTooLongPath,...); >> #4- chdir(lCwd); >> #5- ... >> >> I think there are some limitations but it works very well for our >> uses... and until a "real" fix is proposed... > > Thanks for the bug report and test cases. I just pushed two fixes for > master that fix the problem you were seeing: > > http://git.mpich.org/mpich.git/commit/ed39c901 > http://git.mpich.org/mpich.git/commit/a30a4721a2 > > ==rob > Great! Thank you for the follow up (and both messages)! Eric _______________________________________________ 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] MPIR_Request_complete(232): INTERNAL ERROR: unexpected value in case statement
by Jeff Hammond 16 Jan '15

16 Jan '15

Thanks. That solves my issue (both with the code and the reason I wrote it). It means that the statement on 486 about no restrictions is not exactly correct, but and the standard is not a user guide, one can only reason about it with the entire contents in cache. Jeff On Thu, Jan 15, 2015 at 10:18 PM, Thakur, Rajeev <thakur(a)mcs.anl.gov> wrote: > pg 483, ln 44-45: "Multiple threads completing the same request. A program > in which two threads block, waiting on the same request, is erroneous." > > Rajeev > > > On Jan 16, 2015, at 12:03 AM, Jeff Hammond <jeff.science(a)gmail.com> > wrote: > > MPI-3 page 483 says: "two concurrently running threads may make MPI > calls and the outcome will be as if the calls executed in some order, > even if their execution is interleaved." > > The outcome of my program where the calls execute in some order is > well-defined: the first call completes the request and the second call > returns immediately since req=MPI_REQUEST_NULL. > > Furthermore, MPI-3 page 486 says that MPI_THREAD_MULTIPLE is defined > to mean "Multiple threads may call MPI, with no restrictions." > Without restriction implies that data races are valid. The prior > statement ensures that the result of a program with MPI-related races > is well-defined. > > Do you disagree with my interpretation of MPI-3? > > Jeff > > On Thu, Jan 15, 2015 at 9:41 PM, Thakur, Rajeev <thakur(a)mcs.anl.gov> wrote: > > I would say the program is erroneous. It is calling MPI_Wait concurrently on > the same request, i.e., you are completing one operation twice. You can call > MPI_Wait concurrently, but with different requests. > > Rajeev > > On Jan 15, 2015, at 11:32 PM, Jeff Hammond <jeff.science(a)gmail.com> > wrote: > > I am trying to run the following program. It's obviously a silly > program but I wrote it to make an argument about the MPI standard. I > don't believe it violates the MPI standard, but please let me know if > I am mistaken. > > smakramu-mobl:MPI jrhammon$ cat wait-race.c > #include <stdio.h> > #include <omp.h> > #include <mpi.h> > > int main(int argc, char * argv[]) > { > int provided; > MPI_Init_thread(&argc, &argv, MPI_THREAD_MULTIPLE, &provided); > if (provided<MPI_THREAD_MULTIPLE) { > printf("inadequate thread support\n"); > MPI_Finalize(); > } > > MPI_Request req; > MPI_Ibarrier(MPI_COMM_WORLD, &req); > //req = MPI_REQUEST_NULL; > #pragma omp parallel num_threads(2) shared(req) > { > MPI_Wait(&req, MPI_STATUS_IGNORE); > } > > printf("test finished\n"); > MPI_Finalize(); > return 0; > } > > I compile the program with MPICH git master and GCC 4.9.2 from about a week > ago: > > smakramu-mobl:MPI jrhammon$ mpicc -fopenmp -g -Wall wait-race.c > > smakramu-mobl:MPI jrhammon$ mpichversion > MPICH Version: 3.2a2 > MPICH Release date: unreleased development copy > MPICH Device: ch3:nemesis > MPICH configure: CC=gcc-4.9 CXX=g++-4.9 FC=gfortran-4.9 > F77=gfortran-4.9 --disable-cxx --enable-fortran > --enable-threads=runtime --enable-g=dbg --with-pm=hydra > --prefix=/opt/mpich/dev/gcc/default --enable-wrapper-rpath > --enable-static --enable-shared > MPICH CC: gcc-4.9 -g -O2 > MPICH CXX: no -g > MPICH F77: gfortran-4.9 -g -O2 > MPICH FC: gfortran-4.9 -g -O2 > > Sometimes the program runs fine: > > smakramu-mobl:MPI jrhammon$ mpiexec -n 2 ./a.out > test finished > test finished > > And sometimes it fails like this: > > smakramu-mobl:MPI jrhammon$ mpiexec -n 2 ./a.out > test finished > Fatal error in MPI_Wait: Internal MPI error!, error stack: > MPI_Wait(187).............: MPI_Wait(request=0x7fff5b51ee88, status=0x1) > failed > MPIR_Wait_impl(84)........: > MPIR_Request_complete(232): INTERNAL ERROR: unexpected value in case > statement (value=78309520) > > So either my program violates the MPI standard or there's a bug in > MPICH. Please let me know which it is. > > Thanks, > > Jeff > > -- > Jeff Hammond > jeff.science(a)gmail.com > http://jeffhammond.github.io/ > _______________________________________________ > 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 > jeff.science(a)gmail.com > http://jeffhammond.github.io/ > _______________________________________________ > 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 jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0