Could SELinux or AppArmor be active by default for a new install and
be causing this problem?
Prentice
On 10/21/20 12:22 PM, Jorge SILVA via users wrote:
Hello Gus,
Thank you for your answer.. Unfortunately my problem is much more
basic. I didn't try to run the program in both computers
Hi, a performance question,
I have a distributed stencil loop that's sending several tens of
slightly larger messages every iteration, I post double buffered
receives at initialization and immediately after a receive request is
completed.
I can therefore prove that the receive is posted on the
Hi Jorge,
Can you try to get a stack trace of mpirun using the following command
in a separate terminal?
sudo gdb -batch -ex "thread apply all bt" -p $(ps -C mpirun -o pid= |
head -n 1)
Maybe that will give some insight where mpirun is hanging.
Cheers,
Joseph
On 10/21/20 9:58 PM, Jorge SI
Alan,
thanks for the report, I addressed this issue in
https://github.com/open-mpi/ompi/pull/8116
As a temporary workaround, you can apply the attached patch.
FWIW, f18 (shipped with LLVM 11.0.0) is still in development and uses
gfortran under the hood.
Cheers,
Gilles
On Wed, Oct 21, 2020 at
