From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: linux-acpi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: Regression: 20 ACPI interrupts per second on EEEPC 4G
Date: Sat, 11 Apr 2009 10:14:43 +0100 [thread overview]
Message-ID: <49E05F83.2090500@tuffmail.co.uk> (raw)
In-Reply-To: <49DFE345.3010109@gmail.com>
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@alan-eeepc:/sys/firmware/acpi/interrupts$ cat sci; sleep 5; cat sci
2583
2680
Thanks
Alan
next prev parent reply other threads:[~2009-04-11 9:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 15:39 Regression: 20 ACPI interrupts per second on EEEPC 4G Alan Jenkins
[not found] ` <49DF6835.9040501-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2009-04-11 0:24 ` Alexey Starikovskiy
2009-04-11 9:14 ` Alan Jenkins [this message]
[not found] ` <49E05F83.2090500-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2009-04-12 15:54 ` [BISECTED] " Alan Jenkins
2009-04-13 2:06 ` Zhang Rui
[not found] ` <49E20EBA.2090708-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2009-04-13 2:04 ` yakui_zhao
[not found] ` <1239588248.5564.19.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-04-13 9:39 ` Alan Jenkins
2009-04-13 17:05 ` Matthew Garrett
2009-04-13 17:43 ` Joe Perches
[not found] ` <20090413170531.GA13188-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-04-13 18:42 ` Alan Jenkins
2009-04-14 19:16 ` [PATCH] thermal: Fix polling frequency for systems without passive cooling Matthew Garrett
[not found] ` <20090414191645.GB7940-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-04-17 1:37 ` Zhang Rui
2009-04-18 5:05 ` Len Brown
2009-04-13 14:53 ` [BISECTED] 20 ACPI interrupts per second on EEEPC 4G Matthew Garrett
2009-04-17 20:54 ` Alexey Starikovskiy
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=49E05F83.2090500@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=aystarik@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).