https://bugs.freedesktop.org/show_bug.cgi?id=92214
--- Comment #10 from Roland Scheidegger <sroland at vmware.com> --- Some very quick search turned up this bug, which looks like it could be a winner: https://bugs.archlinux.org/task/43010 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... -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151002/c9d5e549/attachment.html>
