From owner-freebsd-current Sun Jan 23 11:13:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 0C13A14C24 for ; Sun, 23 Jan 2000 11:13:53 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 20038 invoked from network); 23 Jan 2000 19:13:51 -0000 Received: from lcm97.cvzoom.net (208.230.69.97) by ns.cvzoom.net with SMTP; 23 Jan 2000 19:13:51 -0000 Date: Sun, 23 Jan 2000 14:13:17 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Moused hanging... 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 Hi, I've noticed a strange problem with vidcontrol and moused recently with current. I also had the same problem about 3 weeks back, and it doesn't seem to be occurring all that regularly. Here's what I was doing: I had just exited out of X, XFree86 Version 3.9.17. I had two sessions of bladeenc going simultaneously (if that even matters). I'm guessing maybe the issue is with the PCI bus being accessed by moused and the ATA driver at the same time, since bladeenc does generate some disk activity. Anyway, I heard a `pop' through my speakers, and at the same time, moused went dead. I su'd to root, killed and restarted moused. I could not get my moused cursor back (tried vidcontrol -m off ; vidcontrol -m on a couple of times). The only way I could get moused to work again was to reboot. (???) Actually, this is a minor issue, but it is an inconvenience, since I have to reboot to get vidcontrol to work again. I'm sure some people have seen this. The last time this happened, my mouse in X stopped responding. This time, though, no X was running. As for the cause, I'm sure it is a PCI/ISA bus issue. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message