Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jun 2006 14:11:56 -0500
From:      Derek Ragona <derek@computinginnovations.com>
To:        freebsd-gnome@FreeBSD.org
Subject:   nvidia driver and glslideshow causes reboot
Message-ID:  <6.0.0.22.2.20060620133756.0259a080@mail.computinginnovations.com>

next in thread | raw e-mail | index | archive | help
I have a FreeBSD server running 6.1 stable, and gnome 2.14.

I have cvsup'd and done a portupgrade -a.  I even rebuilt the nvidia-driver.

The system is fine until you go to access it AFTER glslideshow is 
running.  Coming out of the screen saver it causes the system to 
reboot.  The system log shows:
====================================================
Jun 20 12:04:37 betty syslogd: kernel boot file is /boot/kernel/kernel
Jun 20 12:04:37 betty kernel:
Jun 20 12:04:37 betty kernel:
Jun 20 12:04:37 betty kernel: Fatal trap 12: page fault while in kernel mode
Jun 20 12:04:37 betty kernel: fault virtual address     = 0x7
Jun 20 12:04:37 betty kernel: fault code                = supervisor read, 
page not present
Jun 20 12:04:37 betty kernel: instruction pointer       = 0x20:0xc71819da
Jun 20 12:04:37 betty kernel: stack pointer             = 0x28:0xf887c6d8
Jun 20 12:04:37 betty kernel: frame pointer             = 0x28:0xf887c6d8
Jun 20 12:04:37 betty kernel: code segment              = base 0x0, limit 
0xfffff, type 0x1b
Jun 20 12:04:37 betty kernel: = DPL 0, pres 1, def32 1, gran 1
Jun 20 12:04:37 betty kernel: processor eflags  = interrupt enabled, 
resume, IOPL = 0
Jun 20 12:04:37 betty kernel: current process           = 2697 (glslideshow)
Jun 20 12:04:37 betty kernel: trap number               = 12
Jun 20 12:04:37 betty kernel: panic: page fault
Jun 20 12:04:37 betty kernel: Uptime: 57m21s
Jun 20 12:04:37 betty kernel: Cannot dump. No dump device defined.
Jun 20 12:04:37 betty kernel: Automatic reboot in 15 seconds - press a key 
on the console to abort
Jun 20 12:04:37 betty kernel: Rebooting...
====================================================

Anyone have an idea if this is a known problem or if there is a 
workaround?  Or should I open a bug report?

Please email me directly, as I am not subscribed to this list.

Thanks,



         -Derek
         derek@computinginnovations.com



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.2.20060620133756.0259a080>