Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #79861

Bug#1038981: capping maximum frequency no longer works in kernel 6.1

From AlMa <AlMa0@ro.ru>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1038981: capping maximum frequency no longer works in kernel 6.1
Date 2023-08-01 01:50 +0200
Message-ID <GXKOe-49VH-5@gated-at.bofh.it> (permalink)
References <GJXrX-qqK-5@gated-at.bofh.it> <GXJp7-49dr-13@gated-at.bofh.it> <GJXrX-qqK-5@gated-at.bofh.it> <GXJp7-49dr-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


> I don't want to be an ass, but why didn't you do such elementary research
> before filing a bug report?

I don't want to be an ass, too, but the fact that you searched for 
exactly "powersave frequency governor" and “Intel p-state” (and NOT 
something else) is elementary to YOU.  I saw the Archlinux page but was 
(and still am) unsure of how much of what is said there applies to 
Debian.  Heaven knows how differently you and them configure the kernels 
(and surely you and them don't take exactly the same kernels anyway).

As for 
https://www.kernel.org/doc/html/v6.1/admin-guide/pm/intel_pstate.html , 
it's dated 2017 (and no later year is mentioned!), whereas the processor 
in #1038981 is from Q2'20, and the kernel is from 2023 (6 years later 
than the document date).  So even if I had found that document myself, I 
might have dismissed it just based on date. (To compare, certain 
configuration files, such as /etc/lvm.conf or /etc/default/grub, get 
partially outdated with every upgrade of Debian stable.) Anyway, does 
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE still exist and, if so, is this 
configuration option off in Debian kernels?  That's what seems to be the 
case based on
https://www.google.com/search?q="CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE"+amd64+site%3Adebian.org 
, but I can't be sure …

The original, user-level and high-level bug was that I noticed that I 
couldn't provably limit the processor speed via tlp after an upgrade 
from Debian 11 to Debian 12.  It took me quite a while (many hours 
spread over a few days) to get from that high level to the level of 
#1038981, and, as you surely understand, at a certain point I have to 
declare the boundary of my current expertise.

Gratefully,
AlMa

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1038981: capping maximum frequency no longer works in kernel 6.1 "Al Ma" <alma0@ro.ru> - 2023-06-24 00:30 +0200
  Bug#1038981: Acknowledgement (capping maximum frequency no longer works in kernel 6.1) AlMa <AlMa0@ro.ru> - 2023-06-24 01:00 +0200
  Bug#1038981: scaling_cur_freq ≰ scaling_max_freq "Al Ma" <alma0@ro.ru> - 2023-07-20 01:30 +0200
  Bug#1038981: capping maximum frequency no longer works in kernel 6.1 Diederik de Haas <didi.debian@cknow.org> - 2023-08-01 00:20 +0200
    Bug#1038981: capping maximum frequency no longer works in kernel 6.1 AlMa <AlMa0@ro.ru> - 2023-08-01 01:50 +0200
      Bug#1038981: capping maximum frequency no longer works in kernel 6.1 Diederik de Haas <didi.debian@cknow.org> - 2023-08-01 10:50 +0200
        Bug#1038981: capping maximum frequency no longer works in kernel 6.1 AlMa <AlMa0@ro.ru> - 2023-08-01 16:50 +0200

csiph-web