<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - screen corruption using SNA and TearFree on Intel GeminiLake"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105720#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - screen corruption using SNA and TearFree on Intel GeminiLake"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105720">bug 105720</a>
from <span class="vcard"><a class="email" href="mailto:clinton.a.taylor@intel.com" title="Clinton Taylor <clinton.a.taylor@intel.com>"> <span class="fn">Clinton Taylor</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=105720#c20">comment #20</a>)
<span class="quote">> Based on Martin's AccelMethod=none logs, we found this:
>
> commit 7418d53c589719f71154c5ec58a2b7c486020587 (HEAD, upstream/master)
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Wed Mar 28 19:38:51 2018 +0100
>
> sna/dri2: Clip application of damage to windowed swapbuffers
>
> Since forever we have been passing region=NULL when doing a windowed
> swapbuffer on vblank, and using that to mark the entire pixmap as being
> damaged. For an uncomposited window, this is incorrect as it points to a
> clipped region of the ScreenPixmap and so we were marking the entire
> ScreenPixmap as being flushed, but only having operated on the windowed
> region. Instead pass along the clip extents if region is unset.
>
> References: <a class="bz_bug_link
bz_status_NEW "
title="NEW - screen corruption using SNA and TearFree on Intel GeminiLake"
href="show_bug.cgi?id=105720">https://bugs.freedesktop.org/show_bug.cgi?id=105720</a>
> Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
>
> It definitely impacts AccelMethod=none and seems to improve AccelMethod=sna
> as well, but I haven't been able to explain why.</span >
This patch does not fix the issue. Issue is still seen on GLK and BXT
platforms.
There are times that the original issue is not seen for over an hour.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>