From owner-freebsd-bugs Wed Jul 9 23:34:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09581 for bugs-outgoing; Wed, 9 Jul 1997 23:34:11 -0700 (PDT) Received: from gatekeeper.ukrv.de (gatekeeper.ukrv.de [193.175.72.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA09568 for ; Wed, 9 Jul 1997 23:34:06 -0700 (PDT) Received: by gatekeeper.ukrv.de; (5.65/1.1.8.2/17Oct95-0336PM) id AA06253; Thu, 10 Jul 1997 08:33:57 +0200 Received: from mailhost(193.175.66.33) by gatekeeper.ukrv.de via smap (V1.3-JSC) id sma006354; Thu Jul 10 08:33:54 1997 Received: from merlin.ukrv.de by mailhost.ukrv.de; (5.65/1.1.8.2/08Mar95-0213PM) id AA18741; Thu, 10 Jul 1997 08:33:54 +0200 Received: by merlin.ukrv.de (4.1/UKRV-Gen PCG 0.1) id AA07266; Thu, 10 Jul 97 08:33:53 +0200 From: Udo Wolter Message-Id: <9707100633.AA07266@merlin.ukrv.de> Subject: Re: PS/2 and Keycode bug In-Reply-To: <199707081711.CAA13841@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jul 9, 97 02:11:06 am" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 10 Jul 1997 08:33:52 +0200 (MET DST) Cc: uwp@ukrv.de, bugs@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL31 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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. That's what I wanted to say. :-) > You appear to be experiencing the lockup under X. If you move the Yes, only under X at this time. > mouse, does the mouse pointer move accordingly? If so, the mouse and No, mouse AND keyboard are dead. > 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). I don't know. Because I can't move anything I don't know what's happening. > What happens if you hit Num-Lock, Caps-Lock or Scroll-Lock? If Never tried. > 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. This sounds good. I'll test it the next time I have a lockup. > 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. Maybe. I'll test it the next time and will tell you. > >doin' nothin'. It only hung up when I really kick the machine to boost > >every bit out of it. > > Like doing what? renice some processes to -20 (e.g. a musicin process -> MPEG-Audio-Encoding) or starting 2 X-servers at once. This worked fantastic in 2.1.7 so it should be ok. Bye, Udo -- Udo Wolter, email: uwp@cs.tu-berlin.de !!! LOW-TECH Page: http://low-tech.home.ml.org !!!