<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Flightgear crashes during splashboot with R600 driver and mesa 11.0.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=92214#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Flightgear crashes during splashboot with R600 driver and mesa 11.0.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=92214">bug 92214</a> from <a class="email" href="mailto:sroland@vmware.com" title="Roland Scheidegger <sroland@vmware.com>"> Roland Scheidegger</a> <pre>Some very quick search turned up this bug, which looks like it could be a winner: <a href="https://bugs.archlinux.org/task/43010">https://bugs.archlinux.org/task/43010</a> Seems some libpthread implementations will try to call hw lock elision instructions on cpus where lock elision isn't supported, but _only_ if unlock is called on an already unlocked lock (so the calling code is buggy which is why it's a won't fix in libpthread). Debug information for libpthread would be nice, or you could disassemble in gdb when it crashes to confirm it's actually calling that. I have no idea where that bug could be but should be worthwile to track it down, normally you don't get the luxury of a straight neat crash when the locking is wrong...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>