July 2016 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Error while using MPI_Send
by Kenneth Raffenetti 25 Jul '16

25 Jul '16

Hi, Normally this type of error would be the result of a firewall blocking communication, but your run is on a single node so that shouldn't be the case. I wonder, since it did work at one point, if there is some bad state on your system that might be cleared with a reboot? It also looks like you are running on a Android system, which we do not have much experience with, and no good way to test ourselves so our ways to help may be limited. Ken On 07/24/2016 11:50 AM, Doha Ehab wrote: > Hello > I am using a cross compiled version of MPICH3, I was trying simple > containing MPI_Send and MPI_Recv, it was working but suddenly I keep > receiving this error messsage: can anyone point out what is wrong and > how to fix it. > > $ mpiexec -v -n 4 /data/parallelCode > host: tab > > ================================================================================================== > mpiexec options: > ---------------- > Base path: /system/xbin/ > Launcher: (null) > Debug level: 1 > Enable X: -1 > > Global environment: > ------------------- > _=/system/xbin/mpiexec > PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin > LOOP_MOUNTPOINT=/mnt/obb > ANDROID_ROOT=/system > SHELL=/system/bin/sh > ANDROID_DATA=/data > ANDROID_ASSETS=/system/app > TERM=vt100 > ANDROID_PROPERTY_WORKSPACE=8,0 > ANDROID_BOOTLOGO=1 > HOSTNAME=hwt1701 > LD_LIBRARY_PATH=/vendor/lib:/system/lib > > BOOTCLASSPATH=/system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/hwframework.jar:/system/framework/hwcustframework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/hwEmui.jar:/system/framework/hwServices.jar:/system/framework/hwAndroid.policy.jar:/system/framework/hwTelephony-common.jar:/system/framework/hwpadext.jar > EMULATED_STORAGE_SOURCE=/mnt/shell/emulated > ANDROID_SOCKET_adbd=10 > EMULATED_STORAGE_TARGET=/storage/emulated > ANDROID_STORAGE=/storage > MKSH=/system/bin/sh > EXTERNAL_STORAGE=/storage/emulated/legacy > USBHOST_STORAGE=/storage/usbdisk > RANDOM=11338 > ASEC_MOUNTPOINT=/mnt/asec > SECONDARY_STORAGE=/storage/sdcard1 > USER=shell > LEGACY_STORAGE=/storage/emulated/legacy > HOME=/data > > Hydra internal environment: > --------------------------- > GFORTRAN_UNBUFFERED_PRECONNECTED=y > > > Proxy information: > ********************* > [1] proxy: tab (1 cores) > Exec list: /data/mmp100 (4 processes); > > > ================================================================================================== > > [mpiexec@tab] Timeout set to -1 (-1 means infinite) > [mpiexec@tab] Got a control port string of tab:48661 > > Proxy launch args: /system/xbin/hydra_pmi_proxy --control-port tab:48661 > --debug --rmk user --launcher ssh --demux poll --pgid 0 --retries 10 > --usize -2 --proxy-id > > Arguments being passed to proxy 0: > --version 3.2 --iface-ip-env-name MPIR_CVAR_CH3_INTERFACE_HOSTNAME > --hostname tab --global-core-map 0,1,1 --pmi-id-map 0,0 > --global-process-count 4 --auto-cleanup 1 --pmi-kvsname kvs_10003_0 > --pmi-process-mapping (vector,(0,1,1)) --ckpoint-num -1 > --global-inherited-env 26 '_=/system/xbin/mpiexec' > 'PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin' > 'LOOP_MOUNTPOINT=/mnt/obb' 'ANDROID_ROOT=/system' 'SHELL=/system/bin/sh' > 'ANDROID_DATA=/data' 'ANDROID_ASSETS=/system/app' 'TERM=vt100' > 'ANDROID_PROPERTY_WORKSPACE=8,0' 'ANDROID_BOOTLOGO=1' 'HOSTNAME=hwt1701' > 'LD_LIBRARY_PATH=/vendor/lib:/system/lib' > 'BOOTCLASSPATH=/system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/hwframework.jar:/system/framework/hwcustframework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/hwEmui.jar:/system/framework/hwServices.jar:/system/framework/hwAndroid.policy.jar:/system/framework/hwTelephony-common.jar:/system/framework/hwpadext.jar' > 'EMULATED_STORAGE_SOURCE=/mnt/shell/emulated' 'ANDROID_SOCKET_adbd=10' > 'EMULATED_STORAGE_TARGET=/storage/emulated' 'ANDROID_STORAGE=/storage' > 'MKSH=/system/bin/sh' 'EXTERNAL_STORAGE=/storage/emulated/legacy' > 'USBHOST_STORAGE=/storage/usbdisk' 'RANDOM=11338' > 'ASEC_MOUNTPOINT=/mnt/asec' 'SECONDARY_STORAGE=/storage/sdcard1' > 'USER=shell' 'LEGACY_STORAGE=/storage/emulated/legacy' 'HOME=/data' > --global-user-env 0 --global-system-env 1 > 'GFORTRAN_UNBUFFERED_PRECONNECTED=y' --proxy-core-count 1 --exec > --exec-appnum 0 --exec-proc-count 4 --exec-local-env 0 --exec-wdir / > --exec-args 1 /data/mmp100 > > [mpiexec@tab] Launch arguments: /system/xbin/hydra_pmi_proxy > --control-port tab:48661 --debug --rmk user --launcher ssh --demux poll > --pgid 0 --retries 10 --usize -2 --proxy-id 0 > [proxy:0:0@tab] got pmi command (from 0): init > pmi_version=1 pmi_subversion=1 > [proxy:0:0@tab] PMI response: cmd=response_to_init pmi_version=1 > pmi_subversion=1 rc=0 > [proxy:0:0@tab] got pmi command (from 0): get_maxes > > [proxy:0:0@tab] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 > vallen_max=1024 > [proxy:0:0@tab] got pmi command (from 6): init > pmi_version=1 pmi_subversion=1 > [proxy:0:0@tab] PMI response: cmd=response_to_init pmi_version=1 > pmi_subversion=1 rc=0 > [proxy:0:0@tab] got pmi command (from 6): get_maxes > > [proxy:0:0@tab] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 > vallen_max=1024 > [proxy:0:0@tab] got pmi command (from 9): init > pmi_version=1 pmi_subversion=1 > [proxy:0:0@tab] PMI response: cmd=response_to_init pmi_version=1 > pmi_subversion=1 rc=0 > [proxy:0:0@tab] got pmi command (from 15): init > pmi_version=1 pmi_subversion=1 > [proxy:0:0@tab] PMI response: cmd=response_to_init pmi_version=1 > pmi_subversion=1 rc=0 > [proxy:0:0@tab] got pmi command (from 0): get_appnum > > [proxy:0:0@tab] PMI response: cmd=appnum appnum=0 > [proxy:0:0@tab] got pmi command (from 9): get_maxes > > [proxy:0:0@tab] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 > vallen_max=1024 > [proxy:0:0@tab] got pmi command (from 0): get_my_kvsname > > [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 > [proxy:0:0@tab] got pmi command (from 15): get_maxes > > [proxy:0:0@tab] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 > vallen_max=1024 > [proxy:0:0@tab] got pmi command (from 0): get_my_kvsname > > [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 > [proxy:0:0@tab] got pmi command (from 9): get_appnum > > [proxy:0:0@tab] PMI response: cmd=appnum appnum=0 > [proxy:0:0@tab] got pmi command (from 0): get > kvsname=kvs_10003_0 key=PMI_process_mapping > [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success > value=(vector,(0,1,1)) > [proxy:0:0@tab] got pmi command (from 15): get_appnum > > [proxy:0:0@tab] PMI response: cmd=appnum appnum=0 > [proxy:0:0@tab] got pmi command (from 6): get_appnum > > [proxy:0:0@tab] PMI response: cmd=appnum appnum=0 > [proxy:0:0@tab] got pmi command (from 9): get_my_kvsname > > [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 > [proxy:0:0@tab] got pmi command (from 15): get_my_kvsname > > [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 > [proxy:0:0@tab] got pmi command (from 6): get_my_kvsname > > [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 > [proxy:0:0@tab] got pmi command (from 6): get_my_kvsname > > [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 > [proxy:0:0@tab] got pmi command (from 9): get_my_kvsname > > [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 > [proxy:0:0@tab] got pmi command (from 0): put > kvsname=kvs_10003_0 key=P0-businesscard > value=port#49751$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] cached command: > P0-businesscard=port#49751$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] PMI response: cmd=put_result rc=0 msg=success > [proxy:0:0@tab] got pmi command (from 9): get > kvsname=kvs_10003_0 key=PMI_process_mapping > [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success > value=(vector,(0,1,1)) > [proxy:0:0@tab] got pmi command (from 0): barrier_in > > [proxy:0:0@tab] got pmi command (from 6): get > kvsname=kvs_10003_0 key=PMI_process_mapping > [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success > value=(vector,(0,1,1)) > [proxy:0:0@tab] got pmi command (from 15): get_my_kvsname > > [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 > [proxy:0:0@tab] got pmi command (from 9): put > kvsname=kvs_10003_0 key=P2-businesscard > value=port#60729$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] cached command: > P2-businesscard=port#60729$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] PMI response: cmd=put_result rc=0 msg=success > [proxy:0:0@tab] got pmi command (from 15): get > kvsname=kvs_10003_0 key=PMI_process_mapping > [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success > value=(vector,(0,1,1)) > [proxy:0:0@tab] got pmi command (from 9): barrier_in > > [proxy:0:0@tab] got pmi command (from 6): put > kvsname=kvs_10003_0 key=P1-businesscard > value=port#44344$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] cached command: > P1-businesscard=port#44344$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] PMI response: cmd=put_result rc=0 msg=success > [proxy:0:0@tab] got pmi command (from 15): put > kvsname=kvs_10003_0 key=P3-businesscard > value=port#51326$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] cached command: > P3-businesscard=port#51326$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] PMI response: cmd=put_result rc=0 msg=success > [proxy:0:0@tab] got pmi command (from 6): barrier_in > > [proxy:0:0@tab] got pmi command (from 15): barrier_in > > [proxy:0:0@tab] flushing 4 put command(s) out > [mpiexec@tab] [pgid: 0] got PMI command: cmd=put > P0-businesscard=port#49751$description#tab$ifname#192.168.1.4$ > P2-businesscard=port#60729$description#tab$ifname#192.168.1.4$ > P1-businesscard=port#44344$description#tab$ifname#192.168.1.4$ > P3-businesscard=port#51326$description#tab$ifname#192.168.1.4$ > [proxy:0:0@tab] forwarding command (cmd=put > P0-businesscard=port#49751$description#tab$ifname#192.168.1.4$ > P2-businesscard=port#60729$description#tab$ifname#192.168.1.4$ > P1-businesscard=port#44344$description#tab$ifname#192.168.1.4$ > P3-businesscard=port#51326$description#tab$ifname#192.168.1.4$) upstream > [proxy:0:0@tab] forwarding command (cmd=barrier_in) upstream > [mpiexec@tab] [pgid: 0] got PMI command: cmd=barrier_in > [mpiexec@tab] PMI response to fd 6 pid 15: cmd=keyval_cache > P0-businesscard=port#49751$description#tab$ifname#192.168.1.4$ > P2-businesscard=port#60729$description#tab$ifname#192.168.1.4$ > P1-businesscard=port#44344$description#tab$ifname#192.168.1.4$ > P3-businesscard=port#51326$description#tab$ifname#192.168.1.4$ > [mpiexec@tab] PMI response to fd 6 pid 15: cmd=barrier_out > [proxy:0:0@tab] PMI response: cmd=barrier_out > [proxy:0:0@tab] PMI response: cmd=barrier_out > [proxy:0:0@tab] PMI response: cmd=barrier_out > [proxy:0:0@tab] PMI response: cmd=barrier_out > [proxy:0:0@tab] got pmi command (from 0): get > kvsname=kvs_10003_0 key=P1-businesscard > [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success > value=port#44344$description#tab$ifname#192.168.1.4$ > Fatal error in MPI_Send: Unknown error class, error stack: > MPI_Send(174)...............................: MPI_Send(buf=0x15c56c, > count=1, MPI_INT, dest=1, tag=1, MPI_COMM_WORLD) failed > MPIDI_CH3i_Progress_wait(242)...............: an error occurred while > handling an event returned by MPIDU_Sock_Wait() > MPIDI_CH3I_Progress_handle_sock_event(697)..: > MPIDI_CH3_Sockconn_handle_connect_event(597): [ch3:sock] failed to > connnect to remote process > MPIDU_Socki_handle_connect(808).............: connection failure > (set=0,sock=1,errno=113:No route to host) > [proxy:0:0@tab] got pmi command (from 0): abort > exitcode=69331543 > [proxy:0:0@tab] we don't understand this command abort; forwarding upstream > [mpiexec@tab] [pgid: 0] got PMI command: cmd=abort exitcode=69331543 > > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Error creating 272 processes on a multicore, single CPU
by Kenneth Raffenetti 25 Jul '16

25 Jul '16

Also the configure line you used to build MPICH would be helpful. On 07/25/2016 09:25 AM, Halim Amer wrote: > I am suspecting you are running into some io limits on your system, such > as the limits of pipe on Linux and Mac, not a process creation problem. > > Could you remove all writes to stdout and try again? > > --Halim > > www.mcs.anl.gov/~aamer > > On 7/22/16 11:19 PM, Gajbe, Manisha wrote: >> Hi, >> >> >> >> I have installed mpich-3.2 on a multicore platform. When I spawn 272 >> processes , I get the error message mentioned below. I am able to create >> upto 271 processes successfully. >> >> >> >> /usr/local/my-mpich-3.2/64bit/bin/mpirun -n 272 ./hello_c >> >> >> >> [cli_0]: write_line: message string doesn't end in newline: :cmd=put >> kvsname=kvs_8846_0 key=r2h1 >> value=r0#0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271$ : >> >> >> >> >> >> >> >> >> *Manisha Gajbe* >> >> *MVE PQV Content* >> >> SCE – System Content Engineering >> >> >> >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Error creating 272 processes on a multicore, single CPU
by Halim Amer 25 Jul '16

25 Jul '16

I am suspecting you are running into some io limits on your system, such as the limits of pipe on Linux and Mac, not a process creation problem. Could you remove all writes to stdout and try again? --Halim www.mcs.anl.gov/~aamer On 7/22/16 11:19 PM, Gajbe, Manisha wrote: > Hi, > > > > I have installed mpich-3.2 on a multicore platform. When I spawn 272 > processes , I get the error message mentioned below. I am able to create > upto 271 processes successfully. > > > > /usr/local/my-mpich-3.2/64bit/bin/mpirun -n 272 ./hello_c > > > > [cli_0]: write_line: message string doesn't end in newline: :cmd=put > kvsname=kvs_8846_0 key=r2h1 > value=r0#0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271$: > > > > > > > > *Manisha Gajbe* > > *MVE PQV Content* > > SCE – System Content Engineering > > > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Error while using MPI_Send
by Doha Ehab 24 Jul '16

24 Jul '16

Hello I am using a cross compiled version of MPICH3, I was trying simple containing MPI_Send and MPI_Recv, it was working but suddenly I keep receiving this error messsage: can anyone point out what is wrong and how to fix it. $ mpiexec -v -n 4 /data/parallelCode host: tab ================================================================================================== mpiexec options: ---------------- Base path: /system/xbin/ Launcher: (null) Debug level: 1 Enable X: -1 Global environment: ------------------- _=/system/xbin/mpiexec PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin LOOP_MOUNTPOINT=/mnt/obb ANDROID_ROOT=/system SHELL=/system/bin/sh ANDROID_DATA=/data ANDROID_ASSETS=/system/app TERM=vt100 ANDROID_PROPERTY_WORKSPACE=8,0 ANDROID_BOOTLOGO=1 HOSTNAME=hwt1701 LD_LIBRARY_PATH=/vendor/lib:/system/lib BOOTCLASSPATH=/system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/hwframework.jar:/system/framework/hwcustframework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/hwEmui.jar:/system/framework/hwServices.jar:/system/framework/hwAndroid.policy.jar:/system/framework/hwTelephony-common.jar:/system/framework/hwpadext.jar EMULATED_STORAGE_SOURCE=/mnt/shell/emulated ANDROID_SOCKET_adbd=10 EMULATED_STORAGE_TARGET=/storage/emulated ANDROID_STORAGE=/storage MKSH=/system/bin/sh EXTERNAL_STORAGE=/storage/emulated/legacy USBHOST_STORAGE=/storage/usbdisk RANDOM=11338 ASEC_MOUNTPOINT=/mnt/asec SECONDARY_STORAGE=/storage/sdcard1 USER=shell LEGACY_STORAGE=/storage/emulated/legacy HOME=/data Hydra internal environment: --------------------------- GFORTRAN_UNBUFFERED_PRECONNECTED=y Proxy information: ********************* [1] proxy: tab (1 cores) Exec list: /data/mmp100 (4 processes); ================================================================================================== [mpiexec@tab] Timeout set to -1 (-1 means infinite) [mpiexec@tab] Got a control port string of tab:48661 Proxy launch args: /system/xbin/hydra_pmi_proxy --control-port tab:48661 --debug --rmk user --launcher ssh --demux poll --pgid 0 --retries 10 --usize -2 --proxy-id Arguments being passed to proxy 0: --version 3.2 --iface-ip-env-name MPIR_CVAR_CH3_INTERFACE_HOSTNAME --hostname tab --global-core-map 0,1,1 --pmi-id-map 0,0 --global-process-count 4 --auto-cleanup 1 --pmi-kvsname kvs_10003_0 --pmi-process-mapping (vector,(0,1,1)) --ckpoint-num -1 --global-inherited-env 26 '_=/system/xbin/mpiexec' 'PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin' 'LOOP_MOUNTPOINT=/mnt/obb' 'ANDROID_ROOT=/system' 'SHELL=/system/bin/sh' 'ANDROID_DATA=/data' 'ANDROID_ASSETS=/system/app' 'TERM=vt100' 'ANDROID_PROPERTY_WORKSPACE=8,0' 'ANDROID_BOOTLOGO=1' 'HOSTNAME=hwt1701' 'LD_LIBRARY_PATH=/vendor/lib:/system/lib' 'BOOTCLASSPATH=/system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/hwframework.jar:/system/framework/hwcustframework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/hwEmui.jar:/system/framework/hwServices.jar:/system/framework/hwAndroid.policy.jar:/system/framework/hwTelephony-common.jar:/system/framework/hwpadext.jar' 'EMULATED_STORAGE_SOURCE=/mnt/shell/emulated' 'ANDROID_SOCKET_adbd=10' 'EMULATED_STORAGE_TARGET=/storage/emulated' 'ANDROID_STORAGE=/storage' 'MKSH=/system/bin/sh' 'EXTERNAL_STORAGE=/storage/emulated/legacy' 'USBHOST_STORAGE=/storage/usbdisk' 'RANDOM=11338' 'ASEC_MOUNTPOINT=/mnt/asec' 'SECONDARY_STORAGE=/storage/sdcard1' 'USER=shell' 'LEGACY_STORAGE=/storage/emulated/legacy' 'HOME=/data' --global-user-env 0 --global-system-env 1 'GFORTRAN_UNBUFFERED_PRECONNECTED=y' --proxy-core-count 1 --exec --exec-appnum 0 --exec-proc-count 4 --exec-local-env 0 --exec-wdir / --exec-args 1 /data/mmp100 [mpiexec@tab] Launch arguments: /system/xbin/hydra_pmi_proxy --control-port tab:48661 --debug --rmk user --launcher ssh --demux poll --pgid 0 --retries 10 --usize -2 --proxy-id 0 [proxy:0:0@tab] got pmi command (from 0): init pmi_version=1 pmi_subversion=1 [proxy:0:0@tab] PMI response: cmd=response_to_init pmi_version=1 pmi_subversion=1 rc=0 [proxy:0:0@tab] got pmi command (from 0): get_maxes [proxy:0:0@tab] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 vallen_max=1024 [proxy:0:0@tab] got pmi command (from 6): init pmi_version=1 pmi_subversion=1 [proxy:0:0@tab] PMI response: cmd=response_to_init pmi_version=1 pmi_subversion=1 rc=0 [proxy:0:0@tab] got pmi command (from 6): get_maxes [proxy:0:0@tab] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 vallen_max=1024 [proxy:0:0@tab] got pmi command (from 9): init pmi_version=1 pmi_subversion=1 [proxy:0:0@tab] PMI response: cmd=response_to_init pmi_version=1 pmi_subversion=1 rc=0 [proxy:0:0@tab] got pmi command (from 15): init pmi_version=1 pmi_subversion=1 [proxy:0:0@tab] PMI response: cmd=response_to_init pmi_version=1 pmi_subversion=1 rc=0 [proxy:0:0@tab] got pmi command (from 0): get_appnum [proxy:0:0@tab] PMI response: cmd=appnum appnum=0 [proxy:0:0@tab] got pmi command (from 9): get_maxes [proxy:0:0@tab] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 vallen_max=1024 [proxy:0:0@tab] got pmi command (from 0): get_my_kvsname [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 [proxy:0:0@tab] got pmi command (from 15): get_maxes [proxy:0:0@tab] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 vallen_max=1024 [proxy:0:0@tab] got pmi command (from 0): get_my_kvsname [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 [proxy:0:0@tab] got pmi command (from 9): get_appnum [proxy:0:0@tab] PMI response: cmd=appnum appnum=0 [proxy:0:0@tab] got pmi command (from 0): get kvsname=kvs_10003_0 key=PMI_process_mapping [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success value=(vector,(0,1,1)) [proxy:0:0@tab] got pmi command (from 15): get_appnum [proxy:0:0@tab] PMI response: cmd=appnum appnum=0 [proxy:0:0@tab] got pmi command (from 6): get_appnum [proxy:0:0@tab] PMI response: cmd=appnum appnum=0 [proxy:0:0@tab] got pmi command (from 9): get_my_kvsname [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 [proxy:0:0@tab] got pmi command (from 15): get_my_kvsname [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 [proxy:0:0@tab] got pmi command (from 6): get_my_kvsname [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 [proxy:0:0@tab] got pmi command (from 6): get_my_kvsname [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 [proxy:0:0@tab] got pmi command (from 9): get_my_kvsname [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 [proxy:0:0@tab] got pmi command (from 0): put kvsname=kvs_10003_0 key=P0-businesscard value=port#49751$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] cached command: P0-businesscard=port#49751$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] PMI response: cmd=put_result rc=0 msg=success [proxy:0:0@tab] got pmi command (from 9): get kvsname=kvs_10003_0 key=PMI_process_mapping [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success value=(vector,(0,1,1)) [proxy:0:0@tab] got pmi command (from 0): barrier_in [proxy:0:0@tab] got pmi command (from 6): get kvsname=kvs_10003_0 key=PMI_process_mapping [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success value=(vector,(0,1,1)) [proxy:0:0@tab] got pmi command (from 15): get_my_kvsname [proxy:0:0@tab] PMI response: cmd=my_kvsname kvsname=kvs_10003_0 [proxy:0:0@tab] got pmi command (from 9): put kvsname=kvs_10003_0 key=P2-businesscard value=port#60729$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] cached command: P2-businesscard=port#60729$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] PMI response: cmd=put_result rc=0 msg=success [proxy:0:0@tab] got pmi command (from 15): get kvsname=kvs_10003_0 key=PMI_process_mapping [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success value=(vector,(0,1,1)) [proxy:0:0@tab] got pmi command (from 9): barrier_in [proxy:0:0@tab] got pmi command (from 6): put kvsname=kvs_10003_0 key=P1-businesscard value=port#44344$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] cached command: P1-businesscard=port#44344$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] PMI response: cmd=put_result rc=0 msg=success [proxy:0:0@tab] got pmi command (from 15): put kvsname=kvs_10003_0 key=P3-businesscard value=port#51326$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] cached command: P3-businesscard=port#51326$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] PMI response: cmd=put_result rc=0 msg=success [proxy:0:0@tab] got pmi command (from 6): barrier_in [proxy:0:0@tab] got pmi command (from 15): barrier_in [proxy:0:0@tab] flushing 4 put command(s) out [mpiexec@tab] [pgid: 0] got PMI command: cmd=put P0-businesscard=port#49751$description#tab$ifname#192.168.1.4$ P2-businesscard=port#60729$description#tab$ifname#192.168.1.4$ P1-businesscard=port#44344$description#tab$ifname#192.168.1.4$ P3-businesscard=port#51326$description#tab$ifname#192.168.1.4$ [proxy:0:0@tab] forwarding command (cmd=put P0-businesscard=port#49751$description#tab$ifname#192.168.1.4$ P2-businesscard=port#60729$description#tab$ifname#192.168.1.4$ P1-businesscard=port#44344$description#tab$ifname#192.168.1.4$ P3-businesscard=port#51326$description#tab$ifname#192.168.1.4$) upstream [proxy:0:0@tab] forwarding command (cmd=barrier_in) upstream [mpiexec@tab] [pgid: 0] got PMI command: cmd=barrier_in [mpiexec@tab] PMI response to fd 6 pid 15: cmd=keyval_cache P0-businesscard=port#49751$description#tab$ifname#192.168.1.4$ P2-businesscard=port#60729$description#tab$ifname#192.168.1.4$ P1-businesscard=port#44344$description#tab$ifname#192.168.1.4$ P3-businesscard=port#51326$description#tab$ifname#192.168.1.4$ [mpiexec@tab] PMI response to fd 6 pid 15: cmd=barrier_out [proxy:0:0@tab] PMI response: cmd=barrier_out [proxy:0:0@tab] PMI response: cmd=barrier_out [proxy:0:0@tab] PMI response: cmd=barrier_out [proxy:0:0@tab] PMI response: cmd=barrier_out [proxy:0:0@tab] got pmi command (from 0): get kvsname=kvs_10003_0 key=P1-businesscard [proxy:0:0@tab] PMI response: cmd=get_result rc=0 msg=success value=port#44344$description#tab$ifname#192.168.1.4$ Fatal error in MPI_Send: Unknown error class, error stack: MPI_Send(174)...............................: MPI_Send(buf=0x15c56c, count=1, MPI_INT, dest=1, tag=1, MPI_COMM_WORLD) failed MPIDI_CH3i_Progress_wait(242)...............: an error occurred while handling an event returned by MPIDU_Sock_Wait() MPIDI_CH3I_Progress_handle_sock_event(697)..: MPIDI_CH3_Sockconn_handle_connect_event(597): [ch3:sock] failed to connnect to remote process MPIDU_Socki_handle_connect(808).............: connection failure (set=0,sock=1,errno=113:No route to host) [proxy:0:0@tab] got pmi command (from 0): abort exitcode=69331543 [proxy:0:0@tab] we don't understand this command abort; forwarding upstream [mpiexec@tab] [pgid: 0] got PMI command: cmd=abort exitcode=69331543 _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Error creating 272 processes on a multicore, single CPU
by Gajbe, Manisha 22 Jul '16

22 Jul '16

Hi, I have installed mpich-3.2 on a multicore platform. When I spawn 272 processes , I get the error message mentioned below. I am able to create upto 271 processes successfully. /usr/local/my-mpich-3.2/64bit/bin/mpirun -n 272 ./hello_c [cli_0]: write_line: message string doesn't end in newline: :cmd=put kvsname=kvs_8846_0 key=r2h1 value=r0#0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271$: Manisha Gajbe MVE PQV Content SCE - System Content Engineering _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] --enable-strictmpi not respected
by Kenneth Raffenetti 21 Jul '16

21 Jul '16

Hi Levi, Yes, this looks like a bug with how we include directories in the Automake SUBDIRS variable. I've created a ticket to track the issue and investigate other occurrences. https://trac.mpich.org/projects/mpich/ticket/2345 Ken On 07/20/2016 04:18 PM, Dettwyler, Levi E wrote: > Hi there, > > I think I've discovered an issue with the mpich-3.2 MPI tests not respecting the --enable-strictmpi flag passed in to the configure script. I'm building the mpich tests against OpenMPI. > > The full configure line I'm using is given below: > > export MPI_PREFIX=/home/build/OMPI > ./configure --enable-strictmpi --disable-cxx --disable-fortran --prefix=$MPI_PREFIX CC=$MPI_PREFIX/bin/mpicc CFLAGS="-I$MPI_PREFIX/include" LDFLAGS="-L$MPI_PREFIX/lib64" > > When running "make" in the mpich-3.2/test/mpi directory, the following error is generated: > > Making all in ft > make[1]: Entering directory `/root/mpich-3.2/test/mpi/ft' > CCLD failure_ack > failure_ack.o: In function `main': > failure_ack.c:(.text+0x160): undefined reference to `MPIX_Comm_failure_ack' > failure_ack.c:(.text+0x1e3): undefined reference to `MPIX_Comm_failure_get_acked' > failure_ack.c:(.text+0x444): undefined reference to `MPIX_Comm_failure_get_acked' > collect2: error: ld returned 1 exit status > make[1]: *** [failure_ack] Error 1 > make[1]: Leaving directory `/root/mpich-3.2/test/mpi/ft' > make: *** [all-recursive] Error 1 > > The compiler is picking up the declaration of MPIX_* from the mpich-3.2/src/include directory, but obviously the OpenMPI libs won't have definitions for those. However, the fact that it's searching for these symbols at all seems to indicate that the --enable-strictmpi option isn't being respected since the MPIX_* functions are nonstandard. > > Any insight into this would be greatly appreciated! > > > Thanks, > > Levi Dettwyler > Intel Corporation > levi.e.dettwyler(a)intel.com > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Errors happened when MPICH was installed
by Pei Li 21 Jul '16

21 Jul '16

Hi, Kenneth, This is the config.log file generated during configure. Thanks, Pei ________________________________________ From: Kenneth Raffenetti [raffenet(a)mcs.anl.gov] Sent: Wednesday, July 20, 2016 10:39 PM To: discuss(a)mpich.org Subject: Re: [mpich-discuss] Errors happened when MPICH was installed Can you also attach the config.log file generated during configure? On 07/20/2016 04:18 AM, Pei Li wrote: > Hello, everyone, > > When I tried to install MPICH3.2 in OPENSUSE 13.2, the errors happened. > Could you help me fix this problem? The details are included in the > m.txt and c.txt files. > > Thanks very much, > > Pei Li > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

--enable-strictmpi not respected
by Dettwyler, Levi E 20 Jul '16

20 Jul '16

Hi there, I think I've discovered an issue with the mpich-3.2 MPI tests not respecting the --enable-strictmpi flag passed in to the configure script. I'm building the mpich tests against OpenMPI. The full configure line I'm using is given below: export MPI_PREFIX=/home/build/OMPI ./configure --enable-strictmpi --disable-cxx --disable-fortran --prefix=$MPI_PREFIX CC=$MPI_PREFIX/bin/mpicc CFLAGS="-I$MPI_PREFIX/include" LDFLAGS="-L$MPI_PREFIX/lib64" When running "make" in the mpich-3.2/test/mpi directory, the following error is generated: Making all in ft make[1]: Entering directory `/root/mpich-3.2/test/mpi/ft' CCLD failure_ack failure_ack.o: In function `main': failure_ack.c:(.text+0x160): undefined reference to `MPIX_Comm_failure_ack' failure_ack.c:(.text+0x1e3): undefined reference to `MPIX_Comm_failure_get_acked' failure_ack.c:(.text+0x444): undefined reference to `MPIX_Comm_failure_get_acked' collect2: error: ld returned 1 exit status make[1]: *** [failure_ack] Error 1 make[1]: Leaving directory `/root/mpich-3.2/test/mpi/ft' make: *** [all-recursive] Error 1 The compiler is picking up the declaration of MPIX_* from the mpich-3.2/src/include directory, but obviously the OpenMPI libs won't have definitions for those. However, the fact that it's searching for these symbols at all seems to indicate that the --enable-strictmpi option isn't being respected since the MPIX_* functions are nonstandard. Any insight into this would be greatly appreciated! Thanks, Levi Dettwyler Intel Corporation levi.e.dettwyler(a)intel.com _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Errors happened when MPICH was installed
by Kenneth Raffenetti 20 Jul '16

20 Jul '16

Can you also attach the config.log file generated during configure? On 07/20/2016 04:18 AM, Pei Li wrote: > Hello, everyone, > > When I tried to install MPICH3.2 in OPENSUSE 13.2, the errors happened. > Could you help me fix this problem? The details are included in the > m.txt and c.txt files. > > Thanks very much, > > Pei Li > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Bug reporting for some mpi/rma tests
by Min Si 20 Jul '16

20 Jul '16

Hi Clï¿½ment, Please use the test suite in the latest release, so you will not get trouble with some bugs that we have already fixed. Min On 7/20/16 4:44 AM, Clï¿½ment Foyer wrote: > Hi Min, > > Although it may have been fixed in later version (as I am currently > using test suite from mpich 3.1), the window creation (l.125) is > stated as follow : > MPI_Win_create( rmabuffer, bufsize, sizeof(int), > MPI_INFO_NULL, MPI_COMM_WORLD, &win ); > with bufsize being equal to RMA_SIZE (2048) on master's side, and 0 on > partner side. However, the bufsize argument is the size of the window > in bytes, not in "displacement_unit" (here being sizeof(int) ). so the > range is int[157: 157+512], but the window is defined with a range > int[0: RMA_SIZE / sizeof(int)], creating an overflow. > > Clï¿½ment FOYER > > Message: 1 > Date: Tue, 12 Jul 2016 09:46:59 -0500 > From: Min Si <msi(a)anl.gov <mailto:[email protected]>> > To: <discuss(a)mpich.org <mailto:[email protected]>> > Subject: Re: [mpich-discuss] Bug reporting for some mpi/rma tests > Message-ID: <fb8a89ae-ca43-317f-74c4-6ec2c49b8c4e(a)anl.gov > <mailto:[email protected]>> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Hi C. FOYER, > > Thanks for reporting bugs to us. > > However, the places in test rma/lockcontention3.c are correct. > The buffers' size is RMA_SIZE (2048) count of int. In case 9, 10, > 11 the > operations' size is longcount(512) count of int, and the largest > target > displacement is OFFSET_3(157), which means the window buffer is > accessed > in range int[157: 157+512]. Thus no overflows. > > In rma/manyrma3.c, as you reported, we missed verification and winbuf > initialization. We will fix it. > > Min > > On 7/12/16 3:08 AM, Cl?ment Foyer wrote: > > Hi everyone, > > > > I think I may have found some bugs in mpich tests for RMA > operations. > > > > First, in rma/lockcontention3.c. > > When calling RMA operations, the different offsets are not taken in > > account on the origin_count and target_count parameters. As the > > buffers are the same sizes, when the count arguments are equal to > > "longcount" (such as in the tests cases 9, 10 and 11), it either > > overflows when the operation is actually done, or, as it should > > preferably be done, it fails with the returns of the > MPI_ERR_RMA_RANGE > > error code. > > Also, on the check function, there are some array overflows, as the > > loops go from 0 to longcount-1, and the array is accessed with the > > OFFSET (buf[OFFSET_1+j]). > > The easiest solution would be to set bufsize (l.111) and getbufsize > > (l.118) to RMA_SIZE+OFFSET_3 (OFFSET_3 being the bigger one), and > > maybe allocate change l.123 to srcbuf = malloc((RMA_SIZE + > > OFFSET_3)*sizeof(*srcbuf)); > > Also, the window is defined with the bufsize as size, which should > > mean that the window is bufsize bytes long. But as it is an array of > > int's, it would rather be bufsize*sizeof(int) long. There might be a > > problem there as well, given the fact that the displacement unit > given > > is actually "sizeof(int)". > > > > rma/manyrma3.c > > No verification is done. Just accumulate, and then we assume the > > result is correct. Also, winbuf is not initialized. > > > > Sincerely yours, > > > > C. FOYER > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0