From owner-freebsd-current Mon May 22 14: 8:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from ucsu.Colorado.EDU (ucsu.Colorado.EDU [128.138.129.83]) by hub.freebsd.org (Postfix) with ESMTP id 2A33937BC5D for ; Mon, 22 May 2000 14:08:55 -0700 (PDT) (envelope-from vinson@ucsu.Colorado.EDU) Received: from localhost (vinson@localhost) by ucsu.Colorado.EDU (8.9.3/8.9.3/ITS-5.0/standard) with SMTP id PAA03883 for ; Mon, 22 May 2000 15:08:55 -0600 (MDT) Date: Mon, 22 May 2000 15:08:55 -0600 (MDT) From: VINSON WAYNE HOWARD To: current@FreeBSD.org Subject: Re: Anyone else seeing jumpy mice? In-Reply-To: <17882.959025378@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While it's nice to supposedly have narowed this down to the SMP cleanup, that doesn't make those of us who are running single processor machines very cofident that the bug's been found. Here's my guess: there may be something interupt driven related to the SMP stuff, but there's also something wrong with moused, as at least two people (one being myself) have said that going to direct reading of the device eliminted their problem. I just didn't want the legitimate bug reports from single processor users to be lost in the search for a SMP cause. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message