From: Len Brown <lenb@kernel.org>
To: cpufreq@lists.linux.org.uk
Cc: Joshua Justice <joshj777@gmail.com>
Subject: Re: cpufreq on Debian, problems
Date: Sun, 11 Mar 2007 19:45:12 -0500 [thread overview]
Message-ID: <200703112045.12149.lenb@kernel.org> (raw)
In-Reply-To: <45F47282.4020209@chrestomanci.org>
On Sunday 11 March 2007 17:20, David Pottage wrote:
> Joshua Justice wrote:
> > I'm running a Pentium 4, 3.40 gigahertz, on Debian Etch 2.6.18-4-686,
> > and I have issues with overheating because cpu throttling isn't working.
Check that your fan is properly installed, including thermal compound.
You should not need throttling to cool a P4.
Indeed, most of them don't support any P-states at all.
-Len
> Is your clock frequency scaling back when your system is not under load?
>
> If it is not, and you want it to, then you need to run the ondemand or
> conservative govenor. Take a look in
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors that
> they are there, then echo a govenor name into
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
> If the clock frequency is changing acording to your system load, but it
> is still overheading, you probably need to improve your cooling hardware.
>
> If it is not practical to improve your CPU cooling, or if your peak
> loads are ocasional, then you can prevent overheating by limiting the
> CPU temperature. I have written a userland perl script that does this
> automaticaly, by monitoring the CPU temperature, and lowering the
> maximum CPU frequency if the temperature gets to high. You can have a
> copy if you like.
next prev parent reply other threads:[~2007-03-12 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 20:04 cpufreq on Debian, problems Joshua Justice
2007-03-11 21:20 ` David Pottage
2007-03-12 0:45 ` Len Brown [this message]
2007-03-12 9:58 ` Bruno Ducrot
2007-03-12 17:48 ` Joshua Justice
2007-03-12 18:18 ` Dave Jones
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=200703112045.12149.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=joshj777@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.