All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: ACPI: EC: GPE storm detected, transactions will use polling mode
Date: Sun, 16 Nov 2008 08:56:20 -0800	[thread overview]
Message-ID: <1226854580.3385.9.camel@LiNuX> (raw)
In-Reply-To: <491FECAE.6050005@gmail.com>

On Sun, 2008-11-16 at 12:49 +0300, Alexey Starikovskiy wrote:
> Justin P. Mattock wrote:
> > Well; reverting:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=06cf7d3c7af902939cd1754abcafb2464060cba8
> > is keeping the system from having a gpe storm
> > (for at least four hours now);
> > haven't had a chance to drain the battery and see
> > the affects from that scenario.
> >
> >   
> Justin, by decreasing threshold, we just change how often _detection_ of 
> the storm fires, not the storm itself.
> 
> Regards,
> Alex.

So increasing the threshold was a good thing
(reveal the problem, not hide the problem);
As for the cause itself, is there any tool
that can be used to at-least gain any info
on this? 
>From looking at the situation
from here with a macbook, the interaction with the battery
seems to be the cause, but then on other notebooks it's 
another situation.(making this problem very intricate).
Anyways I don't have a problem changing the threshold
or using a boot param, to keep this in somewhat control
for the time being until there is a solution.
let me know how I can help.
regards;

-- 
Justin P. Mattock <justinmattock@gmail.com>


      parent reply	other threads:[~2008-11-16 16:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15  4:16 ACPI: EC: GPE storm detected, transactions will use polling mode Justin P. Mattock
2008-11-15  6:43 ` Andrew Morton
2008-11-15  6:56   ` Justin P. Mattock
2008-11-15  9:23   ` Alexey Starikovskiy
2008-11-15 10:37     ` Alan Jenkins
2008-11-15 11:36       ` Rafael J. Wysocki
2008-11-15 12:06         ` Alan Jenkins
2008-11-15 18:39           ` Justin Mattock
2008-11-15 19:19             ` Rafael J. Wysocki
2008-11-15 19:45               ` Justin P. Mattock
2008-11-15 21:48               ` Justin P. Mattock
2008-11-16  6:41               ` Justin P. Mattock
2008-11-16  9:49                 ` Alexey Starikovskiy
2008-11-16 12:44                   ` Rafael J. Wysocki
2008-11-16 15:31                     ` Justin P. Mattock
2008-11-16 16:56                   ` Justin P. Mattock [this message]

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=1226854580.3385.9.camel@LiNuX \
    --to=justinmattock@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=aystarik@gmail.com \
    --cc=lenb@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.