The ABINIT Users Mailing List ( CLOSED )

[Nico Mittenzwey <nico.mittenzwey@s2001.tu-chemnitz.de>]

rsaha@pas.rochester.edu schrieb:

Hi Rajdeep,

>   mpirun -np 2 abinip < tparal_3.files >& m.log 
> 
>  hangs with the following error
> 
> forrtl: severe (174): SIGSEGV, segmentation fault occurred
> Image              PC                Routine            Line        Source  
>            
> libc.so.6          0000002A95CE27E4  Unknown               Unknown  Unknown
> libc.so.6          0000002A95CE4019  Unknown               Unknown  Unknown
> abinip             0000000000E931D7  Unknown               Unknown  Unknown
> abinip             0000000000EA5C9F  Unknown               Unknown  Unknown
> abinip             0000000000EA5C43  Unknown               Unknown  Unknown
> abinip             0000000000C6E563  Unknown               Unknown  Unknown
> abinip             000000000094E8B0  Unknown               Unknown  Unknown
> abinip             0000000000915830  Unknown               Unknown  Unknown
> abinip             000000000040858C  Unknown               Unknown  Unknown
> abinip             0000000000405A3A  Unknown               Unknown  Unknown
> libc.so.6          0000002A95C95E5D  Unknown               Unknown  Unknown
> abinip             000000000040596A  Unknown               Unknown  Unknown
> 
> if wfoptflag 1 and nbdblock is 2 as needed for band parallelisation. 
> However, nbdblock 1 leads to a smooth execution. I am using a 24-node 
> cluster of  dual processor AMD opteron 246 machines running SUSE Linux. 
> Could somebody please look at my build.ac file, suggest where I am going 
> wrong ?


I had a similar error with wfoptflag and nbdblock using the pathscale
compiler, although using the intel fortran compiler solved that problem.
Where exactly did the segmentation fault appear in the log?

Nico