Are you running with ulimit -s unlimited? If not that looks like a out-of-stack crash, which VASP frequently causes.
If you are running with unlimited stack, I could perhaps run that input case on our VASP build. (Which have a bunch of fixes for bad stack usage among other things) On 07/11/2018 11:13 PM, Noam Bernstein wrote: >> On Jul 11, 2018, at 11:29 AM, Jeff Squyres (jsquyres) via users >> <users@lists.open-mpi.org <mailto:users@lists.open-mpi.org>> wrote: >> >> Ok, that would be great -- thanks. >> >> Recompiling Open MPI with --enable-debug will turn on several >> debugging/sanity checks inside Open MPI, and it will also enable >> debugging symbols. Hence, If you can get a failure when a debug Open >> MPI build, it might give you a core file that can be used to get a >> more detailed stack trace, poke around and see if there's a NULL >> pointer somewhere, …etc. > > I haven’t tried to get a core file yes, but it’s not producing any more > info from the runtime stack trace, despite configure with —enable-debug: > > Image PC Routine Line > Source > vasp.gamma_para.i 0000000002DCE8C1 Unknown Unknown > Unknown > vasp.gamma_para.i 0000000002DCC9FB Unknown Unknown > Unknown > vasp.gamma_para.i 0000000002D409E4 Unknown Unknown > Unknown > vasp.gamma_para.i 0000000002D407F6 Unknown Unknown > Unknown > vasp.gamma_para.i 0000000002CDCED9 Unknown Unknown > Unknown > vasp.gamma_para.i 0000000002CE3DB6 Unknown Unknown > Unknown > libpthread-2.12.s 0000003F8E60F7E0 Unknown Unknown > Unknown > mca_btl_vader.so 00002B1AFA5FAC30 Unknown Unknown > Unknown > mca_btl_vader.so 00002B1AFA5FD00D Unknown Unknown > Unknown > libopen-pal.so.40 00002B1AE884327C opal_progress Unknown > Unknown > mca_pml_ob1.so 00002B1AFB855DCE Unknown Unknown > Unknown > mca_pml_ob1.so 00002B1AFB858305 mca_pml_ob1_send Unknown > Unknown > libmpi.so.40.10.1 00002B1AE823A5DA ompi_coll_base_al Unknown > Unknown > mca_coll_tuned.so 00002B1AFC6F0842 ompi_coll_tuned_a Unknown > Unknown > libmpi.so.40.10.1 00002B1AE81B66F5 PMPI_Allreduce Unknown > Unknown > libmpi_mpifh.so.4 00002B1AE7F2259B mpi_allreduce_ Unknown > Unknown > vasp.gamma_para.i 000000000042D1ED m_sum_d_ 1300 > mpi.F > vasp.gamma_para.i 000000000089947D nonl_mp_vnlacc_.R 1754 > nonl.F > vasp.gamma_para.i 0000000000972C51 hamil_mp_hamiltmu 825 > hamil.F > vasp.gamma_para.i 0000000001BD2608 david_mp_eddav_.R 419 > davidson.F > vasp.gamma_para.i 0000000001D2179E elmin_.R 424 > electron.F > vasp.gamma_para.i 0000000002B92452 vamp_IP_electroni 4783 > main.F > vasp.gamma_para.i 0000000002B6E173 MAIN__ 2800 > main.F > vasp.gamma_para.i 000000000041325E Unknown Unknown > Unknown > libc-2.12.so 0000003F8E21ED1D __libc_start_main Unknown > Unknown > vasp.gamma_para.i 0000000000413169 Unknown Unknown > Unknown > > > This is the configure line that was supposedly used to create the library: > ./configure > --prefix=/usr/local/openmpi/3.1.1_debug/x86_64/ib/intel/11.1.080 > --with-tm=/usr/local/torque --enable-mpirun-prefix-by-default > --with-verbs=/usr --with-verbs-libdir=/usr/lib64 --enable-debug > > Is there any way I can confirm that the version of the openmpi library I > think I’m using really was compiled with debugging? > > 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://lists.open-mpi.org/mailman/listinfo/users > -- Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden Internet: a...@hpc2n.umu.se Phone: +46 90 7866134 Fax: +46 90-580 14 Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
