From: Rene Herman <rene.herman@gmail.com>
To: Dave Jones <davej@redhat.com>,
Rene Herman <rene.herman@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
dmitry.torokhov@gmail.com
Subject: Re: [BUG 2.6.20-rc2] atkbd.c: Spurious ACK
Date: Thu, 28 Dec 2006 22:45:08 +0100 [thread overview]
Message-ID: <45943AE4.6080704@gmail.com> (raw)
In-Reply-To: <20061228191204.GB8940@redhat.com>
Dave Jones wrote:
> On Wed, Dec 27, 2006 at 10:32:53PM +0100, Rene Herman wrote:
>> The bug where the kernel repetitively emits "atkbd.c: Spurious ACK
>> on isa0060/serio0. Some program might be trying access hardware
>> directly" (sic) on a panic, thereby scrolling away the information
>> that would help in seeing what exactly the problem was (ie, "Unable
>> to mount root fs" or something) is still present in 2.6.20-rc2.
>
> Do you have a KVM ? Quite a few of those seem to tickle this printk.
No, regular old PS/2 keyboard, directly connected. Due to that exact
uneventfullness and having seen it reported before recently (*) I
assumed everyone was seeing this. If not, I guess I can try to narrow it
down.
It's easy to test for anyone willing: just boot with "root=/dev/null" or
something as a kernel param. The printk's are in sync with the panic
code blinking the leds.
(*) Here there was supposed to be a link to the post I was refferring
to, but googling for it led to http://lkml.org/lkml/2006/11/13/300
Dmitry, could you ask Linus to pull the change? I find this to be an
exceedingly annoying bug. It's just so incredibly silly, having one part
of the kernel helpfully blink leds at you with another part going "hey,
dude! don't do that!"
Rene.
next prev parent reply other threads:[~2006-12-28 21:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 21:32 [BUG 2.6.20-rc2] atkbd.c: Spurious ACK Rene Herman
2006-12-28 19:12 ` Dave Jones
2006-12-28 21:45 ` Rene Herman [this message]
2006-12-29 3:40 ` Dmitry Torokhov
2006-12-29 4:20 ` Rene Herman
2006-12-29 5:00 ` Dmitry Torokhov
2006-12-29 5:17 ` Rene Herman
2006-12-29 5:28 ` Dmitry Torokhov
2006-12-29 5:54 ` Rene Herman
2006-12-29 12:45 ` Laurent Riffard
2006-12-29 19:08 ` Rene Herman
2006-12-30 5:25 ` Dmitry Torokhov
2006-12-30 7:20 ` Rene Herman
2006-12-30 11:19 ` Laurent Riffard
2007-01-06 0:21 ` Tilman Schmidt
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=45943AE4.6080704@gmail.com \
--to=rene.herman@gmail.com \
--cc=davej@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--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