From: Pavel Machek <pavel@suse.cz>
To: Jurriaan on adsl-gate <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: Keyboard on ... reports too many keys pressed
Date: Mon, 16 Feb 2004 12:52:22 +0100 [thread overview]
Message-ID: <20040216115221.GC470@openzaurus.ucw.cz> (raw)
In-Reply-To: <20040207064027.GA20495@gates.of.nowhere>
Hi!
> On my laptop, I get a lot of
>
> Keyboard on ... reports too many keys pressed.
>
> That may well be the case, I use my normal hands on a small
> laptop-keyboard.
> Why is that message printed? There nothing I can do about pressing
> multiple keys by accident, so I don't think it's useful.
>
> It does, however, frequently mess up the commandline, which leads to big
> frustration.
>
> Couldn't this be wrapped in #ifdef ATKBD_DEBUG or something? Is it
> really necessary to see this message?
Its error condition -- keyboard lost track of keys -- and
yes thats worth a printk. Try running klogd.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
prev parent reply other threads:[~2004-02-16 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 6:40 Keyboard on ... reports too many keys pressed Jurriaan on adsl-gate
2004-02-16 11:52 ` Pavel Machek [this message]
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=20040216115221.GC470@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
--cc=vojtech@suse.cz \
/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