On 12.03.2014 (21:20), Aurelien Jarno wrote: > While it shows that the problem is at the CPU level, it's not really a > fix, as the bus is not locked anymore, so it might results in issues in > multithreaded solution. > > The correct solution would be to apply the solution from Intel, that is > adding a nop before every instruction with the lock prefix. This means > rebuilding the code.
Yes, of course! I forgot to mention that I only did this to find the cause of the bug and to get Debian running somehow on the Galileo-Board. To my understanding the lock prefix only makes sense on multi-core systems, so the impatient (galileo users) should be safe by removing the prefix at every occurence until a proper fix is implemented? About that: /proc/cpuinfo doesn't include a "microcode" entry, so I wouldn't bet on a quick fix by Intel. I don't know if this feature is really missing, though. With kind regards Thomas -- Thomas Karmann / CIP-Pool-Administration / Department of Computer Science 4 Organization: University of Erlangen-Nuremberg Address: Martensstrasse 1 91058 Erlangen Germany Website: https://wwwcip.informatik.uni-erlangen.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
