[mpich-discuss] Dual core problem

Fri Apr 9 14:19:55 CDT 2010

Hi,

cpi does not work (or 1/6 that it works)
"mpiexec -n 3 hello.exe" does not work (the same probability)
"mpiexec -n 1 hostname" works perfectly (it works without problems for
each n), it is the first one without problems

it seems that the higher number n, the lower probability of correct output

Ladislav

>  Please provide us more details. Can you run cpi ? Can you run "mpiexec -n
> 3 hello.exe" ? Can you run "mpiexec -n 1 hostname" ?
>
> -Jayesh
> ----- Original Message -----
> From: "Ladislav Huraj" <ladislav.huraj at ucm.sk>
> To: "Jayesh Krishna" <jayesh at mcs.anl.gov>
> Cc: mpich-discuss at mcs.anl.gov
> Sent: Friday, April 9, 2010 11:41:55 AM GMT -06:00 US/Canada Central
> Subject: Re: [mpich-discuss] Dual core problem
>
> Unfortunately it does not work
>
> BR,
> Ladislav
>
>
> Jayesh Krishna  wrote / napĂsal(a):
>> Hi,
>>  Can you cpi (c:\program files\mpich2\examples\cpi.exe) on your notebook
>> ?
>>  Does "mpiexec -n 3 hello.exe" work for you (mpiexec launches all procs
>> on the localhost by default)?
>>
>> Regards,
>> Jayesh
>> ----- Original Message -----
>> From: huraj at ucm.sk
>> To: mpich-discuss at mcs.anl.gov
>> Sent: Friday, April 9, 2010 6:24:05 AM GMT -06:00 US/Canada Central
>> Subject: Re: [mpich-discuss] Dual core problem
>>
>> My version is 1.2.1p1. I have already tried the older as well as newer
>> versions of mpich2 but without success.
>>
>> For job I use e.g.:
>> mpiexec &#8211;hosts 3 localhost localhost localhost hello.exe
>> this one works perfectly with the MPI code on my other PC.
>> I tried lots of others options which are correct (I always checked the
>> correctness on my other PC). From this I deducted that problem seems to
>> be
>> in notebook not in the code. Funny is that in one of 4 cases the outputs
>> are correct.
>>
>> My OS is 32bit WinXP Professional SP3, it is notebook HP Intel Core2 Duo
>> CP.
>>
>>
>>
>>> Hi,
>>>  Which version of MPICH2 are you using (If you are using an older
>>> version
>>> try the latest stable version and see if it helps -
>>> http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=downloads)?
>>>  How are you running your job (mpiexec options)?
>>>  Is your machine 32-bit or 64-bit ?
>>>
>>> Regards,
>>> Jayesh
>>> ----- Original Message -----
>>> From: huraj at ucm.sk
>>> To: mpich-discuss at mcs.anl.gov
>>> Sent: Friday, April 9, 2010 2:40:31 AM GMT -06:00 US/Canada Central
>>> Subject: [mpich-discuss] Dual core problem
>>>
>>> When I run the MPI program the outputs are different. Sometimes the
>>> output
>>> is correct, sometimes I obtain error message and sometimes job
>>> aborting.
>>> See the outputs:
>>>
>>> [01:4088]......ERROR:result command received but the wait_list is
>>> empty.
>>> [01:4088]....ERROR:unable to handle the command: "cmd=result src=1
>>> dest=1
>>> tag=5 cmd_tag=2 cmd_orig=dbput ctx_key=1 result=DBS_SUCCESS "
>>> [01:4088]...ERROR:sock_op_close returned while unknown context is in
>>> state: SMPD_IDLE
>>> [01:2392]......ERROR:result command received but the wait_list is
>>> empty.
>>> [01:2392]....ERROR:unable to handle the command: "cmd=result src=1
>>> dest=1
>>> tag=9 cmd_tag=2 cmd_orig=dbput ctx_key=2 result=DBS_SUCCESS "
>>> [01:2392]...ERROR:sock_op_close returned while unknown context is in
>>> state: SMPD_IDLE
>>>
>>> or
>>> [01:1452]......ERROR:result command received but the wait_list is
>>> empty.
>>> [01:1452]....ERROR:unable to handle the command: "cmd=result src=1
>>> dest=1
>>> tag=4 cmd_tag=1 cmd_orig=dbget ctx_key=0 result=DBS_FAIL "
>>>
>>> job aborted:
>>> rank: node: exit code[: error message]
>>> 0: localhost: 123
>>> 1: localhost: 123
>>> 2: localhost: -1073741819: process 2 exited without calling finalize
>>>
>>> or correctly
>>> Received: Hello, world from process 1!
>>> Received: Hello, world from process 2!
>>> MASTER: All Done!
>>>
>>> The program code is correct; it runs well on different PC.
>>>
>>> I am afraid the problem is in my notebook. The notebook is Intel Core2
>>> Duo
>>> CPU.
>>> I tried to change the setting &#8216;hosts&#8217; in wmpiconfig (to
>>> localhost:2) for dual core but nothing has changed.
>>> I need it only for local using.
>>>
>>> Thanks
>>>
>>> Ladislav
>>>
>>>
>>>
>>>
>>> __________ Information from ESET Mail Security, version of virus
>>> signature
>>> database 5012 (20100409) __________
>>>
>>> The message was checked by ESET Mail Security.
>>> http://www.eset.com
>>>
>>>
>>> _______________________________________________
>>> mpich-discuss mailing list
>>> mpich-discuss at mcs.anl.gov
>>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>> _______________________________________________
>>> mpich-discuss mailing list
>>> mpich-discuss at mcs.anl.gov
>>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>>
>>>
>>> __________ Information from ESET Mail Security, version of virus
>>> signature
>>> database 5012 (20100409) __________
>>>
>>> The message was checked by ESET Mail Security.
>>> http://www.eset.com
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>> __________ Information from ESET Mail Security, version of virus
>> signature database 5012 (20100409) __________
>>
>> The message was checked by ESET Mail Security.
>> http://www.eset.com
>>
>>
>> _______________________________________________
>> mpich-discuss mailing list
>> mpich-discuss at mcs.anl.gov
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>
>>
>> __________ Information from ESET Mail Security, version of virus
>> signature database 5013 (20100409) __________
>>
>> The message was checked by ESET Mail Security.
>> http://www.eset.com
>>
>>
>>
>>
>
>
>
> __________ Information from ESET Mail Security, version of virus signature
> database 5013 (20100409) __________
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>
>
>
>
> __________ Information from ESET Mail Security, version of virus signature
> database 5014 (20100409) __________
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>
>
>

__________ Information from ESET Mail Security, version of virus signature database 5014 (20100409) __________

The message was checked by ESET Mail Security.
http://www.eset.com