From: Jan De Luyck <lkml@kcore.org>
To: Konstantin Kletschke <konsti@ludenkalle.de>,
linux-kernel@vger.kernel.org
Cc: lkml@kcore.org
Subject: Re: Success stories, disappearing Oopses and ps/2 keyboard
Date: Wed, 25 Jun 2003 11:27:37 +0200 [thread overview]
Message-ID: <200306251127.37944.lkml@kcore.org> (raw)
In-Reply-To: <20030625081313.GA1747@sexmachine.doom>
On Wednesday 25 June 2003 10:13, Konstantin Kletschke wrote:
> No, that would be no Problem. Often, if I browse in mutt and press Arrow
> Keys, it is autorepeated suddenly but I only pressed the Key shortly!
> The Kernel does not realize it is released since ages. Pressing again
> the kernel stops repeating. That happens with all keys and when with
> arrow or PageUp/Down keys in slrn it drives me mad!
I have seen this problem ever since I started using 2.5 on my laptop. I can
easily recreate it by pressing two keys at the same time, it seems that then
something gets screwed up and he repeats one of the two keys 20-30 times when
it stops.
I'll test with that clock=pit option later, when I have the chance to reboot.
Jan
--
Q: How did you get into artificial intelligence?
A: Seemed logical -- I didn't have any real intelligence.
next prev parent reply other threads:[~2003-06-25 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 16:40 Success stories, disappearing Oopses and ps/2 keyboard Konstantin Kletschke
2003-06-24 21:04 ` medium Oops on 2.5.73-mm1 Konstantin Kletschke
2003-06-24 21:22 ` Andrew Morton
2003-06-24 22:04 ` Konstantin Kletschke
2003-06-24 22:30 ` Success stories, disappearing Oopses and ps/2 keyboard john stultz
2003-06-25 8:13 ` Konstantin Kletschke
2003-06-25 9:27 ` Jan De Luyck [this message]
2003-06-25 13:23 ` Konstantin Kletschke
2003-06-25 13:41 ` Konstantin Kletschke
2003-06-26 17:29 ` Robert Schwebel
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=200306251127.37944.lkml@kcore.org \
--to=lkml@kcore.org \
--cc=konsti@ludenkalle.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.