On Wed, Mar 12, 2014 at 04:33:45PM +0100, Thomas Karmann wrote: > Intel knows about this, see the errata (page 15): > http://downloadmirror.intel.com/23197/eng/Quark_SW_RelNotes_330232_001.pdf
Thanks for digging on this issue, that indeed explains a lot. It's probably something we can fix in glibc using the workaround proposed by Intel, that said "lock" is a quite common instruction as soon as you have multithreaded code, so there are probably hundred of packages to fix (which seems to confirmed by codesearch.debian.net). The best would be to get the problem fixed at the hardware level, either through a new chip revision or a new microcode. -- Aurelien Jarno GPG: 1024D/F1BCDB73 [email protected] http://www.aurel32.net -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
