From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup Date: Tue, 22 Dec 2015 12:37:24 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0762696885==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 4E4506E5BA for ; Tue, 22 Dec 2015 04:37:24 -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 --===============0762696885== Content-Type: multipart/alternative; boundary="1450787844.68BF2.19391"; charset="UTF-8" --1450787844.68BF2.19391 Date: Tue, 22 Dec 2015 12:37:24 +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 #85 from Kamil P=C3=A1ral --- (In reply to Daniel Exner from comment #80) > Now I get (with radeonsi): >=20 > glretrace game.x86_64.trace=20 > apitrace: warning: caught signal 11 > 47062: error: caught an unhandled exception Great to see it does not crash just for me :-) (In reply to Michael Eagle from comment #82) > On Fedora 23 I'm using this copr: > https://copr.fedoraproject.org/coprs/griever/mesa-git/ Thanks, that helps a lot! (In reply to Daniel Exner from comment #83) > Managed to get some more infos about glretrace crash: Please note I uploaded a gdb backtrace to the apitrace bug mentioned in com= ment 73. Now that I tested latest mesa git (ea8c0b1, 2012-12-21), I can confirm apitrace still crashes, and I uploaded an updated gdb backtrace: https://github.com/apitrace/apitrace/files/69636/gdb.backtrace2.txt However, the question is whether that apitrace crash is related to the gpu = hang we see in XCOM. It certainly makes debugging harder. --=20 You are receiving this mail because: You are the assignee for the bug. --1450787844.68BF2.19391 Date: Tue, 22 Dec 2015 12:37:24 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 85 on bug 80419<= /a> from Kamil P=C3=A1ral 
(In reply to Daniel Exner from comment #80)
> Now I get (with radeonsi):
>=20
> glretrace game.x86_64.trace=20
> apitrace: warning: caught signal 11
> 47062: error: caught an unhandled exception

Great to see it does not crash just for me :-)

(In reply to Michael Eagle from com=
ment #82)
> On Fedora 23 I'm using this copr:
> htt=
ps://copr.fedoraproject.org/coprs/griever/mesa-git/

Thanks, that helps a lot!

(In reply to Daniel Exner from comm=
ent #83)
> Managed to get some more infos about glretrace c=
rash:

Please note I uploaded a gdb backtrace to the apitrace bug mentioned in comment
73. Now that I tested latest mesa git (ea8c0b1, 2012-12-21), I can conf=
irm
apitrace still crashes, and I uploaded an updated gdb backtrace:
https://github.com/apitrace/apitrace/files/69636/gdb.backtrace2.txt

However, the question is whether that apitrace crash is related to the gpu =
hang
we see in XCOM. It certainly makes debugging harder.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1450787844.68BF2.19391-- --===============0762696885== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0762696885==--