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 22:33:43 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0331118095==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0788F6E1B3 for ; Mon, 21 Dec 2015 14:33:43 -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 --===============0331118095== Content-Type: multipart/alternative; boundary="1450737222.af3bcD32.16393"; charset="UTF-8" --1450737222.af3bcD32.16393 Date: Mon, 21 Dec 2015 22:33:42 +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 #73 from Kamil P=C3=A1ral --- I have managed to capture an apitrace while radeon driver locked up *and* recovered afterwards, so that I was able to exit the game normally (this al= most never happens). I was hopeful that in this case it could contain all the ca= lls triggering the lockup, compared to the case where the system locks up completely and does not recover. I've met issues replaying the trace, apitr= ace seems to crash for any XCOM trace I capture. I reported it here: https://github.com/apitrace/apitrace/issues/407 Nevertheless after many attempts I managed to replay the trace twice in full length, and it did not lock up my system again, nor was the lockup visible = in the replay itself (in reality my system got locked up for about 10 seconds,= but in the replay it plays uninterrupted). So it seems that apitrace is not something that can be used reliably to reproduce this issue, unfortunately. --=20 You are receiving this mail because: You are the assignee for the bug. --1450737222.af3bcD32.16393 Date: Mon, 21 Dec 2015 22:33:42 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 73 on bug 80419<= /a> from Kamil P=C3=A1ral 
I have managed to capture an apitrace while radeon driver lock=
ed up *and*
recovered afterwards, so that I was able to exit the game normally (this al=
most
never happens). I was hopeful that in this case it could contain all the ca=
lls
triggering the lockup, compared to the case where the system locks up
completely and does not recover. I've met issues replaying the trace, apitr=
ace
seems to crash for any XCOM trace I capture. I reported it here:
https://github.=
com/apitrace/apitrace/issues/407

Nevertheless after many attempts I managed to replay the trace twice in full
length, and it did not lock up my system again, nor was the lockup visible =
in
the replay itself (in reality my system got locked up for about 10 seconds,=
 but
in the replay it plays uninterrupted). So it seems that apitrace is not
something that can be used reliably to reproduce this issue, unfortunately.=

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