From owner-freebsd-questions Wed Oct 4 12:46:25 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA01257 for questions-outgoing; Wed, 4 Oct 1995 12:46:25 -0700 Received: from virginia.edu (uvaarpa.Virginia.EDU [128.143.2.7]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id MAA01252 for ; Wed, 4 Oct 1995 12:46:19 -0700 Received: from server.cs.virginia.edu by uvaarpa.virginia.edu id aa25663; 4 Oct 95 15:46 EDT Received: from viper.cs.Virginia.EDU (viper-fo.cs.Virginia.EDU) by uvacs.cs.virginia.edu (4.1/5.1.UVA) id AA17055; Wed, 4 Oct 95 15:46:06 EDT Posted-Date: Wed, 4 Oct 1995 15:46:05 -0400 (EDT) Received: by viper.cs.Virginia.EDU (5.x/SMI-2.0) id AA07384; Wed, 4 Oct 1995 15:46:06 -0400 From: bah6f@server.cs.virginia.edu Message-Id: <9510041946.AA07384@viper.cs.Virginia.EDU> Subject: Re: Keyboard locking up To: questions@freebsd.org Date: Wed, 4 Oct 1995 15:46:05 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org Precedence: bulk Pete Carah writes: -> In article <199510040838.EAA09332@acmex.gatech.edu> you write: -> >> I have noticed a problem with 2.1.0-950928 freebsd snap locking up and -> >> someone told me that this was reported a few times. After investigating -> ... -> >> My solution was to disable the green screen saver... am wondering if -> >> there are any revelancy between the two? -> ... -> >we just had this problem on my friend's machine, which we just -> >installed 2.1.0-950928 on today. But he was typing at the time so -> >there's no way the screen saver was coming on, and he is using -> >snake instead of green. At the time it locked, he had just -> >changed vttys(he had 7 going at the time). -> -> I've seen lockups before on switching away from X; I think the problem -> there is that you hit another key before the screen mode+data restore -> is done; with X that takes a while so it is more likely to happen. -> I had to reboot an ISP's main server yesterday because of this one :-( I've seen the X lockup described above, and I can't fix that one. On my computer, however, I've had the keyboard lock up in other circumstances (like just typing normally in X) and the solution was trivial (though annoying). I simply unplug the keyboard and plug it back in. I don't know why this happens, nor do I know how to avoid it. I just know that in this case, you can simply reset the keyboard and go along happily. It seems to happen to me most often when I'm pressing lots of control keys and stuff (i.e. in emacs). It rarely happens when just typing straight text. I don't know if this will solve all the problems above, but it might help one or two. ;) Paco -- Brian "Paco" Hope Research Assistant, Technical Support Staff email: paco@virginia.edu Department of Computer Science WWW: http://www.cs.virginia.edu/~bah6f/ University of Virginia