https://bugs.freedesktop.org/show_bug.cgi?id=102962
Bug ID: 102962 Summary: GPU crash running Overwatch in wine-staging Product: Mesa Version: 17.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: tobi291019@gmail.com QA Contact: dri-devel@lists.freedesktop.org
Running Overwatch in wine-staging 2.17 or 2.16 causes frequent GPU crashes, in particular almost always when selecting Symmetra in the Hero Selection screen. As far as I can tell there is no version of wine-staging (including specific commits) that avoid this issue.
Interestingly, a patched version of wine-staging 2.16 and earlier (https://github.com/gamax92/wine-overwatch) does not seem to trigger this at all. (I suspect their removal of some wined3d related patches started to trigger this, whilst the earlier version avoided it.)
No errors are shown on both wine's and mesa's end, although I have not successfully tried a build with -DDEBUG CFLAG, which I could try in case this is helpful.
I have tried working out which of the patches applied by the repository are avoiding the issue, but haven't work out any good leads.
Running on Arch Linux with linux 4.13.3 (Custom compiled with unrelated patches) and mesa 17.2.1. The issue can be reproduced both with the standard wine-staging package on Arch as well as compiling the mentioned patched version.
It might be worthwile to contact the wine developers about this, but their bug reporting guidelines specifically say to not report driver issues there, so I decided to report here first.
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #1 from Józef Kucia joseph.kucia@gmail.com --- This is likely a Wine/wine-staging bug and shouldn't be reported to Mesa. Why do you think it is a driver bug?
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #2 from Tobias Auerochs tobi291019@gmail.com --- As I mentioned, it causes a GPU crash, meaning the entire graphics session freezes, other than mouse cursor, I'm not referring to wine simply crashing.
I'm not familiar with advanced OpenGL (specifically what wine requires to implement d3d11) and if that would ever be allowed to cause a GPU crash at all to begin with.
Also, to my knowledge (although I cannot test this myself currently), this does not seem to happen on other drivers.
This either runs down to the sequence of OpenGL commands issued by wine tripping mesa or wine not implementing d3d11 well enough and emitting invalid OpenGL commands (which just happen to cause a GPU crash instead of a gl error or process crash) to the best of my knowledge.
If you think this is better reported to wine directly, I can close this and open a report there. (Sorry for the inconvenience then)
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #3 from Matt m.mcnutt@gmail.com --- This bug has been going on for me since wine-staging 2.17 and continues in 2.19 released today.
Some particulars of my setup.
Fiji (Fury) card running patched kernel 4.12 with Display Core patches mesa-git - 17.3.0-0.105.git4f42ea4
I'm not sure what we would need to dissect this issue to determine once and for all if it is purely wine's fault or if it is indeed mesa at fault. When it happens the entire graphics system crashes and is unresponsive.
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #4 from sander.smid@gmail.com --- I created a ticket on Wine for the same issue which contains a full log of the wine session.
Relevant Wine Bug Ticket ------------------------ https://bugs.winehq.org/show_bug.cgi?id=44077
System info ----------- * wine-2.21 (Staging) * Linux oribi 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64 GNU/Linux * Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] * Display Server: x11 (X.Org 1.19.5 ) drivers: nvidia (unloaded: modesetting,fbdev,nv,vesa,nouveau) * Resolution: 1920x1200@59.95hz * OpenGL: renderer: AMD Radeon RX 480 Graphics (AMD POLARIS10 / DRM 3.18.0 / 4.13.12-1-ARCH, LLVM 5.0.0) * version: 4.5 Mesa 17.2.5
https://bugs.freedesktop.org/show_bug.cgi?id=102962
sander.smid@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Vdragon.b@gmail.com
--- Comment #5 from sander.smid@gmail.com --- *** Bug 103681 has been marked as a duplicate of this bug. ***
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #6 from sander.smid@gmail.com --- The Wine devs just closed the issue on their bugtracker as NOTOURBUG.
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #7 from sander.smid@gmail.com --- I can look into providing additional information for this issue. However I'm not familiar with the process of debugging or log gathering for GPU crashes. Any information on the subject is welcome.
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #8 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Tobias Auerochs from comment #2)
As I mentioned, it causes a GPU crash, meaning the entire graphics session freezes, other than mouse cursor, I'm not referring to wine simply crashing.
I'm not familiar with advanced OpenGL (specifically what wine requires to implement d3d11) and if that would ever be allowed to cause a GPU crash at all to begin with.
OpenGL applications can cause GPU hangs quite easily.
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #9 from gloriouseggroll@gmail.com --- Created attachment 138466 --> https://bugs.freedesktop.org/attachment.cgi?id=138466&action=edit broken colors with mesa override
This was originally able to be resolved using MESA_GL_VERSION_OVERRIDE=4.0COMPAT, however commit 72de747c6a6cdd0be84a24932a4452f453861dbe broke that functionality, so that MESA-GL_VERSION_OVERRIDE no longer renders properly, at least on my system. See attached.
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #10 from amd_user lutris@tuta.io --- Why does the system freeze when selecting Symmetra in the Hero Selection screen? Is it a mesa bug or wine bug?
linux 4.17.2 amd ryzen 3 mesa 18.1.2 wine-staging 3.10
https://bugs.freedesktop.org/show_bug.cgi?id=102962
Timothy Arceri t_arceri@yahoo.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO
--- Comment #11 from Timothy Arceri t_arceri@yahoo.com.au --- (In reply to gloriouseggroll from comment #9)
Created attachment 138466 [details] broken colors with mesa override
This was originally able to be resolved using MESA_GL_VERSION_OVERRIDE=4.0COMPAT, however commit 72de747c6a6cdd0be84a24932a4452f453861dbe broke that functionality, so that MESA-GL_VERSION_OVERRIDE no longer renders properly, at least on my system. See attached.
radeonsi now has compat 4.4 enabled by default (in git and upcoming 18.2 release). Does the game now work for you with a recent Mesa from git?
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #12 from Tobias Auerochs tobi291019@gmail.com --- (In reply to Timothy Arceri from comment #11)
(In reply to gloriouseggroll from comment #9)
Created attachment 138466 [details] broken colors with mesa override
This was originally able to be resolved using MESA_GL_VERSION_OVERRIDE=4.0COMPAT, however commit 72de747c6a6cdd0be84a24932a4452f453861dbe broke that functionality, so that MESA-GL_VERSION_OVERRIDE no longer renders properly, at least on my system. See attached.
radeonsi now has compat 4.4 enabled by default (in git and upcoming 18.2 release). Does the game now work for you with a recent Mesa from git?
Tried launching the game with mesa-git 103535.88e56804a7 (unofficial Arch repo), rendering in menus (including backgrounds) worked correctly, however the system still hangs the same way as before (e.g. when selecting Symmetra).
Trying MESA_GL_VERSION_OVERRIDE=4.0COMPAT on mesa-git appears to have no effect at all anymore, or any other version for that matter. (With the override it does not freeze on mesa 18.1.4, but graphics glitches occur with it, without the override it renders correctly and freezes as well, just like mesa-git does)
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #13 from Timothy Arceri t_arceri@yahoo.com.au --- (In reply to Tobias Auerochs from comment #12)
(In reply to Timothy Arceri from comment #11)
(In reply to gloriouseggroll from comment #9)
Created attachment 138466 [details] broken colors with mesa override
This was originally able to be resolved using MESA_GL_VERSION_OVERRIDE=4.0COMPAT, however commit 72de747c6a6cdd0be84a24932a4452f453861dbe broke that functionality, so that MESA-GL_VERSION_OVERRIDE no longer renders properly, at least on my system. See attached.
radeonsi now has compat 4.4 enabled by default (in git and upcoming 18.2 release). Does the game now work for you with a recent Mesa from git?
Tried launching the game with mesa-git 103535.88e56804a7 (unofficial Arch repo), rendering in menus (including backgrounds) worked correctly, however the system still hangs the same way as before (e.g. when selecting Symmetra).
Picked the game up as part of Humble bundle, I seem to be able to select Symmetra without any freeze. Is this still happening for you?
https://bugs.freedesktop.org/show_bug.cgi?id=102962
Timothy Arceri t_arceri@yahoo.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo1mc@gmail.com
--- Comment #14 from Timothy Arceri t_arceri@yahoo.com.au --- *** Bug 104475 has been marked as a duplicate of this bug. ***
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #15 from Tobias Auerochs tobi291019@gmail.com --- (In reply to Timothy Arceri from comment #13)
(In reply to Tobias Auerochs from comment #12)
(In reply to Timothy Arceri from comment #11)
(In reply to gloriouseggroll from comment #9)
Created attachment 138466 [details] broken colors with mesa override
This was originally able to be resolved using MESA_GL_VERSION_OVERRIDE=4.0COMPAT, however commit 72de747c6a6cdd0be84a24932a4452f453861dbe broke that functionality, so that MESA-GL_VERSION_OVERRIDE no longer renders properly, at least on my system. See attached.
radeonsi now has compat 4.4 enabled by default (in git and upcoming 18.2 release). Does the game now work for you with a recent Mesa from git?
Tried launching the game with mesa-git 103535.88e56804a7 (unofficial Arch repo), rendering in menus (including backgrounds) worked correctly, however the system still hangs the same way as before (e.g. when selecting Symmetra).
Picked the game up as part of Humble bundle, I seem to be able to select Symmetra without any freeze. Is this still happening for you?
Tested using mesa 18.2.0 (Arch testing repository) without any mesa overrides and still froze (on second attempt selection worked, but right click shot still froze). Specifically I was also using wine-staging 3.15, llvm 6.0.1 and a customized linux 4.18.3 kernel, maybe newer llvm yields better results (have not gotten around to testing that).
Interestingly I am able to run the game perfectly stable when dxvk is installed (and radv), aside from the expected poor-ish performance.
https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #16 from Simon givethistosites@gmail.com --- I have the same issue - I am running ArchLabs with arch repos, recent drivers, lutris installer of Overwatch. When firing D.Vas rockets or certain other sparkly effects, the gpu hangs. This is dmesg of when it happens: https://pastebin.com/VBtc5nxE
My specs are
CPU: A8 2.3ghz quadcore
RAM: 8GB
Video: Radeon R5 M240 with 1gb "dedicated VRAM" AKA southern island "Mullins" GCN1.0
I am currently using the radeon driver, which works fine (actually very well - I have vdpau and most other relevant packages installed, and glxinfo tells me I have OpenGL core profile 4.5 working). I cant get amdgpu or vulkan to work sadly, so this issue makes overwatch unplayable. I use the stock ARCH kernel 4.18
https://bugs.freedesktop.org/show_bug.cgi?id=102962
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEEDINFO |RESOLVED
--- Comment #17 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/1284.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org