Re: [OMPI users] OpenMPI locking up only on IB

In trying to build 1.2.6 with the pgi compilers it makes an MPI library that works with tcp, sm. But it segfaults on openib. Both our intel compiler version and pgi version of 1.2.6 blow up like this when we force IB. So this is a new issue. Is there a way to shut off early completion in

Re: [OMPI users] mpirun w/ enable-mpi-threads spinning up cputime when app path is invalid

Sorry - went to one of your links to get that info. We know OMPI 1.2.x isn't thread safe. This is unfortunately another example of it. Hopefully, 1.3 will be better. Ralph On 7/2/08 11:01 AM, "Ralph H Castain" wrote: > Out of curiosity - what version of OMPI are you using? >

Re: [OMPI users] mpirun w/ enable-mpi-threads spinning up cputime when app path is invalid

Out of curiosity - what version of OMPI are you using? On 7/2/08 10:46 AM, "Steve Johnson" wrote: > If mpirun is given an application that isn't in the PATH, then instead of > exiting it prints the error that it failed to find the executable and then > proceeds spins up cpu

[OMPI users] mpirun w/ enable-mpi-threads spinning up cputime when app path is invalid

If mpirun is given an application that isn't in the PATH, then instead of exiting it prints the error that it failed to find the executable and then proceeds spins up cpu time. strace shows an endless stream of sched_yield(). For example, if "blah" doesn't exist: mpirun -np 16 blah Ditto if

Re: [OMPI users] OpenMPI locking up only on IB

May be this FAQ will help : http://www.open-mpi.org/faq/?category=openfabrics#v1.2-use-early-completion Brock Palen wrote: We have a code (arts) that locks up only when running on IB. Works fine on tcp and sm. When we ran it in a debugger. It locked up on a MPI_Comm_split() That as far

[OMPI users] OpenMPI locking up only on IB

We have a code (arts) that locks up only when running on IB. Works fine on tcp and sm. When we ran it in a debugger. It locked up on a MPI_Comm_split() That as far as I could tell was valid. Because the split was a hack they did to use MPI_File_open() on a single cpu, we reworked it

Re: [OMPI users] Need some help regarding Linpack execution

You also might want to resend this to the MPICH mailing list ­ this is the Open MPI mailing list ;-) On 7/2/08 8:03 AM, "Swamy Kandadai" wrote: > Hi: > May be you do not have 12 entries in your machine.list file. You need to have > atleast np lines in your machine.list > >

Re: [OMPI users] Need some help regarding Linpack execution

Hi: May be you do not have 12 entries in your machine.list file. You need to have atleast np lines in your machine.list Dr. Swamy N. Kandadai IBM Senior Certified Executive IT Specialist STG WW Modular Systems Benchmark Center STG WW HPC and BI CoC Benchmark Center Phone:( 845) 433 -8429 (8-293)

Re: [OMPI users] Problem with gateway between 2 hosts

> > are the 172.x.y.z nodes behind a NAT (hence the communication back > isn't possible - only the stdout from the rsh/ssh is working in this > case)? > > -- Reuti Actually I dont know exactly , I am asking extra informations to my network architect Interesting thing to notice is that LAM

[OMPI users] Need some help regarding Linpack execution

Hi, I want to perform LINPACK test on my m/c, I have only 1 GB RAM on the m/c where I want to run 12 parallel Linpack processes on SLES 10. I am using of Mpich-1.2.7p1. (Mpich is built with -rsh=ssh option) I have modified HPL.dat accordingly, P = 3 Q = 4(so as

[OMPI users] stall with MPI_Scatter and shared memory

We noticed that the attached mpi program using openmpi (version 1.2.6 or openmpi-1.3a1r18785), stalls. compile: mpicc -o scattertest scattertest.c run: mpiexec -n 4 ./scattertest 1 This is for a ubuntu 32 bit system, equipped with 1 Gbyte of memory. A test on a debian system shows the