From: Daniel Blueman <daniel.blueman@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: horrible usb keyboard bug with latest tests
Date: Fri, 12 Sep 2003 11:14:34 +0200 (MEST) [thread overview]
Message-ID: <9355.1063358074@www6.gmx.net> (raw)
I experienced some problems with the synaptics touchpad on a really old
laptop with linux-2.6.0-test4, where movement detected by the touchpad would
cause a stream of kernel messages to be logged.
I'll test again with test5. I doubt this is related to recent changes with
the posting events to the random pool on key and not mouse movement.
---
Andrew Morton <akpm@osdl.org> wrote in message
news:<uIA4.Pz.7@gated-at.bofh.it>...
> Andries Brouwer <aebr@win.tue.nl> wrote:
> >
> > > For me too, even with a normal keyboard attached to the PS/2 keyboard
port.
> > > In my case it's very rare, and not a 'constant stick' but short
'pulse' of
> > > the same character like displaying 'kkkkkkkkk' in my terminal even if
I'm
> > > sure that I didn't forget my finger on the key. OK, it's not a
showstopper
> > > bug, but sometimes annoying. It's 2.6.0-test3 (vanilla).
> >
> > Yes, I see this too, but very infrequently.
> >
> > For the 2.6 kernels key repeat is not taken from the keyboard but is
> > done via a kernel timer, and clearly the code is not quite correct.
> > I have not yet been able to detect it before I already
> > had hit the next key but maybe somebody else can answer:
> >
> > When does this repeat stop?
> > Does it stop because the next key has been hit?
> >
> > And: does it occur more often when the machine has high load?
>
> It happens to me madly on one of my machines. The machine is just some
> three-year-old PS/2 setup. It's due to mouse activity.
>
> To reproduce:
>
> 1: press and hold a key
>
> 2: start moving the mouse in large, rapid circles
>
> 3: release the key.
>
> The keystrokes continue to be inserted for an arbitrarily long period:
it's
> easy to generate thousands of them. The mouse has to be moved in circles:
> moving it from side-to-side causes small stops which allow things to
> correct themselves.
>
> It's quite irritating in practice.
--
Daniel J Blueman
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post
next reply other threads:[~2003-09-12 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 9:14 Daniel Blueman [this message]
2003-09-13 6:32 ` Mr. Mailing List
-- strict thread matches above, loose matches on Subject: below --
2003-09-11 12:57 Mr. Mailing List
2003-09-11 13:46 ` Gábor Lénárt
2003-09-11 15:23 ` Pau Aliagas
2003-09-11 21:38 ` Andries Brouwer
2003-09-11 22:32 ` Andrew Morton
2003-09-12 3:06 ` Alberto Bertogli
2003-09-11 22:40 ` Andries Brouwer
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=9355.1063358074@www6.gmx.net \
--to=daniel.blueman@gmx.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®