From owner-freebsd-bugs  Mon Apr  7 17:50:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA05752
          for bugs-outgoing; Mon, 7 Apr 1997 17:50:03 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA05746;
          Mon, 7 Apr 1997 17:50:01 -0700 (PDT)
Date: Mon, 7 Apr 1997 17:50:01 -0700 (PDT)
Message-Id: <199704080050.RAA05746@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Subject: Re: kern/2632: enabling psm mouse causes keyboard to not work on Toshiba
	 115CS laptop 
Reply-To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/2632; it has been noted by GNATS.

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: epv@panix.com
Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: kern/2632: enabling psm mouse causes keyboard to not work on Toshiba
	 115CS laptop 
Date: Tue, 08 Apr 1997 09:45:21 +0900

 >>Number:         2632
 >>Category:       kern
 >>Synopsis:       enabling psm mouse causes keyboard to not work on Toshiba 115
 >CS laptop
 >>Confidential:   no
 >>Severity:       serious
 >>Priority:       medium
 >>Responsible:    freebsd-bugs
 >>State:          open
 >>Class:          sw-bug
 >>Submitter-Id:   current-users
 >>Arrival-Date:   Fri Jan 31 17:50:01 PST 1997
 >>Last-Modified:
 >>Originator:     Eric Volpe
 >>Organization:
 >>Release:        2.2-BETA
 >>Environment:
 >FreeBSD lemur.snysel.com 2.20-BETA_A #1	
 >>Description:
 >if psm mouse driver is enabled (either from boot floppy or a kernel 
 >built on the machine from 2.2-BETA source) the kernel correctly 
 >identifies the mouse when booting, but does not respond to the keyboard
 >at all. If the psm device is disabled in userconfig or not compiled into
 >the kernel, the keyboard responds properly. 	
 
 Do you still see the above problem with 2.2-RELEASE? If not, I would
 close this PR.
 
 Kazu