Page 1 of 1

forrtl: severe (174): SIGSEGV, segmentation fault occurred

Posted: Thu Jul 28, 2016 2:10 pm
by pk_ahluwalia7
Sir/mam
I struck to the segmentation error, while doing the calculation on inclusion the spin- orbit coupling parameter ( LSORBIT = TRUE ) or non-collinear parameter ( LNONCOLLINEAR= .TRUE. ). Although, we have successfully installed the full version of vasp without any error.

forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
vasp 0000000003ED4421 Unknown Unknown Unknown
vasp 0000000003ED2B77 Unknown Unknown Unknown
vasp 0000000003E81BB4 Unknown Unknown Unknown
vasp 0000000003E819C6 Unknown Unknown Unknown
vasp 0000000003E2E5EF Unknown Unknown Unknown
vasp 0000000003E3436D Unknown Unknown Unknown
libpthread.so.0 0000003415E0F500 Unknown Unknown Unknown
vasp 00000000006AAFD7 Unknown Unknown Unknown
vasp 00000000008D4FF4 Unknown Unknown Unknown
vasp 0000000000D205E7 Unknown Unknown Unknown
vasp 0000000000455A8C Unknown Unknown Unknown
vasp 000000000043051E Unknown Unknown Unknown
libc.so.6 000000341561ECDD Unknown Unknown Unknown
vasp 0000000000430429 Unknown Unknown Unknown
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
vasp 0000000003ED4421 Unknown Unknown Unknown
vasp 0000000003ED2B77 Unknown Unknown Unknown
vasp 0000000003E81BB4 Unknown Unknown Unknown
vasp 0000000003E819C6 Unknown Unknown Unknown
vasp 0000000003E2E5EF Unknown Unknown Unknown
vasp 0000000003E3436D Unknown Unknown Unknown
libpthread.so.0 0000003415E0F500 Unknown Unknown Unknown
vasp 00000000006AAFD7 Unknown Unknown Unknown
vasp 00000000008D4FF4 Unknown Unknown Unknown
vasp 0000000000D205E7 Unknown Unknown Unknown
vasp 0000000000455A8C Unknown Unknown Unknown
vasp 000000000043051E Unknown Unknown Unknown
libc.so.6 000000341561ECDD Unknown Unknown Unknown
vasp 0000000000430429 Unknown Unknown Unknown

It would be really appreciating if you can give some way out.

Yours Sincerely,

Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr

Posted: Fri Aug 05, 2016 11:52 am
by admin
Very likely is this memory problem. Noncollinear case needs much more memory than a simple case.
Use smaller cell or more cores.

Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr

Posted: Fri Sep 02, 2016 7:08 pm
by rfaccio
Hi
I posted the same problem this year. I tried to run the example from the tutorial, the small one (Fe slab) with the same problem SIGSEV.
I am still unable to run spin-orbit.
Best regards
Ricardo

Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr

Posted: Mon Sep 05, 2016 12:53 pm
by admin
This error was also observed when a different version of a compiler was loaded than that used to compile the code.
Suggested was to rebuild everything (including vasp.5.lib) and make sure that everything was consistent
(check your makefiles and do not use your makefiles from a earlier version).
Cf. http://cms.mpi.univie.ac.at/vasp-forum/ ... EGV#p17363

Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr

Posted: Tue Nov 15, 2016 4:50 pm
by rameshkumar
Dear Sir,

Good day sir!

We just bought a VASP. We have an own workstation (DELL, Model: OPTIPLEX7080). 

We have successfully installed VASP 5.2 version with ifort. While we run to work, we get the following information:

We did not have any problems while working with VASP 4.6 version. If any, could you help me?

[ramesh@localhost si]$ vasp
 vasp.5.2.2 15Apr09 complex
 POSCAR found type information on POSCAR  Si
 POSCAR found :  1 types and    1 ions
 WARNING: PSMAXN for non-local potential too small
 LDA part: xc-table for Pade appr. of Perdew
 POSCAR, INCAR and KPOINTS ok, starting setup
 WARNING: small aliasing (wrap around) errors must be expected
 FFT: planning ...(           1 )
 reading WAVECAR
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source            
vasp               0000000000D1D095  Unknown               Unknown  Unknown
vasp               0000000000D1AE57  Unknown               Unknown  Unknown
vasp               0000000000CB5294  Unknown               Unknown  Unknown
vasp               0000000000CB50A6  Unknown               Unknown  Unknown
vasp               0000000000C57246  Unknown               Unknown  Unknown
vasp               0000000000C5CCF0  Unknown               Unknown  Unknown
libpthread.so.0    0000003B4CE0F7E0  Unknown               Unknown  Unknown
vasp               0000000000C33E70  Unknown               Unknown  Unknown
vasp               0000000000BA492F  Unknown               Unknown  Unknown
vasp               0000000000BC27B3  Unknown               Unknown  Unknown
vasp               000000000055B4FC  Unknown               Unknown  Unknown
vasp               0000000000422D26  Unknown               Unknown  Unknown
vasp               0000000000403BBE  Unknown               Unknown  Unknown
libc.so.6          0000003B4CA1ED1D  Unknown               Unknown  Unknown
vasp               0000000000403AC9  Unknown               Unknown  Unknown

with regards,
S.Rameshkumar
research scholar

Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr

Posted: Thu Dec 01, 2016 9:50 am
by admin
The "Unknowns" indicate that corresponding routines are missing.
That means your installation of vasp is not clean.

Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr

Posted: Thu Dec 21, 2017 9:56 am
by dj120516
Hello:
I faced this error before, and I found a solution, just type "ulimit -s unlimited" in your terminal. Actually, this is an error about stack size. I found this solution in this page:
https://software.intel.com/en-us/forums ... pic/268867

Hope it helpful!

Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr

Posted: Thu Mar 19, 2020 11:38 pm
by jianan_zhang
dj120516 wrote: Thu Dec 21, 2017 9:56 am Hello:
I faced this error before, and I found a solution, just type "ulimit -s unlimited" in your terminal. Actually, this is an error about stack size. I found this solution in this page:
https://software.intel.com/en-us/forums ... pic/268867

Hope it helpful!
I have the same problem and this really solves the problem! actually, you can add this line in ~/.bashrc so every time you have a new terminal this line will be run.