Date: Sun, 14 Mar 1999 21:35:47 +0100 From: Thomas Zenker <thz@tuebingen.netsurf.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable Message-ID: <19990314213546.A269@peotl.tuebingen.netsurf.de> In-Reply-To: <199903141926.LAA93452@apollo.backplane.com>; from Matthew Dillon on Sun, Mar 14, 1999 at 11:26:24AM -0800 References: <199903132253.QAA09676@isua1.iastate.edu> <199903141926.LAA93452@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 14, 1999 at 11:26:24AM -0800, Matthew Dillon wrote: > The vga stuff in the call stack is very suspicious. It looks like it > crashed trying to start up the screen saver. > > If you are using any dynamically loaded modules ( such as the splash > module ), make sure you have recompiled and reinstaslled them. > Exactly the same panic here. This is as 486 system with world and kernel from 7th march. Until today the system freezed simply the screensaver,... today there was the first time I saw the panic and the kernel fell into the debugger after pressing a key to get rid of the saver. (probably the first time that the system had been left on console?) The trace shows stopping the saver and trying to restore the screen, then in vga_load_state+136 a missing page causing a pagefault. ... So later on swap_pager_getpages does a tsleep, but we are the "idle" process. As far as I know, "idle" should never tsleep and may not have pages pagedout. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990314213546.A269>