<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - `DRI_PRIME=1 glxgears -info` halts the system with Intel Graphics [8086:5917] + AMD Graphics [1002:6665]."
href="https://bugs.freedesktop.org/show_bug.cgi?id=103370#c27">Comment # 27</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - `DRI_PRIME=1 glxgears -info` halts the system with Intel Graphics [8086:5917] + AMD Graphics [1002:6665]."
href="https://bugs.freedesktop.org/show_bug.cgi?id=103370">bug 103370</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>Thanks for bisecting, but I don't think that commit can be directly responsible
for a GPU hang. Before that commit, the DRI3 code in Mesa would only use one
back buffer for glxgears, which means that the GPU could only start rendering a
new frame after the previous one had finished presenting. Maybe that somehow
prevented the hang.
A possible test for this theory is running
vblank_mode=0 DRI_PRIME=1 glxgears
with Mesa 12.0.3; does that also trigger the hang?</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>