I'm seeing the most astonishing bug: In devel mode, in introduction_ex4 of all places, miscommunications are causing parallel runs to hang in devel mode. Running through gdb I can actually watch as one process sends "0" and another receives "1".
I haven't yet ruled out a bug on our part (this is in send_receive_packed_range code that does asynchronous I/O; maybe there was a "1" already in the send queue?) but the same code (as well as all other examples) is fine in dbg and opt modes, as well as with openmpi. (I'm building mvapich2 to try that now) I haven't got any idea how it could be a bug on their part either; in particular I see the same bug with MPICH2 1.4.1, 1.5, and MPICH 3.1.3. Switching compilers from GCC 4.8 to Intel 13.1 doesn't help either. So now I'm starting to wonder if there's merely some new MPI header or linker conflict on the system I'm trying all this on. Are there any other mpich/mpich2 users out there who are using the libMesh git master? --- Roy ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
