Open MPI logo

Open MPI User's Mailing List Archives

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

Subject: [OMPI users] forrtl: severe (174): SIGSEGV, segmentation fault occurred
From: Hongyi Zhao (hongyi.zhao_at_[hidden])
Date: 2014-01-02 05:08:01


Hi all,

I compiled openmpi-1.6.5 with ifort-14.0.0, then I use the mpif90
wrapper of openmpi to compile the siesta package - a DFT package,
obtain from here:http://departments.icmab.es/leem/siesta/ .

After I successfully compile the siesta package, then I use it to do
some compuations like this:

$ mpirun -np 2 transiesta < INPUT.fdf > OUTPUT.fdf

In this phase, I meet the followig error:

****************
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line
Source
transiesta 00000000019A8A59 Unknown Unknown Unknown
transiesta 00000000019A73D0 Unknown Unknown Unknown
transiesta 00000000019578F2 Unknown Unknown Unknown
transiesta 000000000190A063 Unknown Unknown Unknown
transiesta 000000000190F9BB Unknown Unknown Unknown
libpthread.so.0 00002AD0C3005030 Unknown Unknown Unknown
transiesta 00000000008109CD Unknown Unknown Unknown
transiesta 000000000068607F Unknown Unknown Unknown
transiesta 000000000069F134 Unknown Unknown Unknown
transiesta 00000000006D5971 Unknown Unknown Unknown
transiesta 00000000006D5A45 Unknown Unknown Unknown
transiesta 000000000047FE56 Unknown Unknown Unknown
libc.so.6 00002AD0C44BCEAD Unknown Unknown Unknown
transiesta 000000000047FD29 Unknown Unknown Unknown
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line
Source
transiesta 00000000019A8A59 Unknown Unknown Unknown
transiesta 00000000019A73D0 Unknown Unknown Unknown
transiesta 00000000019578F2 Unknown Unknown Unknown
transiesta 000000000190A063 Unknown Unknown Unknown
transiesta 000000000190F9BB Unknown Unknown Unknown
libpthread.so.0 00002B302BFB3030 Unknown Unknown Unknown
transiesta 00000000008109CD Unknown Unknown Unknown
transiesta 000000000068607F Unknown Unknown Unknown
transiesta 000000000069F134 Unknown Unknown Unknown
transiesta 00000000006D5971 Unknown Unknown Unknown
transiesta 00000000006D5A45 Unknown Unknown Unknown
transiesta 000000000047FE56 Unknown Unknown Unknown
libc.so.6 00002B302D46AEAD Unknown Unknown Unknown
transiesta 000000000047FD29 Unknown Unknown Unknown
--------------------------------------------------------------------------
mpirun has exited due to process rank 0 with PID 12205 on
node debian-asus exiting improperly. There are two reasons this could occur:

1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"

This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------

****************

I cann't figure out the reason for this issue, any hints will be
highly appreciated.

Regards

-- 
Hongyi Zhao <hongyi.zhao_at_[hidden]>
Xinjiang Technical Institute of Physics and Chemistry
Chinese Academy of Sciences
GnuPG DSA: 0xD108493