From: Michael Stiller <ms@2scale.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.15.1 input subsystem gets confused during IO
Date: Fri, 20 Jan 2006 08:03:58 +0100 [thread overview]
Message-ID: <1137740638.4435.15.camel@localhost.localdomain> (raw)
Hi list,
on my R51 machine the input subsystem gets very confused if
the machine is a bit loaded. If the machine does somewhat IO
(e.g. spamfiltering your evolution inbox via spamd and clamav)
the input subsystem becomes confused somewhat.
The mouse cursor jumps around, sometimes the keyboard has
interesting ideas about how much a key should be repeated.
Interesting dmesg output:
psmouse.c: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
psmouse.c: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
psmouse.c: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed.
atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0).
atkbd.c: Use 'setkeycodes 7f <keycode>' to make it known.
psmouse.c: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
psmouse.c: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
psmouse.c: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
psmouse.c: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed.
atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0).
atkbd.c: Use 'setkeycodes 7f <keycode>' to make it known.
The kernel is compiled with:
CONFIG_HZ_1000=y
CONFIG_DEFAULT_IOSCHED="anticipatory"
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
Any clues? Should i try some other config options?
-Michael
reply other threads:[~2006-01-20 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1137740638.4435.15.camel@localhost.localdomain \
--to=ms@2scale.net \
--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
all inboxes | Powered by JetHome®