[Nek5000-users] Nek: abnormal termination by signal 11

Fri Feb 17 10:55:10 CST 2017

- What version of Nek5000 do you use?
- Is the problem reproduceable? 
- Can you provide a stack trace showing where the SEG FAULT (signal 11) happens


-----Original message-----
> From:nek5000-users at lists.mcs.anl.gov <nek5000-users at lists.mcs.anl.gov>
> Sent: Friday 17th February 2017 17:50
> To: nek5000-users at lists.mcs.anl.gov
> Subject: [Nek5000-users] Nek: abnormal termination by signal 11
> 
> Hi all,
> I have recently encountered the following error during the first time step when running on an IBM/BlueGene Cluster:
> ...	  
> 1  Hmholtz VELZ       5   6.4574E-08   1.0000E-04   1.0000E-08   1.0000E+03   F
>           1  Hmholtz VELZ       6   2.6260E-09   1.0000E-04   1.0000E-08   1.0000E+03   F
>           1  Hmholtz VELZ       5   2.6260E-09   1.9523E-01   1.0000E-08
> 2017-02-10 13:50:24.545 (WARN ) [0x400011c9030] :3236143:ibm.runjob.client.Job: terminated by signal 11
> 2017-02-10 13:50:24.545 (WARN ) [0x400011c9030] :3236143:ibm.runjob.client.Job: abnormal termination by signal 11 from rank 0
> This has happened for different user files, different parameters and resolutions, so I am not sure where to start looking. Has anyone else seen this problem? Is this likely a Nek or an IBM related problem?
> Best wishes,
> Jan
> 
> _______________________________________________
> Nek5000-users mailing list
> Nek5000-users at lists.mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
>