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 :-(
> With 2.6.15-mm2 I again get the mouse stalls and these messages in dmesg :
>
Jesper,
I am sorry, I have not sent updated patch to Andrew yet - I am trying
to figure some ALPS quicks with Frank. I think if you apply that patch
I sent earlier your mouse will work fine.
Sorry about that.
--
Dmitry
-
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]