Summary: | [SUMO][TURKS] Launching War Thunder make GPU stuck, and then system is hard lockup | ||
---|---|---|---|
Product: | Mesa | Reporter: | russianneuromancer |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 17.3 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | GPU lockup dmesg |
Description
russianneuromancer
2017-11-25 07:41:47 UTC
Created attachment 135708 [details]
GPU lockup dmesg
Yes I can confirm this on Radeon HD 4350. Even the game itself shows a dialog about hangup, but then the GPU is hung for a while. I think it restarts eventually and takes down the X server (and KDE session). But then I can normally login to KDE again. After turning off shader optimization with R600_DEBUG=nosb War Thunder works and doesn't crash. There was quite of an improvement in sb, in the last couple of mesa releases (even though bug 105371 would make me hesitant to say now it's 100% fixed) Does war thunder work then in 18.3? Based on https://forum.warthunder.com/index.php?/topic/422637-game-crashes-before-going-into-hangar/&do=findComment&comment=8058647, I seems like this bug hasn't been fixed(although the user in question didn't supply their version of Mesa). A user in the linked source supplied the following system specifications: Dell Precision M4600 Ubuntu 18.04.2 i7 2720QM CPU @ 2.20GHz x 8 32GB RAM GPU AMD Turks (FirePro M5950) The default version of Mesa in Ubuntu 18.04 is 18.0.0rc5. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/619. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.