segmentation fault after running
Posted: Tue Oct 30, 2007 6:04 pm
I finished compiling parallel vasp 4.6, using ifort 10.0.023, fftw-3.1, blas library, mpich 1.2.7, lam/mpi 7.0.6. Things seem to work during the compilation process. However, when I try to run real vasp jobs, I always got the following errors. Does anybody have similar experience, or happen to know what is wrong? Thanks a lot.
POSCAR, INCAR and KPOINTS ok, starting setup
WARNING: wrap around errors must be expected
FFT: planning ... 2
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
vasp 00000000005FB0E9 Unknown Unknown Unknown
vasp 00000000005DC270 Unknown Unknown Unknown
vasp 00000000005DC2C8 Unknown Unknown Unknown
vasp 000000000041C479 Unknown Unknown Unknown
vasp 0000000000404DE2 Unknown Unknown Unknown
libc.so.6 00000032CF01C4BB Unknown Unknown Unknown
vasp 0000000000404D2A Unknown Unknown Unknown
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 4249 failed on node n0 (192.168.3.1) with exit status 174.
POSCAR, INCAR and KPOINTS ok, starting setup
WARNING: wrap around errors must be expected
FFT: planning ... 2
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
vasp 00000000005FB0E9 Unknown Unknown Unknown
vasp 00000000005DC270 Unknown Unknown Unknown
vasp 00000000005DC2C8 Unknown Unknown Unknown
vasp 000000000041C479 Unknown Unknown Unknown
vasp 0000000000404DE2 Unknown Unknown Unknown
libc.so.6 00000032CF01C4BB Unknown Unknown Unknown
vasp 0000000000404D2A Unknown Unknown Unknown
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 4249 failed on node n0 (192.168.3.1) with exit status 174.