public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: Justin Mattock <justinmattock@gmail.com>,
	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: Sun, 8 Jun 2008 16:21:06 +0200	[thread overview]
Message-ID: <20080608142106.GD4739@ucw.cz> (raw)
In-Reply-To: <484AE148.6000204@suse.de>

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?

So what about

a) use dmi blacklist for acers?

or

b) if EC storm is detected print message telling 'please pass
ec_polled=true if you experience keyboard problems', but do nothing
else?

							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2008-06-11 10:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dd18b0c30806062321x2918f6feq7c817bde52ba0c4c@mail.gmail.com>
2008-06-07  6:55 ` ACPI: EC: GPE storm detected, disabling EC GPE 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 [this message]
2008-06-11 10:29         ` Alexey Starikovskiy
2008-06-11 18:39           ` Justin Mattock
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=20080608142106.GD4739@ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=astarikovskiy@suse.de \
    --cc=justinmattock@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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