-
Notifications
You must be signed in to change notification settings - Fork 900
OSC segfaults, v2.x #3267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@karasevb, FIY |
Hmm. And master is ok? |
We don't test it |
And this problem is 100% reproducible. I see it in all runs now. |
OMPI config is pretty basic - no Mellanox components are in this build. |
I think I have an idea as to where the problem is. All my testing is done on a platform that has both fetching and non-fetching atomics. libibverbs only provides fetching. Will see if I can trigger the problem by disabling non-fetching atomics in btl/ugni. |
Fixes open-mpi#3267 Signed-off-by: Nathan Hjelm <[email protected]>
this fixes a regression that went in to v2.x after the v2.1.0 release. |
Fixes open-mpi#3267 Signed-off-by: Nathan Hjelm <[email protected]> (cherry picked from commit fad0803) Signed-off-by: Nathan Hjelm <[email protected]>
Fixes open-mpi#3267 Signed-off-by: Nathan Hjelm <[email protected]> (cherry picked from commit fad0803) Signed-off-by: Nathan Hjelm <[email protected]>
Looks like this is now fixed. |
Today I noticed a segfault in our MTT:
It was running fine for at least a couple of weeks before. This might be related to recently merged #3045.
The text was updated successfully, but these errors were encountered: