[mpich-discuss] There is any change between mpich1 and mpich2 which make this error?

Jim Dinan dinan at mcs.anl.gov
Fri Dec 14 10:18:04 CST 2012


Hi,

It looks like one of your processes seg. faulted and exited with SIGSEGV 
(signal 11).  You should be able to look at the core file or attach a 
debugger to get a backtrace and locate the origin of  the error. 
Without more information, it's hard to give much help.

MPICH2 1.4.1 is also a slightly older version, you could try upgrading 
to the latest version of MPICH and see if the seg fault goes away.

I don't know of any change from MPICH1 to MPICH2 that would have 
resulted in a correct MPI-1 program seg faulting.

  ~Jim.

On 12/14/12 6:51 AM, 유경완 wrote:
> Hi there
>
> I upgraded my server computer and I also upgraded mpich program from
> mpich1(1.2.7p1) to mpich2(1.4.1).
>
> And then there were some problems…
>
> The problem was
>
> There is no error when I run mpich2(mpiexec) with output file which
> compiled at mpich1.
>
> But there is an error when I run mpich2(mpiexec) with output file which
> compiled at mpich2 (there was no error when I compiled at mpich2).
>
> (All compiling which mentioned above use same code)
>
> The error message was
>
> =====================================================================================
>
> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
>
> =   EXIT CODE: 11
>
> =   CLEANING UP REMAINING PROCESSES
>
> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>
> =====================================================================================
>
> [proxy:0:1 at n002] HYD_pmcd_pmip_control_cmd_cb
> (/home/octofous2/libraries/mpich2-1.4.1p1/src/pm/hydra/pm/pmiserv/pmip_cb.c:928):
> assert (!closed) failed
>
> [proxy:0:1 at n002] HYDT_dmxu_poll_wait_for_event
> (/home/octofous2/libraries/mpich2-1.4.1p1/src/pm/hydra/tools/demux/demux_poll.c:77):
> callback returned error status
>
> [proxy:0:1 at n002] main
> (/home/octofous2/libraries/mpich2-1.4.1p1/src/pm/hydra/pm/pmiserv/pmip.c:276):
> demux engine error waiting for event
>
> [mpiexec at octofous2.psl] HYDT_bscu_wait_for_completion
> (/home/octofous2/libraries/mpich2-1.4.1p1/src/pm/hydra/tools/bootstrap/utils/bscu_wait.c:70):
> one of the processes terminated badly; aborting
>
> [mpiexec at octofous2.psl] HYDT_bsci_wait_for_completion
> (/home/octofous2/libraries/mpich2-1.4.1p1/src/pm/hydra/tools/bootstrap/src/bsci_wait.c:23):
> launcher returned error waiting for completion
>
> [mpiexec at octofous2.psl] HYD_pmci_wait_for_completion
> (/home/octofous2/libraries/mpich2-1.4.1p1/src/pm/hydra/pm/pmiserv/pmiserv_pmci.c:191):
> launcher returned error waiting for completion
>
> [mpiexec at octofous2.psl] main
> (/home/octofous2/libraries/mpich2-1.4.1p1/src/pm/hydra/ui/mpich/mpiexec.c:405):
> process manager error waiting for completion
>
> 8 cpus
>
> So.. my quastion was that is there any language change between
> mpich1(1.2.7p1) and mpich2(1.4.1) which makes problem like this?
>
> Or there is any clue to make this problem..?
>
> Thanks for read
>
> Best regards
>
>
>
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
>



More information about the discuss mailing list