From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup Date: Mon, 21 Dec 2015 23:03:10 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1097032594==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CD7076E188 for ; Mon, 21 Dec 2015 15:03:10 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1097032594== Content-Type: multipart/alternative; boundary="1450738990.a7a22Ff2.22809"; charset="UTF-8" --1450738990.a7a22Ff2.22809 Date: Mon, 21 Dec 2015 23:03:10 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D80419 --- Comment #74 from Kamil P=C3=A1ral --- Created attachment 120647 --> https://bugs.freedesktop.org/attachment.cgi?id=3D120647&action=3Dedit 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 s= ay 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 ri= ght before quitting the game): https://drive.google.com/file/d/0B0Opr_geiK5nWUMwVEhJVnZPR2s/view?usp=3Dsha= ring 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). --=20 You are receiving this mail because: You are the assignee for the bug. --1450738990.a7a22Ff2.22809 Date: Mon, 21 Dec 2015 23:03:10 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 74 on bug 80419<= /a> from Kamil P=C3=A1ral
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 s=
ay
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 ri=
ght
before quitting the game):
https://drive.google.com/file/d/0B0Opr_geiK5nWUMwVEhJVnZPR=
2s/view?usp=3Dsharing

I attach my system journal related to this "replay crash". One th=
ing 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: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1450738990.a7a22Ff2.22809-- --===============1097032594== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1097032594==--