From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup Date: Wed, 02 Mar 2016 16:35:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2061226324==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 1F3C96E8EF for ; Wed, 2 Mar 2016 16:35:32 +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 --===============2061226324== Content-Type: multipart/alternative; boundary="14569365312.c19fc0Df1.14431"; charset="UTF-8" --14569365312.c19fc0Df1.14431 Date: Wed, 2 Mar 2016 16:35:31 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=80419 --- Comment #117 from Kamil Páral --- (In reply to Marek Olšák from comment #116) > This thread is too long. Could someone please summarize the issues here? > Also, how does the apitrace crash relate to the GPU hang? I hoped somebody clever would respond, but it seems it'll have to be me. OpenGL layman alert. There were multiple issues discovered in this report: 0. (the core issue) radeonsi hangs the system completely (or sometimes recovers) when playing XCOM, randomly (can be minutes, can be hours) 1. Jose claims XCOM has a bug, issuing invalid OpenGL commands (see comment 115). 2. apitrace is crashing while replaying almost any XCOM trace. My trace from comment 74 is affected by this, so you need a temporary fix from https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366 to stop it from crashing. The fix is not mainlined, because Jose says the purpose of apitrace is to help discover problems, not hide them. 3. Another discovered issue was that apitrace was trimming vertex data too aggressively (comment 113, https://github.com/apitrace/apitrace/issues/407#issuecomment-167866502). That is now fixed in apitrace, but my trace is affected, I'd have to re-record it. The problem is that I was really lucky that I recorded it in the first place, my computer did not hang completely as in 99% of cases, but recovered, and therefore the trace was not cut short. I don't think I'd get that lucky again. Plus Nicolai said he does not need that. The trimmed vertex data does not seem to affect the replay in a negative way, but I assume it might complicate the debugging process. 4. When looping over my trace, I can reproduce the crash pretty quick (i.e. my computer completely hangs), but not deterministically (does not happen on every replay). But it seems there is no further info I could supply from my side to help you debug this. 5. Nicolai said he can reproduce it (probably by running the game, not replaying my trace), but it takes a long time, so he wasn't able to work on this too much. -- You are receiving this mail because: You are the assignee for the bug. --14569365312.c19fc0Df1.14431 Date: Wed, 2 Mar 2016 16:35:31 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 117 on bug 80419 from 
(In reply to Marek Olšák from comment #116)
> This thread is too long. Could someone please summarize the issues here?
> Also, how does the apitrace crash relate to the GPU hang?

I hoped somebody clever would respond, but it seems it'll have to be me. OpenGL
layman alert.

There were multiple issues discovered in this report:
0. (the core issue) radeonsi hangs the system completely (or sometimes
recovers) when playing XCOM, randomly (can be minutes, can be hours)
1. Jose claims XCOM has a bug, issuing invalid OpenGL commands (see comment
115).
2. apitrace is crashing while replaying almost any XCOM trace. My trace from
comment 74 is affected by this, so you need a temporary fix from
https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366 to stop
it from crashing. The fix is not mainlined, because Jose says the purpose of
apitrace is to help discover problems, not hide them.
3. Another discovered issue was that apitrace was trimming vertex data too
aggressively (comment 113,
https://github.com/apitrace/apitrace/issues/407#issuecomment-167866502). That
is now fixed in apitrace, but my trace is affected, I'd have to re-record it.
The problem is that I was really lucky that I recorded it in the first place,
my computer did not hang completely as in 99% of cases, but recovered, and
therefore the trace was not cut short. I don't think I'd get that lucky again.
Plus Nicolai said he does not need that. The trimmed vertex data does not seem
to affect the replay in a negative way, but I assume it might complicate the
debugging process.
4. When looping over my trace, I can reproduce the crash pretty quick (i.e. my
computer completely hangs), but not deterministically (does not happen on every
replay). But it seems there is no further info I could supply from my side to
help you debug this.
5. Nicolai said he can reproduce it (probably by running the game, not
replaying my trace), but it takes a long time, so he wasn't able to work on
this too much.

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