From: Steven Noonan <steven@uplinklabs.net>
To: linux-kernel@vger.kernel.org
Subject: Re: cpufreq scaling strangely, system feels warm
Date: Sun, 4 Oct 2009 22:03:16 -0700 [thread overview]
Message-ID: <f488382f0910042203x38365b9amd557803872cc1435@mail.gmail.com> (raw)
In-Reply-To: <f488382f0910041924p5e9eae48qa19afc81c43fca3d@mail.gmail.com>
On Sun, Oct 4, 2009 at 7:24 PM, Steven Noonan <steven@uplinklabs.net> wrote:
> On Sat, Oct 3, 2009 at 5:54 PM, Steven Noonan <steven@uplinklabs.net> wrote:
>> I have a system that's behaving as though it's under a moderate load,
>> but nothing's happening and the load average is zero. If I change my
>> cpufreq governor to 'conservative' or 'ondemand', the CPU immediately
>> scales up to the maximum clock frequency (as though something was
>> demanding that much power). The system is also very warm, which is
>> abnormal even when the machine is always clocked at its maximum
>> frequency.
>>
>> Top shows that there are no processes which are hogging the CPU, and
>> /proc/interrupts doesn't reveal anything interesting (i.e. an
>> interrupt storm). The only way to get my system to stay cool is to
>> change the cpufreq governor to 'powersave' or 'userspace' (and then
>> clock it at the lowest, manually).
>>
>
> Scratch that. It's probably an interrupt storm. 'perf top' shows
> 19,000 IRQs per second. And I recall that 500-1500 per second was
> normal for this machine. Now the problem is figuring out where the
> interrupt storm is coming from...
>
Went through my kernel config and found some odd settings, fixed them
and recompiled. Now 'ondemand' works as it should, but 'conservative'
always clocks up to the maximum frequency. I can't figure out why.
Is there a way to get cpufreq to print out some explanations in dmesg
as to why 'conservative' is doing what it does?
- Steven
prev parent reply other threads:[~2009-10-05 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 0:54 Steven Noonan
2009-10-05 2:24 ` Steven Noonan
2009-10-05 5:03 ` Steven Noonan [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=f488382f0910042203x38365b9amd557803872cc1435@mail.gmail.com \
--to=steven@uplinklabs.net \
--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
all inboxes | Powered by JetHome®