With 2.6.5-rc5-mm2 I'm getting regular mouse stalls for short periods
of time ~1sec
I'm also seeing this in dmesg :
[ 117.308573] psmouse.c: resync failed, issuing reconnect request
[ 157.100063] psmouse.c: resync failed, issuing reconnect request
[ 167.583936] psmouse.c: resync failed, issuing reconnect request
[ 278.986267] psmouse.c: resync failed, issuing reconnect request
[ 328.320242] psmouse.c: resync failed, issuing reconnect request
[ 358.117414] psmouse.c: resync failed, issuing reconnect request
[ 472.814321] psmouse.c: resync failed, issuing reconnect request
[ 492.781941] psmouse.c: resync failed, issuing reconnect request
[ 525.788327] psmouse.c: resync failed, issuing reconnect request
[ 542.843044] psmouse.c: resync failed, issuing reconnect request
[ 552.129681] psmouse.c: resync failed, issuing reconnect request
The times correspond nicely to the mouse stalls, every time it stalls
I get a new line, so they are definately related.
2.6.5-rc5-git1 works flawlessly.
No hardware has changed.
Mouse is a Logitech MouseMan Wheel (M/N: M-BD53) connected to a
"Master View PRO" KVM switch.
Comlete dmesg output, .config, ver_linux output, lspci output, lsusb
output and cat /proc/cpuinfo output attached. Please just ask if
anything else is needed.
--
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
On Sunday 11 December 2005 08:48, Jesper Juhl wrote:
> With 2.6.5-rc5-mm2 I'm getting regular mouse stalls for short periods
> of time ~1sec
> I'm also seeing this in dmesg :
>
> [ 117.308573] psmouse.c: resync failed, issuing reconnect request
> [ 157.100063] psmouse.c: resync failed, issuing reconnect request
> [ 167.583936] psmouse.c: resync failed, issuing reconnect request
> [ 278.986267] psmouse.c: resync failed, issuing reconnect request
> [ 328.320242] psmouse.c: resync failed, issuing reconnect request
> [ 358.117414] psmouse.c: resync failed, issuing reconnect request
> [ 472.814321] psmouse.c: resync failed, issuing reconnect request
> [ 492.781941] psmouse.c: resync failed, issuing reconnect request
> [ 525.788327] psmouse.c: resync failed, issuing reconnect request
> [ 542.843044] psmouse.c: resync failed, issuing reconnect request
> [ 552.129681] psmouse.c: resync failed, issuing reconnect request
>
> The times correspond nicely to the mouse stalls, every time it stalls
> I get a new line, so they are definately related.
>
> 2.6.5-rc5-git1 works flawlessly.
> No hardware has changed.
> Mouse is a Logitech MouseMan Wheel (M/N: M-BD53) connected to a
> "Master View PRO" KVM switch.
>
> Comlete dmesg output, .config, ver_linux output, lspci output, lsusb
> output and cat /proc/cpuinfo output attached. Please just ask if
> anything else is needed.
>
Could you please do the following:
1. echo 1 > /sys/modules/i8042/parameters/debug
2. switch away from your linux box
3. wait 5 seconds
4. Switch back to Linux box
5. Move mouse slightly
6. echo 0 > /sys/modules/i8042/parameters/debug
7. Send me dmesg
Also, does the resync fail if you are not using KVM and plug the mouse
directly into the box.
To stop resync attempts do:
echo -n 0 > /sys/bus/serio/devices/serioX/resync_time
where serioX is serio port asociated with your mouse.
Thanks!
--
Dmitry
On 12/11/05, Dmitry Torokhov <[email protected]> wrote:
> On Sunday 11 December 2005 08:48, Jesper Juhl wrote:
> > With 2.6.5-rc5-mm2 I'm getting regular mouse stalls for short periods
> > of time ~1sec
> > I'm also seeing this in dmesg :
> >
> > [ 117.308573] psmouse.c: resync failed, issuing reconnect request
> > [ 157.100063] psmouse.c: resync failed, issuing reconnect request
> > [ 167.583936] psmouse.c: resync failed, issuing reconnect request
> > [ 278.986267] psmouse.c: resync failed, issuing reconnect request
> > [ 328.320242] psmouse.c: resync failed, issuing reconnect request
> > [ 358.117414] psmouse.c: resync failed, issuing reconnect request
> > [ 472.814321] psmouse.c: resync failed, issuing reconnect request
> > [ 492.781941] psmouse.c: resync failed, issuing reconnect request
> > [ 525.788327] psmouse.c: resync failed, issuing reconnect request
> > [ 542.843044] psmouse.c: resync failed, issuing reconnect request
> > [ 552.129681] psmouse.c: resync failed, issuing reconnect request
> >
> > The times correspond nicely to the mouse stalls, every time it stalls
> > I get a new line, so they are definately related.
> >
> > 2.6.5-rc5-git1 works flawlessly.
> > No hardware has changed.
> > Mouse is a Logitech MouseMan Wheel (M/N: M-BD53) connected to a
> > "Master View PRO" KVM switch.
> >
> > Comlete dmesg output, .config, ver_linux output, lspci output, lsusb
> > output and cat /proc/cpuinfo output attached. Please just ask if
> > anything else is needed.
> >
>
> Could you please do the following:
>
Sure thing.
> 1. echo 1 > /sys/modules/i8042/parameters/debug
> 2. switch away from your linux box
> 3. wait 5 seconds
> 4. Switch back to Linux box
> 5. Move mouse slightly
> 6. echo 0 > /sys/modules/i8042/parameters/debug
> 7. Send me dmesg
>
Find dmesg.txt attached.
> Also, does the resync fail if you are not using KVM and plug the mouse
> directly into the box.
>
well, unplugging the mouse from the KVM and plugging it into the PC's
PS/2 port directly resulted in this in dmesg :
[ 567.297724] psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost
synchronization, throwing 1 bytes away.
[ 567.807251] psmouse.c: resync failed, issuing reconnect request
[ 568.015721] logips2pp: Detected unknown logitech mouse model 87
and after that I see no more resync failed messages and the mouse doesn't stall.
> 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 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
On Sunday 11 December 2005 14:49, Jesper Juhl wrote:
> well, unplugging the mouse from the KVM and plugging it into the PC's
> PS/2 port directly resulted in this in dmesg :
>
> [ 567.297724] psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost
> synchronization, throwing 1 bytes away.
> [ 567.807251] psmouse.c: resync failed, issuing reconnect request
> [ 568.015721] logips2pp: Detected unknown logitech mouse model 87
>
> and after that I see no more resync failed messages and the mouse doesn't stall.
>
Ok, so your KVM fakes the response to POLL command. But normally
(with resync disabled) your mouse works just fine with your KVM,
you can still use wheel after switching between the boxes, right?
If so I will try adjusting my patch.
In the mean time could you please try the tiny patch below - it
shoudl get rid of "unknown logitech mouse" message. Could you send
me your dmesg after applying the patch?
Thanks!
--
Dmitry
Subject: logips2pp: add signature of MouseMan Wheel Mouse (87)
Input: logips2pp - add signature of MouseMan Wheel Mouse (87)
Signed-off-by: Dmitry Torokhov <[email protected]>
---
drivers/input/mouse/logips2pp.c | 1 +
1 files changed, 1 insertion(+)
Index: work/drivers/input/mouse/logips2pp.c
===================================================================
--- work.orig/drivers/input/mouse/logips2pp.c
+++ work/drivers/input/mouse/logips2pp.c
@@ -228,6 +228,7 @@ static struct ps2pp_info *get_model_info
{ 83, PS2PP_KIND_WHEEL, PS2PP_WHEEL },
{ 85, PS2PP_KIND_WHEEL, PS2PP_WHEEL },
{ 86, PS2PP_KIND_WHEEL, PS2PP_WHEEL },
+ { 87, PS2PP_KIND_WHEEL, PS2PP_WHEEL },
{ 88, PS2PP_KIND_WHEEL, PS2PP_WHEEL },
{ 96, 0, 0 },
{ 97, PS2PP_KIND_TP3, PS2PP_WHEEL | PS2PP_HWHEEL },
On 12/12/05, Dmitry Torokhov <[email protected]> wrote:
> On Sunday 11 December 2005 14:49, Jesper Juhl wrote:
> > well, unplugging the mouse from the KVM and plugging it into the PC's
> > PS/2 port directly resulted in this in dmesg :
> >
> > [ 567.297724] psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost
> > synchronization, throwing 1 bytes away.
> > [ 567.807251] psmouse.c: resync failed, issuing reconnect request
> > [ 568.015721] logips2pp: Detected unknown logitech mouse model 87
> >
> > and after that I see no more resync failed messages and the mouse doesn't stall.
> >
>
> Ok, so your KVM fakes the response to POLL command. But normally
> (with resync disabled) your mouse works just fine with your KVM,
> you can still use wheel after switching between the boxes, right?
The wheel works fine after switching away and back.
> If so I will try adjusting my patch.
>
> In the mean time could you please try the tiny patch below - it
> shoudl get rid of "unknown logitech mouse" message. Could you send
> me your dmesg after applying the patch?
>
Patch seems to do its job :
$ dmesg | grep -i mouse
[ 24.039229] mice: PS/2 mouse device common for all mice
[ 24.790995] input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
[ 192.060997] psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost
synchronization, throwing 1 bytes away.
[ 192.569915] psmouse.c: resync failed, issuing reconnect request
Thanks.
--
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
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?
Thank you in advance,
Dmitry
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.
> Thank you in advance,
>
Thank /you/ for fixing it. :-)
--
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