public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Justin Mattock <justinmattock@gmail.com>
Cc: 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, 08 Jun 2008 01:27:24 +0400	[thread overview]
Message-ID: <484AFD3C.7080600@suse.de> (raw)
In-Reply-To: <dd18b0c30806071335j200daa9t517bf41ab10b2f@mail.gmail.com>

Justin Mattock wrote:
> Interesting, over here I'm using a Macbook Pro ATI chipset. I'm not
> experiencing things like missing keys or anything of that nature.
> but am concerned with what might happen to the hardware in the long
> run. As for the patches I did apply those,
> and it did give me a better idea of what is happening., but just to
> get a right info, when ACPI: EC: gpe storm detected message appears
> does it disable interrupt mode for that moment and then go back to it
> original state, or is it once the gpe storm is triggered the interupt
> mode is disabled until a reboot is performed. from looking at the data
> from the patches that I used from here it looks like something in the
> system triggers that message, but then after a few seconds  goes back
> to its original state, until another storm is detected.
> I don't have a problem with this message if it's triggering and then
> returning to it's original state until another storm triggers this
> message again, but I am concerned with the message being triggered,
> and then the system is stuck in that mode until a reboot.(but if this
> is O.K. for the system then that's cool too).
If interrupt storm from EC is detected EC interrupt will be disabled permanently.
EC driver then starts to poll hardware for events in half-second interval, so it is
still fully functional, but may be there is going to be impact on power consumption, etc.

Regards,
Alex.

  reply	other threads:[~2008-06-07 21:27 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 [this message]
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
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=484AFD3C.7080600@suse.de \
    --to=astarikovskiy@suse.de \
    --cc=akpm@linux-foundation.org \
    --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