[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#330409: marked as done (cpufreqd: restore full scaling range upon removal)

Your message dated Wed, 29 Nov 2023 18:30:32 +0000
with message-id <[🔎] E1r8PKS-0036bV-7x@fasolo.debian.org>
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #330409,
regarding cpufreqd: restore full scaling range upon removal
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 owner@bugs.debian.org
immediately.)


-- 
330409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330409
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cpufreqd
Severity: normal

One notices that
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
924000
has been changed by installation and removal of cpufreqd. It is so
high here.

But installing cpudynd or powernowd don't set it back. So they don't
"play with a full deck". Therefore both cpudynd and powernowd should
do something like
  cat cpuinfo_min_freq > scaling_min_freq
  cat cpuinfo_max_freq > scaling_max_freq
upon installation.  And cpufreqd should do the same upon removal.
This bug will be sent to all three packages.

--- End Message ---
--- Begin Message --- 
Version: 2.4.2-5+rm

Dear submitter,

as the package cpufreqd 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/1056251

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
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---
Reply to: