https://bugs.freedesktop.org/show_bug.cgi?id=104490
Bug ID: 104490 Summary: [radeonsi/290x] Dota2 fails to start (can't create opengl context) Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: darkdefende@gmail.com QA Contact: dri-devel@lists.freedesktop.org
Created attachment 136546 --> https://bugs.freedesktop.org/attachment.cgi?id=136546&action=edit glxinfo
I've been trying to figure out the cause for this bug for quite some time now. Here is the bug ticket on the dota2 github page: https://github.com/ValveSoftware/Dota-2/issues/1368
Since about one week ago, I have been unable to start dota2 on my machine. This happened after I updated my llvm and mesa git version.
If I downgrade to mesa 17.3.1 it works again (without reboot). But it seems to be really hard to track down the commit that broke it as there seems to be some kind of cached behaviour (not the mesa shader cache as I removed the directory and rebooted several times).
For example I downgraded mesa to a commit from 2017-11-17 and it worked. The next day I tried to figure out the commit that broke it. But I could then use the git master version and it seemed to work fine again.
Then the next day I'm back to the same problem and I downgraded again and now it won't start again even if I use mesa from 11-17 (and rebooted). But 17.3.1 still works if I downgrade to that... (no reboot)
I really do not know how to debug this further as I don't know when I'm on the commit that broke it or not. However it seems to always break if I'm on a commit that is newer than 1-2 weeks (after a reboot that is). However it will not fix itself with reboots with commits older than that either...
https://bugs.freedesktop.org/show_bug.cgi?id=104490
--- Comment #1 from Sebastian Parborg darkdefende@gmail.com --- Forgot to mention: As I stated in the github issue, only dota seems to have this problem. No other program/game fails to create a opengl context for me. So I'm quite unsure why it is just dota2 that has problem now.
https://bugs.freedesktop.org/show_bug.cgi?id=104490
--- Comment #2 from Michel Dänzer michel@daenzer.net --- (In reply to Sebastian Parborg from comment #0)
[...] there seems to be some kind of cached behaviour (not the mesa shader cache as I removed the directory [...]
Which directory exactly did you remove? Have you tried setting the environment variable MESA_GLSL_CACHE_DISABLE=true to see if that avoids the problem?
https://bugs.freedesktop.org/show_bug.cgi?id=104490
Mike Lothian mike@fireburn.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mike@fireburn.co.uk
--- Comment #3 from Mike Lothian mike@fireburn.co.uk --- I'm wondering if this has been the issue I've been seeing on Bioshock
Will let out an older Mesa when I get home and bisect if that's the case
https://bugs.freedesktop.org/show_bug.cgi?id=104490
--- Comment #4 from Sebastian Parborg darkdefende@gmail.com --- (In reply to Michel Dänzer from comment #2)
(In reply to Sebastian Parborg from comment #0)
[...] there seems to be some kind of cached behaviour (not the mesa shader cache as I removed the directory [...]
Which directory exactly did you remove? Have you tried setting the environment variable MESA_GLSL_CACHE_DISABLE=true to see if that avoids the problem?
I removed "~/.cache/mesa_shader_cache". I tried that environment variable now and it doesn't seem to solve it either for me (with mesa from 2017-12-01)...
I really do not know how I should try to bisect this...
https://bugs.freedesktop.org/show_bug.cgi?id=104490
--- Comment #5 from Sebastian Parborg darkdefende@gmail.com --- I spoke too soon. It seems like I needed to go back a bit further. And with MESA_GLSL_CACHE_DISABLE=true, it seems like I could pinpoint the commit.
This is the commit that breaks dota2 for me: https://cgit.freedesktop.org/mesa/mesa/commit/?id=0d044351b7043cd0bc94c1cb9b...
I reverted that one and tried the master branch and now it works. I'm guessing that there is some implementation bugs or something as that commit only seems to switch on already implemented stuff.
https://bugs.freedesktop.org/show_bug.cgi?id=104490
--- Comment #6 from Mike Lothian mike@fireburn.co.uk --- I think this also affects i965 too
6ce9006d76c050663af0be61cc88c3215d6f8cea is the first bad commit commit 6ce9006d76c050663af0be61cc88c3215d6f8cea Author: Neil Roberts neil@linux.intel.com Date: Wed Oct 1 20:00:50 2014 +0100
i965: Enable flush control
Reviewed-by: Adam Jackson ajax@redhat.com Reviewed-by: Nicolai Hähnle nicolai.haehnle@amd.com Reviewed-by: Emil Velikov emil.velikov@collabora.com Reviewed-by: Kenneth Graunke kenneth@whitecape.org Signed-off-by: Neil Roberts neil@linux.intel.com
https://bugs.freedesktop.org/show_bug.cgi?id=104490
--- Comment #7 from Mike Lothian mike@fireburn.co.uk --- I can confirm reverting both those commits, allows me to launch BioShock Infinite on both radeonsi and i965 on master
https://bugs.freedesktop.org/show_bug.cgi?id=104490
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop. |.org |org CC| |ajax@nwnk.net Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop. |.org |org Component|Drivers/Gallium/radeonsi |Mesa core
--- Comment #8 from Michel Dänzer michel@daenzer.net --- Adam, any ideas?
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org