public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
	Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI <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 07:31:35 -0800	[thread overview]
Message-ID: <B407D583-A440-402B-AB35-D69BA464F5AD@gmail.com> (raw)
In-Reply-To: <200811161344.07872.rjw@sisk.pl>

Cool,
Then I'll just leave it as is
And move on to other tasks that I have. Thanks for the info and help

Regards;

justin P. Mattock



On Nov 16, 2008, at 4:44 AM, "Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Sunday, 16 of November 2008, 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.
>
> Yes, I think what happens is that we just detect the interrupt storm  
> with the
> lower threshold, so the storm occured anyway previously, but it went  
> unnoticed
> (not necessarily a good thing).
>
> There is nothing to worry about as long as the box works as expected.
>
> Thanks,
> Rafael

  reply	other threads:[~2008-11-16 15:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1226722577.3104.4.camel@LiNuX>
2008-11-15  6:43 ` ACPI: EC: GPE storm detected, transactions will use polling mode 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 [this message]
2008-11-16 16:56                   ` Justin P. 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=B407D583-A440-402B-AB35-D69BA464F5AD@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox