Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

From: Eric Thibodeau (kyron_at_[hidden])
Date: 2006-07-16 18:13:13


/me blushes in shame, it would seem that all I needed to do since the begining was to run a make distclean. I apprantly had some old compiled files lying around. Now I get:

kyron_at_headless ~/1_Files/1_ETS/1_Maitrise/MGL810/Devoir2 $ mpirun --hostfile hostlist -np 4 uname -a
Linux headless 2.6.17-ck1-r1 #1 SMP Tue Jul 11 16:39:18 EDT 2006 x86_64 AMD Opteron(tm) Processor 244 GNU/Linux
Linux headless 2.6.17-ck1-r1 #1 SMP Tue Jul 11 16:39:18 EDT 2006 x86_64 AMD Opteron(tm) Processor 244 GNU/Linux
Linux node0 2.6.16-gentoo-r7 #5 Tue Jul 11 12:30:41 EDT 2006 i686 AMD Athlon(TM) XP 2500+ GNU/Linux
Linux node1 2.6.16-gentoo-r7 #5 Tue Jul 11 12:30:41 EDT 2006 i686 AMD Athlon(TM) XP 2500+ GNU/Linux

Which is correct. Sorry for the misfire, I hadn't thought of cleaning up the compilation dir...

Now that I have that out of the way, I'd like to know how I am supposed to compile my apps so that they can run on an homogenous network with mpi. Here is an example:
kyron_at_headless ~/1_Files/1_ETS/1_Maitrise/MGL810/Devoir2 $ mpicc -L/usr/X/lib -lm -lX11 -O3 mandelbrot-mpi.c -o mandelbrot-mpi
kyron_at_headless ~/1_Files/1_ETS/1_Maitrise/MGL810/Devoir2 $ mpirun --hostfile hostlist -np 3 ~/1_Files/1_ETS/1_Maitrise/MGL810/Devoir2/mandelbrot-mpi
--------------------------------------------------------------------------
Could not execute the executable "/home/kyron/1_Files/1_ETS/1_Maitrise/MGL810/Devoir2/mandelbrot-mpi": Exec format error

This could mean that your PATH or executable name is wrong, or that you do not
have the necessary permissions. Please ensure that the executable is able to be
found and executed.
--------------------------------------------------------------------------
As can be seen with the uname -a that was run previously, I have 2 "local nodes" on the x86_64 and two i686 nodes. I tried to find examples in the Doc on howto compile applications correctly for such a setup without compromising performance but I came short of an example.

Thanks,

Eric
PS: I know..maybe I should start another thread ;)

Le dimanche 16 juillet 2006 14:31, Brian Barrett a écrit :
> On Jul 15, 2006, at 2:58 PM, Eric Thibodeau wrote:
> > But, for some reason, on the Athlon node (in their image on the
> > server I should say) OpenMPI still doesn't seem to be built
> > correctly since it crashes as follows:
> >
> >
> > kyron_at_node0 ~ $ mpirun -np 1 uptime
> >
> > Signal:11 info.si_errno:0(Success) si_code:1(SEGV_MAPERR)
> >
> > Failing at addr:(nil)
> >
> > [0] func:/home/kyron/openmpi_i686/lib/libopal.so.0 [0xb7f6258f]
> >
> > [1] func:[0xffffe440]
> >
> > [2] func:/home/kyron/openmpi_i686/lib/liborte.so.0(orte_init_stage1
> > +0x1d7) [0xb7fa0227]
> >
> > [3] func:/home/kyron/openmpi_i686/lib/liborte.so.0(orte_system_init
> > +0x23) [0xb7fa3683]
> >
> > [4] func:/home/kyron/openmpi_i686/lib/liborte.so.0(orte_init+0x5f)
> > [0xb7f9ff7f]
> >
> > [5] func:mpirun(orterun+0x255) [0x804a015]
> >
> > [6] func:mpirun(main+0x22) [0x8049db6]
> >
> > [7] func:/lib/tls/libc.so.6(__libc_start_main+0xdb) [0xb7de8f0b]
> >
> > [8] func:mpirun [0x8049d11]
> >
> > *** End of error message ***
> >
> > Segmentation fault
> >
> >
> > The crash happens both in the chrooted env and on the nodes. I
> > configured both systems to have Linux and POSIX threads, though I
> > see openmpi is calling the POSIX version (a message on the mailling
> > list had hinted on keeping the Linux threads around...I have to
> > anyways since sone apps like Matlab extensions still depend on
> > this...). The following is the output for the libc info.
>
> That's interesting... We regularly build Open MPI on 32 bit Linux
> machines (and in 32 bit mode on Opteron machines) without too much
> issue. It looks like we're jumping into a NULL pointer, which
> generally means that a ORTE framework failed to initialize itself
> properly. It would be useful if you could rebuild with debugging
> symbols (just add -g to CFLAGS when configuring) and run mpirun in
> gdb. If we can determine where the error is occurring, that would
> definitely help in debugging your problem.
>
> Brian
>
>

-- 
Eric Thibodeau
Neural Bucket Solutions Inc.
T. (514) 736-1436
C. (514) 710-0517