From: Andries Brouwer <aebr@win.tue.nl>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andries Brouwer <aebr@win.tue.nl>,
fire-eyes <sgtphou@fire-eyes.dynup.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.1: atkbd.c errors + mouse errors with a belkin KVM
Date: Mon, 19 Jan 2004 22:40:36 +0100 [thread overview]
Message-ID: <20040119224036.A1101@pclin040.win.tue.nl> (raw)
In-Reply-To: <20040119204348.GA2251@ucw.cz>; from vojtech@suse.cz on Mon, Jan 19, 2004 at 09:43:48PM +0100
On Mon, Jan 19, 2004 at 09:43:48PM +0100, Vojtech Pavlik wrote:
> > > kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on
> > > isa0060/serio0).
> >
> > It is not really an error - the kernel is just being a bit noisy.
> > The 0x7a was really 0xfa, the ACK that a keyboard command succeeded.
> >
> > Sooner or later the noise will go away. For now it is more interesting
> > to fix bugs in behaviour.
>
> Well, the kernel is quite rightfully noisy at this point - getting
> unexpected ACKs is rather suspicious.
Yes, I do not propose that you remove the noise today.
But nothing is wrong.
Several utilities access the keyboard directly. (For example X and kbdrate.)
Since setting keyboard rate and starting X are rather common actions,
most people will see these messages a few times in their syslog.
A few months from now, when we are satisfied that the keyboard code
is in perfect shape, these messages can be silenced by default.
Andries
next prev parent reply other threads:[~2004-01-19 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 18:08 2.6.1: atkbd.c errors + mouse errors with a belkin KVM fire-eyes
2004-01-19 19:29 ` Andries Brouwer
2004-01-19 20:43 ` Vojtech Pavlik
2004-01-19 21:40 ` Andries Brouwer [this message]
2004-01-19 21:50 ` Vojtech Pavlik
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=20040119224036.A1101@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sgtphou@fire-eyes.dynup.net \
--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