> On Dec 7, 2016, at 12:37 PM, Christof Koehler
> <christof.koeh...@bccms.uni-bremen.de> wrote:
>
>
>> Presumably someone here can comment on what the standard says about the
>> validity of terminating without mpi_abort.
>
> Well, probably stop is not a good way to terminate then.
>
> My main point was the change relative to 1.10 anyway :-)
It’s definitely not the clean way to terminate, but I think everyone agrees
that it shouldn’t hang if it can be avoided.
>
>
>>
>> Actually, if you’re willing to share enough input files to reproduce, I
>> could take a look. I just recompiled our VASP with openmpi 2.0.1 to fix a
>> crash that was apparently addressed by some change in the memory allocator
>> in a recent version of openmpi. Just e-mail me if that’s the case.
>
> I think that is no longer necessary ? In principle it is no problem but
> it at the end of a (small) GW calculation, the Si tutorial example.
> So the mail would be abit larger due to the WAVECAR.
I agree. It sounds like it’s clearly a failure to exit from a collective
communication when a process dies (from the point of view of mpi, since
mpi_abort is not being called, it’s just a process dying). Maybe the patch in
Ralph’s e-mail fixes it.
Noam
____________
||
|U.S. NAVAL|
|_RESEARCH_|
LABORATORY
Noam Bernstein, Ph.D.
Center for Materials Physics and Technology
U.S. Naval Research Laboratory
T +1 202 404 8628 F +1 202 404 7546
https://www.nrl.navy.mil <https://www.nrl.navy.mil/>
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
