From nobody  Thu May  1 16:20:44 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA24546;
          Thu, 1 May 1997 16:20:44 -0700 (PDT)
Message-Id: <199705012320.QAA24546@hub.freebsd.org>
Date: Thu, 1 May 1997 16:20:44 -0700 (PDT)
From: mcnab@nas.nasa.gov
To: freebsd-gnats-submit@freebsd.org
Subject: using a PS/2 mouse causes kernel trap in 2.2.1
X-Send-Pr-Version: www-1.0

>Number:         3462
>Category:       i386
>Synopsis:       using a PS/2 mouse causes kernel trap in 2.2.1
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    yokota
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May  1 16:30:01 PDT 1997
>Closed-Date:    Fri Mar 12 03:16:50 PST 1999
>Last-Modified:  Fri Mar 12 03:18:17 PST 1999
>Originator:     A. David McNab
>Release:        2.2.1-RELEASE #0
>Organization:
MRJ
>Environment:
FreeBSD aargh.nas.nasa.gov 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE #0: Wed Apr 30 15:32:13 PDT 1997     root@aargh.nas.nasa.gov:/usr/src/sys/compile/MCNAB  i386
(Std. kernel but customized to my hardware, DDB turned on)
>Description:
Using a PS/2 mouse with std. PC kbd and psm0 enabled causes the
following kernel trap after a while (with DDB turned on):

instruction pointer     = 0x8:0xf01887cb
stack pointer           = 0x10:0xf01a1f3c
frame pointer           = 0x10:0xf01a1f40
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, IOPL = 0
current process         = Idle
interrupt mask          = tty
kernel: type 29 trap, code=0
Stopped at      _read_kbd_data_no_wait+0x37:    andl    $0xff,%eax

>How-To-Repeat:
Hook up a mouse with PS/2 connector, turn on moused, and
move the mouse around for a while.  Happens in X too.
>Fix:
Not known.
>Release-Note:
>Audit-Trail:

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: David McNab <mcnab@nas.nasa.gov>
Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: i386/3462: using a PS/2 mouse causes kernel trap in 2.2.1 
Date: Wed, 25 Jun 1997 17:10:18 +0900

 It's been a while since we exchanged mails last time...
 
 Last month you reported occasional stray trap 29 problems on your P6
 machine when running FreeBSD 2.2.1.
 
 >>Thanks for the patch; however I have installed NetBSD
 >>over my FreeBSD disk at the moment, so I'm afraid I
 >>can't test it at the moment.  There are some
 >>other people around who are interested in running
 >>FreeBSD on the same hardware, so I'll have them apply
 >>and I'll let you know what happens.
 >>
 >>--
 >>David McNab
 >>work: mcnab@nas.nasa.gov
 >>personal: dave@mcnab.org
 >
 >Here is another patch. This one is cleaner than the previous one.  It
 >will modify the following files:
 >
 >sys/i386/i386/trap.c
 >sys/i386/i386/machdep.c
 >sys/i386/i386/exception.s
 >sys/i386/include/trap.h
 >
 >(When you try this one, please back out the previous patch first.)
 >
 >Kazu
 
 Have you or anybody around you tried either one of the two patches
 I sent? If so, did it work?
 
 Kazu

From: David McNab <mcnab@nas.nasa.gov>
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: i386/3462: using a PS/2 mouse causes kernel trap in 2.2.1
Date: Wed, 25 Jun 1997 10:18:41 -0700

 I still haven't tried the trap 29 patch.  I will try to
 get to it before the end of this week; there's a guy
 across the hall who wants me to help him install
 FreeBSD, so this will be a perfect chance.
 
   -- David
Responsible-Changed-From-To: freebsd-bugs->yokota 
Responsible-Changed-By: yokota 
Responsible-Changed-When: Thu Nov 13 20:33:10 PST 1997 
Responsible-Changed-Why:  
I have already talked with the originator in length. 
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Fri Mar 12 03:16:50 PST 1999 
State-Changed-Why:  
Originator switched to NetBSD, hasn't used FreeBSD since; thus 
reproducing the fault is going to be difficult. :-) 
>Unformatted:
