<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:iive@yahoo.com" title="iive@yahoo.com">iive@yahoo.com</a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - PoE: GPU hang with mesa >= 17.2.0 + gallium-nine"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103246">bug 103246</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Keywords</td>
<td>
</td>
<td>regression
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - PoE: GPU hang with mesa >= 17.2.0 + gallium-nine"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103246#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - PoE: GPU hang with mesa >= 17.2.0 + gallium-nine"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103246">bug 103246</a>
from <span class="vcard"><a class="email" href="mailto:iive@yahoo.com" title="iive@yahoo.com">iive@yahoo.com</a>
</span></b>
<pre>The symptoms are typical for shader infinite loop, followed by botched driver
restart. Definitely not Wine fault.
Does the bug still happen with current mesa3d+llvm?
While the game is free, it would still be good idea if you can create an
apitrace recording of a place where the game crashes. Ask in #d3d9 at
irc.freenode about the ftp access, or use google drive or similar file sharing.
(We might use the trace for regression testing in future).
It might be good idea if you also fill bugreport to the github Ixit/Mesa-3D
issue tracker.
I usually place the apitrace wrapper d3d9.dll inside the game directory (main
or where game.exe is). Then using `winecfg` add library override for "d3d9" to
be "native, built-in".
If everything goes well, the wrapper would create a new trace inside the game
directory every time the game is started. So don't forget to remove it when you
are done.
Naturally, use working mesa3d version for the trace. Then install new version
of mesa and check if the trace crashes.
If you can compile mesa3d on your own, you might be able to help narrow down
the problem further. I cannot do that, since my card is using the R600 driver,
so it is very unlikely to have the same shader miscompilation.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>