Bug#419986: server lockups related to dri
Olaf Till wrote:
> (On request of Brice I resubmit this as an extra bug and do not
> include 'xorg.conf' since it does not enable anything except
> "UseFBDev". Rest of report is slightly changed.)
>
Thanks a lot!
> - Commenting out "dri" in the "Module" section of "xorg.conf" fixes
> the problem. Including:
>
> Section "DRI"
> Mode 0666
> EndSection
>
This DRI section only changes the access rights of /dev/dri/card* files
to allow all users to use DRI. Removing load dri from the module section
is enough.
> - During lockup, system still responds to 'ping' via ethernet, and
> still performs background jobs.
>
Logging by ssh and attaching a gdb as I said in the other mail should
help us know what the server is doing then.
> (II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
> dlopen: /usr/lib/xorg/modules/extensions/libGLcore.so: undefined symbol: _glapi_Dispatch
> (EE) Failed to load /usr/lib/xorg/modules/extensions/libGLcore.so
> (II) UnloadModule: "GLcore"
> (EE) Failed to load module "GLcore" (loader failed, 7)
>
Harmless, but you don't need to load GLcore explicitely in the module
section. The server load GLcore automatically later when it needs it.
> (II) LoadModule: "speedo"
> (WW) Warning, couldn't open module speedo
> (II) UnloadModule: "speedo"
> (EE) Failed to load module "speedo" (module does not exist, 0)
>
You can drop the speedo line from your module section.
> (**) RADEON(0): Option "UseFBDev" "true"
> (II) Loading sub module "vgahw"
> (II) LoadModule: "vgahw"
> (II) Loading /usr/lib/xorg/modules/libvgahw.so
> (II) Module vgahw: vendor="X.Org Foundation"
> compiled for 7.1.1, module version = 0.1.0
> ABI class: X.Org Video Driver, version 1.0
> (II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
> (==) RADEON(0): RGB weight 888
> (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
> (++) RADEON(0): "-dpi 100" given in command line, assuming "ConstantDPI" set
> (++) RADEON(0): X server will keep DPI constant for all screen sizes
> (II) Loading sub module "fbdevhw"
> (II) LoadModule: "fbdevhw"
> (II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so
> (II) Module fbdevhw: vendor="X.Org Foundation"
> compiled for 7.1.1, module version = 0.0.2
> ABI class: X.Org Video Driver, version 1.0
> (WW) open /dev/fb0: No such file or directory
> (WW) open /dev/fb1: No such file or directory
> (WW) open /dev/fb2: No such file or directory
> (WW) open /dev/fb3: No such file or directory
> (WW) open /dev/fb4: No such file or directory
> (WW) open /dev/fb5: No such file or directory
> (WW) open /dev/fb6: No such file or directory
> (WW) open /dev/fb7: No such file or directory
> (EE) Unable to find a valid framebuffer device
> (EE) RADEON(0): Failed to open framebuffer device, consult warnings and/or errors above for possible reasons
> (you may have to look at the server log to see warnings)
> (WW) RADEON(0): fbdevHWInit failed, not using framebuffer device
>
Please remove the usefbdev option... in case its failure to start breaks
something.
> Personally I do not need dri. I do not think I can try out
> experimental xserver-xorg-core 2:1.2.99.905-3, since it would require
> a libc6 upgrade. xserver-xorg-core-dbg does not seem to be present in
> stable.
>
You can grab an earlier xserver-xorg-core from
http://snapshot.debian.net/archive/2007/04/10/debian/pool/main/x/xorg-server/
It does not depend on libc6 2.5.
xserver-xorg-core-dbg is built since 1.2.99.905-2, so it's available
there too.
Brice
Reply to: