public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacek Luczak <difrost.kernel@gmail.com>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	len.brown@intel.com
Subject: Re: [ACPI] GPE storm detected on FS Amilo Pro
Date: Thu, 22 Jan 2009 11:25:34 +0100	[thread overview]
Message-ID: <4978499E.2040808@gmail.com> (raw)
In-Reply-To: <49778AAF.5000604@suse.de>

Hi Alex,

Alexey Starikovskiy pisze:
> Hi Jacek,
> 
> You did not receive "GPE storm detected" message in earlier kernel only
> because
> there was no detection of it. You can check if you have one by enabling
> "#define DEBUG" at the beginning of the /drivers/acpi/ec.c and looking
> into dmesg.

I know, I was bit confused as I've seen that message before. I've double checked
and found that it appeared while I was fixing some stuff in 2.6.26 release
cycle, mea culpa.

> If there is no storm,
> you should see ony 2-3 interrupt messages per single transaction. Storm
> detector fires up at 8 excess interrupts.
> 

thanks for your answer, it was exactly what I was looking for.

While I was doing that 2.6.26 work I've found that IRQ 19 (sata ahci chip) is
doing some ugly stuff, I've reported that and stopped in half of my debug as I
didn't had more time to work on that. There was some ,,nobody cared'' bugs and
so one, I will return to that problem now and check if it's still present. All
those IRQ problems were appearing with suspend/resume. Nevertheless it isn't a
point here.

-Jacek

      reply	other threads:[~2009-01-22 10:24 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
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 [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=4978499E.2040808@gmail.com \
    --to=difrost.kernel@gmail.com \
    --cc=astarikovskiy@suse.de \
    --cc=len.brown@intel.com \
    --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