<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - DiRT Rally: wrong frames appear during camera transition"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105179#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - DiRT Rally: wrong frames appear during camera transition"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105179">bug 105179</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 Gregor Münch from <a href="show_bug.cgi?id=105179#c0">comment #0</a>)
<span class="quote">> <a href="https://lists.freedesktop.org/archives/mesa-dev/2018-February/185134.html">https://lists.freedesktop.org/archives/mesa-dev/2018-February/185134.html</a>
>
> "except I got a few ltc errors in DiRT
> Rally. Unclear if it's related to this patch though. Could be a missing
> flush somewhere."
>
> ..I think it is a general mesa issue, except Im wrong here.</span >
This is a nouveau-specific problem, in fact, Maxwell+ only. LTC = level-two
cache. Something specific to NVIDIA hw (other GPUs have it too, but it's always
different and controlled by the hw or driver directly - not something that's
API-accessible, or even generic across drivers).
Also note that the errors only happened when I force-enabled bindless textures
in DiRT Rally (via a config option), which is the feature that the patch was
implementing. The "missing flush" is in reference to something missing inside
of nouveau wrt texture management. There's ample evidence that there's
something off somewhere in there.
In any case, those ills are in no way related to radeonsi or any other driver.</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>