From: Vojtech Pavlik <vojtech@suse.cz>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Michael Buesch <mbuesch@freenet.de>, Simon Gate <simon@noir.se>,
linux-kernel@vger.kernel.org
Subject: Re: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Date: Tue, 17 Feb 2004 14:44:53 +0100 [thread overview]
Message-ID: <20040217134453.GA472@ucw.cz> (raw)
In-Reply-To: <Pine.GSO.4.33.0402161552520.28488-100000@sweetums.bluetronic.net>
On Mon, Feb 16, 2004 at 03:58:20PM -0500, Ricky Beam wrote:
> On Sat, 14 Feb 2004, Michael Buesch wrote:
> >> psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
> >>
> >> My mouse goes crazy for a few secs and then returns to normal for a while. Is this a 2.6.2 problem or is this is something old?
>
> I've seen this junk for many years. It's not limited to just 2.6.
>
> In my current environment, it's the KVM screwing with the mouse data...
> somehow it starts passing through 3 byte commands when the mouse is in
> 4 byte mode. I fixed it by a little trickery to force the mouse to
> reset (not a simple task from the ISR :-) BTW, 250ms is WAY to long to
> wait to detect a lose of sync; mice don't pause at all between bytes.)
Mice don't, but the kernel does, like when it's accessing the harddrive
heavily.
> >here's the fix:
> ...
>
> And exactly what is that supposed to be fixing?
>
> --Ricky
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-02-17 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 21:43 psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away Simon Gate
2004-02-14 21:59 ` Michael Buesch
2004-02-15 8:06 ` Vojtech Pavlik
2004-02-16 20:58 ` Ricky Beam
2004-02-17 13:44 ` Vojtech Pavlik [this message]
2004-02-15 8:06 ` Vojtech Pavlik
2004-02-22 16:23 ` aeriksson
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=20040217134453.GA472@ucw.cz \
--to=vojtech@suse.cz \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
--cc=simon@noir.se \
/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