From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 60802] Corruption with DMA ring on cayman Date: Thu, 21 Feb 2013 06:57:04 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0086863307==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D204CE6073 for ; Wed, 20 Feb 2013 22:57:04 -0800 (PST) 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 --===============0086863307== Content-Type: multipart/alternative; boundary="1361429824.8BCbAb5A0.28138"; charset="us-ascii" --1361429824.8BCbAb5A0.28138 Date: Thu, 21 Feb 2013 06:57:04 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=60802 --- Comment #21 from Jakob Nixdorf --- (In reply to comment #20) > 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 (comment 8). Could you check a second time? I just build 325422c49449acdd8df1eb2ca8ed81f7696c38cc but I can't trigger any dmesg output. What do you use to test for it? -- You are receiving this mail because: You are the assignee for the bug. --1361429824.8BCbAb5A0.28138 Date: Thu, 21 Feb 2013 06:57:04 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 21 on bug 60802 from 
(In reply to comment #20)
> 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 (comment 8). Could you check a second time?

I just build 325422c49449acdd8df1eb2ca8ed81f7696c38cc but I can't trigger any
dmesg output. What do you use to test for it?

You are receiving this mail because:
  • You are the assignee for the bug.
--1361429824.8BCbAb5A0.28138-- --===============0086863307== 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 --===============0086863307==--