| Bug ID | 104490 |
|---|---|
| Summary | [radeonsi/290x] Dota2 fails to start (can't create opengl con= text) |
| 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 [details]<= /a> glxinfo I've been trying to figure out the cause for this bug for quite some time n= ow. Here is the bug ticket on the dota2 github page: https://git= hub.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 direct= ory 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 u= se 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 n= ow 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 wi= ll not fix itself with reboots with commits older than that either...
Forgot to mention: As I stated in the github issue, only dota seems to have this problem. No o= ther program/game fails to create a opengl context for me. So I'm quite unsure w= hy it is just dota2 that has problem now.
(In reply to Sebastian Parborg from comment #0) > [...] there seems to be some kind of cached beha= viour (not the mesa shader > cache as I removed the directory [...] Which directory exactly did you remove? Have you tried setting the environm= ent variable MESA_GLSL_CACHE_DISABLE=3Dtrue to see if that avoids the problem?<= /pre>
| What | Removed | Added |
|---|---|---|
| CC | mike@fireburn.co.uk |
I'm wondering if this has been the issue I've been seeing on B=
ioshock
Will let out an older Mesa when I get home and bisect if that's the case
(In reply to Michel D=C3=A4nzer from comment #2) > (In reply to Sebastian Parborg from comment #0) > > [...] there seems to be some kind of cached behaviour (not the me= sa shader > > cache as I removed the directory [...] >=20 > Which directory exactly did you remove? Have you tried setting the > environment variable MESA_GLSL_CACHE_DISABLE=3Dtrue to see if that avo= ids 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...
I spoke too soon. It seems like I needed to go back a bit furt= her. And with MESA_GLSL_CACHE_DISABLE=3Dtrue, 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=3D0d044351b7043cd0bc94c1cb9b7a2213f8054414 I reverted that one and tried the master branch and now it works. I'm guess= ing that there is some implementation bugs or something as that commit only see= ms to switch on already implemented stuff.
I think this also affects i965 too 6ce9006d76c050663af0be61cc88c3215d6f8cea is the first bad commit=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 commit 6ce9006d76c050663af0be61cc88c3215d6f8cea=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Author: Neil Roberts <neil&#= 64;linux.intel.com>=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Date: Wed Oct 1 20:00:50 2014 +0100=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 i965: Enable flush control=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 Reviewed-by: Adam Jackson <aj= ax@redhat.com>=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Reviewed-by: Nicolai H=C3=A4hnle <nicolai.haehnle@amd.com>=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20 Reviewed-by: Emil Velikov <emil.velikov@collabora.com>=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 Signed-off-by: Neil Roberts <neil@linux.intel.com>
I can confirm reverting both those commits, allows me to launc= h BioShock Infinite on both radeonsi and i965 on master
| What | Removed | Added |
|---|---|---|
| QA Contact | dri-devel@lists.freedesktop.org | mesa-dev@lists.freedesktop.org |
| CC | ajax@nwnk.net | |
| Assignee | dri-devel@lists.freedesktop.org | mesa-dev@lists.freedesktop.org |
| Component | Drivers/Gallium/radeonsi | Mesa core |