From: "Justin Mattock" <justinmattock@gmail.com>
To: "Alexey Starikovskiy" <aystarik@gmail.com>
Cc: "Pavel Machek" <pavel@suse.cz>,
"Alexey Starikovskiy" <astarikovskiy@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: ACPI: EC: GPE storm detected, disabling EC GPE
Date: Wed, 11 Jun 2008 18:39:45 +0000 [thread overview]
Message-ID: <dd18b0c30806111139o2cb0f61m9b0bc2a1f1f4df00@mail.gmail.com> (raw)
In-Reply-To: <484FA90F.3010005@gmail.com>
On Wed, Jun 11, 2008 at 10:29 AM, Alexey Starikovskiy
<aystarik@gmail.com> wrote:
> Pavel Machek wrote:
>>
>> Hi!
>>
>> On Sat 2008-06-07 23:28:08, Alexey Starikovskiy wrote:
>>
>>>
>>> Justin Mattock wrote:
>>>
>>>>
>>>> On Sat, Jun 7, 2008 at 6:55 AM, Andrew Morton
>>
>>
>>>>
>>>> This issue just recently started, 2.6.25-rc9 and below don't give me
>>>> this message.
>>>>
>>>>
>>>
>>> Yes, the problem which we are fighting here is that almost all Acer
>>> notebooks come with
>>> broken EC. It sends interrupts not regarding the fact that we already
>>> ACKed it.
>>> It comes unnoticed on almost all machines (some notice laggy keyboard,
>>> because it's the same controller after all and it's busy with sending ACPI
>>> interrupts and then providing same status byte over and over), but on some
>>> machines keystrokes become missing, which is not tolerable (#9998).
>>>
>>
>> But the acer workaround breaks other machines, right?
>>
>>
>
> As I know, the first workaround broke your machine,
> may be you could check if it is broken now?
>>
>> So what about
>>
>> a) use dmi blacklist for acers?
>>
>>
>
> It is not only Acers. ASUS eeePC is known to be affected, some Apple
> notebook too.
>>
>> or
>>
>> b) if EC storm is detected print message telling 'please pass
>> ec_polled=true if you experience keyboard problems', but do nothing
>> else?
>>
>>
>
> There are no reports about broken machines for 2.6.26-rc5 beside #10724,
> which has same broken controller, sending same amount of stray interrupts.
> If there will be report from a good machine affected by this workaround then
> I will
> certainly go with b)
>
> Thanks,
> Alex.
>
>
>
FWIW: just to let you guys know over here with a Macbook Pro ATI
chipset, as a small test removing the battery
I did not receive this message after 5+ hours of uptime. Normally on a
good run with the battery attached I get around an hour or so before
this triggers.
regards;
--
Justin P. Mattock
next prev parent reply other threads:[~2008-06-11 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 6:21 Justin Mattock
2008-06-07 6:55 ` Andrew Morton
2008-06-07 10:59 ` Maxim Levitsky
2008-06-07 14:31 ` Guillaume Chazarain
2008-06-07 15:47 ` Justin Mattock
2008-06-07 19:28 ` Alexey Starikovskiy
2008-06-07 20:35 ` Justin Mattock
2008-06-07 21:27 ` Alexey Starikovskiy
2008-06-07 23:20 ` Justin Mattock
2008-06-08 14:21 ` Pavel Machek
2008-06-11 10:29 ` Alexey Starikovskiy
2008-06-11 18:39 ` Justin Mattock [this message]
2008-06-10 15:30 ` Len Brown
2008-06-10 18:37 ` Justin Mattock
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=dd18b0c30806111139o2cb0f61m9b0bc2a1f1f4df00@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=astarikovskiy@suse.de \
--cc=aystarik@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®