On Dienstag 02 Juni 2009, Mick wrote: > 2009/6/2 Volker Armin Hemmann <volkerar...@googlemail.com>: > > On Dienstag 02 Juni 2009, Mick wrote: > >> This what I am currently running: > >> > >> x11-base/xorg-server-1.5.3-r6 > >> > >> x11-base/xorg-x11-7.2 > >> > >> Is there anything I can do to fix this? > > > > for starters, more informations. Driver versions used. Xorg.0.log before > > crash, maybe dmesg before crash (you know, for hardware stuff), does the > > crash happen with an unpatched kernel too? etc pp. > > I am running the following drivers: > > x11-drivers/xf86-input-evdev-2.1.3 (hal -debug) > x11-drivers/xf86-input-keyboard-1.3.2 (-debug) > x11-drivers/xf86-input-mouse-1.4.0 (-debug) > x11-drivers/xf86-input-synaptics-1.0.0 (hal -debug) > x11-drivers/xf86-video-ati-6.12.1-r1 (-debug)
> > Also, these are my mtrr settings in the kernel (not sure if they are > correct): > > CONFIG_MTRR=y > CONFIG_MTRR_SANITIZER=y > CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 > CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=4 > they are ok - I would reduce spare nr default to '1' because that is all that is needed. But they should not cause a crash. > I am not sure I understand the question about unpatching the kernel - > do you mean vanilla upstream kernel? (I've always used > gentoo-sources). yes, I mean that. Try the vanilla upstream kernel - because if you hit the crash with vanilla kernel, you can start pestering lkml and/or dri-devel and/or radeon devs mailing list. As long as you are using the patched kernel it is a gentoo problem. If you hit it with vanilla too it is a more global linux problem ;)