December 2011 - Mpich2-core - mailman3.cels.anl.gov

Re: [mpich2-core] Visiting ANL
by Rajeev Thakur 05 Jan '12

05 Jan '12

Vivek, For me, the last week of January would the best. But you don't need me as such. You can come as long as others are there. I am CCing others to see if the Thu or Fri of the MPI Forum week works for them. Friday might. Rajeev On Dec 30, 2011, at 2:28 PM, Vivek Kale wrote: > Dear Dr. Thakur, > > We spoke about visiting ANL at the INRIA jointlab workshop(nov 21-23). I am wondering if sometime first week of jan or second week of jan would work. It looks like second week of Jan might work, though of course it would have to be something like Thursday or Friday since there is the MPI forum on the mon- wed of that week, and it is in California, as you mentioned. The main thing I wanted to visit for is mpich2 shared memory extensions, and hopefully have a face to face meeting with Darius Buntinas about implementation of some of the functions within Mpich2( along with some tests I have for these functions). > > -Vivek

5 5

build failure
by Rajeev Thakur 03 Jan '12

03 Jan '12

The nightly tests were building on Dec 21, but are failing since Dec 22. So some check-in on Dec 22 is the culprit. Rajeev

4 3

trunk doesn't build
by Pavan Balaji 27 Dec '11

27 Dec '11

The mpich2 trunk doesn't build anymore. Hopefully, this problem occurred after 1.5a2 was released. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

bcastlength: Ring ids do not match
by Darius Buntinas 22 Dec '11

22 Dec '11

In the nightlies, bcastlength is reporting an invalid error code because the error ring IDs don't match. I started looking into this, but before I go much further I wanted to check if anyone else is looking into this, or has some background on it. Also, does anyone know if the error ring stuff is documented anywhere? Thanks, -d

3 5

Fwd: src/mpe2/src/slog2sdk/aclocal_util.m4
by Dave Goodell 19 Dec '11

19 Dec '11

Beware SVN. Looks like this bug is only fixed in SVN-1.7.0 and later. -Dave Begin forwarded message: > From: Dave Goodell <goodell(a)mcs.anl.gov> > Date: December 19, 2011 5:12:59 PM CST > To: Dave Goodell <goodell(a)mcs.anl.gov> > Cc: Anthony Chan <chan(a)mcs.anl.gov> > Subject: Re: src/mpe2/src/slog2sdk/aclocal_util.m4 > > Ugh.. looks like it's an SVN bug: http://subversion.tigris.org/issues/show_bug.cgi?id=3351 > > I haven't yet figured out which version of SVN contains the fix. > > It looks like you can work around this by creating a fresh checkout of the SVN working copy though. > > -Dave > > On Dec 19, 2011, at 5:06 PM CST, Dave Goodell wrote: > >> Hmm... this is bizarre. AFAIK the propedit or the propdel should have done it. Let me dig a bit. >> >> -Dave >> >> On Dec 19, 2011, at 4:58 PM CST, Anthony Chan wrote: >> >>> >>> I was happy too early. The problem remains. >>> >>> I even did propdel svn:externals to slog2sdk, but I still see >>> the file after I removed it by hand ??? >>> >>> /homes/chan/mpich_work/mpich2/src/mpe2/src/slog2sdk> svn status >>> ! X aclocal_util.m4 >>> >>> As soon I did a svn update on slo2gsdk directory, the file >>> got restored. >>> >>> /homes/chan/mpich_work/mpich2/src/mpe2/src/slog2sdk> svn update >>> Restored 'aclocal_util.m4' >>> At revision 9397. >>> >>> Maybe I still miss doing some step ? >>> >>> ----- Original Message ----- >>>> Correct. >>>> >>>> -Dave >>>> >>>> On Dec 19, 2011, at 4:01 PM CST, Anthony Chan wrote: >>>> >>>>> >>>>> Thank you very much. That works! Is svn:externals a property of >>>>> the directory and not file ? >>>>> >>>>> ----- Original Message ----- >>>>>> Oops. That should have been: >>>>>> >>>>>> svn propedit svn:externals src/mpe2/src/slog2sdk >>>>>> >>>>>> -Dave >>>>>> >>>>>> On Dec 19, 2011, at 3:53 PM CST, Anthony Chan wrote: >>>>>> >>>>>>> >>>>>>> I had done that before emailing you, but propedit only gives me a >>>>>>> blank file. >>>>>>> >>>>>>> ----- Original Message ----- >>>>>>>> svn propedit svn:externals src/mpe2/src/slog2sdk/aclocal_util.m4 >>>>>>>> >>>>>>>> Then delete whichever entries don't make sense with your editor, >>>>>>>> write >>>>>>>> & quit the file. You'll then need to "svn commit" the edited >>>>>>>> property >>>>>>>> (which you can do in conjunction with other files, if >>>>>>>> appropriate). >>>>>>>> >>>>>>>> -Dave >>>>>>>> >>>>>>>> On Dec 19, 2011, at 3:44 PM CST, Anthony Chan wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> Hi Dave, >>>>>>>>> >>>>>>>>> Can you tell me how to remove the svn:external file >>>>>>>>> src/mpe2/src/slog2sdk/aclocal_util.m4 (added by Pavan >>>>>>>>> for an incorrect fix) ? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> A.Chan >> >

1 0

Re: [mpich2-core] 1.5a2 release
by Rajeev Thakur 19 Dec '11

19 Dec '11

Let's try to get 1.5a2 out before the holiday break. To get ready for that, let's meet tomorrow 1.00-2.00 to go through the tickets. I have reserved 3173. Rajeev > -------- Original Message -------- > Subject: Re: [mpich2-core] 1.5a2 release > Date: Mon, 21 Nov 2011 09:24:50 -0600 > From: Dave Goodell <goodell(a)mcs.anl.gov> > Reply-To: mpich2-core(a)mcs.anl.gov > To: mpich2-core(a)mcs.anl.gov > > I also want to get a few more of the build configurations working, mainly the rest of the netmods. This is nearly done, so I should be able to finish it up by early next week. > > -Dave > > On Nov 20, 2011, at 12:03 PM CST, Pavan Balaji wrote: > >> >> In the SC release rush, we missed out adding a few pieces to the 1.5a1 release. We should try to add them and push out a 1.5a2 release soon (maybe by next week). Here's the list of features I'm aware of. If there's something that cannot wait for a January 1.5a3 release, let me know. >> >> 1. ARMCI-MPI refresh >> 2. MPI-3 tools interface >> 3. Fix for hwloc with libpci. >> >> -- Pavan >> >> -- >> Pavan Balaji >> http://www.mcs.anl.gov/~balaji >

4 8

nightly tests failing
by Rajeev Thakur 19 Dec '11

19 Dec '11

Some change that went in after 11.30am today is causing all tests to seg fault. The 11.30am version was working fine. Rajeev

2 1

Fwd: [mpich-discuss] Errors related to the increased number of tasks
by Rajeev Thakur 16 Dec '11

16 Dec '11

Any idea what this error is? Rajeev Begin forwarded message: > From: Bernard Chambon <bernard.chambon(a)cc.in2p3.fr> > Date: December 16, 2011 8:49:15 AM CST > To: mpich-discuss(a)mcs.anl.gov > Subject: Re: [mpich-discuss] Errors related to the increased number of tasks > Reply-To: mpich-discuss(a)mcs.anl.gov > > Hi, > > Le 15 déc. 2011 à 17:22, Bernard Chambon a écrit : > >> I'm still working on failures encountered as the number of tasks increases >> (Using mpich2-1.4, compiled with gcc 4.1, on Scientific Linux 5 , 2.6.18-238.12cc.el5) >> > > Other tests, on the same machine with mpich2 1.0 then 1.1, 1.2 etc > > >mpich2version > MPICH2 Version: 1.0.8p1 > MPICH2 Release date: Unknown, built on Tue Apr 21 13:52:10 CEST 2009 > MPICH2 Device: ch3:sock > MPICH2 configure: -prefix=/usr/local/mpich2 > MPICH2 CC: gcc -O2 > MPICH2 CXX: c++ -O2 > MPICH2 F77: g77 -O2 > MPICH2 F90: f95 -O2 > > >mpicc -O2 -I $MPICH_HOME/include -L $MPICH_HOME/lib -o bin/basic_test basic_test.c > > >mpiexec -np 256 bin/basic_test > Running 256 tasks > > >mpiexec -np 512 bin/basic_test > Running 512 tasks > > >mpiexec -np 512 bin/basic_test > Running 512 tasks > > > > With Mpich2 1.1 and beyond , I got error with around 150 tasks > I probably ommitted something when compiling those versions , but I don't know where to look for > > > >mpich2version > MPICH2 Version: 1.1b1 > MPICH2 Release date: Unknown, built on Fri Dec 16 15:30:19 CET 2011 > MPICH2 Device: ch3:nemesis > MPICH2 configure: --prefix=//scratch/BC/mpich2-1.1 > MPICH2 CC: /usr/bin/gcc -m64 -O2 > MPICH2 CXX: c++ -m64 -O2 > MPICH2 F77: /usr/bin/f77 -O2 > MPICH2 F90: f95 -O2 > > > >mpicc -O2 -I $MPICH_HOME/include -L $MPICH_HOME/lib -o bin/basic_test basic_test.c > >mpiexec -np 100 bin/basic_test > Running 100 tasks > > >mpiexec -np 120 bin/basic_test > Running 120 tasks > > >mpiexec -np 150 bin/basic_test > Assertion failed in file /scratch/BC/mpich2-1.1b1/src/util/wrappers/mpiu_shm_wrappers.h at line 919: seg_sz > 0 > internal ABORT - process 0 > rank 0 in job 26 ccwpge0001_56217 caused collective abort of all ranks > exit status of rank 0: return code 1 > > > >mpich2version > MPICH2 Version: 1.2.1 > MPICH2 Release date: Unknown, built on Fri Dec 16 13:40:20 CET 2011 > MPICH2 Device: ch3:nemesis > MPICH2 configure: --prefix=//scratch/BC/mpich2-1.2 > MPICH2 CC: /usr/bin/gcc -m64 -O2 > MPICH2 CXX: c++ -m64 -O2 > MPICH2 F77: /usr/bin/f77 -O2 > MPICH2 F90: f95 -O2 > > >mpicc -O2 -I $MPICH_HOME/include -L $MPICH_HOME/lib -o bin/basic_test basic_test.c > > > >mpiexec -np 96 bin/basic_test > Running 96 tasks > >mpiexec -np 96 bin/basic_test > Running 96 tasks > >mpiexec -np 120 bin/basic_test > Running 120 tasks > >mpiexec -np 120 bin/basic_test > Running 120 tasks > >mpiexec -np 130 bin/basic_test > Assertion failed in file /scratch/BC/mpich2-1.2.1/src/util/wrappers/mpiu_shm_wrappers.h at line 923: seg_sz > 0 > internal ABORT - process 0 > rank 0 in job 16 ccwpge0001_56217 caused collective abort of all ranks > exit status of rank 0: return code 1 > > Best regards > > > PS : > the test code > > int basicTest(int argc, char** argv) { > if (MPI_Init(&argc, &argv) != MPI_SUCCESS ) { > printf("Error calling MPI_Init !!, exiting \n") ; fflush(stdout); > return(1); > } > > int rank; > if ( MPI_Comm_rank(MPI_COMM_WORLD, &rank)!= MPI_SUCCESS ) { > printf("Error calling MPI_Comm_rank !!, exiting \n") ; fflush(stdout); > MPI_Abort(MPI_COMM_WORLD, 1); > return(1); > } > > if (rank == 0) { > int nprocs; > if (MPI_Comm_size(MPI_COMM_WORLD, &nprocs)!= MPI_SUCCESS ) { > printf("Error calling MPI_Comm_size !!, exiting \n") ; fflush(stdout); > MPI_Abort(MPI_COMM_WORLD, 1); > return(1); > } > > printf("Running %d tasks \n", nprocs) ; fflush(stdout); > MPI_Finalize(); > return(0); > } else { > sleep(1); > MPI_Finalize(); // Necessaire ssi <= mpich2-1.2 > return(0); > } > > } > /******************************/ > int main(int argc, char** argv) { > basicTest(argc, argv); > } > > > --------------- > Bernard CHAMBON > IN2P3 / CNRS > 04 72 69 42 18 > > _______________________________________________ > mpich-discuss mailing list mpich-discuss(a)mcs.anl.gov > To manage subscription options or unsubscribe: > https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss

2 1

Fwd: [mpich-discuss] Problem using mpi_type_create_f90_integer
by Rajeev Thakur 14 Dec '11

14 Dec '11

Is this related to the earlier bug report from Cray about type_create_f90 stuff? Rajeev Begin forwarded message: > From: Thomas Jahns <jahns(a)dkrz.de> > Date: December 14, 2011 7:33:39 AM CST > To: mpich-discuss(a)mcs.anl.gov > Subject: [mpich-discuss] Problem using mpi_type_create_f90_integer > Reply-To: mpich-discuss(a)mcs.anl.gov > > Hello, > > I'm having some problems when using mpi_type_create_f90_integer, where, for 8 > byte integers (i.e. requesting 18 decimal places), I get an immediate error for > and for 4 byte integers I get a later segmentation-fault when committing a > struct type containing the result of mpi_type_create_f90_integer, both bugs > happen with the current Intel Fortran compiler 12.1.0 20110811 and NAG Fortran > Compiler Release 5.2(747) (with gcc 4.6.1 host compiler for the NAG). > > The below example exhibits both problem when run after compilation with defining > either WITH_BUG1 or WITH_BUG2. > > In the case of WITH_BUG1 I get: > > $ ~/opt/mpich2-1.4.1p1-nag52-x64-linux/bin/mpif90 -fpp -DWITH_BUG1 bug.f90 > NAG Fortran Compiler Release 5.2(747) > Extension: /home/tjahns/opt/mpich2-1.4.1p1-nag52-x64-linux/include/mpif.h, line > 479: Byte count on numeric data type > detected at *@8 > Extension: /home/tjahns/opt/mpich2-1.4.1p1-nag52-x64-linux/include/mpif.h, line > 492: Byte count on numeric data type > detected at *@8 > Extension: /home/tjahns/opt/mpich2-1.4.1p1-nag52-x64-linux/include/mpif.h, line > 493: Byte count on numeric data type > detected at *@8 > Warning: bug.f90, line 44: Unused external reference MPI_WTICK > detected at TEST_F90INT@<end-of-statement> > Warning: bug.f90, line 44: Unused external reference PMPI_WTICK > detected at TEST_F90INT@<end-of-statement> > Warning: bug.f90, line 44: Unused external reference PMPI_WTIME > detected at TEST_F90INT@<end-of-statement> > Warning: bug.f90, line 44: Unused external reference MPI_WTIME > detected at TEST_F90INT@<end-of-statement> > [NAG Fortran Compiler normal termination, 7 warnings] > $ ./a.out > Fatal error in MPI_Type_create_f90_integer: Other MPI error, error stack: > MPI_Type_create_f90_integer(117): MPI_Type_create_f90_int (range=14) failed > MPI_Type_create_f90_integer(97).: No integer type with 14 digits of range is > avaiable > > The second bug manifests itself in a segmentation fault I've traced to dlp being > invalid in MPID_Segment_init. > > $ ~/opt/mpich2-1.4.1p1-nag52-x64-linux/bin/mpif90 -fpp -DWITH_BUG2 bug.f90 > NAG Fortran Compiler Release 5.2(747) > Extension: /home/tjahns/opt/mpich2-1.4.1p1-nag52-x64-linux/include/mpif.h, line > 479: Byte count on numeric data type > detected at *@8 > Extension: /home/tjahns/opt/mpich2-1.4.1p1-nag52-x64-linux/include/mpif.h, line > 492: Byte count on numeric data type > detected at *@8 > Extension: /home/tjahns/opt/mpich2-1.4.1p1-nag52-x64-linux/include/mpif.h, line > 493: Byte count on numeric data type > detected at *@8 > Warning: bug.f90, line 44: Unused external reference MPI_WTICK > detected at TEST_F90INT@<end-of-statement> > Warning: bug.f90, line 44: Unused external reference PMPI_WTICK > detected at TEST_F90INT@<end-of-statement> > Warning: bug.f90, line 44: Unused external reference PMPI_WTIME > detected at TEST_F90INT@<end-of-statement> > Warning: bug.f90, line 44: Unused external reference MPI_WTIME > detected at TEST_F90INT@<end-of-statement> > [NAG Fortran Compiler normal termination, 7 warnings] > $ gdb ./a.out > GNU gdb (GDB) 7.0.1-debian > Copyright (C) 2009 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from > /home/tjahns/bug-reporting/mpich2-mpi_type_create_f90_integer_problem/a.out...done. > (gdb) r > Starting program: > /home/tjahns/bug-reporting/mpich2-mpi_type_create_f90_integer_problem/a.out > [Thread debugging using libthread_db enabled] > > Program received signal SIGSEGV, Segmentation fault. > MPID_Segment_init (buf=0x0, count=<value optimized out>, handle=-1946157051, > segp=0x703da0, flag=<value optimized out>) > at > ../../../../../../mpich2-1.4.1p1/src/mpid/common/datatype/dataloop/segment.c:173 > 173 DLOOP_Stackelm_load(elmp, dlp, 0); > (gdb) bt > #0 MPID_Segment_init (buf=0x0, count=<value optimized out>, > handle=-1946157051, segp=0x703da0, flag=<value optimized out>) > at > ../../../../../../mpich2-1.4.1p1/src/mpid/common/datatype/dataloop/segment.c:173 > #1 0x000000000045e5ed in DLOOP_Dataloop_create_flattened_struct (count=2, > blklens=0x703d7c, disps=0x703d88, oldtypes=0x703d70, dlp_p=0x6d63b0, > dlsz_p=0x6d63b8, dldepth_p=0x6d63bc, flag=0) > at > ../../../../../../mpich2-1.4.1p1/src/mpid/common/datatype/dataloop/dataloop_create_struct.c:581 > #2 MPID_Dataloop_create_struct (count=2, blklens=0x703d7c, disps=0x703d88, > oldtypes=0x703d70, dlp_p=0x6d63b0, dlsz_p=0x6d63b8, dldepth_p=0x6d63bc, > flag=0) > at > ../../../../../../mpich2-1.4.1p1/src/mpid/common/datatype/dataloop/dataloop_create_struct.c:244 > #3 0x000000000045b91b in MPID_Dataloop_create (type=-1946157050, > dlp_p=0x6d63b0, dlsz_p=0x6d63b8, dldepth_p=0x6d63bc, flag=0) > at > ../../../../../../mpich2-1.4.1p1/src/mpid/common/datatype/dataloop/dataloop_create.c:279 > #4 0x0000000000416b72 in MPID_Type_commit (datatype_p=0x7fffffffc5e4) > at ../../../../../mpich2-1.4.1p1/src/mpid/common/datatype/mpid_type_commit.c:43 > #5 0x000000000040dd7a in MPIR_Type_commit_impl ( > datatype=<value optimized out>) > at ../../../../mpich2-1.4.1p1/src/mpi/datatype/type_commit.c:43 > #6 0x000000000040df4b in PMPI_Type_commit (datatype=0x7fffffffc5e4) > at ../../../../mpich2-1.4.1p1/src/mpi/datatype/type_commit.c:114 > #7 0x000000000040d849 in pmpi_type_commit_ (v1=<value optimized out>, > ierr=0x7fffffffc5e8) > at ../../../../mpich2-1.4.1p1/src/binding/f77/type_commitf.c:190 > #8 0x000000000040d609 in main (argc=1, argv=0x7fffffffc6d8) at bug.f90:24 > (gdb) > > If any extra information might be useful, I'll be happy to provide. > > Regards, > Thomas > -- > Thomas Jahns > DKRZ GmbH, Department: Application software > > Deutsches Klimarechenzentrum > Bundesstraße 45a > D-20146 Hamburg > > Phone: +49-40-460094-151 > Fax: +49-40-460094-270 > Email: Thomas Jahns <jahns(a)dkrz.de> > _______________________________________________ > mpich-discuss mailing list mpich-discuss(a)mcs.anl.gov > To manage subscription options or unsubscribe: > https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss

4 3

Testing
by William Gropp 14 Dec '11

14 Dec '11

I ran the specialtests (a necessary part of testing before a release; see http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release ), and found a number of failures. I think I have a fix for the last one (debuginfo failure), and some of the others are due to known problems. I haven't looked at the rlog failure. Some of the other tests required updates to the speciatest script due to changes in the environment. This is also a reminder that the list of tests to perform before a release was created from experience - every test on that list has failed at some time in the past. The nightlies (including most essentially the random tests) are a good start, but passing the nightlies alone is nowhere near sufficient for a release. Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign

2 2