-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Illegal instruction when importing numpy #60
Comments
Still an issue after the BLAS migration, although now the segfault happens in
conda list
|
runs fine here on ubuntu, I have a much older cpu than skylake though (something around 2011) |
Yes, it seems specific to skylake. |
It works if I force openblas 0.3.4:
|
maybe we should update openblas pin then conda-forge/conda-forge-pinning-feedstock#201 |
The new blas packages depend on openblas 0.3.5 |
oh i thought the issue was with 0.3.3 but the log shows 0.3.5 as you say, so that's maybe a regression in 0.3.5 |
It sounds like this is probably the same issue seen in OpenMathLib/OpenBLAS#2067? The issue seems to have been not accounting for the fact that VMs can disable some features of the underlying CPU. If this is the same issue then it has already been fixed in OpenBLAS master. You can set an environment variable as in that thread to work around the issue in the meantime. |
it may be OpenMathLib/OpenBLAS#1949, one could try to backport it here |
Setting the environment variable works. The issue seems to be that VirtualBox incorrectly detects my CPU as an Intel i7-6700K (which as no AVX512) and OpenBLAS correctly detects an i7-6820X (which has AVX512). |
How do you check this? Mine is a 7900X, so almost certainly the same issue |
Got to Machine->Show Log, and filter for "CPUM". |
Confirmed. Just for the record, this solution (overriding environment variable) allows numpy to be loaded despite the wrong CPU detection:
I suppose the other solution is to downgrade to openblas < 0.3.5
I am going with the second solution since it is cleaner and I don't need the latest openblas (was on a much older version of openblas anyway, before whatever that triggered the upgrade of openblas) |
I added an environment variable to my Dockerfile in order to keep the code clean but in the end one must decide case-by-case about how to deal with that I guess. |
Looks like we can't do anything here. Please open an issue upstream if the issue is still there |
Issue:
Creating an environment with the latest numpy leads to a core dump on import:
$ conda create -n np -c conda-forge numpy $ conda activate np $ python -c 'import numpy' Illegal instruction (core dumped)
Running it through
gdb
showsI'm running Ubuntu 16.04 in a VirtualBox VM on a Windows 10 host, with an Intel i7-7820X.
Environment (
conda list
):Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: