Re: [BUG 2.6.20-rc2] atkbd.c: Spurious ACK
From: Dmitry Torokhov
Date: Thu Dec 28 2006 - 22:41:12 EST
On Thursday 28 December 2006 16:45, Rene Herman wrote:
> 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
> 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!"
The change to suppress ACKs from paic blinking is already in Linus's tree.
I just tried booting with root=/dev/sdg and I had leds blinking but no
messages from atkbd were seen.
Could it be that you loaded older kernel by accident? Does anybody else
still seeing "Spurios ACK" messages during kernel panic?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/