From owner-freebsd-hackers Sat Mar 13 20:44:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ninsei.com (24.64.9.93.ab.wave.home.com [24.64.9.93]) by hub.freebsd.org (Postfix) with SMTP id CF0A814BDA for ; Sat, 13 Mar 1999 20:44:18 -0800 (PST) (envelope-from dreamer@freelow.ninsei.com) Received: (qmail 36772 invoked by uid 1001); 14 Mar 1999 04:43:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Mar 1999 04:43:58 -0000 Date: Sat, 13 Mar 1999 21:43:58 -0700 (MST) From: Steven Young To: Alfred Perlstein Cc: Kent Vander Velden , freebsd-hackers@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 13 Mar 1999, Alfred Perlstein wrote: > As a temporary workaround please disable the screen saver code. > I was having the same problems with 4.0 and taking out the saver > module kept my machine from crashing. For the record, I have been experiencing a large number of kernel panics under 3.1-RELEASE due to the screen saver. Happens with all the different screen saver modules, basically whenever I hit a key or whatever to get rid of the screen saver, the system crashes and burns. Disabling the screen saver entirely and not compiling in the pseudo-device seem to have fixed the problem, but I'm probably one of the last five people on the planet that still uses an amber monitor that actually needs a screen blanker. ;) Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message