Hi Brian,
I'm tracking a two different problems here. The first is that mtl-portals4
is segfaulting in PtlPut(). The second is a btl-portals4 problem you
described here:
> Not specifying CM gets an earlier segfault (defaults to ob1) and looks to
be a progress thread initialization problem.
I h
Howard,
If I run examples/hello_c explicitly with —mca pml ob1, it runs fine.
If I just let mpirun pick out things, it bombs in the OMPI progress thread.
Here is the trace:
[node39:126438] mca: base: components_register: registering framework pml
components
[node39:126438] mca: base: component
HI Brian,
Thanks for the info. I'm not sure I quite get the response though. Is
the race condition in the way
Open MPI Portals4 MTL is using portals or is a problem in the portals
implementation itself?
Howard
2018-02-08 9:20 GMT-07:00 D. Brian Larkins :
> Howard,
>
> Looks like ob1 is work
Howard,
Looks like ob1 is working fine. When I looked into the problems with ob1, it
looked like the progress thread was polling the Portals event queue before it
had been initialized.
b.
$ mpirun -n 2 --mca pml ob1 --mca btl self,vader,openib osu_latency
WARNING: Ummunotify not found: Not usi
HI Brian,
As a sanity check, can you see if the ob1 pml works okay, i.e.
mpirun -n 2 --mca pml ob1 --mca btl self,vader,openib ./osu_latency
Howard
2018-02-07 11:03 GMT-07:00 brian larkins :
> Hello,
>
> I’m doing some work with Portals4 and am trying to run some MPI programs
> using the Por
