<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Assert in nouveau_pushbuf_data"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91632#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Assert in nouveau_pushbuf_data"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91632">bug 91632</a>
from <span class="vcard"><a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> <span class="fn">Ilia Mirkin</span></a>
</span></b>
<pre>(In reply to Allan Sandfeld from <a href="show_bug.cgi?id=91632#c2">comment #2</a>)
<span class="quote">> The original qtwebengine bug is at
> <a href="https://bugreports.qt.io/browse/QTBUG-41242">https://bugreports.qt.io/browse/QTBUG-41242</a>
>
> One interesting thing I discovered was that using the EGL/GLES mode instead
> of GLX/GL solved the issue. I assume at your level it shouldn't be that
> different. So it could be a difference in how EGL vs GLX acts.</span >
The issue was happening for me with Unigine Heaven run with DRI3 + DRI_PRIME=1.
Then I started running it with vblank_mode=0 and all my problems disappeared. I
haven't checked whether removing vblank_mode=0 would cause the issues to
reappear. I was happy to blame it on the DRI3 boogeyman and moved on (I tend
not to have a good grasp on these types of issues in the first place...
normally I wouldn't touch DRI3 but it really makes nouveau dev quite a bit
easier with a primary non-nvidia adapter since I can load/unload nouveau/nvidia
at will and still have things display on my regular screen).
Not sure how vsync would cause the problems, but I was getting actual shader
traps reported in dmesg. Do you (or whoever is having the issue) have that as
well?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>