public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: Rene Herman <rene.herman@gmail.com>
Cc: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 2.6.20-rc2] atkbd.c: Spurious ACK
Date: Fri, 29 Dec 2006 00:28:01 -0500	[thread overview]
Message-ID: <200612290028.01531.dtor@insightbb.com> (raw)
In-Reply-To: <4594A4DC.5090404@gmail.com>

On Friday 29 December 2006 00:17, Rene Herman wrote:
> Dmitry Torokhov wrote:
> 
> >>> 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?
> >> Well, no, I'm really on 2.6.20-rc2, from a freshly cloned tree. And I do 
> >> get atkbd.c complaining at me when I boot with root=/dev/wrong-device.
> >>
> >> Could you point me to the changeset in question? I couldn't find it 
> >> searching for "leds" in the log.
> >>
> > 
> > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=817e6ba3623de9cdc66c6aba90eae30b5588ff11
> 
> Yes, I do have that in my tree. From the looks of it it's probably not 
> surprising, but the following gets me blinking leds without the spurious 
> ACK messages. Maybe still useful to know?
> 
> diff --git a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c
> index debe944..9c70d34 100644
> --- a/drivers/input/serio/i8042.c
> +++ b/drivers/input/serio/i8042.c
> @@ -371,7 +371,7 @@ static irqreturn_t i8042_interrupt(int i
>   	if (unlikely(i8042_suppress_kbd_ack))
>   		if (port_no == I8042_KBD_PORT_NO &&
>   		    (data == 0xfa || data == 0xfe)) {
> -			i8042_suppress_kbd_ack = 0;
> +			/* i8042_suppress_kbd_ack = 0; */
>   			goto out;

That would indicate that your keyboard generates multiple acks... I wonder
if you could boot with i8042.debug=1 and somehow capture the data flow
during panic (do you have a digital camera?).

-- 
Dmitry

  reply	other threads:[~2006-12-29  5:28 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
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 [this message]
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=200612290028.01531.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@gmail.com \
    /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