From owner-freebsd-current Sun May 21 19:56: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 250EB37BAB8 for ; Sun, 21 May 2000 19:55:55 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA04103; Sun, 21 May 2000 20:55:50 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id UAA66468; Sun, 21 May 2000 20:55:29 -0600 (MDT) Message-Id: <200005220255.UAA66468@billy-club.village.org> To: "Jordan K. Hubbard" Subject: Re: Anyone else seeing jumpy mice? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 May 2000 19:48:49 PDT." <3970.958963729@localhost> References: <3970.958963729@localhost> Date: Sun, 21 May 2000 20:55:28 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3970.958963729@localhost> "Jordan K. Hubbard" writes: : No, I don't mean rodents who've nibbled on chocolate-covered expresso : beans, I mean PS/2 mice which fall victim to this new problem: : : May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != 0000). : : I've seen it for the last few weeks and can only think that something : must be stomping on the psm driver now (or the driver is missing : interrupts for reasons of its own). Anyone else seeing this? I see this from time to time on whacked out mice that come into my posession. Sadly, I see it most on my laptop. It seems to happen less offten when I have PSM_HOOKRESUME PSM_RESETAFTERSUSPEND defined in my kernel config file. I've also seen this when I've tried to hot plug mice. This includes when power is lost to my KVM switch. When that happens, I gotta reboot all the machines that are attached to it since something is whacko at that point, I get those messages, or worse no mice and no message at all. I know one isn't supposed to hot plug mice, but there are times when one is using a KVM switch when it sure would be nice to reset the driver. Hmmm, there's a psmdetach. Is there anyway to force a device to be detached? I know unloading the driver will do it, but one can't unload the driver compiled into the kernel, can one? And even if you could, I'd run the risk of loading a driver that doesn't match my kernel. Hmmm, time for a good ioctl interface to newbus :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message