From: Laurent Riffard <laurent.riffard@free.fr>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: Rene Herman <rene.herman@gmail.com>,
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 13:45:05 +0100 [thread overview]
Message-ID: <45950DD1.2010208@free.fr> (raw)
In-Reply-To: <4594ADAD.1030400@gmail.com>
Le 29.12.2006 06:54, Rene Herman a écrit :
> Dmitry Torokhov wrote:
>
>> On Friday 29 December 2006 00:17, Rene Herman wrote:
>
>>> 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?).
>
> Not even an analog camera, but with or without the above, I get a single:
>
> " <7>drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [ 902]"
>
> when it panics. During a full boot, I get:
>
> ===
[snip]
> ===
>
> Rene.
>
Dmitry,
How about this output? (got this after a kernel panic)
====
drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [35172]
drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [35172]
atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [35296]
drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [35297]
atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [35420]
drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [35421]
atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [35544]
drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [35545]
atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
===
~~
laurent
next prev parent reply other threads:[~2006-12-29 12:45 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
2006-12-29 5:54 ` Rene Herman
2006-12-29 12:45 ` Laurent Riffard [this message]
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=45950DD1.2010208@free.fr \
--to=laurent.riffard@free.fr \
--cc=davej@redhat.com \
--cc=dtor@insightbb.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