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: Fri, 26 Jul 2013 14:44:17 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0166321968==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id BB1CFE72A1 for ; Fri, 26 Jul 2013 07:44:17 -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 --===============0166321968== Content-Type: multipart/alternative; boundary="1374849857.AdBe0A4B0.12921"; charset="us-ascii" --1374849857.AdBe0A4B0.12921 Date: Fri, 26 Jul 2013 14:44:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=67276 --- Comment #13 from Joshua Cov. --- (In reply to comment #12) > (In reply to comment #11) > > The bug still appears, so this is not the faulty patch. Obviously it happens > > during cold boot, otherwise I haven't seen it. > > > > Can you help me to debug this? > > > > I have to say I haven't seen this with kernel-3.9 and all UVD and DPM staff > > applied. It worked there flawlessly. > > Bisect? I cannot forcibly trigger the problem. That's why I'm hoping for more detailed debug messages. Maybe something connected with ring-testing or maybe data feeding for those rings or anything that hs to do with the ring. I'm also wondering why the problem don't appear when I restart the pc? Is it some kind of a racing condition? How can I get the info that's in the ring at the time the error occurs? How is the ring testing done? -- You are receiving this mail because: You are the assignee for the bug. --1374849857.AdBe0A4B0.12921 Date: Fri, 26 Jul 2013 14:44:17 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 13 on bug 67276 from 
(In reply to comment #12)
> (In reply to comment #11)
> > The bug still appears, so this is not the faulty patch. Obviously it happens
> > during cold boot, otherwise I haven't seen it.
> > 
> > Can you help me to debug this?
> > 
> > I have to say I haven't seen this with kernel-3.9 and all UVD and DPM staff
> > applied. It worked there flawlessly.
> 
> Bisect?

I cannot forcibly trigger the problem. That's why I'm hoping for more detailed
debug messages. Maybe something connected with ring-testing or maybe data
feeding for those rings or anything that hs to do with the ring.

I'm also wondering why the problem don't appear when I restart the pc? Is it
some kind of a racing condition? How can I get the info that's in the ring at
the time the error occurs? How is the ring testing done?

You are receiving this mail because:
  • You are the assignee for the bug.
--1374849857.AdBe0A4B0.12921-- --===============0166321968== 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 --===============0166321968==--