https://bugs.freedesktop.org/show_bug.cgi?id=103900
Bug ID: 103900 Summary: [SUMO][TURKS] Launching War Thunder make GPU stuck, and then system is hard lockup Product: Mesa Version: 17.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel@lists.freedesktop.org Reporter: russianneuromancer@ya.ru QA Contact: dri-devel@lists.freedesktop.org
Hello!
Launching War Thunder make GPU stuck, and then system is hard lockup. This issue is starting to happen after upgrade from Mesa 17.2.2 with libdrm 2.4.83 to 17.3.0rc4 with libdrm 2.4.85 (from Padoka Stable PPA https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa ) on Kubuntu 17.10 x86_64. As soon as I rollback to Mesa 17.2.2 and libdrm 2.4.83, GPU lockup is no longer reproducible, but then there is another issue: bug 100387
Issue is reproducible on both of iGPU and dGPU. Please look into attached log.
Hardware: Acer Aspire 7560G, AMD A8-3500M AMD Radeon HD 6620G iGPU, AMD Radeon HD 6650M dGPU.
Software: Kubuntu 17.10 x86_64, Linux 4.14.1. radeon DDX and modesetting DDX was tested, no difference.
https://bugs.freedesktop.org/show_bug.cgi?id=103900
--- Comment #1 from russianneuromancer@ya.ru --- Created attachment 135708 --> https://bugs.freedesktop.org/attachment.cgi?id=135708&action=edit GPU lockup dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=103900
--- Comment #2 from aceman acelists@atlas.sk --- 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.
https://bugs.freedesktop.org/show_bug.cgi?id=103900
--- Comment #3 from rene@tehno.ee --- After turning off shader optimization with R600_DEBUG=nosb War Thunder works and doesn't crash.
https://bugs.freedesktop.org/show_bug.cgi?id=103900
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO
--- Comment #4 from mirh mirh@protonmail.ch --- 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?
https://bugs.freedesktop.org/show_bug.cgi?id=103900
--- Comment #5 from Syfer Polski syferpl@gmail.com --- Based on https://forum.warthunder.com/index.php?/topic/422637-game-crashes-before-goi..., 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.
https://bugs.freedesktop.org/show_bug.cgi?id=103900
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |MOVED
--- Comment #6 from GitLab Migration User gitlab-migration@fdo.invalid --- -- 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.
dri-devel@lists.freedesktop.org