<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#c75">Comment # 75</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:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to Kamil Páral from <a href="show_bug.cgi?id=80419#c74">comment #74</a>) > There's this line: > (EE) 2: /lib64/libc.so.6 (__memcpy_avx_unaligned+0x1ab) [0x7fe7ee3ffafb] > which is the same function that I reported to be crashing in apitrace: > <a href="https://github.com/apitrace/apitrace/issues/407">https://github.com/apitrace/apitrace/issues/407</a> > > Is this just a coincidence, or these two bugs are related (or the very same)? Presumably coincidence. The apitrace crashes are segmentation faults, i.e. probably due to overrunning some buffer[0]. The Xorg crash is a bus error, which is probably fallout of the GPU hang. That said, we could probably confirm either way if we could look at a gdb backtrace of the Xorg crash. [0] FWIW, replaying the apitrace with valgrind on llvmpipe, I'm also seeing invalid memory access, so it might be a bug in apitrace or some shared Gallium / Mesa code rather than in the radeonsi driver.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>