From: Jesper Juhl <jesper.juhl@gmail.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: LKML List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: Mouse stalls (again) with 2.6.15-mm2
Date: Mon, 9 Jan 2006 21:46:19 +0100 [thread overview]
Message-ID: <9a8748490601091246m2adfa0a5pc455ed05758e43b6@mail.gmail.com> (raw)
In-Reply-To: <9a8748490601091237s57071e57mbd2c4172a0e4dd@mail.gmail.com>
On 1/9/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 12/21/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> > On 12/21/05, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > > On 12/11/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> > > > On 12/11/05, Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> > > >
> > > > > To stop resync attempts do:
> > > > >
> > > > > echo -n 0 > /sys/bus/serio/devices/serioX/resync_time
> > > > >
> > > > > where serioX is serio port asociated with your mouse.
> > > > >
> > > > This cures the problem nicely with no obvious ill effects with the
> > > > mouse plugged into the KVM...
> > > >
> > >
> > > Jesper,
> > >
> > > Could you please try applying the attached patch to -mm and see if you
> > > still have "resync failed" messages when you don't "echo 0" into
> > > resync_time attribute?
> > >
> > I applied the patch to 2.6.15-rc5-mm3, took out the "echo 0 to
> > resync_time" workaround that I had in rc.local and I no longer see the
> > "resync failed" messages in dmesg.
> > With this patch applied everything seems to be working OK with the
> > mouse attached to the KVM.
> >
>
> Hi Dmitry,
>
> I'm sorry to report that this problem made a comeback :-(
I guess I should mention that it's slightly different this time.
Last time the mouse would stall every 5 seconds regardless of it being
in motion or not. This time around the mouse doesn't stall if I keep
moving it. Only when I leave it still for ~10 seconds or more does it
stall when I then try to move it again. It stalls for something like 1
or 2 seconds, then moves fine until left alone for >= 10 sec again.
> With 2.6.15-mm2 I again get the mouse stalls and these messages in dmesg :
>
> [ 64.351000] psmouse.c: resync failed, issuing reconnect request
> [ 94.210000] psmouse.c: resync failed, issuing reconnect request
> [ 132.850000] psmouse.c: resync failed, issuing reconnect request
> [ 148.498000] psmouse.c: resync failed, issuing reconnect request
> [ 185.414000] psmouse.c: resync failed, issuing reconnect request
> [ 220.509000] psmouse.c: resync failed, issuing reconnect request
> [ 375.436000] psmouse.c: resync failed, issuing reconnect request
> [ 406.410000] psmouse.c: resync failed, issuing reconnect request
> [ 419.382000] psmouse.c: resync failed, issuing reconnect request
> [ 432.016000] psmouse.c: resync failed, issuing reconnect request
> [ 448.275000] psmouse.c: resync failed, issuing reconnect request
> [ 462.244000] psmouse.c: resync failed, issuing reconnect request
> [ 477.461000] psmouse.c: resync failed, issuing reconnect request
> [ 490.851000] psmouse.c: resync failed, issuing reconnect request
> [ 533.566000] psmouse.c: resync failed, issuing reconnect request
> [ 563.348000] psmouse.c: resync failed, issuing reconnect request
> [ 580.606000] psmouse.c: resync failed, issuing reconnect request
> [ 620.961000] psmouse.c: resync failed, issuing reconnect request
> [ 639.404000] psmouse.c: resync failed, issuing reconnect request
> [ 690.256000] psmouse.c: resync failed, issuing reconnect request
> [ 698.772000] psmouse.c: resync failed, issuing reconnect request
> [ 716.679000] psmouse.c: resync failed, issuing reconnect request
>
> 2.6.15 is fine.
>
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-01-09 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:37 Mouse stalls (again) with 2.6.15-mm2 Jesper Juhl
2006-01-09 20:46 ` Jesper Juhl [this message]
2006-01-09 20:56 ` Jesper Juhl
2006-01-09 20:59 ` Dmitry Torokhov
2006-01-13 6:54 ` Dmitry Torokhov
2006-01-13 14:10 ` Frank Sorenson
2006-01-14 6:01 ` Dmitry Torokhov
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=9a8748490601091246m2adfa0a5pc455ed05758e43b6@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.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;
as well as URLs for NNTP newsgroup(s).