Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754454AbYKPQ4j (ORCPT ); Sun, 16 Nov 2008 11:56:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753555AbYKPQ42 (ORCPT ); Sun, 16 Nov 2008 11:56:28 -0500 Received: from wa-out-1112.google.com ([209.85.146.178]:35546 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753509AbYKPQ41 (ORCPT ); Sun, 16 Nov 2008 11:56:27 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=LlMVvJq29lHfmVTWqOdDNHzrIzJxOMbcOX0ihGQtkW/6sGXKfwElOEZCBOavTHvQcZ g5mScebuO1v2B/Z3R76M6Fr+xdKox+j1fl8FWdjpcAHCmfbSHGoY+uku9hoF8+5UskHT +9zMJKiPJvt8ROEkb6i7XZHmCAwYaAuMKxtjI= Subject: Re: ACPI: EC: GPE storm detected, transactions will use polling mode From: "Justin P. Mattock" To: Alexey Starikovskiy Cc: "Rafael J. Wysocki" , Alan Jenkins , Andrew Morton , Linux Kernel Mailing List , linux-acpi@vger.kernel.org, Len Brown In-Reply-To: <491FECAE.6050005@gmail.com> References: <1226722577.3104.4.camel@LiNuX> <491EBB2D.70106@tuffmail.co.uk> <200811152019.31744.rjw@sisk.pl> <1226817681.3133.7.camel@LiNuX> <491FECAE.6050005@gmail.com> Content-Type: text/plain Date: Sun, 16 Nov 2008 08:56:20 -0800 Message-Id: <1226854580.3385.9.camel@LiNuX> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1437 Lines: 39 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/