From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Anthony DiSante <theant@nodivisions.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mouse still losing sync and thus jumping around
Date: Wed, 23 Feb 2005 22:18:56 -0500 [thread overview]
Message-ID: <200502232218.56665.dtor_core@ameritech.net> (raw)
In-Reply-To: <421D4460.6050308@nodivisions.com>
On Wednesday 23 February 2005 22:05, Anthony DiSante wrote:
> Dmitry Torokhov wrote:
> > Yes, It usually happens either under high load, when mouse interrupts are
> > significantly delayed. Or sometimes it happen when applications poll
> > battey status and on some boxes it takes pretty long time. And because
> > it is usually the same chip that serves keyboard/mouse it again delays
> > mouse interrupts.
>
> I have this problem with recent 2.6.10 kernels too, but it has nothing to do
> with load in my case; it happens whenever I switch my KVM to the linux box.
>
Hi Anthony,
This is a bit different problem and we trying to find a reliable solution
for it.
> Long ago and far away, it used to be that switching out of X, then back in
> (ctrl-alt-F1, then ctrl-alt-F7) would reset the mouse and stop the jumping.
> At some point in late 2.4/early 2.6 that stopped working, and the only fix
> was to unplug the mouse from the KVM switch and re-plug it.
>
> In Oct 2004 I posted to lkml with subject "KVM -> jumping mouse... still no
> solution?" Dmitry Torokhov (hi :) responded that this would work on 2.6.9-rc3+:
>
> echo -n "reconnect" > /sys/bus/serio/devices/serioX/driver
>
> That was GREAT and it worked for a while, but now my last few 2.6.10 kernels
> don't seem to care when I do that, and again, unplugging the mouse is the
> only thing that works. I'm currently running 2.6.10-gentoo-r6.
>
It still should work fine, but in a bit different form:
echo -n "reconnect" > /sys/bus/serio/devices/serioX/drvctl
I.e. substitute "driver" with "drvctl" as now "driver" is a symlink to
a currently bound driver that is set up by driver core.
--
Dmitry
next prev parent reply other threads:[~2005-02-24 3:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 13:22 mouse still losing sync and thus jumping around Nils Kalchhauser
2005-02-23 14:17 ` Dmitry Torokhov
2005-02-23 16:29 ` Nils Kalchhauser
2005-02-23 16:53 ` Dmitry Torokhov
2005-02-24 3:05 ` Anthony DiSante
2005-02-24 3:18 ` Dmitry Torokhov [this message]
2005-02-24 8:16 ` Anthony DiSante
-- strict thread matches above, loose matches on Subject: below --
2005-03-03 14:21 Bennie Kahler-Venter
2005-03-21 22:22 ` Andrew Morton
2005-05-25 22:07 ` Andrew Morton
2005-05-26 8:19 ` Bennie Kahler-Venter
2005-05-27 12:58 ` Bennie Kahler-Venter
2005-05-27 13:57 ` Dmitry Torokhov
2005-06-13 21:40 Voluspa
2005-06-13 21:47 ` Dmitry Torokhov
2005-06-13 23:45 ` Voluspa
2005-06-13 21:59 ` bhaskara
2005-06-13 22:03 ` Dmitry Torokhov
2005-06-13 22:22 ` bhaskara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200502232218.56665.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=theant@nodivisions.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox