From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 67276] kernel-3.11 [drm:r600_uvd_ring_test] *ERROR* radeon: ring 5 test failed (0xCAFEDEAD) Date: Thu, 25 Jul 2013 13:54:30 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1553771159==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A1952E5C24 for ; Thu, 25 Jul 2013 06:54:30 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1553771159== Content-Type: multipart/alternative; boundary="1374760470.8De7470.26340"; charset="us-ascii" --1374760470.8De7470.26340 Date: Thu, 25 Jul 2013 13:54:30 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=67276 --- Comment #8 from Joshua Cov. --- (In reply to comment #7) > (In reply to comment #5) > > > > 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. -- You are receiving this mail because: You are the assignee for the bug. --1374760470.8De7470.26340 Date: Thu, 25 Jul 2013 13:54:30 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 8 on bug 67276 from 
(In reply to comment #7)
> (In reply to comment #5)
> > 
> > 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.

You are receiving this mail because:
  • You are the assignee for the bug.
--1374760470.8De7470.26340-- --===============1553771159== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1553771159==--