Comment # 74
on bug 80419
from Kamil Páral
Created attachment 120647 [details] system journal containing gpu hang during apitrace replay And according to the Murphy's law, after I posted my previous comment, I replayed the trace once again and it crashed my computer. Voila! (I can't say it happened at the exact time of the replay as the original recorded hang, because I wasn't looking at it, but it happened). The trace file is here (1.5 GB compressed, recorded hang at the very end right before quitting the game): https://drive.google.com/file/d/0B0Opr_geiK5nWUMwVEhJVnZPR2s/view?usp=sharing I attach my system journal related to this "replay crash". One thing got my interest. Look at this Xorg backtrace: (EE) Backtrace: (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59afb9] (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7fe7ee2ebb1f] (EE) 2: /lib64/libc.so.6 (__memcpy_avx_unaligned+0x1ab) [0x7fe7ee3ffafb] (EE) 3: /usr/lib64/dri/radeonsi_dri.so (__driDriverGetExtensions_vmwgfx+0x108dbe) [0x7fe7e6c33efe] (EE) 4: /usr/lib64/dri/radeonsi_dri.so (__driDriverGetExtensions_vmwgfx+0x1091a3) [0x7fe7e6c345a3] (EE) 5: /usr/lib64/dri/radeonsi_dri.so (__driDriverGetExtensions_vmwgfx+0x109c02) [0x7fe7e6c35a42] (EE) 6: /usr/lib64/dri/radeonsi_dri.so (__driDriverGetExtensions_vmwgfx+0x163098) [0x7fe7e6ce84f8] (EE) 7: /usr/lib64/dri/radeonsi_dri.so (__driDriverGetExtensions_vmwgfx+0xfacb7) [0x7fe7e6c17d27] (EE) 8: /usr/lib64/dri/radeonsi_dri.so (__driDriverGetExtensions_vmwgfx+0xfaf23) [0x7fe7e6c181b3] (EE) 9: /usr/lib64/dri/radeonsi_dri.so (__driDriverGetExtensions_vmwgfx+0xfb358) [0x7fe7e6c18b48] (EE) 10: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0x168d9) [0x7fe7e81b0b69] (EE) 11: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0x175d2) [0x7fe7e81b2372] (EE) 12: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0x4237) [0x7fe7e818bf67] (EE) 13: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0x80a3) [0x7fe7e8193be3] (EE) 14: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0x9ec9) [0x7fe7e8197529] (EE) 15: /usr/libexec/Xorg (DamageRegionAppend+0x621) [0x51eeb1] (EE) 16: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0x1108a) [0x7fe7e81a5f7a] (EE) 17: /usr/libexec/Xorg (AddTraps+0x4cf2) [0x519d82] (EE) 18: /usr/libexec/Xorg (SendErrorToClient+0x2df) [0x4369bf] (EE) 19: /usr/libexec/Xorg (remove_fs_handlers+0x453) [0x43a9e3] (EE) 20: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fe7ee2d7580] (EE) 21: /usr/libexec/Xorg (_start+0x29) [0x424ce9] (EE) 22: ? (?+0x29) [0x29] (EE) (EE) Bus error at address 0x7fe7e8b71000 (EE) Fatal server error: (EE) Caught signal 7 (Bus error). Server aborting 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)? (I'm sorry, I still have the same month-old mesa as in comment 70, I didn't figure out how to update it easily before I started tinkering with the replays).
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
