From owner-freebsd-current  Sat Dec 16 12:35:34 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA29667
          for current-outgoing; Sat, 16 Dec 1995 12:35:34 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA29658
          for <freebsd-current@freebsd.org>; Sat, 16 Dec 1995 12:35:30 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA09302; Sun, 17 Dec 1995 07:32:16 +1100
Date: Sun, 17 Dec 1995 07:32:16 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199512162032.HAA09302@godzilla.zeta.org.au>
To: freebsd-current@freebsd.org, roberto@keltia.freenix.fr
Subject: Re: Mouse not working for two days
Sender: owner-current@freebsd.org
Precedence: bulk

>There have been great  changes in -CURRENT these  days and I'd like to know
>which one broke my mouse under X11... 

>The pointer is there, interrupts are generated but the pointer doesn't move
>at all when one moves it. 

Some buggy 16650 came in unannounced with the staticization changes.  
It breaks COM_NOFIFO() for at least 16650's and stops the output fifo
being used at speeds <= 4800.  These bugs shouldn't matter for mouses.
Perhaps the second bug interferes with the SMC bugfix (what happens
when the fifos are reset while the fifos are not enabled?).

Try using sio.c revision 1.126 or earlier.

Bruce