| Bug ID | 103246 |
|---|---|
| Summary | PoE: GPU hang with mesa >= 17.2.0 + gallium-nine |
| Product | Mesa |
| Version | 17.2 |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | major |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | kmk3.bugs@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 134818 [details] Related packages info General system info: System information: Wine build: wine-2.18 (Staging) Platform: i386 Version: Windows 7 Host system: Linux Host version: 4.13.5-1-MANJARO GPU: R9 280X (GCN 1.0) GPU driver: xf86-video-ati 1:7.10.0-1 (radeonsi) DE: plasma-desktop 5.10.5-1 Game info: https://appdb.winehq.org/objectManager.php?sClass=version&iId=30942 Game version: 3.0.1e (Steam) # Overview So, when using mesa 17.2+ with wine-staging-nine, the whole system crashes when entering certain areas on PoE. After trying to enter my Hideout in the game, the loading screen appears for a few seconds (as usual), then a sound loop occurs for about 3 seconds, then silence and the whole system is completely unresponsive. The keyboard does not work and the monitor has no video output (blue screen). Then, I just hard-reset the system. Also, a few days ago, the game somehow crashed without bringing the whole system down, it just showed a "game crashed" dialog box. # Game-specific info I tried to enter the affected areas from Highgate (Act 9), which seems to have no major issues after wandering around a bit. So far, it seems to crash on Sarn and the personal Hideout. The only similarity that I can think of is the presence of Vagan and Vorici in both areas. But, AFAIK, it seems unlikely that characters textures would cause a GPU hang. # Rambling It is the exact same symptom (including the sound loop) that occured on my 6770m with Linux 3.13+, when I tried to run "startx" without setting "radeon.dpm=0". # Debug The whole screen, including the terminal wine is launched from freezes, so I'm unable to see if wine printed anything during/after the crash. I tried setting MESA_DEBUG=1 and MESA_LOG_FILE, but nothing is ever written to the log file (it is not even created). I'm not sure if it is because everything really hangs, no mesa errors actually occur or if I need to compile it with debug flags. In the case of the latter, should I just follow this guide? https://wiki.ixit.cz/d3d9_debugging Also, I'm not really sure whether the problem is on mesa or gallium-nine. If you know how to debug this, please leave a comment. # Packages After testing with different packages, the problem occurs only with wine-staging-nine. Tested on wine-staging-nine 2.16+ (2.16-2.18) and mesa 17.2.0+ (17.2.0-17.2.2). Mesa < 17.2.0 has no problems with wine, wine-staging nor wine-staging-nine. Wine + gallium-nine works well enough with mesa < 17.2.0. Misc: At least on manjaro, mesa 17.1.8 depends on llvm 4.0 and mesa 17.2+ depends on llvm 5.0. Not sure if the version could be related to the issue.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
