GNU bug report logs - #37904
CPU overheating on recent laptops

Previous Next

Full log

Message #17 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Arne Babenhauserheide <arne_bab <at> web.de>
To: bug-guix <at> gnu.org
Cc: 37904 <at> debbugs.gnu.org
Subject: Re: bug#37904: CPU overheating on recent laptops
Date: Sat, 26 Oct 2019 00:19:04 +0200

[Message part 1 (text/plain, inline)]

Ludovic Courtès <ludo <at> 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

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.