Dear Qianlin,<br><br>Signal 9, which seems to be causing the crash, usually indicates a segmentation fault in the code bing run by mpiexec. I had something similar happen to me recently under c++ and mpich. Turned out I was trying to delete the contents of a pointer twice.<br>
<br>In my case Linux did a core dump, which I could trace with gdb and determine approximately where the segmentation fault occurred. So if you can find a core dump in your program's working directory, the problem is probably in the VASP code, not in mpich2.<br>
<br>Keep in mind that I'm just a user of mpich2 and very well could be wrong.<br><br>Regards,<br> Yuriy<br><br>> Dear mpich2-support,<br>
><br>
> Based on mpif90, I have installed the parallel version of a
commercilal code VASP . Sometimes mpich2 can work well with vasp, but it
also failed for some VASP-treated jobs with the following error
messages:<br>
> ------------------------------<div id=":9m" class="ii gt">-----<br>
> running on 8 nodes<br>
> distr: one band on 1 nodes, 8 groups<br>
> vasp.4.6.21 23Feb03 complex<br>
> POSCAR found : 3 types and 30 ions<br>
> LDA part: xc-table for Ceperly-Alder, Vosko type interpolation
para-ferro<br>
> POSCAR, INCAR and KPOINTS ok, starting setup<br>
> WARNING: wrap around errors must be expected<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> FFT: planning ... 2<br>
> reading WAVECAR<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is
run in background, redirect from /dev/null<br>
> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4
a.out < /dev/null &<br>
> WARNING: random wavefunctions but no delay for mixing, default for
NELMDL<br>
> entering main loop<br>
> N E dE d eps ncg
rms rms(c)<br>
> rank 6 in job 36 qltang1_54199 caused collective abort of all
ranks<br>
> exit status of rank 6: killed by signal 9<br>
> rank 3 in job 36 qltang1_54199 caused collective abort of all
ranks<br>
> exit status of rank 3: killed by signal 9<br>
> -----------------------------<br>
> I want to know how to solve the above question. Thank you alot.<br>
><br>
> Best regards,<br>
> Qianlin</div>