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

[nek5000-users at lists.mcs.anl.gov]

Jan,

Memory layout on different architectures is different...

There is some sort of memory issue in the restart process under the scenario
you described --- it is entirely my fault --- but I've not been able to readily track it down.
Given that this situation does not often arise and that we have a standard fix, I've
focused on other issues, but I apologize for causing you to lose time on this.

Paul

________________________________________
From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov]
Sent: Friday, March 10, 2017 8:39 AM
To: nek5000-users at lists.mcs.anl.gov
Subject: Re: [Nek5000-users] Nek: abnormal termination by signal 11

Hi Stefan and Paul,
I just made a short test and it seems Pauls advice actually helped. I increased lelt so that the total memory available  stayed the same and the run started fine.
This was with a single restart file with MPIIO on the IBM big endian system, but I think  I also had some restart files created on Intel.
I will look into the memory footprint and the new master next week.
Any idea why this only happens on IBM?
Many thanks for the advice,
Jan
>

_______________________________________________
Nek5000-users mailing list
Nek5000-users at lists.mcs.anl.gov
https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users