(In reply to Kamil Páral from comment #74)
> 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:
> https://github.com/apitrace/apitrace/issues/407
> 
> 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.