<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Corruption with DMA ring on cayman"
href="https://bugs.freedesktop.org/show_bug.cgi?id=60802#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Corruption with DMA ring on cayman"
href="https://bugs.freedesktop.org/show_bug.cgi?id=60802">bug 60802</a>
from <span class="vcard"><a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> <span class="fn">Alexandre Demers</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=60802#c18">comment #18</a>)
<span class="quote">> Ok, just finished bisecting, this is the first commit with the dmesg errors:
>
> e110c98cae0ceae47db6cf26c08707505ce92479 is the first bad commit
> commit e110c98cae0ceae47db6cf26c08707505ce92479
> Author: Alex Deucher <<a href="mailto:alexander.deucher@amd.com">alexander.deucher@amd.com</a>>
> Date: Sun Jan 27 22:13:52 2013 -0500
>
> r600g: don't emit WAIT_UNTIL on cayman/TN (v2)
>
> It shouldn't be needed and older kernels don't support
> it.
>
> v2: Replace with PS partial flush as before.
>
> Fixes:
> <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Launching weston fails with error "radeon 0000:01:00.0: forbidden register 0x00008040 at 558""
href="show_bug.cgi?id=59945">https://bugs.freedesktop.org/show_bug.cgi?id=59945</a>
>
> Signed-off-by: Alex Deucher <<a href="mailto:alexander.deucher@amd.com">alexander.deucher@amd.com</a>>
> Reviewed-by: Marek Olšák <<a href="mailto:maraeo@gmail.com">maraeo@gmail.com</a>>
>
> And if I remember correctly I first noticed it with kernel 3.7.5 or 3.7.6,
> but I thing this was also around the time this mesa commit was pushed so it
> may have nothing to do with this kernel versions.</span >
I ended up with a different commit than yours when bisecting:
325422c49449acdd8df1eb2ca8ed81f7696c38cc is the first bad commit
commit 325422c49449acdd8df1eb2ca8ed81f7696c38cc
It's the one just prior yours and it is also the one identified as being the
culprit of the current bug (<a href="show_bug.cgi?id=60802#c8">comment 8</a>). Could you check a second time?</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>