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

Bug#566528: marked as done ([cpufreqd] cpufreq-info no longer returns correct frequency range)

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 #566528,
regarding [cpufreqd] cpufreq-info no longer returns correct frequency range
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.)


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

--- Please enter the report below this line. ---

since 2.3.3-4 something goes wrong with setting correct min/max settings used 
governer.  Correct hardware limts are however detected.

cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 3.17 GHz
  available frequency steps: 3.17 GHz, 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, 
performance
  current policy: frequency should be within 3.17 GHz and 3.17 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 3.17 GHz (asserted by call to hardware).
  cpufreq stats: 3.17 GHz:99,89%, 2.67 GHz:0,00%, 2.33 GHz:0,00%, 2.00 
GHz:0,11%  (4)
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 3.17 GHz
  available frequency steps: 3.17 GHz, 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, 
performance
  current policy: frequency should be within 3.17 GHz and 3.17 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 3.17 GHz (asserted by call to hardware).
  cpufreq stats: 3.17 GHz:99,89%, 2.67 GHz:0,00%, 2.33 GHz:0,00%, 2.00 
GHz:0,11%  (2)

Linux ws-151 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 
GNU/Linux


--- System information. ---
Architecture: amd64
Kernel:       Linux 2.6.32-trunk-amd64

Debian Release: squeeze/sid
  500 testing         security.debian.org 
  500 testing         ftp.nl.debian.org 

--- Package information. ---
Depends               (Version) | Installed
===============================-+-================
libc6                (>= 2.7-1) | 2.10.2-2
libcpufreq0                     | 006-2
libsensors3     (>= 1:2.10.3-1) | 1:2.10.8-2
libsysfs2                       | 2.1.0-6
lsb-base               (>= 3.0) | 3.2-23


Recommends      (Version) | Installed
=========================-+-===========
acpid                     | 1:2.0.0-1


Suggests          (Version) | Installed
===========================-+-===========
cpufrequtils                | 006-2

--- 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: