From: yakui_zhao <yakui.zhao@intel.com>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Alexey Starikovskiy <aystarik@gmail.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: [BISECTED] 20 ACPI interrupts per second on EEEPC 4G
Date: Mon, 13 Apr 2009 10:04:08 +0800 [thread overview]
Message-ID: <1239588248.5564.19.camel@localhost.localdomain> (raw)
In-Reply-To: <49E20EBA.2090708@tuffmail.co.uk>
On Sun, 2009-04-12 at 23:54 +0800, Alan Jenkins wrote:
> 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@alan-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 :-).
Does the issue still exist if the following commit is reverted?
Thanks.
>
>
> b1569e99c795bf83b4ddf41c4f1c42761ab7f75e is first bad commit
> commit b1569e99c795bf83b4ddf41c4f1c42761ab7f75e
> Author: Matthew Garrett <mjg59@srcf.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-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-13 2:03 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
2009-04-11 0:24 ` Alexey Starikovskiy
2009-04-11 9:14 ` Alan Jenkins
2009-04-12 15:54 ` [BISECTED] " Alan Jenkins
2009-04-13 2:04 ` yakui_zhao [this message]
2009-04-13 9:39 ` Alan Jenkins
2009-04-13 17:05 ` Matthew Garrett
2009-04-13 17:43 ` Joe Perches
2009-04-13 18:42 ` Alan Jenkins
2009-04-14 19:16 ` [PATCH] thermal: Fix polling frequency for systems without passive cooling Matthew Garrett
2009-04-17 1:37 ` Zhang Rui
2009-04-18 5:05 ` Len Brown
2009-04-13 2:06 ` [BISECTED] 20 ACPI interrupts per second on EEEPC 4G Zhang Rui
2009-04-13 14:53 ` 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=1239588248.5564.19.camel@localhost.localdomain \
--to=yakui.zhao@intel.com \
--cc=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 \
--cc=mjg59@srcf.ucam.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