trap invalid opcode in libopenblas
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openblas (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Hi!
I'm running Ubuntu 12.10 x86-64, and I recently tried to replace ATLAS with OpenBLAS on my system. I was hoping to get a speedup on my computations (which I'm performing using python-numpy). I did:
sudo apt-get remove libatlas3gf-base libatlas-dev
sudo apt-get install libopenblas-dev
However, it would appear that something went wrong:
$ python -c"import numpy; x = numpy.random.
Illegal instruction
$ tail /var/log/syslog -n 1
Feb 11 14:00:28 xua kernel: [ 456.729279] python[12206] trap invalid opcode ip:7f3b48b57220 sp:7f3b4506ecf8 error:0 in libopenblas.
According to `apt-cache show libopenblas-bas` it is decided at runtime which kernel will be run. It looks like in my case (AMD Bulldozer, FX-8150) it tries to run the wrong kernel. Any help would be appreciated.
Changed in openblas (Ubuntu): | |
status: | Incomplete → Fix Released |
Hi Thomas,
Can you include the output of cat /proc/cpuinfo so we can see what instructions your CPU is claiming it can do?
Also, I think a backtrace would help; I *think* you should find you have some log files in /var/crash , I'm guessing that from this test they'll appear to be against python but I may be wrong; but if you can find the one that's generated from this simple test case and then I think:
apport-cli -u 1122030 /var/crash/ whatever- the-crash- file-is- called
should attach the backtrace to this bug, then we can figure out which instruction it's trying to use in what function.
(I think!).
Dave