| Priority | medium |
|---|---|
| Bug ID | 80419 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | XCOM: Enemy Known Causes lockup |
| Severity | normal |
| Classification | Unclassified |
| OS | Linux (All) |
| Reporter | theamazingjanet@googlemail.com |
| Hardware | x86-64 (AMD64) |
| Status | NEW |
| Version | 10.1 |
| Component | Drivers/Gallium/radeonsi |
| Product | Mesa |
Running the recently released XCOM: Enemy Unknown, after a few minutes of playing the game will lockup the display completely. Mouse movement still shows but nothing is responsive. Occurs for the whole display, evidenced by running the game in windowed mode. Keyboard input is also unresponsive, forcing a hard reset. Ubuntu 14.04 AMD HD7770 2GB Mesa 10.1.3 Only response from Feral on the issue was to use Catalyst.
| What | Removed | Added |
|---|---|---|
| Summary | XCOM: Enemy Known Causes lockup | XCOM: Enemy Unknown Causes lockup |
Please attach /var/log/Xorg.0.log and the output of dmesg and =
glxinfo.
> AMD HD7770 2GB
> Mesa 10.1.3
Which version of LLVM? Might be worth trying Mesa 10.2 or even current Git
master if possible.
Created attachment 101631 [details]
X log
Created attachment 101632 [details]
Dmesg
Created attachment 101633 [details]
glxinfo
> Which version of LLVM? Might be worth trying Mesa 10.2 or even current Git
> master if possible.
I'm using llvm 3.4 (default Ubuntu). Will try Mesa 10.2 as soon as possible.
Tried it with Oibaf PPA, llvm 3.4.2 and Mesa git and the issue is still there. Seemd to lock up even quicker this time.
Any chance you could try an LLVM 3.5 snapshot? Also, if you could log in via ssh and grab dmesg after the problem occurs, = that might be interesting.
I have been playing xcom:enemy within for a few hours on an up-to-date x86_64 fedora rawhide. No lock-up yet, but slow like hell. Tahiti XT.
(In reply to comment #8) > I have been playing xcom:enemy within for a few hours on an up-to-date > x86_64 fedora rawhide. > No lock-up yet, but slow like hell. Tahiti XT. I can reproduce the lockup with mesa 10.2.1 with llvm-3.4.2, mesa-git with llvm-3.5svn and a radeon PITCAIRN/kernel 3.15.1/kernel 3.16rc1 (Archlinux x86_64)
I stand corrected: Got the lockup and crash in the middle of a mission. up-to-date x86_64 fedora rawhide. Tahiti XT.
(In reply to comment #7) > Any chance you could try an LLVM 3.5 snapshot? > > Also, if you could log in via ssh and grab dmesg after the problem occurs, > that might be interesting. I don't have a second machine of my own setup to try it from but I'll see what I can do. For now, Xorg.0.log.old seems to better match up with the time of the error, and shows a mumber of EQ overflow errors that aren't in Xorg.0.log.
Created attachment 101680 [details]
X log.old
(In reply to comment #= 11) > For now, Xorg.0.log.old seems to better match up= with the time of the error, > and shows a mumber of EQ overflow errors that aren't in Xorg.0.log. Those are just symptoms of the GPU hang, they don't say anything about its cause. The corresponding dmesg output should be available in /var/log/kern.log* as well. Also, I wonder if this is reproducible enough to create an apitrace reprodu= cing it?
Created attachment 101844 [details]
Dmesg 2
SSH'd and tried dmesg like you said and attached. I've been trying apitrace but the game depends on Steam and uses a seperate launcher to start the game and can't figure out how to get a proper trace becaue of it. Launching what looks like the game binary directly (game.x86_64) and it still brings up the launcher. Just this morning I was able to play without incident for ~ 1 hour for the first time, then locked up almost immediately in a mission again after restarting.
(In reply to comment #= 15) > SSH'd and tried dmesg like you said and attached= . Thanks, but this doesn't have anything about a GPU lockup or anything like that.
>Thanks, but this doesn't have anything about a GPU lockup or anything like that.
I looked through it and figured as much but attached anyway as maybe I just
wasn't looking for the right thing. It's the output given when the game locked
up the display, so I don't know what else to do besides apitrace.
On steam, you can select the game, right click on it, select p=
roprieties=E2=80=8E ,
launch options and put
apitrace %command%
you can run the game with gdb, strace , etc using this option. it will out=
put
to the console, so start steam in a terminal if you need to see the output<=
/pre>
(In reply to comment #= 18) > On steam, you can select the game, right click o= n it, select proprieties=E2=80=8E , > launch options and put >=20 > apitrace %command% >=20 > you can run the game with gdb, strace , etc using this option. it will > output to the console, so start steam in a terminal if you need to see= the > output Thanks, but the game simply segfaults when I do this: Dumped crashlog to /home/ryan/.local/share/feral-interactive/XCOM/crashes//50524115-5e25-7dad-= 395afa0f-6f10b83e.dmp /home/ryan/.local/share/Steam/SteamApps/common/XCom-Enemy-Unknown/binaries/= linux/xcom.sh: line 39: 9211 Segmentation fault (core dumped) ${DEBUGGER} "${GAMEBINA= RY}" $@ Game removed: AppID 200510 "XCOM: Enemy Unknown", ProcID 9211 Feral have mentioned to me that they're willing to give Mesa/RadeonSI devs Steam keys to help find and fix the issue, I just need to email them (http://steamcommunity.com/app/200510/discussio= ns/0/648811852226640080/#c522730701427327317). If you guys are willing I'll do that.
My name is Edwin Smith and I work for Feral Interactive. We don't support the mesa drivers due to the stability issues compared to the closed source drivers however we can pass on any crash logs and if it helps some complimentary XCOM keys to the members of the driver team to help with the debugging effort. The crash looks like a complete GPU hang that locks up the entire card. If it helps I can look into getting exact instructions on how to attach apitrace to the Steam release.
(In reply to comment #20) > The crash looks like a complete GPU hang that locks up the entire card. If > it helps I can look into getting exact instructions on how to attach > apitrace to the Steam release. That would certainly help. Thanks for taking the time to do this.
To use apitrace on XCOM, follow these instructions:
1. In the Steam client library list, right click the game
2. Select "Properties"
3. Switch to the "GENERAL" tab
4. Press "SET LAUNCH OPTIONS..."
5. Put this in the text box "DEBUGGER="apitrace trace" %command%"
6. Press OK
7. Close the Properties Window
8. Hit Play
9. Select the game to test
10. Find the trace file in the steam library
common/XCom-Enemy-Unknown/game.x86_64.trace or
common/XCom-Enemy-Unknown/xew/game.x86_64.trace depending on
which game was launched.
We've also seen the GPU hang using fglrx, but haven't reproduced a GPU hang
with Intel graphics.