<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - XCOM: Enemy Unknown Causes lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=80419#c87">Comment # 87</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - XCOM: Enemy Unknown Causes lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=80419">bug 80419</a> from <a class="email" href="mailto:kamil.paral@gmail.com" title="Kamil Páral <kamil.paral@gmail.com>"> Kamil Páral</a> <pre>Created <a href="attachment.cgi?id=120655" name="attach_120655" title="gdb backtrace from xorg when system locks up during glretrace replay">attachment 120655</a> <a href="attachment.cgi?id=120655&action=edit" title="gdb backtrace from xorg when system locks up during glretrace replay">[details]</a> gdb backtrace from xorg when system locks up during glretrace replay Thanks Nicolai and others for looking into this. I have some good news. The apitrace developer patched glretrace, so that it no longer crashes during replay. He says it's a bug inside XCOM. He also says the problem might likely cause the radeonsi driver crash as well. See his comment here: <a href="https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366">https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366</a> (If this indeed turns out to be an XCOM bug, it would be nice if we could put some safeguards into the driver and didn't crash for invalid commands, but I'm saying that as someone who knows exactly zero about gpu driver programming). Also, now that glretrace does not crash, I'm able to easily loop the trace until its very end. In just a handful of replays, my system locked up 3 times. I haven't seen all lockups, but at least once it occurred exactly at the point where the lockup occurred while recording (at the very end). So it seems I'm able to reproduce this with reasonable likelihood, and therefore can test some fixes if needed. (In reply to Michel Dänzer from <a href="show_bug.cgi?id=80419#c77">comment #77</a>) > No need, it's not important. The assumption for now is that the Xorg crash > is caused by the GPU hang. If you happen to get a gdb backtrace of it in the > future, that will help verify this assumption, but it's no more than nice to > have. I have it now, attaching.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>