*Hi, I got errors when I running lamtest-7.1.5b... "laminfo" shows this:*
LAM/MPI: 7.1.5b1
Prefix: /usr/local
Architecture: x86_64-unknown-linux-gnu
Configured by: root
Configured on: Mon Apr 27 19:00:12 CLT 2009
Configure host: cbuach
Memory manager: ptmalloc2
C bindings: yes
C++ bindings: yes
Fortran bindings: no
C compiler: gcc
C++ compiler: g++
Fortran compiler: false
Fortran symbols: none
C profiling: yes
C++ profiling: yes
Fortran profiling: no
C++ exceptions: no
Thread support: yes
ROMIO support: yes
IMPI support: no
Debug support: no
Purify clean: no
SSI boot: globus (API v1.1, Module v0.6)
SSI boot: rsh (API v1.1, Module v1.1)
SSI boot: slurm (API v1.1, Module v1.0)
SSI coll: lam_basic (API v1.1, Module v7.1)
SSI coll: shmem (API v1.1, Module v1.0)
SSI coll: smp (API v1.1, Module v1.2)
SSI rpi: crtcp (API v1.1, Module v1.1)
SSI rpi: lamd (API v1.0, Module v7.1)
SSI rpi: sysv (API v1.0, Module v7.1)
SSI rpi: tcp (API v1.0, Module v7.1)
SSI rpi: usysv (API v1.0, Module v7.1)
SSI cr: self (API v1.0, Module v1.0)
*"./configure" shows this:*
Configuring LAM test suite version 7.1.5b1
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for mpicc... yes
checking for gcc... mpicc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether mpicc accepts -g... yes
checking for mpicc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of mpicc... gcc3
checking for mpic++... yes
checking whether we are using the GNU C++ compiler... yes
checking whether mpic++ accepts -g... yes
checking dependency style of mpic++... gcc3
checking for mpif77... yes
checking whether we are using the GNU Fortran 77 compiler... no
checking whether mpif77 accepts -g... no
checking for ranlib... ranlib
checking for mpi.h... yes
checking for MPI_Initialized in -lmpi... yes
checking if have Fortran MPI bindings... no
checking if supposed to have Fortran MPI bindings... no
checking if have MPI-2 C++ support... yes
checking if have MPI-2 IO support... yes
checking if using LAM/MPI... yes
checking for LAM/Trillium... no
checking if have uniform filesystem... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config/runtests.sh
config.status: creating config/Makefile
config.status: creating reporting/Makefile
config.status: creating ccl/Makefile
config.status: creating ccl/intercomm/Makefile
config.status: creating comm/Makefile
config.status: creating dtyp/Makefile
config.status: creating dynamic/Makefile
config.status: creating env/Makefile
config.status: creating group/Makefile
config.status: creating info/Makefile
config.status: creating io/Makefile
config.status: creating lam/Makefile
config.status: creating lam/basic/Makefile
config.status: creating lam/ccl/Makefile
config.status: creating lam/dynamic/Makefile
config.status: creating lam/env/Makefile
config.status: creating onesided/Makefile
config.status: creating pt2pt/Makefile
config.status: creating topo/Makefile
config.status: creating reporting/lamtest_config.h
config.status: reporting/lamtest_config.h is unchanged
config.status: executing depfiles commands
config.status: executing default commands
*When I run "make check" appear the error like this and are iteratives:*
It seems that some error has occurred during MPI_INIT. This will
cause your process to abort. These kinds of errors are usually
system-related, such as running out of disk space, running out of
memory, or something more serious such as data not being passed
between processes properly. That is, you should not be seeing this
error message; if you are, something is likely Very Wrong with your
system. :-(
Perhaps this Unix error message will help:
Unix errno: 14
Bad address
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
*** Oops -- I cannot open the LAM help file.
*** I tried looking for it in the following places:
***
*** $HOME/lam-helpfile
*** $HOME/lam-7.1.5b1-helpfile
*** $HOME/etc/lam-helpfile
*** $HOME/etc/lam-7.1.5b1-helpfile
*** $LAMHELPDIR/lam-helpfile
*** $LAMHELPDIR/lam-7.1.5b1-helpfile
*** $LAMHOME/etc/lam-helpfile
*** $LAMHOME/etc/lam-7.1.5b1-helpfile
*** $SYSCONFDIR/lam-helpfile
*** $SYSCONFDIR/lam-7.1.5b1-helpfile
***
*** You were supposed to get help on the program "MPI"
*** about the topic "bad-mpi-init"
***
*** Sorry!
-----------------------------------------------------------------------------
It seems that [at least] one of the processes that was started with
mpirun did not invoke MPI_INIT before quitting (it is possible that
more than one process did not invoke MPI_INIT -- mpirun was only
notified of the first one, which was on node n0).
mpirun can *only* be used with MPI programs (i.e., programs that
invoke MPI_INIT and MPI_FINALIZE). You can use the "lamexec" program
to run non-MPI programs over the lambooted nodes.
-----------------------------------------------------------------------------
I attached de config.log in addition. I would appreciate any help, thanks.
--
Dímar González S.
Estudiante Ingienería Civil en Informática
Universidad Austral de Chile
|
