[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49E20EBA.2090708@tuffmail.co.uk>
Date: Sun, 12 Apr 2009 16:54:34 +0100
From: Alan Jenkins <alan-jenkins@...fmail.co.uk>
To: Matthew Garrett <mjg59@...f.ucam.org>
CC: Alexey Starikovskiy <aystarik@...il.com>,
linux-acpi@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: [BISECTED] 20 ACPI interrupts per second on EEEPC 4G
Alan Jenkins wrote:
> Alexey Starikovskiy wrote:
>> Alan Jenkins wrote:
>>> On latest git, powertop shows 20 ACPI interrupts per second.
>>> Previously, this was closer to 1 per second. See attached output (a
>>> vs b, "a" is from 2.6.29-rc8).
>>>
>>> This is from a pretty sparse KDE desktop. Normally I run
>>> gnome-power-manager, but I killed it to make sure that wasn't
>>> causing any problems.
>>>
>
>>> gpe18: 60975 enabled
>>> gpe_all: 60975
>>> sci: 60975
>>>
>>> which I presume means lots of EC interrupts.
>>>
>>> [ 0.134068] ACPI: EC: GPE = 0x18, I/O: command/status = 0x66,
>>> data = 0x62
>>>
>
>> This patch looks to be a suspect:
>> 34ff4dbccccce54c83b1234d39b7ad9e548a75dd,
>> Please check if reversing it helps
>
> No, I still get 20 ACPI interrupts per second.
>
> I tried without powertop, just in case that was provoking it, but it
> still happens:
>
> alan@...n-eeepc:/sys/firmware/acpi/interrupts$ cat sci; sleep 5; cat sci
> 2583
> 2680
I did wonder whether this was due to thermal polling. So look what I
found with bisection :-).
b1569e99c795bf83b4ddf41c4f1c42761ab7f75e is first bad commit
commit b1569e99c795bf83b4ddf41c4f1c42761ab7f75e
Author: Matthew Garrett <mjg59@...f.ucam.org>
Date: Wed Dec 3 17:55:32 2008 +0000
ACPI: move thermal trip handling to generic thermal layer
The ACPI code currently carries its own thermal trip handling,
meaning that
any other thermal implementation will need to reimplement it. Move
the code
to the generic thermal layer.
Regards
Alan
--
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/
Powered by blists - more mailing lists