[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-03-03 Thread Thomas U.
I've tried the amd64 version. Everything looks fine, no more SIGILL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1122030 Title: trap invalid opcode in libopenblas To manage notifications about

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-03-03 Thread Julian Taylor
** Changed in: openblas (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1122030 Title: trap invalid opcode in libopenblas To manage notifications

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-03-02 Thread Julian Taylor
this might be fixed in 0.2.6 as it has a bulldozer dgemm kernel which does not use the femms instruction. Can you install the package from raring and try? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-03-02 Thread Thomas U.
Hi! I can try, but as far as I can see, raring currently only has 2.5.1: http://packages.ubuntu.com/raring/libopenblas-base But for what it's worth, I pulled the openblas source from github on the 15. Februrary and that runs without problems. -- You received this bug notification because you

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-03-02 Thread Julian Taylor
sorry the syncing took longer than I expected, 0.2.6 is now available in raring-proposed: https://launchpad.net/ubuntu/+source/openblas/0.2.6-1~exp1 it would be good if you could give the packages a try too (click on amd64 or i386 under Builds for the packages) thanks -- You received this bug

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-02-12 Thread Thomas U.
~$ dpkg -l \*blas\* | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-02-11 Thread Dave Gilbert
Hi Thomas, Can you include the output ofcat /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

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-02-11 Thread Thomas U.
Attacked to this message you will find the result of `cat /proc/cpuinfo` ** Attachment added: result of cat /proc/cpuinfo https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1122030/+attachment/3524609/+files/cpuinfo -- You received this bug notification because you are a member of

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-02-11 Thread Thomas U.
Sorry for posting this in a separate message, but I didn't figure out how to attach more than 1 file to a message. Unfortunately apport-cli doesn't work on my end, giving me the following: ~$ apport-cli -u 1122030 /var/crash/_usr_bin_python2.7.1000.crash ERROR: The launchpadlib Python module is

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-02-11 Thread Dave Gilbert
Hi Thomas, Thanks - that's looking the same as bug 1117335 (which is libblas rather than openblas), but I think you're in the same function. Can you confirm exactly which version of libopenblas you have; can you do: dpkg -l \*blas\* | cat Thanks, Dave -- You received this bug notification

[Bug 1122030] Re: trap invalid opcode in libopenblas

2013-02-11 Thread Dave Gilbert
http://devgurus.amd.com/thread/159993 maybe - they removed 3DNow from some newer chips; my disassembly of that core of yours is that it's a femms instruction which is what that thread discusses; looks like blas makes too many assumptions. ** Changed in: openblas (Ubuntu) Importance: Undecided