It has been explained in a different thread on [ofa-general] that the
problem lies in a combination of the OpenIB-cma provider not setting the
local and remote port numbers on endpoints correctly and Open MPI
stepping over the IA to save the port number to circumvent this problem,
thereby confusing
Hi,
We use VASP 4.6 in parallel with opemmpi 1.1.2 without any problems on
x86_64 with opensuse and compiled with gcc and Intel fortran and use
torque PBS.
I used standard configure to build openmpi something like
./configure --prefix=/usr/local --enable-static --with-threads
--with-tm=/usr/loc
You say that fixes the problem, does it work even when running more than
one MPI process per node? (that is the case the hack fixes) Simply
doing an mpirun with a -np paremeter higher than the number of nodes you
have set up should trigger this case, and making sure to use '-mca btl
udapl,self
I've run the whole IMB Benchmark Suite on 2, 3, and 4 nodes with 2
processes per node and --mca btl udapl,self. I didn't encouter any problems.
The comment above line 197 says that dat_ep_query() returns wrong port
numbers (which it does indeed), but I can't find any call to
dat_ep_query() in the
OK, strange but good. Yeah I wouldn't be surprised if something has
been changed, though I wouldn't know what, and I don't have time right
now to go digging :( Maybe Don Kerr knows something?
Andrew
Boris Bierbaum wrote:
I've run the whole IMB Benchmark Suite on 2, 3, and 4 nodes with 2
pr
Looking at that section it appears that we store the port value locally
in udapl_addr and use the local copy, so changing the udapl attribute
may not be doing anything for the BTL. I will run some tests as well.
-DON
Andrew Friedley wrote:
OK, strange but good. Yeah I wouldn't be surprised
I thought about it again: There's probably no call to dat_ep_query()
*because* it returns wrong port numbers and the port numbers saved by
the uDAPL BTL code itself are used.
I'll leave the debugging to those who know the code ... ;-)
Boris
Andrew Friedley wrote:
> OK, strange but good. Yeah I
Thank Kevin and Brook for replying to my question. I am going to try
out what Kevin suggested.
Steven.
On 5/9/07, Kevin Radican wrote:
Hi,
We use VASP 4.6 in parallel with opemmpi 1.1.2 without any problems on
x86_64 with opensuse and compiled with gcc and Intel fortran and use
torque PBS.
Hi, Kevin and all. I tried with the following:
./configure --prefix=/usr/local/openmpi-1.2.1 --disable-ipv6
--with-tm=/usr/local/pbs --enable-mpirun-prefix-by-default
--enable-mpi-f90 --with-threads=posix --enable-static
and added the mpi.o in my VASP's makefile but i still got error.
I forg
Oh, no. I tried with ACML and had the same set of errors.
Steven.
On 5/9/07, Steven Truong wrote:
Hi, Kevin and all. I tried with the following:
./configure --prefix=/usr/local/openmpi-1.2.1 --disable-ipv6
--with-tm=/usr/local/pbs --enable-mpirun-prefix-by-default
--enable-mpi-f90 --with-t
Can you send a simple test that reproduces these errors?
I.e., if there's a single, simple package that you can send
instructions on how to build, it would be most helpful if we could
reproduce the error (and therefore figure out how to fix it).
Thanks!
On May 9, 2007, at 2:19 PM, Steven
Hi, Jeff. Thank you very much for looking into this issue. I am
afraid that I can not give you the application/package because it is a
comercial software. I believe that a lot of people are using this
VASP software package http://cms.mpi.univie.ac.at/vasp/.
My current environment uses MPICH
I have mailed the VASP maintainer asking for a copy of the code.
Let's see what happens.
On May 9, 2007, at 2:44 PM, Steven Truong wrote:
Hi, Jeff. Thank you very much for looking into this issue. I am
afraid that I can not give you the application/package because it is a
comercial softw
Due to many requests, the deadline has been extended to May 21, 2007.
sorry for cross-posting
CALL FOR PAPERS
HPCC-07
The 2007 International Conference on High
Thank Jeff very much for your efforts and helps.
On 5/9/07, Jeff Squyres wrote:
I have mailed the VASP maintainer asking for a copy of the code.
Let's see what happens.
On May 9, 2007, at 2:44 PM, Steven Truong wrote:
> Hi, Jeff. Thank you very much for looking into this issue. I am
> afr
Greetings eveyrong,
My name is Mike, and I have recently downloaded the OMPI v1.2.1 and decide
to run the OSU bandwidth benchmark. However, I have noticed a few weird
things during my run.
Btw, I am using FreeBSD 6.2.
The OSU bandwidth test basically pre-post many ISend and IRecv. It tries to
m
16 matches
Mail list logo
