From owner-freebsd-questions  Mon Nov 13 14:00:03 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA02454
          for questions-outgoing; Mon, 13 Nov 1995 14:00:03 -0800
Received: from jazz.trumpet.com.au (root@jazz.trumpet.com.au [203.5.119.51])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA02447
          ; Mon, 13 Nov 1995 13:59:50 -0800
Received: (from paul@localhost) by jazz.trumpet.com.au (8.6.11/8.6.9) id IAA13577; Tue, 14 Nov 1995 08:59:42 +1100
Date: Tue, 14 Nov 1995 08:59:42 +1100 (EST)
From: Paul Reece <paul@trumpet.net.au>
X-Sender: paul@jazz
To: scrappy@hub.org, freebsd-questions@FreeBSD.org,
        freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org
Subject: Re: FreeBSD 2.0.5R hanging inexplicably...
In-Reply-To: <199511131419.OAA08697@ns0.netcraft.co.uk>
Message-ID: <Pine.BSF.3.91.951114085833.13434C-100000@jazz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.org
Precedence: bulk

On Mon, 13 Nov 1995, Paul Richards wrote:

> In reply to Paul Reece who said
> > 
> > On Sun, 12 Nov 1995, Marc G. Fournier wrote:
> > 
> > > 	For the second time in two days, my system just hung, in that,
> > > essentially, no keyboard input was being permitted.
> > > 
> 
> Which version are you running?
> 
> I had this happen a lot with 2.0.5 since it didn't handle keyboard
> disconnection and unplugging and putting the keyboard back made it
> dissappear. I also had it happen "randomly"  quite frequently but
> I put that down to the some quirk triggering the same problem.
> 
> When I upgraded to stable the problem went away BUT I did have it happen
> to me once about three days ago shortly after reboot (5 mins say) just
> after upgrading to stable again. That's the only time it's happened in the
> last 6 weeks or so but there may be a problem lurking in there somewhere.
> 
> This is with PCVT.
> 
> I've had worse problems with syscons. There's something wrong with syscons
> vt switching, it's not completely reproducable but it happens frequently
> enough that I've now switched all our machines to pcvt. The symptom is that
> when you switch VT the screen goes completely blank and further attempts
> to switch VT just gets a beep (as though no VT was configured). Everything
> is still running (getty etc) but the screen is just totally blank. Only way
> to recover the console is to reboot.

well, my problem is a full lockup on the whole machine - no core dumps etc
etc..  A reset is the only thing that will fix it :(

Turn off screen savers - no problems (this is with syscons btw)

 - P