all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37904@debbugs.gnu.org, Arne Babenhauserheide <arne_bab@web.de>
Subject: bug#37904: CPU overheating on recent laptops
Date: Tue, 12 Jul 2022 10:49:18 -0400	[thread overview]
Message-ID: <87wnci75e9.fsf@gmail.com> (raw)
In-Reply-To: <87pnikii3r.fsf@web.de> (Arne Babenhauserheide's message of "Sat,  26 Oct 2019 00:19:04 +0200")

Hi Ludo,

Arne Babenhauserheide <arne_bab@web.de> writes:

> Ludovic Courtès <ludo@gnu.org> writes:
>>> For laptops and other battery-powered devices, ‘conservative’ is
>>> preferred over ‘ondemand’.  It's probably a sane default choice for
>>> all.
>
>> --8<---------------cut here---------------start------------->8---
>> $ cat /sys/devices/system/cpu/cpu?/cpufreq/scaling_available_governors
>> performance powersave
>
>> $ uname -a
>> Linux ribbon 5.3.7-gnu #1 SMP 1 x86_64 GNU/Linux
>> --8<---------------cut here---------------end--------------->8---
>>
>> Do you see more governors on your side?  How could that be?
>
> Do you have a recent Intel CPU? From what I know they removed support
> for conservative, because their powersave is in fact conservative.
>
> Also they don’t necessarily stick to the frequency you set for them. To
> ensure that they keep the frequency, I have a script running that sets
> the speed every minute:
>
> (define cpupower-powersave-job
>   ;; Set the governor to powersave every minute.
>   ;; The job's action is a shell command.
>   ;; TODO: migrate to clearer syntax:   #~(job '(next-hour '(3)) (string-append #$btrfs-progs "/bin/btrfs scrub start -c 3 /")))
>   #~(job "* * * * *"            ;Vixie cron syntax
>          "cpupower frequency-set -g powersave -u 1200000")) ;; use powersave governor with a maximum frequency of 1200MHz
>
> (this is a problem which also hits other distributions)

Is this problem still an issue?  Based on what Arne says above, it seems
it isn't a fault in Guix, so perhaps we can close the issue and seek
resolution upstream if a problem remains?

Thanks,

Maxim




  reply	other threads:[~2022-07-12 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 14:57 bug#37904: CPU overheating on recent laptops Ludovic Courtès
2019-10-24 16:30 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-25 20:49   ` Ludovic Courtès
2019-10-25 22:19     ` Arne Babenhauserheide
2022-07-12 14:49       ` Maxim Cournoyer [this message]
2022-07-12 14:55         ` 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

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

  git send-email \
    --in-reply-to=87wnci75e9.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=37904@debbugs.gnu.org \
    --cc=arne_bab@web.de \
    --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 external index

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

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.