From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dell Precision Workstation Overheating
Date: Fri, 20 Apr 2018 10:25:33 -0400 [thread overview]
Message-ID: <CAGfcS_=JCyrv47DD-ZWusACrmx4Jhy5RKaUBUuGUE-yNo6D_kA@mail.gmail.com> (raw)
In-Reply-To: <CAAD4mYg2qjZ5KKFNW_tz5RKyB6_wj44-FaxydNor3VU+t4TJ0Q@mail.gmail.com>
On Thu, Apr 19, 2018 at 9:22 PM, R0b0t1 <r030t1@gmail.com> wrote:
>
> Is there a way to at least mimic the conservative CPU usage that
> Windows exhibits?
>
I'll set aside the obvious hardware issues and touch on workarounds.
I had an old system that had some heating issues (my guess is due to
heatsink seating or something like that), and I used cpufreqd at the
time. This is a daemon that polls CPU temp (among other things) and
can be set to change the frequency policy of the kernel based on
thresholds. I had it set to force the kernel into a powersave
governor when the temp exceeded a threshold. The resulting behavior
was that the clock speed would cycle between min/max and maintain the
temp at the threshold when the system was under a sustained load.
However, for short bursts of activity the CPU was unconstrained.
That software is obsolete today and was removed from the Gentoo repos
a while ago.
I'd take a look at thermald or ncpufreqd in the repo as starting
points. The docs I googled on thermald suggest that it might do the
job with zero config tweaks.
Without using any software you could also just directly set the
frequency limits in the kernel (accessible somewhere in the bowels of
/proc or /sys). However, that is going to cause a performance hit
even for short demands that the heatsink can handle.
Ultimately though you're going to be better off if you can actually
fix the thermal issues themselves.
--
Rich
prev parent reply other threads:[~2018-04-20 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 1:22 [gentoo-user] Dell Precision Workstation Overheating R0b0t1
2018-04-20 2:26 ` Corbin Bird
2018-04-20 2:33 ` R0b0t1
2018-04-20 3:16 ` mad.scientist.at.large
2018-04-20 11:55 ` Corbin Bird
2018-04-20 12:21 ` Mick
2018-04-20 14:11 ` R0b0t1
2018-04-20 14:40 ` Mick
2018-04-20 14:42 ` Corbin Bird
2018-04-20 14:43 ` Dale
2018-05-07 23:29 ` mad.scientist.at.large
2018-04-20 2:58 ` Adam Carter
2018-04-20 14:25 ` Rich Freeman [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='CAGfcS_=JCyrv47DD-ZWusACrmx4Jhy5RKaUBUuGUE-yNo6D_kA@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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