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

Re: [mpich-discuss] Assertion failed in file src/mpid/ch3/src/ch3u_handle_send_req.c at line 61 (RMA && Derived datatypes)
by Balaji, Pavan 10 Nov '14

10 Nov '14

Victor, We believe this has been fixed in mpich/master. Please download the latest mpich nightly snapshot and give it a try to see if it fixes the issue for you. FYI, the mpich website is down for maintenance at the moment. It should be back up in a couple of hours (or sooner). — Pavan > On Nov 10, 2014, at 6:57 AM, Victor Vysotskiy <victor.vysotskiy(a)teokem.lu.se> wrote: > > Dear Developers, > > recently I have mentioned a problem with assertion failed in file src/mpid/ch3/src/ch3u_handle_send_req.c: > > > http://lists.mpich.org/pipermail/discuss/2014-October/003354.html > > Finally, I was able to narrow problem to a small piece of code. Enclosed please find the test-bed code. In order to reproduce the problem, please compile and execute it with the following arguments: > > mpicc mpi_tvec2_rma.c -o mpi_tvec2_rma > > mpirun -np 8 ./mpi_tvec2_rma 80 400000 > > Assertion failed in file src/mpid/ch3/src/ch3u_handle_send_req.c at line 61: win_ptr->at_completion_counter >= 0 > > internal ABORT - process 0 > > =================================================================================== > > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > > = PID 12900 RUNNING AT n6 > > = EXIT CODE: 1 > > = CLEANING UP REMAINING PROCESSES > > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > > > =================================================================================== > > > > However, everything works out with "8 400000", and with "16 400000". This problem is reproducible on my 4-core laptop as well as on the 16-core HP SL203S GEN8 compute node. The GCC v4.7.3 and Intel v15.0.0 were used to compile MPICH v3.1.3 on my laptop and on HP SL203S, respectively. Moreover, the MPICH v3.1.3 used includes the '920661c3931' commit by Xin Zhao. > > > > Could you please comment on this issue? Is it a bug in MPICH, or something is wrong with the test-bed code attached? > > > > With best regards, > > Victor. > > <mpi_tvec2_rma.c>_______________________________________________ > 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 _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Assertion failed in file src/mpid/ch3/src/ch3u_handle_send_req.c at line 61 (RMA && Derived datatypes)
by Victor Vysotskiy 10 Nov '14

10 Nov '14

Dear Developers, recently I have mentioned a problem with assertion failed in file src/mpid/ch3/src/ch3u_handle_send_req.c: http://lists.mpich.org/pipermail/discuss/2014-October/003354.html Finally, I was able to narrow problem to a small piece of code. Enclosed please find the test-bed code. In order to reproduce the problem, please compile and execute it with the following arguments: mpicc mpi_tvec2_rma.c -o mpi_tvec2_rma mpirun -np 8 ./mpi_tvec2_rma 80 400000 Assertion failed in file src/mpid/ch3/src/ch3u_handle_send_req.c at line 61: win_ptr->at_completion_counter >= 0 internal ABORT - process 0 =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = PID 12900 RUNNING AT n6 = EXIT CODE: 1 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES =================================================================================== However, everything works out with "8 400000", and with "16 400000". This problem is reproducible on my 4-core laptop as well as on the 16-core HP SL203S GEN8 compute node. The GCC v4.7.3 and Intel v15.0.0 were used to compile MPICH v3.1.3 on my laptop and on HP SL203S, respectively. Moreover, the MPICH v3.1.3 used includes the '920661c3931' commit by Xin Zhao. Could you please comment on this issue? Is it a bug in MPICH, or something is wrong with the test-bed code attached? With best regards, Victor. _______________________________________________ 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 of running the MPICH2
by Lu, Huiwei 09 Nov '14

09 Nov '14

Hi, Chafik, Due to lack of developer resources, MPICH no longer supports the Windows platform. Please refer to our FAQ for more information: http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_can… We recommend you use Microsoft MPI, which can be found here: http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx — Huiwei > On Nov 9, 2014, at 2:29 PM, Chafik sanaa <san.chafik(a)gmail.com> wrote: > >> I am trying to run MPICH2 from the Windows 7 environment but I can't get the wmpiexec.exe working and get the following error message: Error: No smpd passphrase specified through the registry or .smpd file, exiting.i have already registered user account in mpiexec.exe > _______________________________________________ > 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 of running the MPICH2
by Chafik sanaa 09 Nov '14

09 Nov '14

*I am trying to run MPICH2 from the Windows 7 environment but I can't get **the wmpiexec.exe working and get the following error message:** Error: No smpd passphrase specified through the registry or .smpd file, **exiting.**i have already registered user account in mpiexec.exe* _______________________________________________ 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] Compile Fortran code with -static
by Shuchi Yang 08 Nov '14

08 Nov '14

Thanks, I am trying it now. Best, Shuchi On Sat, Nov 8, 2014 at 9:39 AM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > If you don't need to use the MPI-IO functions, try configuring with > --disable-romio. > > Rajeev > > On Nov 8, 2014, at 9:58 AM, Shuchi Yang <yang.shuchi(a)gmail.com> wrote: > > > 1) At Ubuntu 14.04, Intel Fortran 2015 xe > > Download mpich-3.13 > > It works well with general purpose > > 2) I need compile the fortran code with -static to run on machine > without Intel Fortran environment so I use -static option to compile both > MPICH and FORTRAN code. I met the following error > > > > /mpich/lib/libmpi.a(lib_libmpi_la-tcp_init.o): In function > `MPID_nem_tcp_get_business_card': > > src/mpid/ch3/channels/nemesis/netmod/tcp/tcp_init.c:(.text+0x319): > warning: Using 'gethostbyname' in statically linked applications requires > at runtime the shared libraries from the glibc version used for linking > > /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_IwriteContig': > > adio/common/ad_iwrite.c:(.text+0xb7): undefined reference to > `aio_write64' > > /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio': > > adio/common/ad_iwrite.c:(.text+0x2dc): undefined reference to > `aio_write64' > > adio/common/ad_iwrite.c:(.text+0x2e6): undefined reference to > `aio_read64' > > /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio_poll_fn': > > adio/common/ad_iwrite.c:(.text+0x4d0): undefined reference to > `aio_error64' > > adio/common/ad_iwrite.c:(.text+0x4f0): undefined reference to > `aio_return64' > > /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio_wait_fn': > > adio/common/ad_iwrite.c:(.text+0x65d): undefined reference to > `aio_suspend64' > > adio/common/ad_iwrite.c:(.text+0x6a0): undefined reference to > `aio_error64' > > adio/common/ad_iwrite.c:(.text+0x6b5): undefined reference to > `aio_return64' > > > > I tried to link librt.a and libaio.a, it does not work with the > following option: > > -L/usr/lib/x86_64-linux-gnu -lrt -laio > > > > Any comments and suggestion will be welcome. > > > > Shuchi > > > > _______________________________________________ > > 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] Compile Fortran code with -static
by Rajeev Thakur 08 Nov '14

08 Nov '14

If you don't need to use the MPI-IO functions, try configuring with --disable-romio. Rajeev On Nov 8, 2014, at 9:58 AM, Shuchi Yang <yang.shuchi(a)gmail.com> wrote: > 1) At Ubuntu 14.04, Intel Fortran 2015 xe > Download mpich-3.13 > It works well with general purpose > 2) I need compile the fortran code with -static to run on machine without Intel Fortran environment so I use -static option to compile both MPICH and FORTRAN code. I met the following error > > /mpich/lib/libmpi.a(lib_libmpi_la-tcp_init.o): In function `MPID_nem_tcp_get_business_card': > src/mpid/ch3/channels/nemesis/netmod/tcp/tcp_init.c:(.text+0x319): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking > /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_IwriteContig': > adio/common/ad_iwrite.c:(.text+0xb7): undefined reference to `aio_write64' > /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio': > adio/common/ad_iwrite.c:(.text+0x2dc): undefined reference to `aio_write64' > adio/common/ad_iwrite.c:(.text+0x2e6): undefined reference to `aio_read64' > /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio_poll_fn': > adio/common/ad_iwrite.c:(.text+0x4d0): undefined reference to `aio_error64' > adio/common/ad_iwrite.c:(.text+0x4f0): undefined reference to `aio_return64' > /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio_wait_fn': > adio/common/ad_iwrite.c:(.text+0x65d): undefined reference to `aio_suspend64' > adio/common/ad_iwrite.c:(.text+0x6a0): undefined reference to `aio_error64' > adio/common/ad_iwrite.c:(.text+0x6b5): undefined reference to `aio_return64' > > I tried to link librt.a and libaio.a, it does not work with the following option: > -L/usr/lib/x86_64-linux-gnu -lrt -laio > > Any comments and suggestion will be welcome. > > Shuchi > > _______________________________________________ > 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

Compile Fortran code with -static
by Shuchi Yang 08 Nov '14

08 Nov '14

1) At Ubuntu 14.04, Intel Fortran 2015 xe Download mpich-3.13 It works well with general purpose 2) I need compile the fortran code with -static to run on machine without Intel Fortran environment so I use -static option to compile both MPICH and FORTRAN code. I met the following error /mpich/lib/libmpi.a(lib_libmpi_la-tcp_init.o): In function `MPID_nem_tcp_get_business_card': src/mpid/ch3/channels/nemesis/netmod/tcp/tcp_init.c:(.text+0x319): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_IwriteContig': adio/common/ad_iwrite.c:(.text+0xb7): undefined reference to `aio_write64' /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio': adio/common/ad_iwrite.c:(.text+0x2dc): undefined reference to `aio_write64' adio/common/ad_iwrite.c:(.text+0x2e6): undefined reference to `aio_read64' /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio_poll_fn': adio/common/ad_iwrite.c:(.text+0x4d0): undefined reference to `aio_error64' adio/common/ad_iwrite.c:(.text+0x4f0): undefined reference to `aio_return64' /mpich/lib/libmpi.a(ad_iwrite.o): In function `ADIOI_GEN_aio_wait_fn': adio/common/ad_iwrite.c:(.text+0x65d): undefined reference to `aio_suspend64' adio/common/ad_iwrite.c:(.text+0x6a0): undefined reference to `aio_error64' adio/common/ad_iwrite.c:(.text+0x6b5): undefined reference to `aio_return64' I tried to link librt.a and libaio.a, it does not work with the following option: -L/usr/lib/x86_64-linux-gnu -lrt -laio Any comments and suggestion will be welcome. Shuchi _______________________________________________ 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] Force MPICH2 to not use network adapter
by Balaji, Pavan 07 Nov '14

07 Nov '14

Hi Igor, Unfortunately, Windows is not supported anymore in MPICH. http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_can… But 1.4.1p1 should be automatically detecting and using shared memory inside the node, and not using the network. Sorry, I know that doesn’t help you. But this is an unsupported platform and version of MPICH. Regards, — Pavan > On Nov 7, 2014, at 10:07 AM, Igor Raskin <igor.raskin(a)weblakes.com> wrote: > > Hi Pavan, > > Thank you for your response. > > I should have given more details about the platform and MPICH2 I am using. > > The platform is Windows 7 Professional. > > The version of MPICH2 is 1.4.1 (32-bit) which is latest version of MPICH2 that I can find. > > To what version of MPICH2 should I upgrade? > > Thank you and best regards, > Igor > > -----Original Message----- > From: Balaji, Pavan [mailto:[email protected]] > Sent: Friday, November 07, 2014 12:50 AM > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Force MPICH2 to not use network adapter > > Igor, > > Based on the fact that you are asking about smpd and -localonly options, I’m assuming you are using a super-ancient vesion of MPICH that dinosaurs used to compute with. Perhaps you can upgrade to the latest version? For the past 10 years or so, we have been automatically detecting shared memory and using it internally without going over the network. > > — Pavan > >> On Nov 6, 2014, at 8:28 PM, Igor Raskin <igor.raskin(a)weblakes.com> wrote: >> >> Hello, >> >> I am running a multi-process calculations using MPICH2 from Argonne National Laboratory. The run is on a single machine, so -localonly option of mpiexec is used. Usually everything works. >> If the network adapter is enabled when the run starts, and if I disable it during the run, the run fails with error stating: >> >> op_read error on left context: Error = -1 >> >> op_read error on parent context: Error = -1 >> >> unable to read the cmd header on the left context, Error = -1 . >> unable to read the cmd header on the parent context, Error = -1 . >> Error posting readv, An existing connection was forcibly closed by the >> remote host.(10054) connection to my parent broken, aborting. >> state machine failed. >> However, if the network adapter is disabled when the run is started, I can enable/disable the adapter as many times as I want, and the run still proceeds to the end. >> >> Is there a way to run mpiexec or modify smpd configuration such that MPICH2 is not using network adapter for inter-process communication for local runs even if the adapter is available when the run starts? >> >> Thank you, >> >> Igor >> _______________________________________________ >> 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 > > _______________________________________________ > 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 -- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji _______________________________________________ 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] environment settings to select the preferred TCP netmask
by Junchao Zhang 07 Nov '14

07 Nov '14

On Fri, Nov 7, 2014 at 4:07 PM, Ebalunode, Jerry O <jebaluno(a)central.uh.edu> wrote: > Hello all: > I am currently using mpich3.1.3. I need help in tuning the environment > settings to select the prefferred TCP netmask or network. The variables > > MPICH_TCP_NETMASK > MPICH_NETMASK > MPIR_CVAR_NEMESIS_TCP_NETMASK > > don’t seem to the working > MPICHers, do we have variables for this purpose? "mpivars | grep MASK" finds none. > > Also, how can I tune the eager threshhold. Intel MPI uses I_MPI_THRESHOLD > for doing this. Thanks for all the help advance. > mpivars | grep EAGER > > -Jerry > > University of Houston > > > > _______________________________________________ > 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

environment settings to select the preferred TCP netmask
by Ebalunode, Jerry O 07 Nov '14

07 Nov '14

Hello all: I am currently using mpich3.1.3. I need help in tuning the environment settings to select the prefferred TCP netmask or network. The variables MPICH_TCP_NETMASK MPICH_NETMASK MPIR_CVAR_NEMESIS_TCP_NETMASK don’t seem to the working Also, how can I tune the eager threshhold. Intel MPI uses I_MPI_THRESHOLD for doing this. Thanks for all the help advance. -Jerry University of Houston _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0