linux-kernel - Re: [ACPI] GPE storm detected on FS Amilo Pro

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 Jan 2009 11:25:34 +0100
From:	Jacek Luczak <difrost.kernel@...il.com>
To:	Alexey Starikovskiy <astarikovskiy@...e.de>
CC:	LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, len.brown@...el.com
Subject: Re: [ACPI] GPE storm detected on FS Amilo Pro

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/