On 1/9/06, Jesper Juhl <[email protected]> wrote:
> On 12/21/05, Jesper Juhl <[email protected]> wrote:
> > On 12/21/05, Dmitry Torokhov <[email protected]> wrote:
> > > On 12/11/05, Jesper Juhl <[email protected]> wrote:
> > > > On 12/11/05, Dmitry Torokhov <[email protected]> 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 <[email protected]>
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]