unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26919@debbugs.gnu.org
Subject: bug#26919: [PATCH] Add thermald and thermald-service-type (for cpu frequency scaling)
Date: Sun, 14 May 2017 18:56:05 -0500	[thread overview]
Message-ID: <87efvr802y.fsf@dustycloud.org> (raw)
In-Reply-To: <87lgpztdq0.fsf@gnu.org>

Ludovic Courtès writes:

> Leo Famulari <leo@famulari.name> skribis:
>
>> Ludovic Courtès writes:
>>> Do you think it’s something we should add to ‘%base-services’, or is it
>>> too hardware-dependent?
>>
>> It does seem like an unusual requirement to me, since most systems
>> should do thermal management automatically in the CPU and BIOS.
>>
>> I can run my physical machines (GuixSD or Debian) at full CPU
>> utilization for extended periods of time without overheating.
>
> Yes, same here actually.  Could it be due to this particular Libreboot +
> X200 combination?  Or are we just lucky that other systems don’t
> overheat as well?
>
> Ludo’.

I'm on a libreboot + x200 machine.  Notably it never overheats... unless
it's docked.  Then it's liable to overheat, because the circulation
while being docked is, I guess, pretty bad?  Unfortunately, I am docked
pretty much all the time!

Do you use a dock regularly, out of curiosity?  It could be that it's
time to open up and de-dustrabbit :)

 - Chris

  reply	other threads:[~2017-05-14 23:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14  5:29 bug#26919: [PATCH] Add thermald and thermald-service-type (for cpu frequency scaling) Christopher Allan Webber
2017-05-14 13:07 ` Ludovic Courtès
2017-05-14 15:49   ` Christopher Allan Webber
2017-05-14 17:00     ` Leo Famulari
2017-05-14 19:55       ` Ludovic Courtès
2017-05-14 23:56         ` Christopher Allan Webber [this message]
2017-05-15  7:46           ` Ludovic Courtès
2017-05-30 16:00     ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87efvr802y.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=26919@debbugs.gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).