From owner-freebsd-hackers Thu Mar 30 22:56:46 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA14757 for hackers-outgoing; Thu, 30 Mar 1995 22:56:46 -0800 Received: from ns.dknet.dk (root@ns.dknet.dk [193.88.44.42]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA14751 for ; Thu, 30 Mar 1995 22:56:41 -0800 Received: from login.dknet.dk by ns.dknet.dk with SMTP id AA29034 (5.65c8/IDA-1.4.4j for ); Fri, 31 Mar 1995 08:56:25 +0200 Received: by login.dknet.dk (4.1/SMI-4.1DKnet00) id AA03715; Fri, 31 Mar 95 08:54:43 +0200 From: sos@login.dknet.dk (S|ren Schmidt) Message-Id: <9503310654.AA03715@login.dknet.dk> Subject: Re: Fade screen saver page faults To: pritc003@maroon.tc.umn.edu (Mike Pritchard) Date: Fri, 31 Mar 95 8:54:43 MET DST Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199503310308.VAA00167@mpp.com>; from "Mike Pritchard" at Mar 30, 95 9:08 pm X-Charset: ASCII X-Char-Esc: 29 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > I was trying to enable to "fade" screen saver, but anytime that > the screen saver tries to start, I get a panic with the message > "page fault while in kernel mode". All of the other screen savers > work just fine. Running a modstat shows that the fade saver > is loading at the same address as all of the other savers. > Examining the crash dump shows that it faults right at the line in > in syscons.c where it attempts to call the screen saver (making it > look like the saver never loaded, but modstat says it is fine). Hm, I hate to says this, but it used to work.... I'll look at it -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org | sos@login.dknet.dk) FreeBSD Core Team So much code to hack -- so little time ..