Re: X doesn't work anymore

[Rafal Boni <rafal%pobox.com@localhost>]

On Fri, Jul 10, 2009 at 10:12:06PM -0400, Rafal Boni wrote:
> On Fri, Jul 10, 2009 at 11:48:56PM +0200, Kurt Schreiner wrote:
> > Form /var/log/messages:
> > 
> > Jul 10 23:34:49 ipaddi /netbsd: agp0 at pchb0: can't find internal VGA 
> > device config space
> > Jul 10 23:34:49 ipaddi /netbsd: radeondrm0 at vga0: ATI FireGL M24 GL
> > Jul 10 23:34:49 ipaddi /netbsd: radeondrm0: Initialized radeon 1.29.0 
> > 20080613
> > Jul 10 23:36:14 ipaddi /netbsd: info: [drm] Setting GART location based on 
> > new memory map
> > Jul 10 23:36:14 ipaddi /netbsd: info: [drm] Loading R300 Microcode
> > Jul 10 23:36:14 ipaddi /netbsd: info: [drm] Num pipes: 1
> > Jul 10 23:36:14 ipaddi /netbsd: info: [drm] writeback test failed
> > Jul 10 23:36:14 ipaddi /netbsd: info: [drm] wait idle failed status : 
> > 0x80010140 0x00000000
> > Jul 10 23:36:45 ipaddi /netbsd: info: [drm] wait idle failed status : 
> > 0x80010140 0x00000000
> > Jul 10 23:38:46 ipaddi /netbsd: info: [drm] wait idle failed status : 
> > 0x80010140 0x00000000
> 
> Yeah, I see this too on my X300 M22 after the upgrade to external DRM; I
> suspect it's once again related to scatter-gather stuff, but I haven't
> had the time to look in more detail (certainly before the last changes
> to that code in the old DRM, X + DRM on that card failed in other odd
> ways, though it would "fix" itself if I restarted X after the initial,
> screwed-up session; it would also work just fine w/out DRM).

Interestingly enough, starting at hw.dri.debug output for a few hours
trying this and that, I couldn't figure out what in DRI-land was making
the card so unhappy... and then thought to actually verify if it was the
DRI bits or the X server (I said before I thought a kernel upgrade was
enough to make this fail -- but didn't have notes on what I upgraded
in what order and what I tested at what point).

Long story short, running a 5.99.14 DRM-enabled kernel with a 5.0 user-
land and native (5.0-release) Xorg 1.4.2 works just dandy with DRI on,
so it looks like the failure is caused by something in the new 1.6.xx
X server, new Mesa hardware renderer library for the R300, or something
related.

I'm not sure I feel better or worse about that, though :-/
--rafal

PS: I haven't tried with the latest-and-greatest Xorg 1.6.2, I was
still running a -current userland / native Xorg from ~ 6/23 when I
tripped over this failure.

-- 
  Time is an illusion; lunchtime, doubly so.     |/\/\|           Rafal Boni
                   -- Ford Prefect               |\/\/|      
rafal%pobox.com@localhost