Subject: Re: R200 lockup (was Re: DRI/X error resolution)
From: Stephen Olander Waters <swaters@luy.info>
To: Ryan Richter <ryan@tau.solarneutrino.net>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
In-Reply-To: <20060922043801.GE16939@tau.solarneutrino.net>
References: <1158898988.3280.8.camel@ix>
	 <20060922043801.GE16939@tau.solarneutrino.net>
Content-Type: text/plain
Date: Thu, 21 Sep 2006 23:54:01 -0500
Message-Id: <1158900841.3280.12.camel@ix>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1095
Lines: 32

On Fri, 2006-09-22 at 00:38 -0400, Ryan Richter wrote:
> On Thu, Sep 21, 2006 at 11:23:08PM -0500, Stephen Olander Waters wrote:
> > Hey,
> > 
> > Did they ever fix that bug you reported here?
> > http://lkml.org/lkml/2005/5/11/121
> > 
> > I'm having the same problem! Argh!
> 
> No, sad to say it still happens to us too.  Argh is right!
> 
> I'll cc this to dri-devel and lkml in case anyone wants to try hunting
> the bug again.
> 
> FWIW, I'm still seeing the ioctl(5, 0x6444, 0) / SIGALARM behavior I
> reported originally.  This has continued to happen regularly with all
> 2.6 kernels up to 2.6.17.6 and Xfree/X.org up to 6.9.

Here is the bug I'm working from (includes hardware, software, etc.):
https://bugs.freedesktop.org/show_bug.cgi?id=6111

DRI will work if you set: Option "BusType" "PCI" ... but that's not a
real solution. :)

-s


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/