| Summary: | gdm can't start | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Valensky <valensm> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | adam.c.stephens, x11 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | xfree log file | ||
|
Description
Martin Valensky
2004-01-31 05:57:13 UTC
Created attachment 24685 [details]
xfree log file
sorry there has been no move on this, is this stil a problem ? What xfree are you using exactly ? Try starting gdm from an xterm, see if there is any ouput, since it's most likely not xfree itself. i am having this same issue. it first surfaced when i upgraded gtk to 2.4.0-r1. at the time i was using gdm-2.4.1.7-r1. this first problem was gdm would start and then just hang there displaying the pointer and nothing else. i wondered if it was an issue with the gtk upgrade, so i reinstalled gdm. this left me with the symptoms in the bug. X starts then crashes repeatedly. i do want to point out that my messages log shows:
Apr 20 00:37:20 default kernel: mtrr: your processor doesn't support write-combining
Apr 20 00:37:20 default kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Apr 20 00:37:20 default kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Apr 20 00:37:20 default kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Apr 20 00:37:20 default kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
i noticed another user in the forums with this issue as well.
* x11-base/xfree
Latest version installed: 4.3.99.902-r2
Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.2-rc1-gentoo)
=================================================================
System uname: 2.6.2-rc1-gentoo i686 AMD-K7(tm) Processor
Gentoo Base System version 1.4.10
distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=i686 -funroll-loops -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distcc sandbox"
GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo"
MAKEOPTS="-j5"
PKGDIR="/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="3dnow X aalib acpi alsa apache2 apm avi berkdb cdr cjk crypt cups curl dga dvd dvdr encode esd evms2 faad flac flash foomaticdb gd gdbm gif gnome gnutls gphoto2 gpm gstreamer gtk gtk2 gtkhtml imap imlib ipv6 java jpeg kde kerberos libg++ libwww lirc mad matroska mikmod mmx motif mozilla mpeg mysql ncurses nls nvidia oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba scanner sdl slang spell sse ssl svga tcltk tcpd tiff truetype v4l vim-with-x wxwindows x86 xml2 xmms xosd xv xvid zlib"
this happens with gdm-2.4.4.7-r1 as well. if it's a problem with xfree-4.3.99 only i don't think we're going to do much about it ... Please try to reproduce this with xorg-x11. ok, switched to xorg-x11. gdm still crashing repeatedly. using gdm-2.4.4.7-r1 Apr 20 05:02:56 default gdm[6450]: gdm_main: Here we go... Apr 20 05:02:56 default gdm[6450]: gdm_start_first_unborn_local: Starting :0 Apr 20 05:02:56 default gdm[6450]: gdm_display_manage: Managing :0 Apr 20 05:02:56 default gdm[6450]: loop check: last_start 0, last_loop 0, now: 1082451776, retry_count: 0 Apr 20 05:02:56 default gdm[6450]: Resetting counts for loop of death detection Apr 20 05:02:56 default gdm[6452]: gdm_slave_start: Starting slave process for :0 Apr 20 05:02:56 default gdm[6452]: gdm_slave_start: Loop Thingie Apr 20 05:02:56 default gdm[6452]: Sending VT_NUM == -1 for slave 6452 Apr 20 05:02:56 default gdm[6452]: Sending VT_NUM 6452 -1 Apr 20 05:02:56 default gdm[6450]: gdm_display_manage: Forked slave: 6452 Apr 20 05:02:56 default gdm[6450]: Handling message: 'VT_NUM 6452 -1' Apr 20 05:02:56 default gdm[6450]: Got VT_NUM == -1 Apr 20 05:02:56 default gdm[6452]: gdm_server_start: :0 Apr 20 05:02:56 default gdm[6452]: gdm_auth_secure_display: Setting up access for :0 Apr 20 05:02:56 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal Apr 20 05:02:56 default gdm[6452]: gdm_auth_secure_display: Setting up access Apr 20 05:02:56 default gdm[6452]: gdm_auth_secure_display: Setting up access for :0 - 1 entries Apr 20 05:02:56 default gdm[6452]: Sending COOKIE == <secret> for slave 6452 Apr 20 05:02:56 default gdm[6452]: Sending COOKIE 6452 ce... Apr 20 05:02:56 default gdm[6450]: Handling message: 'COOKIE 6452 ce...' Apr 20 05:02:56 default gdm[6450]: Got COOKIE == <secret> Apr 20 05:02:56 default gdm[6452]: gdm_server_spawn: Forked server on pid 6453 Apr 20 05:02:56 default gdm[6452]: do_server_wait: Before mainloop waiting for server Apr 20 05:02:56 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal Apr 20 05:02:57 default gdm[6453]: gdm_server_spawn: '/usr/X11R6/bin/X :0 -nolisten tcp -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7' Apr 20 05:02:57 default gdm[6452]: gdm_server_start: After mainloop waiting for server Apr 20 05:02:57 default gdm[6452]: gdm_server_start: Completed :0! Apr 20 05:02:57 default gdm[6452]: Sending VT_NUM == 7 for slave 6452 Apr 20 05:02:57 default gdm[6452]: Sending VT_NUM 6452 7 Apr 20 05:02:57 default gdm[6450]: (child 6452) gdm_server_usr1_handler: Got SIGUSR1, server running Apr 20 05:02:57 default gdm[6450]: Handling message: 'VT_NUM 6452 7' Apr 20 05:02:57 default gdm[6450]: Got VT_NUM == 7 Apr 20 05:02:57 default gdm[6452]: Sending XPID == 6453 for slave 6452 Apr 20 05:02:57 default gdm[6452]: Sending XPID 6452 6453 Apr 20 05:02:57 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal Apr 20 05:02:57 default gdm[6450]: Handling message: 'XPID 6452 6453' Apr 20 05:02:57 default gdm[6450]: Got XPID == 6453 Apr 20 05:02:57 default gdm[6452]: gdm_slave_run: Opening display :0 Apr 20 05:02:57 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal Apr 20 05:02:58 default kernel: mtrr: your processor doesn't support write-combining Apr 20 05:03:00 default gdm[6452]: Sending START_NEXT_LOCAL Apr 20 05:03:00 default gdm[6450]: Handling message: 'START_NEXT_LOCAL' Apr 20 05:03:00 default gdm[6452]: gdm_slave_greeter: Running greeter on :0 Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_child_handler Apr 20 05:03:00 default gdm[6452]: gdm_slave_greeter: Greeter on pid 6458 Apr 20 05:03:00 default gdm[6452]: Sending GREETPID == 6458 for slave 6452 Apr 20 05:03:00 default gdm[6452]: Sending GREETPID 6452 6458 Apr 20 05:03:00 default gdm[6450]: Handling message: 'GREETPID 6452 6458' Apr 20 05:03:00 default gdm[6450]: Got GREETPID == 6458 Apr 20 05:03:00 default CRON[6460]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons ) Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal Apr 20 05:03:00 default gdm[6452]: gdm_slave_wait_for_login: In loop Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_child_handler Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_child_handler: 6458 died Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_child_handler: 6458 died of 6 Apr 20 05:03:00 default gdm[6452]: term_quit: Final cleanup Apr 20 05:03:00 default gdm[6452]: gdm_slave_quick_exit: Will kill everything from the display Apr 20 05:03:00 default gdm[6452]: Running gdm_verify_cleanup and pamh != NULL Apr 20 05:03:00 default gdm[6452]: gdm_server_stop: Server for :0 going down! Apr 20 05:03:00 default gdm[6452]: gdm_server_stop: Killing server pid 6453 Apr 20 05:03:01 default gdm[6452]: gdm_server_stop: Server pid 6453 dead Apr 20 05:03:01 default gdm[6452]: gdm_slave_quick_exit: Killed everything from the display Apr 20 05:03:01 default gdm[6450]: mainloop_sig_callback: Got signal 17 Apr 20 05:03:01 default gdm[6450]: gdm_cleanup_children: child 6452 returned 65 Apr 20 05:03:01 default gdm[6450]: gdm_child_action: In remanage and messages: Apr 20 04:37:13 default kernel: mtrr: your processor doesn't support write-combining Apr 20 04:44:19 default last message repeated 5 times Apr 20 05:00:45 default last message repeated 2 times Apr 20 05:02:58 default last message repeated 6 times i have solved this problem for me. i recompiled my kernel (i was actually using 2.6.3 contrary to what my emerge info shows). i am now running 2.6.5 with the same kernel config and gdm works flawlessly for me. there appears to be an issue with the mtrr, gtk-2.4, and gdm with 2.6.3? let me know if you would like me to test anything. thanks dunno, if it works with newer kernels I don't care to investigate much further. I'm on a kernel 2.6.3 system btw and it works just fine. Anyone got any other insights, otherwise i'm closing this ? See foser's previous comment |
