It looks like one of the MTL components is registering a progress call with the
opal_progress thread, and then unloading when de-selected. Registering with
opal_progress should only be done once the MTL has been selected and will run
> On Jul 23, 2015, at 5:05 PM, Paul Hargrove wrote:
>
> Yoh
Yohann,
With PR409 as it stands right now (commit 6daef310) I see no change to the
behavior.
I still get a SEGV below opal_progress() unless I use either
-mca mtl ^ofi
OR
-mca pml cm
A backtrace from gdb appears below.
-Paul
(gdb) where
#0 0x7f5bc7b59867 in ?? () from /lib64/libgcc_s
Paul,
While looking at the issue, we noticed that we were missing some code that
deals with MTL priorities.
PR 409 (https://github.com/open-mpi/ompi-release/pull/409) is attempting to fix
that.
Hopefully, this will also fix the error you encountered.
Thanks again,
Yohann
From: devel [mailto:
