Your message dated Sun, 16 Jun 2024 00:58:58 +0000
with message-id <[email protected]>
and subject line Bug#1073079: Removed package(s) from unstable
has caused the Debian Bug report #626839,
regarding CPUFreqUtils not scaling frequencies properly when using userspace
governer and cpufreq-set on intel atom processor
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
626839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626839
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cpufrequtils
Version: 007-1
After setting the governer "userspace", I am able to assign all cpu frequencies
except 1.07GHz on the Intel Atom processor for the Dell Mini 9.
root@box:/home/neybis# cpufreq-set -g userspace -c 0
root@box:/home/neybis# cpufreq-set -f 800MHz -c 0
root@box:/home/neybis# cpufreq-info -c 0
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
available cpufreq governors: userspace, powersave, conservative, ondemand,
performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
cpufreq stats: 1.60 GHz:17.22%, 1.33 GHz:37.18%, 1.07 GHz:0.07%, 800
MHz:45.52% (2021)
root@box:/home/neybis# cpufreq-set -f 1.6GHz -c 0
root@box:/home/neybis# cpufreq-info -c 0
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
available cpufreq governors: userspace, powersave, conservative, ondemand,
performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz (asserted by call to hardware).
cpufreq stats: 1.60 GHz:17.20%, 1.33 GHz:37.00%, 1.07 GHz:0.07%, 800
MHz:45.72% (2022)
root@box:/home/neybis# cpufreq-set -f 1.33GHz -c 0
root@box:/home/neybis# cpufreq-info -c 0
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
available cpufreq governors: userspace, powersave, conservative, ondemand,
performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1.33 GHz (asserted by call to hardware).
cpufreq stats: 1.60 GHz:17.45%, 1.33 GHz:36.93%, 1.07 GHz:0.07%, 800
MHz:45.55% (2023)
root@box:/home/neybis# cpufreq-set -f 1.07GHz -c 0
root@box:/home/neybis# cpufreq-info -c 0
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
available cpufreq governors: userspace, powersave, conservative, ondemand,
performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1.33 GHz (asserted by call to hardware).
cpufreq stats: 1.60 GHz:17.39%, 1.33 GHz:37.14%, 1.07 GHz:0.07%, 800
MHz:45.40% (2023)
root@box:/home/neybis#
I did no configuration after installing the necessary packages. Everything
worked out of the box. Not sure what could cause this. Maybe its not grabbing
the arguments properly or the driver is not fully functional. : /
--- End Message ---
--- Begin Message ---
Version: 008-2+rm
Dear submitter,
as the package cpufrequtils has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1073079
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
