<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - kernel-3.11 [drm:r600_uvd_ring_test] *ERROR* radeon: ring 5 test failed (0xCAFEDEAD)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67276#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - kernel-3.11 [drm:r600_uvd_ring_test] *ERROR* radeon: ring 5 test failed (0xCAFEDEAD)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67276">bug 67276</a>
from <span class="vcard"><a class="email" href="mailto:agd5f@yahoo.com" title="Alex Deucher <agd5f@yahoo.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=67276#c8">comment #8</a>)
<span class="quote">> I'll take a look later if I can backport the reservation code back to 3.10
> (if it's worth). I see some commits (280cf2118675..8f262540e61c7, or
> especially ecff665f5e in git://people.freedesktop.org/~airlied/linux
> drm-next) but I think it's easier to just remove commit
> 1b6e5fd5f4fc152064f4f71cea0bcfeb49e29b8b from your patchset and see if the
> problem still occurs in the next 3-4 days.</span >
Probably easiest to just drop the patch. The new reservation code doesn't
provide any advantages at this point.</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>