From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
"Justin P. Mattock" <justinmattock@gmail.com>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
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: Sat, 15 Nov 2008 12:36:15 +0100 [thread overview]
Message-ID: <200811151236.16748.rjw@sisk.pl> (raw)
In-Reply-To: <9b2b86520811150237r454b0a38l8d34f0e322573da@mail.gmail.com>
On Saturday, 15 of November 2008, Alan Jenkins wrote:
> On Sat, Nov 15, 2008 at 9:23 AM, Alexey Starikovskiy <aystarik@gmail.com> wrote:
> > Andrew Morton wrote:
> >>
> >> (cc linux-acpi)
> >>
> >> On Fri, 14 Nov 2008 20:16:17 -0800 "Justin P. Mattock"
> >> <justinmattock@gmail.com> wrote:
> >>
> >>
> >>>
> >>> just pulled the latest git today and am now noticing
> >>> the lovely gpe storm being triggered.(dmesg below);
> >>>
> >>
> >> Are any other effects observeable?
> >>
> >> I assume that 2.6.27 didn't do this.
> >>
> >>
> >
> > It did. Justin even opened a bug -- #11724.
>
> In case anyone else tries to follow that, it's actually #10724 :).
Yes, the "transaction in interrupt context" patch fixed that IIRC and the one
of the patches in the recet ACPI merge broke it again.
Justin, can you see if reverting one or more of the following commits helps:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8517934ef6aaa28d6e055b98df65b31cedbd1372
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=06cf7d3c7af902939cd1754abcafb2464060cba8
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0b7084ac67fb84f0cf2f8bc02d7e0dea8521dd2d
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a2f93aeadf97e870ff385030633a73e21146815d
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=dd15f8c42af09031e27da5b4d697ce925511f2e1
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f8248434e6a11d7cd314281be3b39bbcf82fc243
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594
(please revert in this order)?
Thanks,
Rafael
next prev parent reply other threads:[~2008-11-15 11: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 [this message]
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
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=200811151236.16748.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=aystarik@gmail.com \
--cc=justinmattock@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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