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

Fwd: MPI_T_ERR_ ... error codes for FORTRAN
by Junchao Zhang 30 Sep '14

30 Sep '14

Hi, Mike, From MPI-3.0 A.1.1., I can not see it requires all constants are valid in C and FORTRAN. Instead, in 14.3, it says "Since the MPI tool information interface primarily focuses on tools and support libraries, MPI implementations are only required to provide C bindings for functions introduced in this section." And in MPICH's f08 bindings, it is the same (i.e. no support of MPI-T). --Junchao Zhang On Tue, Sep 30, 2014 at 10:39 AM, Michael L. Stokes <Michael.Stokes(a)uah.edu> wrote: > On 09/30/2014 10:36 AM, discuss-owner(a)mpich.org wrote: > >> According to the MPI-3.0 spec (A.1.1), C and FORTRAN constants are >> supposed to be shared (with noted exceptions). >> These include the MPI_T_ERR_ ... error codes. But from what I can >> determine, none of the MPI_T_ERR_ error codes >> seem to compile under the mpif77 compiler (intel) using MPICH 3.1.2. So I >> post the following questions: >> >> 1) Am i interpreting the specs correctly in that all constants (error >> codes in this instance) are valid in C and FORTRAN? >> >> 2) Is the behavior I'm seeing correct given the current intel compiler >> and version of MPICH? The snippet of code I'm >> using is the following. Here I'm using a perl script hereto document to >> write FORTRAN code where $target is any >> of the MPI error codes, and $ext is 'f' in this case. >> >> PROGRAM ERRORCODE >> IMPLICIT NONE >> INCLUDE "mpif.h" >> >> IF( $target.ge.MPI_SUCCESS .and. >> + $target.le.MPI_ERR_LASTCODE) THEN >> WRITE(6,1) >> 1 FORMAT('$ext "$target" >> +is verified ') >> ELSE >> WRITE(6,2) >> 2 FORMAT('$ext "$target" >> +is not verified ') >> ENDIF >> >> CALL EXIT(0) >> END PROGRAM ERRORCODE >> >> 3) Will this behavior change under the f08 FORTRAN bindings? >> >> Thanks >> Mike >> > > _______________________________________________ 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] MPI_Intercomm_create() for merging two spawned groups
by Carsten Clauss 29 Sep '14

29 Sep '14

Dear Wesley, Thank you very much for your quick response and the tips you gave me -- that really helped a lot! With kind regards, Carsten PS Please feel free to add the code to the test suite. On 09/26/2014 06:29 PM, Wesley Bland wrote: > I believe that your code is correct. I’ve gone through it to simplify > things a bit (attached) and see the same errors as you. That’s probably > a bug in MPICH that needs to be fixed unless someone else comes along > and says that for MPI_INTERCOMM_CREATE to work, all processes must be in > the same peer_comm, which doesn’t seem to be what the standard says to > me. I’ll create a ticket and add you as a CC so you can keep track of > things. > > In the meantime, you can avoid this problem by using one of the other > ways of setting up communication between two group of processes. You can > use the connect/accept functions as per this ticket: > http://trac.mpich.org/projects/mpich/ticket/495 or you can change the > way you spawn processes to have all processes in MPI_COMM_WORLD be > involved in spawning the new processes. I don’t know if that will > actually work for your application, but it’s a stopgap measure while we > fix this bug. > > Thanks, > Wesley > > >> On Sep 26, 2014, at 10:50 AM, Carsten Clauss <c.clauss(a)fz-juelich.de> wrote: >> >> Dear all, >> >> I have a code where two processes (forming the original MPI_COMM_WORLD) each spawn one additional child process (using MPI_COMM_SELF as spawning group). >> >> Now I want to create an intra-comm that covers all of these four processes. >> >> For doing so, I initially merge the two inter-comms resulting from the spawn calls into two new intra-comms (by using MPI_Intercomm_merge()). >> >> Then I create via MPI_intercomm_create() a new inter-comm that connects these two by using the original world communicator as peer-com. >> >> Finally, I merge the resulting inter-comm into the desired intra-comm. >> >> When using Open MPI, my code (it's derived from the MPICH test spaiccreate2.c, see attachment) works fine on my local machine. >> However, when running it with MPICH-3.1.2, I get the following error message: >> >> PMPI_Intercomm_create(601).....: MPI_Intercomm_create(comm=0x84000006, local_leader=1, MPI_COMM_WORLD, remote_leader=1, tag=123, newintercomm=0x7fff8323ee3c) failed >> MPIR_Intercomm_create_impl(258): >> MPID_GPID_ToLpidArray(461).....: Internal MPI error: Unknown gpid (1809769587)0 >> Fatal error in PMPI_Intercomm_create: Internal MPI error!, error stack: >> PMPI_Intercomm_create(601).....: MPI_Intercomm_create(comm=0x84000004, local_leader=1, MPI_COMM_WORLD, remote_leader=0, tag=123, newintercomm=0x7fff6e0b4c7c) failed >> MPIR_Intercomm_create_impl(258): >> MPID_GPID_ToLpidArray(461).....: Internal MPI error: Unknown gpid (1607388239)0 >> >> Here are my questions: >> 1) Is the above mentioned approach the right way to reach my goal? >> 2) Is the semantics of the attached code MPI compliant? >> 3) What is the reason for the error message when using MPICH? >> >> Thanks in advance and with kind regards, >> Carsten >> >> -- >> Carsten Clauss >>www.par-tec.com <http://www.par-tec.com> >> _____________________________________ >> ParTec Cluster Competence Center GmbH >> >> Possartstrasse 20 >> D-81679 Muenchen >> >> Geschäftsführer RA. Dipl.-Ing. Bernhard Frohwitter Eingetragen beim >> Amtsgericht München HRB 151545 Steuer-Nr. 08/32305, Ust-ID DE235527064 >> <spaiccreate3.c>_______________________________________________ >> 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 -- Carsten Clauss www.par-tec.com _____________________________________ ParTec Cluster Competence Center GmbH Possartstrasse 20 D-81679 Muenchen Geschäftsführer RA. Dipl.-Ing. Bernhard Frohwitter Eingetragen beim Amtsgericht München HRB 151545 Steuer-Nr. 08/32305, Ust-ID DE235527064 _______________________________________________ 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] Error: failed to allocate memory for an unexpected message
by Wesley Bland 28 Sep '14

28 Sep '14

The problem in this situation usually is that you're not posting enough receives and too many of your messages are getting buffered by the MPI library. Make sure you match up your sends and receives and whenever possible you post your receives early. Wesley > On Sep 28, 2014, at 7:13 AM, XingFENG <xingfeng(a)cse.unsw.edu.au> wrote: > > Hi all, > > I am running a MPI program on two machines. I got errors as follows: > > > ==================================================================== > Fatal error in MPI_Test: Other MPI error, error stack: > MPI_Test(153)......................: MPI_Test(request=0xa0a088, flag=0x7fff470e86fc, status=0x7fff470e86e0) failed > MPIDI_CH3I_Progress(150)...........: > MPID_nem_mpich2_test_recv(800).....: > MPID_nem_tcp_connpoll(1720)........: > state_commrdy_handler(1556)........: > MPID_nem_tcp_recv_handler(1459)....: > MPID_nem_handle_pkt(493)...........: > MPIDI_CH3_PktHandler_EagerSend(589): Failed to allocate memory for an unexpected message. 261892 unexpected messages queued. > Fatal error in MPI_Test: Other MPI error, error stack: > MPI_Test(153)......................: MPI_Test(request=0xadb128, flag=0x7fff33cba448, status=0x7fff33cba430) failed > MPIDI_CH3I_Progress(150)...........: > MPID_nem_mpich2_test_recv(800).....: > MPID_nem_tcp_connpoll(1720)........: > state_commrdy_handler(1556)........: > MPID_nem_tcp_recv_handler(1459)....: > MPID_nem_handle_pkt(493)...........: > MPIDI_CH3_PktHandler_EagerSend(589): Failed to allocate memory for an unexpected message. 261890 unexpected messages queued. > rank 1 in job 11 slave_36134 caused collective abort of all ranks > exit status of rank 1: killed by signal 9 > > ==================================================================== > > > I have never seen such errors before. What is the cause of this error? Is it an out of memory error? ( There is 20% remaining memory on machines ) > > Any help would be greatly appreciated. Thanks in advance! > > > -- > Best Regards. > --- > Xing FENG > PhD Candidate > Database Research Group > > School of Computer Science and Engineering > University of New South Wales > NSW 2052, Sydney > > Phone: (+61) 413 857 288 > _______________________________________________ > 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

Error: failed to allocate memory for an unexpected message
by XingFENG 28 Sep '14

28 Sep '14

Hi all, I am running a MPI program on two machines. I got errors as follows: ==================================================================== Fatal error in MPI_Test: Other MPI error, error stack: MPI_Test(153)......................: MPI_Test(request=0xa0a088, flag=0x7fff470e86fc, status=0x7fff470e86e0) failed MPIDI_CH3I_Progress(150)...........: MPID_nem_mpich2_test_recv(800).....: MPID_nem_tcp_connpoll(1720)........: state_commrdy_handler(1556)........: MPID_nem_tcp_recv_handler(1459)....: MPID_nem_handle_pkt(493)...........: MPIDI_CH3_PktHandler_EagerSend(589): Failed to allocate memory for an unexpected message. 261892 unexpected messages queued. Fatal error in MPI_Test: Other MPI error, error stack: MPI_Test(153)......................: MPI_Test(request=0xadb128, flag=0x7fff33cba448, status=0x7fff33cba430) failed MPIDI_CH3I_Progress(150)...........: MPID_nem_mpich2_test_recv(800).....: MPID_nem_tcp_connpoll(1720)........: state_commrdy_handler(1556)........: MPID_nem_tcp_recv_handler(1459)....: MPID_nem_handle_pkt(493)...........: MPIDI_CH3_PktHandler_EagerSend(589): Failed to allocate memory for an unexpected message. 261890 unexpected messages queued. rank 1 in job 11 slave_36134 caused collective abort of all ranks exit status of rank 1: killed by signal 9 ==================================================================== I have never seen such errors before. What is the cause of this error? Is it an out of memory error? ( There is 20% remaining memory on machines ) Any help would be greatly appreciated. Thanks in advance! -- Best Regards. --- Xing FENG PhD Candidate Database Research Group School of Computer Science and Engineering University of New South Wales NSW 2052, Sydney Phone: (+61) 413 857 288 _______________________________________________ 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] Does MPICH implements polling mechanism on MPI_Recv?
by Wesley Bland 27 Sep '14

27 Sep '14

Probably while all of the processes are I the MPI stack waiting most of them are blocking on a mutex that will only let one of them into the MPI progress engine. Depending on how your application is architected, you could have just one thread make progress in MPI by calling Waitany and then just use Test or Testany in the other threads. Unless your using per object locking, you won't have multiple processes polling the network at the same time. Wesley > On Sep 27, 2014, at 7:39 AM, Anatoly G <anatolyrishon(a)gmail.com> wrote: > > You are absolutely right. > But some engineer designed to execute another application on computer while system is in ready state. > This application executed only when my application in ready state. > I'm not familiar with the reason, but currently this is a situation. > One more question: > My application designed not by me, then I can't explain you design reason for the solution. > I have number of communicators which are cloned from MPI_COMM_WORLD. I execute on each communicator MPI_Waitany on separate thread. The data mostly arrives on single communicator only, but other threads are just waiting. I mean that single thread is actually working with MPI, others are on busy wait. Do I have polling penalty in this case? > > Regards, > Anatoly. > > > >> On Tue, Sep 23, 2014 at 4:49 PM, Rob Latham <robl(a)mcs.anl.gov> wrote: >> >> >> On 09/23/2014 09:38 AM, Wesley Bland wrote: >> >>> Out of curiosity, what is the issue with using 100% of the CPU? If >>> you’re not using it for your application (which it appears that you >>> aren’t since you’re calling MPI_Wait), what difference does it make if >>> MPI uses all of it? >> >> power consumption, I'd imagine. >> >> ==rob >> >> -- >> Rob Latham >> Mathematics and Computer Science Division >> Argonne National Lab, IL USA >> >> _______________________________________________ >> 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] Does MPICH implements polling mechanism on MPI_Recv?
by Anatoly G 27 Sep '14

27 Sep '14

You are absolutely right. But some engineer designed to execute another application on computer while system is in ready state. This application executed only when my application in ready state. I'm not familiar with the reason, but currently this is a situation. One more question: My application designed not by me, then I can't explain you design reason for the solution. I have number of communicators which are cloned from MPI_COMM_WORLD. I execute on each communicator MPI_Waitany on separate thread. The data mostly arrives on single communicator only, but other threads are just waiting. I mean that single thread is actually working with MPI, others are on busy wait. Do I have polling penalty in this case? Regards, Anatoly. On Tue, Sep 23, 2014 at 4:49 PM, Rob Latham <robl(a)mcs.anl.gov> wrote: > > > On 09/23/2014 09:38 AM, Wesley Bland wrote: > > Out of curiosity, what is the issue with using 100% of the CPU? If >> you’re not using it for your application (which it appears that you >> aren’t since you’re calling MPI_Wait), what difference does it make if >> MPI uses all of it? >> > > power consumption, I'd imagine. > > ==rob > > -- > Rob Latham > Mathematics and Computer Science Division > Argonne National Lab, IL USA > > _______________________________________________ > 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] MPI_Intercomm_create() for merging two spawned groups
by Wesley Bland 26 Sep '14

26 Sep '14

You’re right, that does look the same. I’ll mark the new one as a duplicate then. > On Sep 26, 2014, at 12:45 PM, Dave Goodell (dgoodell) <dgoodell(a)cisco.com> wrote: > > Wesley, > > I haven't read the test case code, but based on the description in this thread I think this is probably a duplicate of ticket #1502: http://trac.mpich.org/projects/mpich/ticket/1502 > > FWIW, I think that issue has since been fixed in Open MPI, though I haven't tested it myself. > > -Dave > > On Sep 26, 2014, at 11:29 AM, Wesley Bland <wbland(a)anl.gov> wrote: > >> I believe that your code is correct. I’ve gone through it to simplify things a bit (attached) and see the same errors as you. That’s probably a bug in MPICH that needs to be fixed unless someone else comes along and says that for MPI_INTERCOMM_CREATE to work, all processes must be in the same peer_comm, which doesn’t seem to be what the standard says to me. I’ll create a ticket and add you as a CC so you can keep track of things. >> >> In the meantime, you can avoid this problem by using one of the other ways of setting up communication between two group of processes. You can use the connect/accept functions as per this ticket: http://trac.mpich.org/projects/mpich/ticket/495 or you can change the way you spawn processes to have all processes in MPI_COMM_WORLD be involved in spawning the new processes. I don’t know if that will actually work for your application, but it’s a stopgap measure while we fix this bug. >> >> Thanks, >> Wesley >> >> >>> On Sep 26, 2014, at 10:50 AM, Carsten Clauss <c.clauss(a)fz-juelich.de> wrote: >>> >>> Dear all, >>> >>> I have a code where two processes (forming the original MPI_COMM_WORLD) each spawn one additional child process (using MPI_COMM_SELF as spawning group). >>> >>> Now I want to create an intra-comm that covers all of these four processes. >>> >>> For doing so, I initially merge the two inter-comms resulting from the spawn calls into two new intra-comms (by using MPI_Intercomm_merge()). >>> >>> Then I create via MPI_intercomm_create() a new inter-comm that connects these two by using the original world communicator as peer-com. >>> >>> Finally, I merge the resulting inter-comm into the desired intra-comm. >>> >>> When using Open MPI, my code (it's derived from the MPICH test spaiccreate2.c, see attachment) works fine on my local machine. >>> However, when running it with MPICH-3.1.2, I get the following error message: >>> >>> PMPI_Intercomm_create(601).....: MPI_Intercomm_create(comm=0x84000006, local_leader=1, MPI_COMM_WORLD, remote_leader=1, tag=123, newintercomm=0x7fff8323ee3c) failed >>> MPIR_Intercomm_create_impl(258): >>> MPID_GPID_ToLpidArray(461).....: Internal MPI error: Unknown gpid (1809769587)0 >>> Fatal error in PMPI_Intercomm_create: Internal MPI error!, error stack: >>> PMPI_Intercomm_create(601).....: MPI_Intercomm_create(comm=0x84000004, local_leader=1, MPI_COMM_WORLD, remote_leader=0, tag=123, newintercomm=0x7fff6e0b4c7c) failed >>> MPIR_Intercomm_create_impl(258): >>> MPID_GPID_ToLpidArray(461).....: Internal MPI error: Unknown gpid (1607388239)0 >>> >>> Here are my questions: >>> 1) Is the above mentioned approach the right way to reach my goal? >>> 2) Is the semantics of the attached code MPI compliant? >>> 3) What is the reason for the error message when using MPICH? >>> >>> Thanks in advance and with kind regards, >>> Carsten >>> >>> -- >>> Carsten Clauss >>> www.par-tec.com >>> _____________________________________ >>> ParTec Cluster Competence Center GmbH >>> >>> Possartstrasse 20 >>> D-81679 Muenchen >>> >>> Geschäftsführer RA. Dipl.-Ing. Bernhard Frohwitter Eingetragen beim >>> Amtsgericht München HRB 151545 Steuer-Nr. 08/32305, Ust-ID DE235527064 >>> <spaiccreate3.c>_______________________________________________ >>> 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 >> <inter_create_merge.c> > > _______________________________________________ > 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] MPI_Intercomm_create() for merging two spawned groups
by Dave Goodell (dgoodell) 26 Sep '14

26 Sep '14

Wesley, I haven't read the test case code, but based on the description in this thread I think this is probably a duplicate of ticket #1502: http://trac.mpich.org/projects/mpich/ticket/1502 FWIW, I think that issue has since been fixed in Open MPI, though I haven't tested it myself. -Dave On Sep 26, 2014, at 11:29 AM, Wesley Bland <wbland(a)anl.gov> wrote: > I believe that your code is correct. I’ve gone through it to simplify things a bit (attached) and see the same errors as you. That’s probably a bug in MPICH that needs to be fixed unless someone else comes along and says that for MPI_INTERCOMM_CREATE to work, all processes must be in the same peer_comm, which doesn’t seem to be what the standard says to me. I’ll create a ticket and add you as a CC so you can keep track of things. > > In the meantime, you can avoid this problem by using one of the other ways of setting up communication between two group of processes. You can use the connect/accept functions as per this ticket: http://trac.mpich.org/projects/mpich/ticket/495 or you can change the way you spawn processes to have all processes in MPI_COMM_WORLD be involved in spawning the new processes. I don’t know if that will actually work for your application, but it’s a stopgap measure while we fix this bug. > > Thanks, > Wesley > > > > On Sep 26, 2014, at 10:50 AM, Carsten Clauss <c.clauss(a)fz-juelich.de> wrote: > > > > Dear all, > > > > I have a code where two processes (forming the original MPI_COMM_WORLD) each spawn one additional child process (using MPI_COMM_SELF as spawning group). > > > > Now I want to create an intra-comm that covers all of these four processes. > > > > For doing so, I initially merge the two inter-comms resulting from the spawn calls into two new intra-comms (by using MPI_Intercomm_merge()). > > > > Then I create via MPI_intercomm_create() a new inter-comm that connects these two by using the original world communicator as peer-com. > > > > Finally, I merge the resulting inter-comm into the desired intra-comm. > > > > When using Open MPI, my code (it's derived from the MPICH test spaiccreate2.c, see attachment) works fine on my local machine. > > However, when running it with MPICH-3.1.2, I get the following error message: > > > > PMPI_Intercomm_create(601).....: MPI_Intercomm_create(comm=0x84000006, local_leader=1, MPI_COMM_WORLD, remote_leader=1, tag=123, newintercomm=0x7fff8323ee3c) failed > > MPIR_Intercomm_create_impl(258): > > MPID_GPID_ToLpidArray(461).....: Internal MPI error: Unknown gpid (1809769587)0 > > Fatal error in PMPI_Intercomm_create: Internal MPI error!, error stack: > > PMPI_Intercomm_create(601).....: MPI_Intercomm_create(comm=0x84000004, local_leader=1, MPI_COMM_WORLD, remote_leader=0, tag=123, newintercomm=0x7fff6e0b4c7c) failed > > MPIR_Intercomm_create_impl(258): > > MPID_GPID_ToLpidArray(461).....: Internal MPI error: Unknown gpid (1607388239)0 > > > > Here are my questions: > > 1) Is the above mentioned approach the right way to reach my goal? > > 2) Is the semantics of the attached code MPI compliant? > > 3) What is the reason for the error message when using MPICH? > > > > Thanks in advance and with kind regards, > > Carsten > > > > -- > > Carsten Clauss > > www.par-tec.com > > _____________________________________ > > ParTec Cluster Competence Center GmbH > > > > Possartstrasse 20 > > D-81679 Muenchen > > > > Geschäftsführer RA. Dipl.-Ing. Bernhard Frohwitter Eingetragen beim > > Amtsgericht München HRB 151545 Steuer-Nr. 08/32305, Ust-ID DE235527064 > > <spaiccreate3.c>_______________________________________________ > > 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 > <inter_create_merge.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] MPI_Intercomm_create() for merging two spawned groups
by Wesley Bland 26 Sep '14

26 Sep '14

1 0

MPI_Intercomm_create() for merging two spawned groups
by Carsten Clauss 26 Sep '14

26 Sep '14

Dear all, I have a code where two processes (forming the original MPI_COMM_WORLD) each spawn one additional child process (using MPI_COMM_SELF as spawning group). Now I want to create an intra-comm that covers all of these four processes. For doing so, I initially merge the two inter-comms resulting from the spawn calls into two new intra-comms (by using MPI_Intercomm_merge()). Then I create via MPI_intercomm_create() a new inter-comm that connects these two by using the original world communicator as peer-com. Finally, I merge the resulting inter-comm into the desired intra-comm. When using Open MPI, my code (it's derived from the MPICH test spaiccreate2.c, see attachment) works fine on my local machine. However, when running it with MPICH-3.1.2, I get the following error message: PMPI_Intercomm_create(601).....: MPI_Intercomm_create(comm=0x84000006, local_leader=1, MPI_COMM_WORLD, remote_leader=1, tag=123, newintercomm=0x7fff8323ee3c) failed MPIR_Intercomm_create_impl(258): MPID_GPID_ToLpidArray(461).....: Internal MPI error: Unknown gpid (1809769587)0 Fatal error in PMPI_Intercomm_create: Internal MPI error!, error stack: PMPI_Intercomm_create(601).....: MPI_Intercomm_create(comm=0x84000004, local_leader=1, MPI_COMM_WORLD, remote_leader=0, tag=123, newintercomm=0x7fff6e0b4c7c) failed MPIR_Intercomm_create_impl(258): MPID_GPID_ToLpidArray(461).....: Internal MPI error: Unknown gpid (1607388239)0 Here are my questions: 1) Is the above mentioned approach the right way to reach my goal? 2) Is the semantics of the attached code MPI compliant? 3) What is the reason for the error message when using MPICH? Thanks in advance and with kind regards, Carsten -- Carsten Clauss www.par-tec.com _____________________________________ ParTec Cluster Competence Center GmbH Possartstrasse 20 D-81679 Muenchen Geschäftsführer RA. Dipl.-Ing. Bernhard Frohwitter Eingetragen beim Amtsgericht München HRB 151545 Steuer-Nr. 08/32305, Ust-ID DE235527064 _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0