From owner-freebsd-hackers Thu Oct 17 09:39:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10978 for hackers-outgoing; Thu, 17 Oct 1996 09:39:43 -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 JAA10973 for ; Thu, 17 Oct 1996 09:39:40 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id JAA03666; Thu, 17 Oct 1996 09:39:35 -0700 (PDT) To: "Brian N. Handy" cc: freebsd-hackers@FreeBSD.org Subject: Re: 2.2-961006-SNAP keyboard lockup In-reply-to: Your message of "Thu, 17 Oct 1996 08:54:27 PDT." Date: Thu, 17 Oct 1996 09:39:35 -0700 Message-ID: <3664.845570375@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > 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.) When it locks up, is it possible to run this from a mouse menu button or something and see if it fixes it? echo "set ipending=2" | gdb -k -w /kernel /dev/mem >/dev/null 2>&1 I have the same problem, but it only happens when I xmodmap the keyboard to swap my capslock and DEL keys. Before I did this (the result of switching keyboards to one which didn't do it in hardware), I never had a problem at all. Jordan