From owner-freebsd-bugs Mon Apr 21 05:30:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA10310 for bugs-outgoing; Mon, 21 Apr 1997 05:30:07 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA10302; Mon, 21 Apr 1997 05:30:04 -0700 (PDT) Date: Mon, 21 Apr 1997 05:30:04 -0700 (PDT) Message-Id: <199704211230.FAA10302@freefall.freebsd.org> To: freebsd-bugs Cc: From: Kazutaka YOKOTA Subject: Re: i386/3082: keyboard locks up unexpectedly Reply-To: Kazutaka YOKOTA Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR i386/3082; it has been noted by GNATS. From: Kazutaka YOKOTA To: raj@iphase.com Cc: FreeBSD-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: i386/3082: keyboard locks up unexpectedly Date: Mon, 21 Apr 1997 21:28:25 +0900 >>Number: 3082 >>Category: i386 >>Synopsis: keyboard locks up unexpectedly [....] >>Release: FreeBSD 2.1.6 i386 >>Environment: > > Pentium pro system. > FreeBSD 2.1.6 installed with default sc0 console in config file. > Lines for PS/2 and bus mice commented out in the config file. > > Execution of "uname -a" produced the following output: > > FreeBSD lifeson 2.1.6-RELEASE FreeBSD 2.1.6-RELEASE #4: > root@lifeson:/usr/src/sys/compile/lifeson i386 > >>Description: > > System locks up unexpectedly. There's no set pattern to this. > When this happens, any sort of input from the keyboard becomes > impossible. Even Ctl-C doesn't work. Actually no key works. This is a known problem. It's intermittent and difficult to reproduce. When this happens again, login to the system via serial or network and try the following command. kbdcontrol -r fast < /dev/ttyv0 (You may have to become root to do this.) The command actually changes the keyboard typematic rate and it doesn't do anything special to recover from lock up, but, the keyboard MAY become functional as a side effect under FreeBSD 2.1.X. If you are using X and a PS/2 mouse when the lock up happens and run the above command, the PS/2 mouse may go wild. This is harmless. Switch away from X to another vty (by pressing Ctl+Alt+Fn, yes, I expect the keyboard is working again after the kbdcontrol command) and come back to X, then the mouse should be OK. Hope this might help. Kazu