From: "Ernst Rohlicek jun." <ernst.rohlicek@inode.at>
To: linux-kernel@vger.kernel.org
Subject: 2.6.16_rc1 psmouse hangs without KVM
Date: Fri, 20 Jan 2006 17:15:37 +0100 [thread overview]
Message-ID: <43D10CA9.4030307@inode.at> (raw)
Hello list,
My first post to the linux-kernel mailing list - a little report on
mouse hang experiences on a PS/2 mouse :-)
Since the change from 2.6.14 to 2.6.16_rc1, I got mouse hangs using a
first-generation MS IntelliEye Explorer with USB->PS2 converter, no KVM,
which ran smoothly on the official 2.6.14.
The syslog message is ...
psmouse.c: resync failed, issuing reconnect request
and I have the exact symptoms - hang after about 10 sec mouse
inactivity, then after 2 secs it's back to normal - as described in the
thread ...
Date Mon, 9 Jan 2006 21:37:49 +0100
Subject Mouse stalls (again) with 2.6.15-mm2
between Jesper Juhl and Dmitry Torokhov.
(http://lkml.org/lkml/2006/1/9/313)
and a statement by Dmitry was to do resync retries every few seconds for
KVM users.
This certainly is a good idea for KVM users, but since Jesper and me are
counter-examples to this frequent resyncing, I suggest that this is made
an option in the kernel, like "KVM fixes - resync mouse in background".
I personally had to turn off resyncing using the suggested
echo -n 0 > /sys/bus/serio/devices/serioX/resync_time
to get back the expected fluent behavior, since without a KVM, there is
no automatic resyncing required ...
Of course I stand ready for corrections or for giving more detailed info
if required.
----
Ernst Rohlicek jun.
next reply other threads:[~2006-01-20 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 16:15 Ernst Rohlicek jun. [this message]
2006-01-20 16:38 ` 2.6.16_rc1 psmouse hangs without KVM Dmitry Torokhov
2006-01-22 13:35 ` Michael Stiller
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=43D10CA9.4030307@inode.at \
--to=ernst.rohlicek@inode.at \
--cc=linux-kernel@vger.kernel.org \
/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