From owner-freebsd-current Sun Jan 23 20:58:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 51474158D1 for ; Sun, 23 Jan 2000 20:58:08 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:L77xthDu81M0YIj4VmdSa7MRDhYUVgw4@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id NAA18040; Mon, 24 Jan 2000 13:57:44 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id OAA20809; Mon, 24 Jan 2000 14:03:19 +0900 (JST) Message-Id: <200001240503.OAA20809@zodiac.mech.utsunomiya-u.ac.jp> To: Donn Miller Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Moused hanging... In-reply-to: Your message of "Sun, 23 Jan 2000 14:13:17 EST." References: Date: Mon, 24 Jan 2000 14:03:18 +0900 From: Kazutaka YOKOTA 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. What type of mouse is it, PS/2, serial, or USB? Is the power supply in your system big enough? Is the mouse's cable and connector look OK? >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 cannot immediately see why only the mouse suddenly died, while the rest of the system was healthy, >I su'd to root, killed and >restarted moused. Please try `kill -HUP' to moused next time. This will make moused reopen the mouse port. >I could not get my moused cursor back (tried vidcontrol >-m off ; vidcontrol -m on a couple of times). I never heard this before. When did you make this kernel? Would you tell me the revision number of /sys/dev/syscons/syscons.c and /sys/dev/syscons/scmouse.c? >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. I am not sure. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message