<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c8">Comment # 8</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 <a class="email" href="mailto:joshuacov@gmail.com" title="Joshua Cov. <joshuacov@gmail.com>"> Joshua Cov.</a> <pre>(In reply to <a href="show_bug.cgi?id=67276#c7">comment #7</a>) > (In reply to <a href="show_bug.cgi?id=67276#c5">comment #5</a>) > > > > Can this commit be the culprit of the problem? > > Yes, it could be. As I said, it was a fix for the new reservation code > which it sounds like you didn't pull in. 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>