I've just updated to the modular xorg-server 1.0.2-r1. I re-emerged ati-drivers 8.23.7 and rebooted. When /etc/init.d/xdm is issued, I get the following kernel panic: Oops: 0000 [#1] PREEMPT Modules linked in: fglrx ati_agp agpgart snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_ati_ixp snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc ndiswrapper CPU: 0 EIP: 0060:[<c0116f8f>] Tainted: P VLI EFLAGS: 00010086 (2.6.16-gentoo #1) EIP is at __wake_up_common+0xf/0x60 eax: ... ebx: ... ecx: ... edx: ... esi: ... edi: ... ebp: ... esp: ... ds: 007b es: 007b ss: 0068 Process hal-unmount.dev (pid: ..., threadinfo=... task=...) Stack: ... Call Trace: [<...>] __wake_up+... [<...>] ke_irq_handler_wrap+... [fglrx] [<...>] handle_IRQ_event+... [<...>] __do_IRQ+... [<...>] common_interrupt+... [<...>] anon_vma_unlink+... [<...>] unlink_file_vma+... [<...>] free_pgtables+... [<...>] exit_mmap+... [<...>] mmput+... [<...>] do_exit+... [<...>] do_group_exit+... [<...>] sysenter_past_exit+... Code: ... Kernel panic - not syncing: Fatal exception in interrupt Here's my emerge --info: Portage 2.1_pre7-r1 (default-linux/x86/2005.1, gcc-3.4.6, glibc-2.4-r1, 2.6.16-gentoo i686) ================================================================= System uname: 2.6.16-gentoo i686 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.12.0_pre16 dev-lang/python: 2.3.5-r2, 2.4.2-r1 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer -mmmx -m3dnow -msse -msse2 -mfpmath=sse" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer -mmmx -m3dnow -msse -msse2 -mfpmath=sse" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/" LANG="de_DE.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--sort-common" LINGUAS="de" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X a52 aac acpi alsa apache2 apm asf avi berkdb bitmap-fonts bzip2 cdr crypt dri dts dvd dvdr dvdread eds emboss encode esd exif ffmpeg foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 hal imagemagick imlib java jpeg kqemu libg++ libwww mad mikmod mmx mmxext mono motif mozsvg mp3 mpeg ncurses nls nptl nptlonly nsplugin nvidia ogg oggvorbis openal opengl oss pam pcre pdf pdflib perl png postgres python qt quicktime readline real rtc sdl session spell sse sse2 ssl svg tcpd threads tiff truetype truetype-fonts type1-fonts unicode usb userlocales v4l v4l2 vcd vorbis win32codecs x264 xine xml2 xv xvid xvmc zlib elibc_glibc input_devices_evdev input_devices_keyboard input_devices_mouse kernel_linux linguas_de userland_GNU video_cards_fbdev video_cards_nv video_cards_nvidia video_cards_v4l video_cards_vesa" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LC_ALL, PORTDIR_OVERLAY Thanks a lot!
Same problem here. (Also same configuration regarding environment)
I had something similar (can't check the exact message right now). What triggered it in my case seemed to be the synaptics driver though. X couldn't find the core pointer device - a kernel oops seemd to follow upon that. Do any of you use synaptics?
(In reply to comment #2) > I had something similar (can't check the exact message right now). > > What triggered it in my case seemed to be the synaptics driver though. X > couldn't find the core pointer device - a kernel oops seemd to follow upon > that. > > Do any of you use synaptics? > Yes, but rebuilding x11-drivers/synaptics does not solve that prob.
This version is no longer in the tree. Try w/ up-to-date ati-drivers please. Thanks.
