r128 driver problem with FC5

[Adam Jackson]

On Friday 16 June 2006 12:50, Nigel Henry wrote:
> (WW) ****INVALID IO ALLOCATION**** b: 0x9000 e: 0x90ff correcting
> Requesting insufficient memory window!: start: 0x9000 end: 0x90ff size
> 0xf0120100
> Requesting insufficient memory window!: start: 0x9400 end: 0x94ff size
> 0xf0120100
> Requesting insufficient memory window!: start: 0x9800 end: 0x98ff size
> 0xf0120100
> Requesting insufficient memory window!: start: 0x9c00 end: 0x9cff size
> 0xf0120100
> (EE) Cannot find a replacement memory range

These look pretty off.  Can you give more complete log output than this?  It 
looks like your log is being redirected to /dev/null, but if you start X by 
hand by just saying "/usr/bin/Xorg :0" you should get a more complete log 
in /var/log/Xorg.0.log

> Backtrace:
> 0: /usr/bin/Xorg(xf86SigHandler+0x87) [0x80b86c7]
> 1: [0x472420]
> 2: /usr/lib/xorg/modules/drivers/r128_drv.so(R128FreeScreen+0x2b)
> [0x13ea9b] 3: /usr/bin/Xorg(xf86DeleteScreen+0x5e) [0x80c50ee]
> 4: /usr/bin/Xorg(InitOutput+0x9e4) [0x80a2364]
> 5: /usr/bin/Xorg(main+0x276) [0x806ffc6]
> 6: /lib/libc.so.6(__libc_start_main+0xdc) [0x4a5724]
> 7: /usr/bin/Xorg(FontFileCompleteXLFD+0xb1) [0x806f511]

It looks like it's refusing to believe in the Rage128 device, and then going 
through a cleanup path with a bug.  If you have a second machine, you can 
debug this better.  On the machine with the rage128, install the 
xorg-x11-drv-ati-debuginfo and xorg-x11-server-debuginfo packages, and then 
ssh in from the other machine, start gdb as root, type 'run :0', and catch 
the backtrace when it segfaults.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20060619/89765bab/attachment.pgp>