From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Re: [drm:r100_ring_test] *ERROR* radeon: ring test
	failed
Date: Tue, 27 Oct 2009 15:41:14 -0400
Message-ID: <20091027194114.GA15333@phenom.dumpdata.com>
References: <20091012200248.GA16486@phenom.dumpdata.com>
	<20091014211415.GQ1434@reaktio.net>
	<20091015200409.GD11348@phenom.dumpdata.com>
	<20091016090159.GI1434@reaktio.net>
	<20091020165805.GA12035@phenom.dumpdata.com>
	<20091021115434.GF1434@reaktio.net>
	<20091021183130.GA11691@phenom.dumpdata.com>
	<20091027154651.GI1434@reaktio.net>
	<20091027170019.GA5961@phenom.dumpdata.com>
	<20091027194539.GP1434@reaktio.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <20091027194539.GP1434@reaktio.net>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, Xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

> > We can figure this out.  Pasi, I don't have a modesetting working machine,
> > but you do. Can you compile your pv_ops with the fix I provided earlier,
> > along with enabling CONFIG_DMA_API_DEBUG=y. Once mode-setting is turned
> > on and your machine is humming along (maybe even run glxgears), compile
> > the attached module and load it. You should get a kernel dump
> > off all devices that are using the DMA buffers. Can you e-mail me that back
> > please?
> > 
> > 
> 
> I've never actually tried X on this box.. it seems X doesn't start.

As in, even on baremetal it does not work?
> 
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/radeondebug/dmesg-2.6.31.4-2009-10-27.txt
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/radeondebug/Xorg.0.log-2009-10-27

This is weird. The EDID reporting seems to be stuck in a endless loop:

(II) RADEON(0): EDID for output DVI-0
(II) RADEON(0): EDID for output VGA-0
...
(II) RADEON(0): EDID for output DVI-0
(II) RADEON(0): EDID for output VGA-0
..
and then last one where it is cut off (probably when you rebooted the box?)