From owner-freebsd-current  Thu Jan 22 17:35:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA11830
          for current-outgoing; Thu, 22 Jan 1998 17:35:35 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dragondata.com (home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11820
          for <FreeBSD-Current@FreeBSD.ORG>; Thu, 22 Jan 1998 17:35:31 -0800 (PST)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.5/8.8.5) id TAA27091;
	Thu, 22 Jan 1998 19:35:14 -0600 (CST)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199801230135.TAA27091@home.dragondata.com>
Subject: Re: PS/2 Mouse Problems
In-Reply-To: <Pine.BSF.3.96.980122191928.392A-100000@liquid.binc.net> from Andrew Bazan at "Jan 22, 98 07:23:14 pm"
To: subcero@binc.net (Andrew Bazan)
Date: Thu, 22 Jan 1998 19:35:13 -0600 (CST)
Cc: FreeBSD-Current@FreeBSD.ORG
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-freebsd-current@FreeBSD.ORG
Precedence: bulk

> 	Hi,
> 
> I recently upgraded my system from 2.2.5-STABLE to 3.0-CURRENT -- did a
> complete harddrive flush (not really my choice) and reinstalled
> everything. Ever since I upgraded to -CURRENT, my PS/2 mouse has been
> giving me an immense amount of trouble. Basically, I don't usually run
> moused, and the first time I entered X and tried to move my mouse my
> harddrive made a bad crunching noise for a few seconds, and my mouse
> didn't move -- after awhile, I got a kernel error.
> 
> I've CVSUP'd my sources, and I have the latest kernel as of about 3 this
> afternoon. I've had the problem with all the builds, and have no clue
> what's going on. I tried running moused to see if that would help
> anything, but it just crunched my harddrive when I moved the mouse and
> somehow (???) screwed up /proc so that I get a '/proc size mismatch' when
> I try to use a program that accesses it. I've tried all the easy solutions
> I can think of, and I'm wondering if this is a bug I haven't heard about
> in the kernel, or if it's just a new config issue I have to deal with.
> 
> Thanks for your time,
> 
> Andrew
> 
> 

You wouldn't happen to be sharing your PS/2 mouse port IRQ with something
else, would you?

Kevin