All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: astarikovskiy@suse.de, len.brown@intel.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] GPE storm detected on FS Amilo Pro
Date: Wed, 21 Jan 2009 17:00:47 +0100	[thread overview]
Message-ID: <200901211700.48357.rjw@sisk.pl> (raw)
In-Reply-To: <4977352B.1040303@gmail.com>

On Wednesday 21 January 2009, Jacek Luczak wrote:
> Hi All,

Hi Jacek,

> I've got that ,,GPE storm detected'' issue on my Fujitsu Siemens Amilo Pro
> notebook.  I was using 2.6.25.20 (which was fine) for a long while and recently
> started testing some latest git versions starting from 2.6.29-rc2 where I've
> discovered that issue. So I've made some back kernels and it shows up from
> 2.6.26 kernel. Bisection between 2.6.25 and 2.6.26 shows that patch:
> 
> fa95ba04e6ba11d71e1b87becd054b38faf546c8 is first bad commit
> commit fa95ba04e6ba11d71e1b87becd054b38faf546c8
> Author: Alexey Starikovskiy <astarikovskiy@suse.de>
> Date:   Fri Mar 21 19:36:02 2008 +0300
> 
>     ACPI: EC: Detect irq storm
> 
>     Problem seems to be that hw fails to clear GPE after we service it and write 1
>     into corresponding bit. Thus, as soon as we get interrupts enabled again, we
>     receive a new one. Google gives too many results for "acer interrupt storm" for
>     this being one-broken-machine case.
> 
>     Reference: http://bugzilla.kernel.org/show_bug.cgi?id=9998
> 
>     Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de>
>     Signed-off-by: Len Brown <len.brown@intel.com>
> 
> The bug[1] (reopened recently) seems to be quite different than the one in my
> case. I've got no ,,side effects'' of that GPE storm. Notebook works fine and I
> didn't discovered any interrupts problems.

So everything appears to be OK except that your hardware has a problem,
which is correctly worked around and the message just tells you what happens.

> Up to 2.6.28 GPE storm information is printed early[2]:
> 
> Setting up standard PCI resources
> ACPI: EC: Look up EC in DSDT
> ACPI: Interpreter enabled
> ACPI: (supports S0 S3 S4 S5)
> ACPI: Using IOAPIC for interrupt routing
> ACPI: EC: non-query interrupt received, switching to interrupt mode
> ACPI: EC: GPE storm detected, disabling EC GPE
> ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
> ACPI: EC: driver started in poll mode
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> 
> While recent git[3] which I'm now running, shows it after setting-up AC adapter[4]:
> 
> ACPI: AC Adapter [ADP1] (on-line)
> ACPI: EC: GPE storm detected, transactions will use polling mode
> Switched to high resolution mode on CPU 1
> Switched to high resolution mode on CPU 0
> ACPI: EC: missing confirmations, switch off interrupt mode.
> ACPI: Battery Slot [BAT0] (battery present)
> input: Power Button (FF) as /class/input/input0
> ACPI: Power Button (FF) [PWRF]
> input: Lid Switch as /class/input/input1
> ACPI: Lid Switch [LID0]
> input: Sleep Button (CM) as /class/input/input2
> ACPI: Sleep Button (CM) [SLPB]
> 
> I'm not sure if the origin of that GPE storm is the same in both cases. Will try
> to do bisection here later if needed.
> 
> NOTE: In git kernel I've noticed that after boot and obtaining IP from DHCP I've
> got such message:
> 
> Jan 21 14:44:32 difrost kernel: sky2 eth0: enabling interface
> Jan 21 14:44:33 difrost kernel: sky2 eth0: Link is up at 100 Mbps, full duplex,
> flow control rx
> Jan 21 14:45:36 difrost kernel: ACPI: EC: missing confirmations, switch off
> interrupt mode.
> 
> This is not fully reproducible, didn't shown on [4].

This may be related to the issue behind the GPM storm message.

Thanks,
Rafael

  reply	other threads:[~2009-01-21 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 14:46 [ACPI] GPE storm detected on FS Amilo Pro Jacek Luczak
2009-01-21 16:00 ` Rafael J. Wysocki [this message]
2009-01-22 10:17   ` Jacek Luczak
2009-01-22 12:22     ` Rafael J. Wysocki
2009-01-21 20:50 ` Alexey Starikovskiy
2009-01-22 10:25   ` Jacek Luczak

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=200901211700.48357.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=astarikovskiy@suse.de \
    --cc=difrost.kernel@gmail.com \
    --cc=len.brown@intel.com \
    --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 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.