From owner-freebsd-hackers Thu Oct 17 08:54:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA08205 for hackers-outgoing; Thu, 17 Oct 1996 08:54:28 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA08200 for ; Thu, 17 Oct 1996 08:54:25 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA14324; Thu, 17 Oct 1996 08:54:27 -0700 Date: Thu, 17 Oct 1996 08:54:27 -0700 (PDT) From: "Brian N. Handy" To: freebsd-hackers@FreeBSD.org Subject: Re: 2.2-961006-SNAP keyboard lockup In-Reply-To: <199610170549.XAA00642@fluffy.aros.net> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >It's never happened under X, most likely because I'm never > a) switching vty's >or > b) hitting the certain keys that cause it to lock. I do occasionally have keyboard lockups too, but only under X. I'm not sure that mine is a FreeBSD problem however -- I'm running Xaccel. If I log out my session (The mouse still works) and log back in, I find that I have control of the keyboard again. (I run 960801-SNAP.) I'm not sure yet what sorts of things set off my problem. I wasn't going to report it until I had a better grip on what causes it, but maybe it's a useful datapoint. Regards, Brian