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, 13 Jun 2016 08:28:55 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0306592497==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 7D76D6E401 for ; Mon, 13 Jun 2016 08:28:56 +0000 (UTC) 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 --===============0306592497== Content-Type: multipart/alternative; boundary="14658065366.724f1515F.29166"; charset="UTF-8" --14658065366.724f1515F.29166 Date: Mon, 13 Jun 2016 08:28:56 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D80419 --- Comment #134 from Nicolai H=C3=A4hnle --- Hi Daniel, curious, but I doubt the crash is related to the lockup. Most likely, buffer creation fails in radeon_cs_create_fence and then we get a N= ULL pointer dereference. If you could get a backtrace with line numbers to conf= irm that would be nice. In any case, GPU lockups can only be caused by actually submitting somethin= g to the GPU, which we obviously don't do once the game process crashes... so mo= re likely, the GPU lockup happens first and then causes the subsequent failure somehow. --=20 You are receiving this mail because: You are the assignee for the bug.= --14658065366.724f1515F.29166 Date: Mon, 13 Jun 2016 08:28:56 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 134 on bug 80419<= /a> from Nicolai H=C3=A4hnle 
Hi Daniel, curious, but I doubt the crash is related to the lo=
ckup. Most
likely, buffer creation fails in radeon_cs_create_fence and then we get a N=
ULL
pointer dereference. If you could get a backtrace with line numbers to conf=
irm
that would be nice.

In any case, GPU lockups can only be caused by actually submitting somethin=
g to
the GPU, which we obviously don't do once the game process crashes... so mo=
re
likely, the GPU lockup happens first and then causes the subsequent failure
somehow.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14658065366.724f1515F.29166-- --===============0306592497== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0306592497==--