unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: 37904@debbugs.gnu.org
Subject: bug#37904: CPU overheating on recent laptops
Date: Sat, 26 Oct 2019 00:19:04 +0200	[thread overview]
Message-ID: <87pnikii3r.fsf@web.de> (raw)
In-Reply-To: <87imocmtxw.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]


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)

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

  reply	other threads:[~2019-10-25 22:20 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 [this message]
2022-07-12 14:49       ` Maxim Cournoyer
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

  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=87pnikii3r.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=37904@debbugs.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).