From: Kronos <kronos@kronoz.cjb.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.3] Mouse loosing sync (again)
Date: Fri, 27 Feb 2004 22:34:26 +0100 [thread overview]
Message-ID: <20040227213426.GA28041@dreamland.darkstar.lan> (raw)
In-Reply-To: <20040227212346.GA981@ucw.cz>
Il Fri, Feb 27, 2004 at 10:23:46PM +0100, Vojtech Pavlik ha scritto:
> On Fri, Feb 27, 2004 at 10:08:01PM +0100, Kronos wrote:
>
> > > > These happened while surfing web with little activity on eth0 and while disks
> > > > were almost idle (-u1 is set on both of them). Using vmstat I see that
> > > > I'm getting around 1300 interrupts per second while moving mouse (less
> > > > than 1100 while doing nothing), so I don't think that there's something
> > > > spinning in ISR for too long.
> > > >
> > > > Problem first appeared in 2.6.2, 2.6.1 is unaffected. I see that in
> > > > 2.6.3 there's a patch which is supposed to fix this, but it still
> > > > happens for me.
> > > >
> > > > Any clue?
> > >
> > > The bad parity messages definitely suggest a problem with the mouse
> > > cable - either too long or broken.
> >
> > Hum, but why does it work with older kernels? If I boot with 2.6.1 it
> > works without problems.
>
> 2.6.1 ignores bad parity in mouse data.
Oh, I see. Thanks for the clarification, I'll try and see if I can
reproduce with another mouse.
Luca
--
Home: http://kronoz.cjb.net
"L'ottimista pensa che questo sia il migliore dei mondi possibili.
Il pessimista sa che e` vero" -- J. Robert Oppenheimer
prev parent reply other threads:[~2004-02-27 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 20:14 Kronos
2004-02-27 21:00 ` Vojtech Pavlik
2004-02-27 21:08 ` Kronos
2004-02-27 21:23 ` Vojtech Pavlik
2004-02-27 21:34 ` Kronos [this message]
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=20040227213426.GA28041@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®