From owner-freebsd-bugs Tue Jul 8 11:13:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA29588 for bugs-outgoing; Tue, 8 Jul 1997 11:13:01 -0700 (PDT) Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA29583 for ; Tue, 8 Jul 1997 11:12:58 -0700 (PDT) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by nasu.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id DAA31413 for ; Wed, 9 Jul 1997 03:03:13 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (bDjTJsW5VTgh1+evIclcW8jyXLrk7Z+8@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by outmail.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id DAA31353 for ; Wed, 9 Jul 1997 03:03:13 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id CAA13841; Wed, 9 Jul 1997 02:11:07 +0900 (JST) Message-Id: <199707081711.CAA13841@zodiac.mech.utsunomiya-u.ac.jp> To: Udo Wolter cc: bugs@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: PS/2 and Keycode bug In-reply-to: Your message of "Tue, 08 Jul 1997 16:35:13 +0200." <9707081435.AA03245@merlin.ukrv.de> References: <9707081435.AA03245@merlin.ukrv.de> Date: Wed, 09 Jul 1997 02:11:06 +0900 From: Kazutaka YOKOTA Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I'm surprised more people haven't complained. > >I'm also complaining. I'm using a PS/2 mouse at work and a mousesystems serial >mouse at home, but I have those keyboard lockups at both places ! The PS/2 mouse and the serial mouse are completely different and are handled in different ways under FreeBSD. Therefore, if the keyboard lockup you are describing happens in both systems in the same way, then I think it is unlikely that the cause of the lockup is with the mice. >The mouse and keyboard are still hanging while the machine's still working, >I can rlogin from other machines and kill X etc. You appear to be experiencing the lockup under X. If you move the mouse, does the mouse pointer move accordingly? If so, the mouse and the X server are all right (you may not be able to display menu or move windows, but that's not the mouse driver's fault). >But the keyboard never >comes back, I never get any console until I reboot. What happens if you hit Num-Lock, Caps-Lock or Scroll-Lock? If hitting these keys changes the keyboard LEDs, the keyboard driver is working. Another way to test the keyboard driver is to login to the system via telnet or rlogin from another host, become root, and issue `kbdcontrol -r fast < /dev/ttyv0'. If the keyboard driver is dead, the command will fail. You see, there always is a possibility that it is either the window manager or a client program that is not responding to mouse or keyboard input, and the keyboard and mouse drivers are sending correct data to the X server. >I've read in the buglist that the keyboard hang ist still there. Funny: I >have these problems since 2.2.1, in 2.1.7 there were no problems. I believe >my keyboard hangs only when the load gets too high. It never hung while I'm >doin' nothin'. It only hung up when I really kick the machine to boost >every bit out of it. Like doing what? Kazu