From: Christopher Fraser <chrisf@filmlight.ltd.uk>
To: linux-kernel@vger.kernel.org
Subject: Mouse and keyboard problems with 2.6.0-test9
Date: Tue, 28 Oct 2003 19:26:09 +0000 [thread overview]
Message-ID: <3F9EC2D1.1050707@filmlight.ltd.uk> (raw)
I've been having mouse and keyboard problems with kernels since
2.6.0-test6 (at least). The machine I'm testign with has a Supermicro
X5DA8 (Intel E7507 chipset) motherboard with two 3Ghz Xeon CPUs and was
install with Red Hat 9 and updates modutils, kinitrd etc.
When doing large amounts of I/O (we're reading > 300MB/s from disk,
processing it and downloading it across AGP) while running XFree86 the
psmouse gets into a state where it loses synchronisation and cannot
recover. The pointer warps to the top right of the desktop and moving
the mouse generates spurious mouse down events. Switching to a virtual
console and back to the X desktop sometimes recovers, but usually not.
I've tried the psmouse_noext option, various rates including 200 (which
seemed to make things better for a while) and the recent psmouse_rate
with the rate to 0 without success. I've also tried a generic Dell
wheelmouse and and one of those optical Microsoft Intellimouse things.
The keyboard problem is that atkbd.c gets into a state where it starts
generating message like the following for each key press:
Unknown key pressed (translated set 2, code 0x0, data 0x0, on
isa0060/serio0)
These flood the console, making the machine difficult to use. This
mostly happens when I switch between XFree86 and virtual consoles, so it
may be due to my generic PS2 keyboard generating spurious release events
(as mentioned previously
<http://www.ussg.iu.edu/hypermail/linux/kernel/0309.1/2185.html>).
Commenting out the warning in atkdb.c makes the console usable again.
Any suggestions on things to try would be greatfully appreciated.
Regards,
Christopher.
reply other threads:[~2003-10-28 19:26 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=3F9EC2D1.1050707@filmlight.ltd.uk \
--to=chrisf@filmlight.ltd.uk \
--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®