Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: X doesn't work anymore



On Fri, Jul 10, 2009 at 11:48:56PM +0200, Kurt Schreiner wrote:
> That worked 'till ~ mid June - at least that was the last time I tried.
> 
> /var/log/messages.1.gz:Jun 19 22:02:26 ipaddi /netbsd: radeondrm0 at vga0: 
> ATI FireGL M24 GL (unit 0)
[...]

> > Where does the Xserver spin?
> Doing an ioctl on /dev/dri/card0:
> 
>    571      1 Xorg     CALL  ioctl(0xb,_IO('d',0x44),0)
>    571      1 Xorg     RET   ioctl -1 errno 16 Device busy
>    571      1 Xorg     CALL  ioctl(0xb,_IO('d',0x44),0)
>    571      1 Xorg     RET   ioctl -1 errno 16 Device busy
[...]
> 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).

> There's no "radeondrm0: interrupting at ioapic0 pin 16" as in the
> working case above...

I think that's because the X server hasn't made it far enough to ask for
the IRQ handler to be installed / enabled... I think it gets wedged pretty
early in the DRM initialization.

--rafal

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


Home | Main Index | Thread Index | Old Index