From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup
Date: Fri, 18 Dec 2015 09:45:53 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1789906884=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 9D99D6EA44
for ; Fri, 18 Dec 2015 01:45:53 -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
--===============1789906884==
Content-Type: multipart/alternative; boundary="1450431953.c1A42.26849"; charset="UTF-8"
--1450431953.c1A42.26849
Date: Fri, 18 Dec 2015 09:45:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
https://bugs.freedesktop.org/show_bug.cgi?id=80419
--- Comment #65 from David Beswick ---
Hello everyone,
Just to keep you up to date, I switched tack and have been using the
"GALLIUM_DDEBUG" environment variable to try and capture data about the crash.
I found out about this option via a Google search. As I understand it, it
creates fences around each GPU operation to detect when and if they complete,
dumping the contents of the draw call if it doesn't finish in a timely way.
Unfortunately, I haven't been able to reproduce the crash with this variable
enabled, despite playing for more than 5 hours (not consecutively.) The
GALLIUM_DDEBUG mode is certainly working as performance is quite severely
impacted. Maybe the way GALLIUM_DDEBUG is implemented unfortunately also
prevents the issue from happening.
All I can say so far is that I suspect the problem is related to vertex buffer
drawing. On one occasion I disabled the fences around vertex buffer drawing
while enabling GALLIUM_DDEBUG (to try and get some more performance) and I did
experience a hard lock as usual. I will continue running in this mode to see if
it turns up a result.
If anyone else would like to try, you can modify the
"~/.steam/steamapps/common/XCom-Enemy-Unknown/binaries/linux/xcom.sh" file. On
a line before the call to "${GAMEBINARY}", write "export GALLIUM_DDEBUG=800".
You can probably also set this environment variable before running Steam.
Thank you Paulo for your suggestion, I will try that if I have time to see if
it affects the frequency of the crashes.
The commit I tested with was 55365a7ad50c2e4547f58995a8e3411d8f2b00a2
--
You are receiving this mail because:
You are the assignee for the bug.
--1450431953.c1A42.26849
Date: Fri, 18 Dec 2015 09:45:53 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Comment # 65
on bug 80419
from David Beswick
Hello everyone,
Just to keep you up to date, I switched tack and have been using the
"GALLIUM_DDEBUG" environment variable to try and capture data about the crash.
I found out about this option via a Google search. As I understand it, it
creates fences around each GPU operation to detect when and if they complete,
dumping the contents of the draw call if it doesn't finish in a timely way.
Unfortunately, I haven't been able to reproduce the crash with this variable
enabled, despite playing for more than 5 hours (not consecutively.) The
GALLIUM_DDEBUG mode is certainly working as performance is quite severely
impacted. Maybe the way GALLIUM_DDEBUG is implemented unfortunately also
prevents the issue from happening.
All I can say so far is that I suspect the problem is related to vertex buffer
drawing. On one occasion I disabled the fences around vertex buffer drawing
while enabling GALLIUM_DDEBUG (to try and get some more performance) and I did
experience a hard lock as usual. I will continue running in this mode to see if
it turns up a result.
If anyone else would like to try, you can modify the
"~/.steam/steamapps/common/XCom-Enemy-Unknown/binaries/linux/xcom.sh" file. On
a line before the call to "${GAMEBINARY}", write "export GALLIUM_DDEBUG=800".
You can probably also set this environment variable before running Steam.
Thank you Paulo for your suggestion, I will try that if I have time to see if
it affects the frequency of the crashes.
The commit I tested with was 55365a7ad50c2e4547f58995a8e3411d8f2b00a2
You are receiving this mail because:
- You are the assignee for the bug.
--1450431953.c1A42.26849--
--===============1789906884==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0
cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK
--===============1789906884==--