Fresh install of gnome 2.24 & FreeBSD 7.1 woes (logout crashes,
`failed to restart'...)...
Joe Marcus Clarke
marcus at freebsd.org
Mon Feb 16 10:42:07 PST 2009
Jeffrey Racine wrote:
> Hi Joe.
>
> Thanks for your assistance.
>
> On Mon, 2009-02-16 at 01:05 -0500, Joe Marcus Clarke wrote:
>> On Mon, 2009-02-09 at 12:30 -0500, Jeffrey Racine wrote:
>>> Hi.
>>>
>>> I recently posted that I was having issues on a Dell Optiplex SX280
>>> after upgrading that had no problems with gnome 2.22 running FreeBSD
>>> 7.0. However, my upgrade to 2.24 did not go smoothly. I could not log
>>> out of a gnome session and trying `reboot' as root crashed the system.
>>>
>>> Prior to the upgrade system had been up for months with zero issues.
>>> But, I thought perhaps it was the fact that this system has been
>>> upgraded many times so perhaps things were getting linked to old libs.
>>> Hence, on Friday I did a fresh install of FreeBSD 7.1 from a CD and
>>> complete compile of gnome 2.4 from scratch. Yes, I have dbus_enable
>>> and hald_enable in rc.conf and gnome_enable.
>>>
>>> There appear to be some serious issues that others have recently
>>> noted. I don't know if it is xorg 7.4, gnome 2.24, or FreeBSD 7.1. Any
>>> suggestions as to what to try would be most welcome. Here are the
>>> symptoms, and many thanks for any suggestions.
>>>
>>> 1) With gnome_enable, I cannot restart or stop the computer from the
>>> gdm login screen - I get a `failed to...' message.
>>>
>>> 2) If I remove gnome_enable from rc.conf but leave hald_enable and
>>> gdm_enable set, then log in as a regular user, when I logout the
>>> system crashes cold
>>>
>>> Note - these are exactly the symptoms I was having when I upgraded the
>>> system prior to the fresh install. Any suggestions as to how to
>>> proceed to diagnose the issue would be most welcome.
>> Restart and shutdown require one to be active on the console. They also
>> require procfs to be mounted on /proc. If this is not done, those
>> functions will certainly fail.
>
> Hmmm... I didn't have this in fstab under FreeBSD 7.0 and gnome 2.22 and
> it worked fine. I also don't see this as _required_ in the install faq
> or hal faq for what that is worth (perhaps my faulty reading). But, as
> you point out, this now provides the appropriate menu settings and
> behavior, though I am still getting crashes.
>
>> As for the logout crash, nothing in GNOME should be crashing the system
>> (except maybe fusefs). Try rebuilding fusefs-kmod (if you have it
>> loaded).
>
> Rebuilt, though not sure what you mean by if you have it
> `loaded' (nothing I explicitly call/use). Does not appear to help.
>
>> If that doesn't work, you'll need to get a backtrace of the
>> kernel panic. This may require you to setup a serial console.
>
> Many thanks. Here it is.
>
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> This GDB was configured as "i386-marcel-freebsd"...
>
> Unread portion of the kernel message buffer:
> <118>.
> <118>Shutting down local daemons:
> <118>.
> <118>Writing entropy file:
> <118>.
> <118>.
> <118>Feb 16 12:54:07 pc-racine1 syslogd: exiting on signal 15
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0x188
> fault code = supervisor read, page not present
> instruction pointer = 0x20:0xc07b0564
> stack pointer = 0x28:0xe7b89af8
> frame pointer = 0x28:0xe7b89b10
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 3
> current process = 967 (Xorg)
> trap number = 12
> panic: page fault
> cpuid = 0
> Uptime: 45s
> Physical memory: 2025 MB
> Dumping 105 MB: 90 74 58 42 26 10
>
> Reading symbols from /boot/kernel/acpi.ko...Reading symbols
> from /boot/kernel/acpi.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/acpi.ko
> Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols
> from /boot/kernel/linprocfs.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/linprocfs.ko
> Reading symbols from /boot/kernel/linux.ko...Reading symbols
> from /boot/kernel/linux.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/linux.ko
> Reading symbols from /boot/kernel/i915.ko...Reading symbols
> from /boot/kernel/i915.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/i915.ko
> Reading symbols from /boot/kernel/drm.ko...Reading symbols
> from /boot/kernel/drm.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/drm.ko
> #0 doadump () at pcpu.h:196
> 196 pcpu.h: No such file or directory.
> in pcpu.h
> (kgdb) backtrace
> #0 doadump () at pcpu.h:196
> #1 0xc07be607 in boot (howto=260)
> at /usr/src/sys/kern/kern_shutdown.c:418
> #2 0xc07be8d9 in panic (fmt=Variable "fmt" is not available.
> ) at /usr/src/sys/kern/kern_shutdown.c:574
> #3 0xc0ad0aec in trap_fatal (frame=0xe7b89ab8, eva=392)
> at /usr/src/sys/i386/i386/trap.c:939
> #4 0xc0ad0d70 in trap_pfault (frame=0xe7b89ab8, usermode=0, eva=392)
> at /usr/src/sys/i386/i386/trap.c:852
> #5 0xc0ad172c in trap (frame=0xe7b89ab8)
> at /usr/src/sys/i386/i386/trap.c:530
> #6 0xc0ab759b in calltrap () at /usr/src/sys/i386/i386/exception.s:159
> #7 0xc07b0564 in _mtx_lock_sleep (m=0xc52b5cc0, tid=3314965792, opts=0,
> file=0xc5a60953
> "/usr/src/sys/modules/drm/i915/../../../dev/drm/i915_irq.c",
> line=118) at /usr/src/sys/kern/kern_mutex.c:339
> #8 0xc07b0a02 in _mtx_lock_flags (m=0xc52b5cc0, opts=0, file=0xc5a60953
> "/usr/src/sys/modules/drm/i915/../../../dev/drm/i915_irq.c", line=118)
> at /usr/src/sys/kern/kern_mutex.c:186
> #9 0xc5a5f403 in i915_irq_wait (kdev=0xc562a700, cmd=Variable "cmd" is
> not available.
Looks like an issue with the Intel DRM kernel module. Take this up on x11 at .
Joe
> ) at /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_irq.c:117
> #10 0xc5a6aa4a in drm_ioctl (kdev=0xc562a700, cmd=2147771461,
> data=0xc52bfc60 "\025\006", flags=67, p=0xc5965d20)
> at /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drv.c:911
> #11 0xc07832a7 in giant_ioctl (dev=0xc562a700, cmd=2147771461,
> data=0xc52bfc60 "\025\006", fflag=67, td=0xc5965d20)
> at /usr/src/sys/kern/kern_conf.c:408
> #12 0xc074d4b7 in devfs_ioctl_f (fp=0xc5a2f474, com=2147771461,
> data=0xc52bfc60, cred=0xc5508e00, td=0xc5965d20)
> at /usr/src/sys/fs/devfs/devfs_vnops.c:595
> #13 0xc07f5565 in kern_ioctl (td=0xc5965d20, fd=9, com=2147771461,
> data=0xc52bfc60 "\025\006") at file.h:268
> #14 0xc07f56c4 in ioctl (td=0xc5965d20, uap=0xe7b89cfc)
> at /usr/src/sys/kern/sys_generic.c:570
> #15 0xc0ad10c5 in syscall (frame=0xe7b89d38)
> at /usr/src/sys/i386/i386/trap.c:1090
> #16 0xc0ab7600 in Xint0x80_syscall ()
> at /usr/src/sys/i386/i386/exception.s:255
> #17 0x00000033 in ?? ()
> Previous frame inner to this frame (corrupt stack?)
> (kgdb) quit
>
>> Joe
>
> Many thanks again Joe.
>
> -- Jeff
>
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
More information about the freebsd-gnome
mailing list