On Mon, Oct 07, 2002 at 02:16:17PM -0500, Branden Robinson wrote: > Those are some pretty aggressive options you've got going there. The > fbdev layer plus PCI retries plus AGPMode 4. I wouldn't be surprised if > you'd get more stability by backing off on some of those. However, a > bug's a bug. > > Welcome to the new, improved for XFree86 4.2 SEGV club; I need you to do > the following: > > 1) apt-get install xserver-xfree86-dbg gdb; > 2) Run the XFree86-debug server in an environment where the coredumpsize > is unlimited; > 3) gdb /usr/X11R6/bin/XFree86-debug core; > 4) Type "bt full" at the gdb prompt; > 5) Send this bug the output.
Further investigation has revealed that there is no SEGV occurring -- the Xserver process goes into a tight loop and eats 99% CPU. The console appears completely dead, but I can sometimes log in remotely over the network and run processes etc. I've also discovered that Changing Option "UseFBDev" "true" to Option "UseFBDev" "false" fixes the problem. This change to /etc/X11/XF86Config-4 also gets rid of the warning "DRIUnlock called when not locked" in the X log. Worth passing on to upstream I guess. cheers, Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
