- discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] send and recieve not working over ethernet
by D Griffiths 01 Dec '12

01 Dec '12

Okay, I'll try reinstalling a 64-bit OS. Thanks for your time.

1 0

Re: [mpich-discuss] Support for MIC in mpich2-1.5
by Pavan Balaji 01 Dec '12

01 Dec '12

Sorry for the delay in responding, John. I'm catching up on my email. Looks like some bug in the scif code. I tried to reproduce it on my machine, but I can't. Can you give a little more information on the setup? -- Pavan On 11/30/2012 04:36 PM US Central Time, John Fettig wrote: > Any thoughts about this? > > Regards, > John > > > On Tue, Nov 13, 2012 at 5:07 PM, John Fettig <john.fettig(a)gmail.com > <mailto:[email protected]>> wrote: > > On Mon, Nov 5, 2012 at 9:37 PM, Pavan Balaji <balaji(a)mcs.anl.gov > <mailto:[email protected]>> wrote: > > > On 11/05/12 13:12, John Fettig wrote: > > I believe I have a working build, I'll append my cross file > to the end > of this email if anybody else wants to try it. > > > Thanks! > > > I have a followup question: is there any support for > launching jobs > that use both the MIC and the host CPU? > > > Yes. Once you have setup MPICH on both the host and MIC, you > can launch jobs across them. > > If you didn't pass any configure option, it'll use TCP/IP, which > is very slow. If you configure with > --with-device=ch3:nemesis:scif, it'll use the SCIF protocol, > which is much faster. > > > I compiled examples/hellow.c for both the MIC and the host CPU, and > copied it to the card. This seems to work: > > $ mpiexec -hosts 172.31.1.1:1 <http://172.31.1.1:1>,172.31.1.254:1 > <http://172.31.1.254:1> -n 1 ./hellow.mic : -n 1 ./hellow > Hello world from process 1 of 2 > Hello world from process 0 of 2 > > However, if I try to run more processes it crashes: > > $ mpiexec -hosts 172.31.1.1:3 <http://172.31.1.1:3>,172.31.1.254:3 > <http://172.31.1.254:3> -n 3 ./hellow.mic : -n 3 ./hellow > Hello world from process 4 of 6 > Hello world from process 0 of 6 > Hello world from process 3 of 6 > Hello world from process 1 of 6 > 0: 3: 00000033: 00000042: readv err 0 > Fatal error in MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(293).................: MPI_Finalize failed > MPI_Finalize(213).................: > MPID_Finalize(117)................: > MPIDI_CH3U_VC_WaitForClose(385)...: an error occurred while the > device was waiting for all open connections to close > MPIDI_CH3I_Progress(367)..........: > MPID_nem_mpich2_blocking_recv(904): > state_commrdy_handler(175)........: > state_commrdy_handler(138)........: > MPID_nem_scif_recv_handler(115)...: Communication error with rank 3 > MPID_nem_scif_recv_handler(35)....: scif_scif_read failed > (scif_scif_read failed with error 'Success') > 1: 3: 00000033: 00000042: readv err 0 > Fatal error in MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(293).................: MPI_Finalize failed > MPI_Finalize(213).................: > MPID_Finalize(117)................: > MPIDI_CH3U_VC_WaitForClose(385)...: an error occurred while the > device was waiting for all open connections to close > MPIDI_CH3I_Progress(367)..........: > MPID_nem_mpich2_blocking_recv(904): > state_commrdy_handler(175)........: > state_commrdy_handler(138)........: > MPID_nem_scif_recv_handler(115)...: Communication error with rank 3 > MPID_nem_scif_recv_handler(35)....: scif_scif_read failed > (scif_scif_read failed with error 'Success') > Hello world from process 5 of 6 > Fatal error in MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(293).................: MPI_Finalize failed > MPI_Finalize(213).................: > MPID_Finalize(117)................: > MPIDI_CH3U_VC_WaitForClose(385)...: an error occurred while the > device was waiting for all open connections to close > MPIDI_CH3I_Progress(367)..........: > MPID_nem_mpich2_blocking_recv(904): > state_commrdy_handler(184)........: poll of socket fds failed > Fatal error in MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(293).................: MPI_Finalize failed > MPI_Finalize(213).................: > MPID_Finalize(117)................: > MPIDI_CH3U_VC_WaitForClose(385)...: an error occurred while the > device was waiting for all open connections to close > MPIDI_CH3I_Progress(367)..........: > MPID_nem_mpich2_blocking_recv(904): > state_commrdy_handler(184)........: poll of socket fds failed > > =================================================================================== > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > = EXIT CODE: 1 > = CLEANING UP REMAINING PROCESSES > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > =================================================================================== > [proxy:0:[email protected]] HYD_pmcd_pmip_control_cmd_cb > (./pm/pmiserv/pmip_cb.c:883): assert (!closed) failed > [proxy:0:[email protected]] HYDT_dmxu_poll_wait_for_event > (./tools/demux/demux_poll.c:77): callback returned error status > [proxy:0:[email protected]] main (./pm/pmiserv/pmip.c:210): demux engine > error waiting for event > [mpiexec@host] HYDT_bscu_wait_for_completion > (./tools/bootstrap/utils/bscu_wait.c:76): one of the processes > terminated badly; aborting > [mpiexec@host] HYDT_bsci_wait_for_completion > (./tools/bootstrap/src/bsci_wait.c:23): launcher returned error > waiting for completion > [mpiexec@host] HYD_pmci_wait_for_completion > (./pm/pmiserv/pmiserv_pmci.c:216): launcher returned error waiting > for completion > [mpiexec@host] main (./ui/mpich/mpiexec.c:325): process manager > error waiting for completion > > Any ideas? > > John > > -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] send and recieve not working over ethernet
by Pavan Balaji 01 Dec '12

01 Dec '12

Please keep the discuss@mpich mailing list cc'ed. Yes, this is a problem. Is one of your machines actually a 32-bit machine or did you just install a 32-bit OS on a 64-bit machine? If it's the latter, you could reinstall a 64-bit OS. If you can't do that, another option is to build MPICH in 32-bit mode on both machines by passing CFLAGS=-m32 to configure on the 64-bit machine. This will require that you have the right 32-bit libraries installed on your 64-bit machine (such as the 32-bit libc library). This option is typically for expert users, and is not a recommended option for most users. -- Pavan On 12/01/2012 09:34 AM US Central Time, D Griffiths wrote: > x86_64 for the one, i686 for the other. I take it this is the problem? > > Thanks for getting back to me so quickly. -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] send and recieve not working over ethernet
by Pavan Balaji 01 Dec '12

01 Dec '12

Are the architectures of the two machines identical? Both x86 64-bit? Did you install a 64-bit OS on both machines ("uname -m" == "x86_64")? -- Pavan On 12/01/2012 08:34 AM US Central Time, D Griffiths wrote: > I am completely new to MPI so I hope Iï¿½m not asking anything too silly. > I have two computers, one running Ubuntu and the other running > Scientific Linux. They recognise each other as hosts, I can ssh from > each without a password and have disabled any firewalls. > > Although I can run a simple Hello World application, the trouble starts > when I try to use MPI_SEND and MPI_RECV. I am trying a simple program to > send an int variable from one node to the other (see source code below). > > If I run the code with two processes on the same computer I get the > correct output: > > dan@siriusa:~/mpich2/tutorial2$ mpiexec -n 2 ./result2 > > Process 0 sending number 4 > Process 1 received number 4 from process 0 > > However, if I try to run the code using both computers, I get: > > dan@siriusa:~/mpich2/tutorial2$ mpiexec -n 2 -f hosts ./result2 > > Process 0 sending number 4 > Process 1 received number -1078477356 from process 0 > > My host file: > > dan@siriusa:~/mpich2/tutorial2$ cat hosts > > 192.168.88.1 > 192.168.88.2 > > So there is some sort of problemwith using the send/recieve functions > over the network. As I said I am a beginner at this, so any help will be > greatly appreciated. Thanks in advance. > > Code: > > #include <mpi.h> > > #include <stdio.h> > #include <stdlib.h> > > int main(int argc, char** argv) { > > // Initialize the MPI environment > MPI_Init(NULL, NULL); > // Find out rank, size > int world_rank; > MPI_Comm_rank(MPI_COMM_WORLD, &world_rank); > int world_size; > MPI_Comm_size(MPI_COMM_WORLD, &world_size); > // Get the name of the processor > char processor_name[MPI_MAX_PROCESSOR_NAME]; > int name_len; > MPI_Get_processor_name(processor_name, &name_len); > > // We are assuming at least 2 processes for this task > if (world_size < 2) { > fprintf(stderr, "World size must be greater than 1 for %s\n", > argv[0]); > MPI_Abort(MPI_COMM_WORLD, 1); > } > > int number; > if (world_rank == 0) { > // If we are rank 0, set the number to -1 and send it to process 1 > number = 4; > printf("Process 0 sending number %d\n",number); > MPI_Send(&number, 1, MPI_INT, 1, 0, MPI_COMM_WORLD); > > } else if (world_rank == 1) { > MPI_Recv(&number, 1, MPI_INT, 0, 0, MPI_COMM_WORLD, > MPI_STATUS_IGNORE); > printf("Process 1 received number %d from process 0\n", number); > } > > MPI_Finalize(); > } > > > _______________________________________________ > 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

send and recieve not working over ethernet
by D Griffiths 01 Dec '12

01 Dec '12

I am completely new to MPI so I hope I’m not asking anything too silly. I have two computers, one running Ubuntu and the other running Scientific Linux. They recognise each other as hosts, I can ssh from each without a password and have disabled any firewalls. Although I can run a simple Hello World application, the trouble starts when I try to use MPI_SEND and MPI_RECV. I am trying a simple program to send an int variable from one node to the other (see source code below). If I run the code with two processes on the same computer I get the correct output: dan@siriusa:~/mpich2/tutorial2$ mpiexec -n 2 ./result2 Process 0 sending number 4 Process 1 received number 4 from process 0 However, if I try to run the code using both computers, I get: dan@siriusa:~/mpich2/tutorial2$ mpiexec -n 2 -f hosts ./result2 Process 0 sending number 4 Process 1 received number -1078477356 from process 0 My host file: dan@siriusa:~/mpich2/tutorial2$ cat hosts 192.168.88.1 192.168.88.2 So there is some sort of problem with using the send/recieve functions over the network. As I said I am a beginner at this, so any help will be greatly appreciated. Thanks in advance. Code: #include <mpi.h> #include <stdio.h> #include <stdlib.h> int main(int argc, char** argv) { // Initialize the MPI environment MPI_Init(NULL, NULL); // Find out rank, size int world_rank; MPI_Comm_rank(MPI_COMM_WORLD, &world_rank); int world_size; MPI_Comm_size(MPI_COMM_WORLD, &world_size); // Get the name of the processor char processor_name[MPI_MAX_PROCESSOR_NAME]; int name_len; MPI_Get_processor_name(processor_name, &name_len); // We are assuming at least 2 processes for this task if (world_size < 2) { fprintf(stderr, "World size must be greater than 1 for %s\n", argv[0]); MPI_Abort(MPI_COMM_WORLD, 1); } int number; if (world_rank == 0) { // If we are rank 0, set the number to -1 and send it to process 1 number = 4; printf("Process 0 sending number %d\n",number); MPI_Send(&number, 1, MPI_INT, 1, 0, MPI_COMM_WORLD); } else if (world_rank == 1) { MPI_Recv(&number, 1, MPI_INT, 0, 0, MPI_COMM_WORLD, MPI_STATUS_IGNORE); printf("Process 1 received number %d from process 0\n", number); } MPI_Finalize(); }

1 0

Re: [mpich-discuss] using MPICH_FAILED_PROCESSES
by Ma, Zhaoming 30 Nov '12

30 Nov '12

Hi Darius, Here is the error message when the default error handler was used, Fatal error in MPIR_CommGetAttr: Invalid argument, error stack: MPIR_CommGetAttr(261): MPIR_Comm_get_attr(MPI_COMM_WORLD, comm_keyval=-153930956 8, attribute_val=(nil), flag=0x7fff7f5dc048) failed MPIR_CommGetAttr(85).: Null pointer in parameter attr_val /Users/zm35101:$ mpiexec -n 2 ./MPI_test Fatal error in MPIR_CommGetAttr: Invalid argument, error stack: MPIR_CommGetAttr(261): MPIR_Comm_get_attr(MPI_COMM_WORLD, comm_keyval=-1539309568, attribute_val=(nil), flag=0x7fffb364fdf8) failed MPIR_CommGetAttr(85).: Null pointer in parameter attr_val Zhaoming -----Original Message----- From: discuss-bounces(a)mpich.org [mailto:[email protected]] On Behalf Of discuss-request(a)mpich.org Sent: Friday, November 30, 2012 4:37 PM To: discuss(a)mpich.org Subject: discuss Digest, Vol 1, Issue 18 Send discuss mailing list submissions to discuss(a)mpich.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.mpich.org/mailman/listinfo/discuss or, via email, send a message with subject or body 'help' to discuss-request(a)mpich.org You can reach the person managing the list at discuss-owner(a)mpich.org When replying, please edit your Subject line so it is more specific than "Re: Contents of discuss digest..." Today's Topics: 1. Re: How to specify number of cores for each process (Pavan Balaji) 2. Re: How to specify number of cores for each process (Pavan Balaji) 3. Re: How to specify number of cores for each process (Pavan Balaji) 4. MPI and signal handlers (Matthieu Dorier) 5. Re: using MPICH_FAILED_PROCESSES (Darius Buntinas) 6. Re: MPI and signal handlers (Darius Buntinas) 7. Re: MPI and signal handlers (Matthieu Dorier) 8. Hanging code in MPI_Comm_Spawn (Tim Gallagher) 9. Re: Hanging code in MPI_Comm_Spawn (Reuti) 10. Re: Support for MIC in mpich2-1.5 (John Fettig) ---------------------------------------------------------------------- Message: 1 Date: Wed, 28 Nov 2012 07:41:46 -0600 From: Pavan Balaji <balaji(a)mcs.anl.gov> To: discuss(a)mpich.org Subject: Re: [mpich-discuss] How to specify number of cores for each process Message-ID: <50B6149A.6030903(a)mcs.anl.gov> Content-Type: text/plain; charset=ISO-8859-1 There are two problems in your usage below. 1. I'm guessing that your host file specifies only one core for each host. Something like: host1 host2 Did you look through the mpiexec usage document that tells you how to specify multiple cores on each host? http://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager You should do something like: host1:16 host2:16 (please read the documentation on the above link for more information). 2. There's option called -binding auto. Did you mean -binding none? -- Pavan On 11/27/2012 09:37 PM US Central Time, Zachary Stanko wrote: > Hello, > > I am running an MPI program on a machine with two 16-core processors > yet, no matter what configuration I use with mpiexec, I am only > receiving 4 simultaneous processes. > I would like to maximize this machine's potential and run 8 or 16 > processes. I have tried all of the channel selections and tried the > -binding option. > Since I need to specify a different working directory for each process > (due to many output files with naming conflicts), I have a config file > with 8 lines of the form: > > -n 1 -binding auto -dir <mydir01> <myprog> <inpfile> -n 1 -binding > auto -dir <mydir02> <myprog> <inpfile> ...etc > > and I run: > > mpiexec -configfile <filename> > > Am I doing something wrong, or does MPICH just know best and cannot > run more than 4 jobs at a time on this system? > > Thanks, > > Zak > > > _______________________________________________ > 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 ------------------------------ Message: 2 Date: Wed, 28 Nov 2012 07:43:01 -0600 From: Pavan Balaji <balaji(a)mcs.anl.gov> To: discuss(a)mpich.org Subject: Re: [mpich-discuss] How to specify number of cores for each process Message-ID: <50B614E5.7020801(a)mcs.anl.gov> Content-Type: text/plain; charset=ISO-8859-1 As Zachary explained below, each process is in a different directory, so he'll need to use an MPMD launch and can't do -n 16 directly. -- Pavan On 11/27/2012 09:42 PM US Central Time, Jeff Hammond wrote: > Did you try "mpiexec -n 16 ..."? > > Sent from my iPhone > > On Nov 27, 2012, at 10:37 PM, Zachary Stanko <zstanko(a)usgs.gov > <mailto:[email protected]>> wrote: > >> Hello, >> >> I am running an MPI program on a machine with two 16-core processors >> yet, no matter what configuration I use with mpiexec, I am only >> receiving 4 simultaneous processes. >> I would like to maximize this machine's potential and run 8 or 16 >> processes. I have tried all of the channel selections and tried the >> -binding option. >> Since I need to specify a different working directory for each process >> (due to many output files with naming conflicts), I have a config file >> with 8 lines of the form: >> >> -n 1 -binding auto -dir <mydir01> <myprog> <inpfile> >> -n 1 -binding auto -dir <mydir02> <myprog> <inpfile> >> ...etc >> >> and I run: >> >> mpiexec -configfile <filename> >> >> Am I doing something wrong, or does MPICH just know best and cannot >> run more than 4 jobs at a time on this system? >> >> Thanks, >> >> Zak >> _______________________________________________ >> discuss mailing list <mailto:[email protected]>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 > -- Pavan Balaji http://www.mcs.anl.gov/~balaji ------------------------------ Message: 3 Date: Wed, 28 Nov 2012 07:44:52 -0600 From: Pavan Balaji <balaji(a)mcs.anl.gov> To: discuss(a)mpich.org Subject: Re: [mpich-discuss] How to specify number of cores for each process Message-ID: <50B61554.6090209(a)mcs.anl.gov> Content-Type: text/plain; charset=ISO-8859-1 On 11/28/2012 07:41 AM US Central Time, Pavan Balaji wrote: > 2. There's option called -binding auto. Did you mean -binding none? Gah. I meant, there's *no* option called -binding auto. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji ------------------------------ Message: 4 Date: Wed, 28 Nov 2012 15:54:59 +0100 (CET) From: Matthieu Dorier <matthieu.dorier(a)irisa.fr> To: discuss(a)mpich.org Subject: [mpich-discuss] MPI and signal handlers Message-ID: <665045738.7499664.1354114498957.JavaMail.root(a)irisa.fr> Content-Type: text/plain; charset="iso-8859-1" Hello, I read in the MPI-3 standard that allowing MPI calls within signal handlers is implementation dependent (I guess it's the same in previous standards) . Does mpich allow MPI calls within signal handlers? Also which signals are used by mpich? Does mpich use SIGSEGV? Thank you, Matthieu Dorier PhD student at ENS Cachan Brittany and IRISA http://people.irisa.fr/Matthieu.Dorier

1 0

Re: [mpich-discuss] Support for MIC in mpich2-1.5
by John Fettig 30 Nov '12

30 Nov '12

Any thoughts about this? Regards, John On Tue, Nov 13, 2012 at 5:07 PM, John Fettig <john.fettig(a)gmail.com> wrote: > On Mon, Nov 5, 2012 at 9:37 PM, Pavan Balaji <balaji(a)mcs.anl.gov> wrote: > >> >> On 11/05/12 13:12, John Fettig wrote: >> >>> I believe I have a working build, I'll append my cross file to the end >>> of this email if anybody else wants to try it. >>> >> >> Thanks! >> >> >> I have a followup question: is there any support for launching jobs >>> that use both the MIC and the host CPU? >>> >> >> Yes. Once you have setup MPICH on both the host and MIC, you can launch >> jobs across them. >> >> If you didn't pass any configure option, it'll use TCP/IP, which is very >> slow. If you configure with --with-device=ch3:nemesis:scif, it'll use the >> SCIF protocol, which is much faster. >> > > I compiled examples/hellow.c for both the MIC and the host CPU, and copied > it to the card. This seems to work: > > $ mpiexec -hosts 172.31.1.1:1,172.31.1.254:1 -n 1 ./hellow.mic : -n 1 > ./hellow > Hello world from process 1 of 2 > Hello world from process 0 of 2 > > However, if I try to run more processes it crashes: > > $ mpiexec -hosts 172.31.1.1:3,172.31.1.254:3 -n 3 ./hellow.mic : -n 3 > ./hellow > Hello world from process 4 of 6 > Hello world from process 0 of 6 > Hello world from process 3 of 6 > Hello world from process 1 of 6 > 0: 3: 00000033: 00000042: readv err 0 > Fatal error in MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(293).................: MPI_Finalize failed > MPI_Finalize(213).................: > MPID_Finalize(117)................: > MPIDI_CH3U_VC_WaitForClose(385)...: an error occurred while the device was > waiting for all open connections to close > MPIDI_CH3I_Progress(367)..........: > MPID_nem_mpich2_blocking_recv(904): > state_commrdy_handler(175)........: > state_commrdy_handler(138)........: > MPID_nem_scif_recv_handler(115)...: Communication error with rank 3 > MPID_nem_scif_recv_handler(35)....: scif_scif_read failed (scif_scif_read > failed with error 'Success') > 1: 3: 00000033: 00000042: readv err 0 > Fatal error in MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(293).................: MPI_Finalize failed > MPI_Finalize(213).................: > MPID_Finalize(117)................: > MPIDI_CH3U_VC_WaitForClose(385)...: an error occurred while the device was > waiting for all open connections to close > MPIDI_CH3I_Progress(367)..........: > MPID_nem_mpich2_blocking_recv(904): > state_commrdy_handler(175)........: > state_commrdy_handler(138)........: > MPID_nem_scif_recv_handler(115)...: Communication error with rank 3 > MPID_nem_scif_recv_handler(35)....: scif_scif_read failed (scif_scif_read > failed with error 'Success') > Hello world from process 5 of 6 > Fatal error in MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(293).................: MPI_Finalize failed > MPI_Finalize(213).................: > MPID_Finalize(117)................: > MPIDI_CH3U_VC_WaitForClose(385)...: an error occurred while the device was > waiting for all open connections to close > MPIDI_CH3I_Progress(367)..........: > MPID_nem_mpich2_blocking_recv(904): > state_commrdy_handler(184)........: poll of socket fds failed > Fatal error in MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(293).................: MPI_Finalize failed > MPI_Finalize(213).................: > MPID_Finalize(117)................: > MPIDI_CH3U_VC_WaitForClose(385)...: an error occurred while the device was > waiting for all open connections to close > MPIDI_CH3I_Progress(367)..........: > MPID_nem_mpich2_blocking_recv(904): > state_commrdy_handler(184)........: poll of socket fds failed > > > =================================================================================== > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > = EXIT CODE: 1 > = CLEANING UP REMAINING PROCESSES > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > > =================================================================================== > [proxy:0:[email protected]] HYD_pmcd_pmip_control_cmd_cb > (./pm/pmiserv/pmip_cb.c:883): assert (!closed) failed > [proxy:0:[email protected]] HYDT_dmxu_poll_wait_for_event > (./tools/demux/demux_poll.c:77): callback returned error status > [proxy:0:[email protected]] main (./pm/pmiserv/pmip.c:210): demux engine error > waiting for event > [mpiexec@host] HYDT_bscu_wait_for_completion > (./tools/bootstrap/utils/bscu_wait.c:76): one of the processes terminated > badly; aborting > [mpiexec@host] HYDT_bsci_wait_for_completion > (./tools/bootstrap/src/bsci_wait.c:23): launcher returned error waiting for > completion > [mpiexec@host] HYD_pmci_wait_for_completion > (./pm/pmiserv/pmiserv_pmci.c:216): launcher returned error waiting for > completion > [mpiexec@host] main (./ui/mpich/mpiexec.c:325): process manager error > waiting for completion > > Any ideas? > > John >

1 0

Re: [mpich-discuss] Hanging code in MPI_Comm_Spawn
by Reuti 29 Nov '12

29 Nov '12

Am 29.11.2012 um 20:18 schrieb Tim Gallagher: > I have a Fortran application that uses MPI_Comm_Spawn. When I run with it compiled using gfortran/gcc (and mpich compiled with gfortran/gcc), it just hangs forever. When I run with it compiled using ifort/icc (and mpich compiled with ifort/icc), it runs correctly. > > When I run it in GDB with the GNU compiler suite and interrupt it once it's stuck, it tells me: > > Program received signal SIGINT, Interrupt. > 0x00007ffff7800fc9 in pmpi_comm_spawn__ () from /opt/mpi/mpich/gnu/system/lib64/libmpich.so.8 > > and this is with both mpich 1.4 and 1.5. Did you compile MPICH2 on your own and set the LD_LIBRARY_PATH correctly? In 1.4.1p1 I have only libmpich.so.3.3 and so I assume the libmpich.so.8 is a one from your installation? IIRC by default MPICH2 generates static libs. -- Reuti > Does anybody have any suggestions for what could be going on? It really just sits there, doing absolutely nothing, forever. No timeouts, no errors or warnings. I'm not ruling out a bug in my codes, but I don't even know where to begin. > > Thanks, > > Tim > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Hanging code in MPI_Comm_Spawn
by Tim Gallagher 29 Nov '12

29 Nov '12

Hi, I have a Fortran application that uses MPI_Comm_Spawn. When I run with it compiled using gfortran/gcc (and mpich compiled with gfortran/gcc), it just hangs forever. When I run with it compiled using ifort/icc (and mpich compiled with ifort/icc), it runs correctly. When I run it in GDB with the GNU compiler suite and interrupt it once it's stuck, it tells me: Program received signal SIGINT, Interrupt. 0x00007ffff7800fc9 in pmpi_comm_spawn__ () from /opt/mpi/mpich/gnu/system/lib64/libmpich.so.8 and this is with both mpich 1.4 and 1.5. Does anybody have any suggestions for what could be going on? It really just sits there, doing absolutely nothing, forever. No timeouts, no errors or warnings. I'm not ruling out a bug in my codes, but I don't even know where to begin. Thanks, Tim

1 0

Re: [mpich-discuss] MPI and signal handlers
by Matthieu Dorier 28 Nov '12

28 Nov '12

Alright, thanks. Matthieu ----- Mail original ----- > De: "Darius Buntinas" <buntinas(a)mcs.anl.gov> > À: discuss(a)mpich.org > Envoyé: Mercredi 28 Novembre 2012 17:22:46 > Objet: Re: [mpich-discuss] MPI and signal handlers > > Sorry, MPICH doesn't allow MPI calls from signal handlers. > > -d > > > On Nov 28, 2012, at 8:54 AM, Matthieu Dorier wrote: > > > Hello, > > > > I read in the MPI-3 standard that allowing MPI calls within signal > > handlers is implementation dependent (I guess it's the same in > > previous standards). > > Does mpich allow MPI calls within signal handlers? > > > > Also which signals are used by mpich? Does mpich use SIGSEGV? > > > > Thank you, > > > > Matthieu Dorier > > PhD student at ENS Cachan Brittany and IRISA > > http://people.irisa.fr/Matthieu.Dorier > > _______________________________________________ > > 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