Re: R200 lockup (was Re: DRI/X error resolution)

[Dave Jones]

On Fri, Sep 22, 2006 at 03:29:48PM +1000, Dave Airlie wrote:
 > On 9/22/06, Ryan Richter <ryan@xxxxxxxxxxxxxxxxxxxxx> wrote:
 > > On Thu, Sep 21, 2006 at 11:54:01PM -0500, Stephen Olander Waters wrote:
 > > > 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. :)
 > 
 > I really think this more AGP related a bug in the driver for the VIA
 > AGP chipsets what AGP chipset are you guys using?

Looking at that bug though, most of the reporters are on AMD64 systems,
which uses amd64-agp, not via-agp. (We leave the chipset GART alone,
and just use the on-CPU one).

This..

agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: X tried to set rate=x12. Setting to AGP3 x8 mode.
agpgart: X requested AGPx8 but bridge not capable.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode

should be fixed in recent Xorg/kernels.  There is a v3 8x->4x
fallback failure that some people trigger, but that manifests itself
in other ways with different messages (where it tries to fall
back to 0x mode, and madness ensues), there's a fix for that
in Andrews -mm tree that should be going to Linus RSN.

Other than that, I'm unaware of any outstanding nasties in the
AGP drivers. I'm not really sure what to suggest for further
debugging.

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