-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
OpenBLAS 0.3.8 issue on AMD Threadripper cpu #8747
Comments
I'm sure OpenBLAS 0.3.7 does the same. Work around that with OPENBLAS_CORETYPE, the same as was done for issue #4287. |
re: 0.3.7. I don't think so, we've been using this box for 3 months now, and got into this problem only after update to 0.3.8 i think. It's pretty new issue there. re: OPENBLAS_CORETYPE - nope, doesn't help. |
@saudet you're right, 0.3.7 reproduces the same issue. So probably this crash is caused by the graph being added to resources. I'll close this issue, we'll sort it out in some other way i think now. |
Setting the OPENBLAS_CORETYPE environment variable to "Athlon" or "Core2" doesn't help? That's strange. That should disable pretty much all optimizations. Anyway, one more thing to try is to use MKL instead. The presets for OpenBLAS can load it with the system properties given here: |
Athlon doesn't help. We'll try Core2 now |
I've just checked, same situation - no success unfortunately |
This is probably the cause: OpenMathLib/OpenBLAS#2526 |
Who's building OpenBLAS for JavaCPP? |
The changes from commit bytedeco/javacpp-presets@cb00315 have been deployed. |
ND4J tests (including those that were consistently crashing on this system) are confirmed passing on 3990x with Linux (ubuntu 20.04) with the following version modifications: |
Everything is fine on 3950 and 3970 as well 👍 |
OpenBLAS 0.3.8 crashes on AMD Threadripper 3970X cpu, with SIGILL error code.
We always got following crash while testing TFGraphTestAllHelper.log_determinant.rank3:
This issue is a blocker for us, since we basically unable to use devbox for java tests
The text was updated successfully, but these errors were encountered: