From owner-freebsd-current  Mon Aug 12 19:54:29 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA07993
          for current-outgoing; Mon, 12 Aug 1996 19:54:29 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07981;
          Mon, 12 Aug 1996 19:54:26 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id TAA03453; Mon, 12 Aug 1996 19:52:49 -0700 (PDT)
To: Archie Cobbs <archie@whistle.com>
cc: jlemon@americantv.com, freebsd-current@FreeBSD.org, sos@FreeBSD.org
Subject: Re: locking up 
In-reply-to: Your message of "Mon, 12 Aug 1996 16:22:51 PDT."
             <199608122322.QAA04171@bubba.whistle.com> 
Date: Mon, 12 Aug 1996 19:52:49 -0700
Message-ID: <3451.839904769@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> I get this a lot. It always happens when I'm pressing the CAPS LOCK key
> at the same time as some other key. I HATE IT because I end up having to
> kill about 30 vi sessions, etc., etc...
> 
> This is on 2.1.0-R with XFree86 S3 server.

Does the gdb trick work to get you out?  Looks like this is a bug in
our console code then, and not the X server itself.

> By the way, after killing the X server, you can find the "lost" character
> typed (the one that caused the hang) on the virtual console you started
> X from (eg, at the login prompt)...

Yep!!!  Exact same symptoms here.  Oh Soooooooreeeeeen..  We have
another nice little bug for you! :-)

					Jordan