From owner-freebsd-current Tue Aug 13 03:22:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA05544 for current-outgoing; Tue, 13 Aug 1996 03:22:51 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA05537; Tue, 13 Aug 1996 03:22:47 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id LAA11628; Tue, 13 Aug 1996 11:20:59 +0100 Date: Tue, 13 Aug 1996 11:20:58 +0100 (BST) From: Doug Rabson To: Josh MacDonald cc: "Jordan K. Hubbard" , jlemon@americantv.com, freebsd-current@freebsd.org, sos@freebsd.org Subject: Re: locking up In-Reply-To: <199608130414.VAA23940@paris.CS.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 12 Aug 1996, Josh MacDonald wrote: > > > 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 > > Hey yeah me too, cause I use caps-lock for my control key. Three or four > times a day I'll have this happen. I'm running XInside. I remember seeing some comments in the pcvt source code that some laptop keyboards can lose interrupts when updating the keyboard LEDs. This seems suspicious since most of the X keyboard lockups seem to involve the caps lock key. Maybe we should poll the keyboard sometimes just in case an interrupt has been lost. Calling scintr from a timeout 5 times a second would do the trick I suppose. Makes me feel slightly ill though. There must be a better way... -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426