<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [965g] batch corruption, clflush?"
href="https://bugs.freedesktop.org/show_bug.cgi?id=61477#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [965g] batch corruption, clflush?"
href="https://bugs.freedesktop.org/show_bug.cgi?id=61477">bug 61477</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=61477#c9">comment #9</a>)
<span class="quote">> The only interesting thing I've find is the pattern of 0x0040a0c0 in the
> batch. It repeats with a stride divisible by 128 and hits every odd dword.
> Vertical light blue lines in a y-tiled picture? Unfortunately no active
> y-tiled bo we could blame this on.</span >
Yup, but the repeating data is not pixel data, looks more like contents from a
stale batch. And I can easily convince myself that each time it is just once
cacheline worth of bad data.
(In reply to <a href="show_bug.cgi?id=61477#c14">comment #14</a>)
<span class="quote">> Okay, I bisected xf86-video-intel (for the corruption of window borders),
> with the result:
>
> ab01fd696e1137ddfb9a85ae68c15c05900f0e8e is the first bad commit
> commit ab01fd696e1137ddfb9a85ae68c15c05900f0e8e
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Sat Jan 12 09:17:03 2013 +0000
>
> sna: Experiment with a CPU mapping for certain fallbacks</span >
That ties right in with the theory that coherency on 965g is hosed in certain
situations - as I already know snooping is broken and this could just a very
similar effect.</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>