-
Jeff Squyres
jsquy...@cisco.com
From: users on behalf of Jeff Squyres
(jsquyres) via users
Sent: Thursday, May 5, 2022 3:31 PM
To: George Bosilca; Open MPI Users
Cc: Jeff Squyres (jsquyres)
Subject: Re: [OMPI users] mpirun hangs on m1 mac w openmpi-4.1.3
Scott a
3:19 PM
To: Open MPI Users
Cc: Jeff Squyres (jsquyres); Scott Sayres
Subject: Re: [OMPI users] mpirun hangs on m1 mac w openmpi-4.1.3
That is weird, but maybe it is not a deadlock, but a very slow progress. In the
child can you print the fdmax and i in the frame do_child.
George.
On Thu, May 5
That is weird, but maybe it is not a deadlock, but a very slow progress. In
the child can you print the fdmax and i in the frame do_child.
George.
On Thu, May 5, 2022 at 11:50 AM Scott Sayres via users <
users@lists.open-mpi.org> wrote:
> Jeff, thanks.
> from 1:
>
> (lldb) process attach --pid
Jeff, thanks.
from 1:
(lldb) process attach --pid 95083
Process 95083 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
frame #0: 0x0001bde25628 libsystem_kernel.dylib`close + 8
libsystem_kernel.dylib`close:
-> 0x1bde25628 <+8>: b.lo 0x1bde25648
You can use "lldb -p PID" to attach to a running process.
--
Jeff Squyres
jsquy...@cisco.com
From: Scott Sayres
Sent: Thursday, May 5, 2022 11:22 AM
To: Jeff Squyres (jsquyres)
Cc: Open MPI Users
Subject: Re: [OMPI users] mpirun hangs on m1 mac
Jeff,
It does launch two mpirun processes (when hung from another terminal window)
scottsayres 95083 99.0 0.0 408918416 1472 s002 R 8:20AM
0:04.48 mpirun -np 4 foo.sh
scottsayres 95085 0.0 0.0 408628368 1632 s006 S+8:20AM
0:00.00 egrep mpirun|foo.sh
scottsayres
the
> child process... which is weird).
>
> --
> Jeff Squyres
> jsquy...@cisco.com
>
>
> From: Scott Sayres
> Sent: Wednesday, May 4, 2022 4:02 PM
> To: Jeff Squyres (jsquyres)
> Cc: Open MPI Users
> Subject: Re: [OMPI users] mpirun hangs on m1 mac w openmpi-4.1.
-
Jeff Squyres
jsquy...@cisco.com
From: Scott Sayres
Sent: Wednesday, May 4, 2022 4:02 PM
To: Jeff Squyres (jsquyres)
Cc: Open MPI Users
Subject: Re: [OMPI users] mpirun hangs on m1 mac w openmpi-4.1.3
foo.sh is executable, again hangs without output.
I co
gt;
>> mpirun -np 1 foo.sh
>>
>> If you start seeing output, good!If it completes, better!
>>
>> If it hangs, and/or if you don't see any output at all, do this:
>>
>> ps auxwww | egrep 'mpirun|foo.sh'
>>
>> It should show mpirun and 2 copies of foo.sh (and pr
> ps auxwww | egrep 'mpirun|foo.sh'
>
> It should show mpirun and 2 copies of foo.sh (and probably a grep). Does
> it?
>
> --
> Jeff Squyres
> jsquy...@cisco.com
>
>
> From: Scott Sayres
> Sent: Wednesday, May 4, 2022 2:47
From: Scott Sayres
Sent: Wednesday, May 4, 2022 2:47 PM
To: Open MPI Users
Cc: Jeff Squyres (jsquyres)
Subject: Re: [OMPI users] mpirun hangs on m1 mac w openmpi-4.1.3
Following Jeff's advice, I have rebuilt open-mpi by hand using the -g option.
This shows more information as below
Following Jeff's advice, I have rebuilt open-mpi by hand using the -g
option. This shows more information as below. I am attempting George's
advice of how to track the child but notice that gdb does not support
arm64. attempting to update lldb.
scottsayres@scotts-mbp openmpi-4.1.3 % lldb
: Wednesday, May 4, 2022 12:35 PM
To: Open MPI Users
Cc: George Bosilca
Subject: Re: [OMPI users] mpirun hangs on m1 mac w openmpi-4.1.3
I compiled a fresh copy of the 4.1.3 branch on my M1 laptop, and I can run both
MPI and non-MPI apps without any issues.
Try running `lldb mpirun -- -np 1 hostname
Scott,
This shows the deadlock arrives during the local spawn. Here is how things
are supposed to work: the mpirun process (parent) will fork (the child),
and these 2 processes are connected through a pipe. The child will then
execve the desired command (hostname in your case), and this will
Hi George, Thanks! You have just taught me a new trick. Although I do not
yet understand the output, it is below:
scottsayres@scotts-mbp ~ % lldb mpirun -- -np 1 hostname
(lldb) target create "mpirun"
Current executable set to 'mpirun' (arm64).
(lldb) settings set -- target.run-args "-np"
I compiled a fresh copy of the 4.1.3 branch on my M1 laptop, and I can run
both MPI and non-MPI apps without any issues.
Try running `lldb mpirun -- -np 1 hostname` and once it deadlocks, do a
CTRL+C to get back on the debugger and then `backtrace` to see where it is
waiting.
George.
On Wed,
Thanks for looking at this Jeff.
No, I cannot use mpirun to launch a non-MPI application.The command
"mpirun -np 2 hostname" also hangs.
I get the following output if I add the -d command before (I've replaced
the server with the hashtags) :
[scotts-mbp.3500.dhcp.###:05469] procdir:
Are you able to use mpirun to launch a non-MPI application? E.g.:
mpirun -np 2 hostname
And if that works, can you run the simple example MPI apps in the "examples"
directory of the MPI source tarball (the "hello world" and "ring" programs)?
E.g.:
cd examples
make
mpirun -np 4 hello_c
18 matches
Mail list logo
