-mpi.org
Sent: Tuesday, August 30, 2016 6:37:51 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
Sorry - previous version had a typo in it:
diff --git a/orte/mca/state/orted/state_orted.c
b/orte/mca/state/orted/state_orted.c
index e506cc9..eb0c4b4 100644
--- a/orte
Yes, I can definitely help to test the patch.
Jingchao
From: users on behalf of r...@open-mpi.org
Sent: Tuesday, August 30, 2016 2:23:12 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
Oh my - that indeed illustrated the problem
> Sent: Tuesday, August 30, 2016 1:45:45 PM
> To: Open MPI Users
> Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
>
> Well, that helped a bit. For some reason, your system is skipping a step in
> the launch state machine, and so we never hit the step where we setup th
o:users-boun...@lists.open-mpi.org>> on behalf of r...@open-mpi.org
> <mailto:r...@open-mpi.org> mailto:r...@open-mpi.org>>
> Sent: Tuesday, August 30, 2016 12:56:33 PM
> To: Open MPI Users
> Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
>
>
and resubmit, then it hangs. It happened with the
job above as well. Very odd.
From: users on behalf of r...@open-mpi.org
Sent: Tuesday, August 30, 2016 12:56:33 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
Hmmm...well,
fd, ORTE_NAME_PRINT(dst_name));
>
> /* don't do this if the dst vpid is invalid or the fd is negative! */
> if (ORTE_VPID_INVALID == dst_name->vpid || fd < 0) {
> return ORTE_SUCCESS;
> }
>
> /*OPAL_OUTPUT_VERBOSE((1, ort
rs on behalf of r...@open-mpi.org
Sent: Monday, August 29, 2016 11:42:00 AM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
I’m sorry, but something is simply very wrong here. Are you sure you are
pointed at the correct LD_LIBRARY_PATH? Perhaps add a “BOO” or something
nit
> Rank 10 has cleared MPI_Init
> Rank 11 has cleared MPI_Init
> Rank 12 has cleared MPI_Init
> Rank 13 has cleared MPI_Init
> Rank 17 has cleared MPI_Init
> Rank 19 has cleared MPI_Init
>
> Thanks,
>
> Dr. Jingchao Zhang
> Holland Computing Center
> Univers
has cleared MPI_Init
Thanks,
Dr. Jingchao Zhang
Holland Computing Center
University of Nebraska-Lincoln
402-472-6400
From: users on behalf of r...@open-mpi.org
Sent: Saturday, August 27, 2016 12:31:53 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue w
t; I saw the pull request and did a test with v2.0.1rc1, but the problem
>>> persists. Any ideas?
>>>
>>> Thanks,
>>>
>>> Dr. Jingchao Zhang
>>> Holland Computing Center
>>> University of Nebraska-Lincoln
>>> 402-472-6400
>>>
versity of Nebraska-Lincoln
>> 402-472-6400
>> From: users on behalf of
>> r...@open-mpi.org
>> Sent: Wednesday, August 24, 2016 1:27:28 PM
>> To: Open MPI Users
>> Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
>>
>> Bingo - found it, fix
t: Wednesday, August 24, 2016 1:27:28 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
Bingo - found it, fix submitted and hope to get it into 2.0.1
Thanks for the assist!
Ralph
On Aug 24, 2016, at 12:15 PM, Jingchao Zhang
mailto:zh...@unl.edu>> wrote:
I confi
r
>> University of Nebraska-Lincoln
>> 402-472-6400
>> From: users > <mailto:users-boun...@lists.open-mpi.org>> on behalf of r...@open-mpi.org
>> <mailto:r...@open-mpi.org> mailto:r...@open-mpi.org>>
>> Sent: Wednesday, August 24, 2016 12:14:26 P
, August 24, 2016 1:27:28 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
Bingo - found it, fix submitted and hope to get it into 2.0.1
Thanks for the assist!
Ralph
On Aug 24, 2016, at 12:15 PM, Jingchao Zhang
mailto:zh...@unl.edu>> wrote:
I configured v2.
chao Zhang
>> Holland Computing Center
>> University of Nebraska-Lincoln
>> 402-472-6400
>> From: users > <mailto:users-boun...@lists.open-mpi.org>> on behalf of r...@open-mpi.org
>> <mailto:r...@open-mpi.org> mailto:r...@open-mpi.org>>
>>
6 12:14:26 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
Afraid I can’t replicate a problem at all, whether rank=0 is local or not. I’m
also using bash, but on CentOS-7, so I suspect the OS is the difference.
Can you configure OMPI with --enable-debug, and then ru
Holland Computing Center
> University of Nebraska-Lincoln
> 402-472-6400
> From: users <mailto:users-boun...@lists.open-mpi.org>> on behalf of r...@open-mpi.org
> <mailto:r...@open-mpi.org> mailto:r...@open-mpi.org>>
> Sent: Tuesday, August 23, 2016 8:14:48 PM
&
x86_64 GNU/Linux
Dr. Jingchao Zhang
Holland Computing Center
University of Nebraska-Lincoln
402-472-6400
From: users on behalf of r...@open-mpi.org
Sent: Tuesday, August 23, 2016 8:14:48 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi
-Jingchao
>
> Dr. Jingchao Zhang
> Holland Computing Center
> University of Nebraska-Lincoln
> 402-472-6400
> From: users <mailto:users-boun...@lists.open-mpi.org>> on behalf of r...@open-mpi.org
> <mailto:r...@open-mpi.org> mailto:r...@open-mpi.org>>
&
pen-mpi.org
Sent: Tuesday, August 23, 2016 4:03:07 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
The IO forwarding messages all flow over the Ethernet, so the type of fabric is
irrelevant. The number of procs involved would definitely have an impact, but
that might
; 402-472-6400
> From: users <mailto:users-boun...@lists.open-mpi.org>> on behalf of r...@open-mpi.org
> <mailto:r...@open-mpi.org> mailto:r...@open-mpi.org>>
> Sent: Monday, August 22, 2016 10:23:42 PM
> To: Open MPI Users
> Subject: Re: [OMPI users] stdin issue with op
Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
FWIW: I just tested forwarding up to 100MBytes via stdin using the simple test
shown below with OMPI v2.0.1rc1, and it worked fine. So I’d suggest upgrading
when the official release comes out, or going ahead and at least testing
n look into the issue and fix it.
>
> Dr. Jingchao Zhang
> Holland Computing Center
> University of Nebraska-Lincoln
> 402-472-6400
> From: users <mailto:users-boun...@lists.open-mpi.org>> on behalf of r...@open-mpi.org
> <mailto:r...@open-mpi.org> mailto:r...
. Jingchao Zhang
Holland Computing Center
University of Nebraska-Lincoln
402-472-6400
From: users on behalf of r...@open-mpi.org
Sent: Monday, August 22, 2016 3:04:50 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
Well, I can try to find
sers-boun...@lists.open-mpi.org>> on behalf of r...@open-mpi.org
> <mailto:r...@open-mpi.org> mailto:r...@open-mpi.org>>
> Sent: Monday, August 22, 2016 2:17:10 PM
> To: Open MPI Users
> Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
>
> Hmmm...perh
sers on behalf of r...@open-mpi.org
Sent: Monday, August 22, 2016 2:17:10 PM
To: Open MPI Users
Subject: Re: [OMPI users] stdin issue with openmpi/2.0.0
Hmmm...perhaps we can break this out a bit? The stdin will be going to your
rank=0 proc. It sounds like you have some subsequent step that calls M
On Monday, August 22, 2016, Jingchao Zhang wrote:
> Hi all,
>
>
> We compiled openmpi/2.0.0 with gcc/6.1.0 and intel/13.1.3. Both of them
> have odd behaviors when trying to read from standard input.
>
>
> For example, if we start the application lammps across 4 nodes, each node
> 16 cores, conne
Hmmm...perhaps we can break this out a bit? The stdin will be going to your
rank=0 proc. It sounds like you have some subsequent step that calls MPI_Bcast?
Can you first verify that the input is being correctly delivered to rank=0?
This will help us isolate if the problem is in the IO forwarding
Hi all,
We compiled openmpi/2.0.0 with gcc/6.1.0 and intel/13.1.3. Both of them have
odd behaviors when trying to read from standard input.
For example, if we start the application lammps across 4 nodes, each node 16
cores, connected by Intel QDR Infiniband, mpirun works fine for the 1st time
Hi,
Am 03.10.2010 um 18:25 schrieb Andrei Fokau:
> We have a a program which is normally (running w/o MPI) controlled by Ctrl+C
> and then a number of options. Is it possible to set STDIN for a command
> executed via mpirun? The following page describes parameter -stdin, but it
> seems to be n
We have a a program which is normally (running w/o MPI) controlled by Ctrl+C
and then a number of options. Is it possible to set STDIN for a command
executed via mpirun? The following page describes parameter -stdin, but it
seems to be not supported by OMPI's mpirun.
http://w3.ualg.pt/~dubuf/calhau
31 matches
Mail list logo
