public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-kernel@vger.kernel.org, dtor_core@ameritech.net
Subject: Re: pc keyboard driver spewing "Unknown key released"
Date: Mon, 20 Feb 2006 23:02:17 +0100	[thread overview]
Message-ID: <20060220220217.GA31968@suse.cz> (raw)
In-Reply-To: <20060220210240.GA15408@kvack.org>

On Mon, Feb 20, 2006 at 04:02:40PM -0500, Benjamin LaHaise wrote:

> With 2.6.16-rc4 on my laptop, I seem to be getting a lot of the following 
> spewed onto the console.  It's not reproducible on demand, but seems to be 
> related to multi-key press/release sequences when banging away a bit too 
> quickly...
> 
> 		-ben
> 
> atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0).
> atkbd.c: Use 'setkeycodes 7f <keycode>' to make it known.
 
Interesting. This is the '0xff' code sent by the keyboard (meaning "I'm
confused, someone pressed too many keys or is banging on me way too
quickly - I don't guarantee to send all keypresses or keyreleases
anymore") and is interpreted incorrectly by atkbd.c.

It should spew a different message ("Too many keys pressed") to your
console. 

If you can, please enable debugging for i8042, using

	echo -n 1 > /sys/module/i8042/parameters/debug

then try to reproduce it, and send your 'dmesg' to me.

-- 
Vojtech Pavlik
Director SuSE Labs

      reply	other threads:[~2006-02-20 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 21:02 pc keyboard driver spewing "Unknown key released" Benjamin LaHaise
2006-02-20 22:02 ` Vojtech Pavlik [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=20060220220217.GA31968@suse.cz \
    --to=vojtech@suse.cz \
    --cc=bcrl@kvack.org \
    --cc=dtor_core@ameritech.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