On Feb 20, 2009, at 10:08 AM, Jeff Pummill wrote:
It's probably not the same issue as this is one of the very few
codes that I maintain which is C++ and not fortran :-(
Ok. Note that the error Nysal pointed out was a problem with our
handling of stdin. That might be an issue as well; shou
It's probably not the same issue as this is one of the very few codes
that I maintain which is C++ and not fortran :-(
It behaved similarly on another system when I built it against a new
version (1.0??) of MVAPICH. I had to roll back a version from that as well.
I may contact the lammps peop
Actually, there was a big Fortran bug that crept in after 1.3 that was
just fixed on the trunk last night. If you're using Fortran
applications with some compilers (e.g., Intel), the 1.3.1 nightly
snapshots may have hung in some cases. The problem should be fixed in
tonight's 1.3.1 nightl
It could be the same bug reported here
http://www.open-mpi.org/community/lists/users/2009/02/8010.php
Can you try a recent snapshot of 1.3.1
(http://www.open-mpi.org/nightly/v1.3/) to verify if this has been fixed
--Nysal
On Thu, 2009-02-19 at 16:09 -0600, Jeff Pummill wrote:
> I built a fresh v
Is it possible to attach to any of the MPI processes and see where it
is hung?
On Feb 19, 2009, at 5:09 PM, Jeff Pummill wrote:
I built a fresh version of lammps v29Jan09 against Open MPI 1.3
which in turn was built with Gnu compilers v4.2.4 on an Ubuntu 8.04
x86_64 box. This Open MPI bui
I built a fresh version of lammps v29Jan09 against Open MPI 1.3 which in
turn was built with Gnu compilers v4.2.4 on an Ubuntu 8.04 x86_64 box.
This Open MPI build was able to generate usable binaries such as XHPL
and NPB, but the lammps binary it generated was not usable.
I tried it with a co
