[mpich-discuss] Fatal error in MPI_Test: Invalid MPI_Request
Gus Correa
gus at ldeo.columbia.edu
Mon Feb 23 11:32:25 CST 2009
Hi Samir, list
I am wondering if the mpicxx and mpiexec you are using
belong to the same MPICH2 build (considering the problems you
reported before).
What is the output of "which mpicxx" and "which mpiexec"?
You may want to use full path names to mpicxx and mpiexec,
as Anthony Chan recommended in another email.
Problems with PATH and multiple versions and builds of MPI
that hang around all Linux computers
has been an endless source of frustration for many.
I myself prefer to use full path names when I am testing
MPI programs, to avoid any confusion and distress.
I hope this helps,
Gus Correa
---------------------------------------------------------------------
Gustavo Correa
Lamont-Doherty Earth Observatory - Columbia University
Palisades, NY, 10964-8000 - USA
---------------------------------------------------------------------
Samir Khanal wrote:
> Hi All
> I tried and did the following.
>
> [skhanal at comet ~]$ mpicxx -L /home/skhanal/bgtw/lib -lbgtw bgtwRingTest.cpp -o Ring
> [skhanal at comet ~]$ mpiexec -n 4 ./Ring
> Fatal error in MPI_Test: Invalid MPI_Request, error stack:
> MPI_Test(152): MPI_Test(request=0x1f820388, flag=0x7fffb8236134, status=0x7fffb82360a0) failed
> MPI_Test(75).: Invalid MPI_Requestrank 0 in job 35 comet.cs.bgsu.edu_35155 caused collective abort of all ranks
> exit status of rank 0: killed by signal 9
>
> What does this mean?
> Samir
>
> Ps: I am using mpich2 1.0.8
More information about the mpich-discuss
mailing list