On Mar 25, 2013, at 10:21 PM, Timothy Stitt wrote:
> I've inherited a MPI code that was written ~8-10 years ago
Always a fun situation to be in. :-)
> and it predominately uses MPI persistent communication routines for data
> transfers e.g. MPI_SEND_INIT, MPI_RECV_INIT, MPI_START etc. I was
On Mar 22, 2013, at 8:34 AM, Siegmar Gross
wrote:
> openSuSE Linux 12.1, x86_64, SunC 5.12, 32-bit
> --
>
> linpc1 openmpi-1.9-Linux.x86_64.32_cc 113 tail log.make.Linux.x86_64.32_cc
> Making all in mpi/fortran/use-mpi-f08
> make[2]: Entering directo
On Mar 22, 2013, at 8:06 AM, Siegmar Gross
wrote:
> openSuSE Linux 12.1, x86_64, SunC 5.12, 32-bit
> --
>
> tyr openmpi-1.7-Linux.x86_64.32_cc 547 tail log.make.Linux.x86_64.32_cc
> Making all in mpi/fortran/use-mpi-f08
> make[2]: Entering directory `
On Mar 21, 2013, at 9:52 PM, David A. Boger wrote:
> If I add "-mca oob_tcp_if_exclude cscotun0", then the corresponding address
> for that vpn interface no longer shows up in contact.txt, but the problem
> remains. I also add "-mca btl ^cscotun0 -mca btl_tcp_if_exclude cscotun0"
> with no eff
Sorry for the delay in replying.
I see that there's an NPB 3.3.1 available these days -- did that fix the bug,
perchance?
On Mar 20, 2013, at 5:08 PM, kme...@cs.uh.edu wrote:
> Hello ,
>
> I am running NAS parallel benchmark's BTIO benchmark (NPB v 3.3) for class
> D and 1 process.
>
> `make
Just curious -- what docs are you referring to? I don't see opal_signal
referred to in the README, orterun.1, or the faq...
On Mar 20, 2013, at 11:32 AM, Ralph Castain wrote:
> Simple to do - I added a clearer error message to the trunk and marked it for
> inclusion in the eventual v1.7.1 re
Yes, it looks like you have a heterogeneous system (i.e., a binary compiled on
one server doesn't necessarily run properly on another server).
In this case, you should see the heterogeneous section of the FAQ.
Fair warning, though -- heterogeneous systems are more difficult to
manage/maintain/u
It may be because the other system is running upgraded version of linux
which is not having infiniband drivers. Any solution?
On Tue, Mar 26, 2013 at 12:42 PM, Syed Ahsan Ali wrote:
> Tried this but mpirun exits with this error
>
> mpirun -np 40 /home/MET/hrm/bin/hrm
> librdmacm: couldn't read A
Tried this but mpirun exits with this error
mpirun -np 40 /home/MET/hrm/bin/hrm
librdmacm: couldn't read ABI version.
librdmacm: assuming: 4
librdmacm: couldn't read ABI version.
librdmacm: assuming: 4
librdmacm: couldn't read ABI version.
librdmacm: assuming: 4
librdmacm: couldn't read ABI versio
