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 #733545, regarding cpufreqd should honour bios_limit when setting max/min freq 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.) -- 733545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733545 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: Fails to set profiles
- From: martin f krafft <madduck@debian.org>
- Date: Mon, 30 Dec 2013 10:13:01 +1300
- Message-id: <20131229211301.GA3829@fishbowl.rw.madduck.net>
Package: cpufreqd Version: 2.4.2-2 Severity: important For weeks now, I've not been able to get cpufreqd to work. The log (and -V7) shows only the following: cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/energy_full (No such file or directory) cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/energy_now (No such file or directory) cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/power_now (No such file or directory) acpid: client connected from 3638[0:0] acpid: 1 client rule loaded cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/energy_full (No such file or directory) cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/energy_now (No such file or directory) cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/power_now (No such file or directory) cpufreqd: cpufreqd_set_profile : Couldn't set profile "Performance High" set for cpu0 (2400000-2400000-performance) cpufreqd: cpufreqd_loop : Cannot set policy, Rule unchanged ("none"). and indeed, those files do not exist: # ls /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 alarm charge_full_design cycle_count model_name serial_number technology voltage_min_design capacity charge_now device power status type voltage_now charge_full current_now manufacturer present subsystem uevent I am running the 3.11-2 kernel. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cpufreqd depends on: ii libc6 2.17-97 ii libcpufreq0 008-1 ii libsensors4 1:3.3.4-2 ii libsysfs2 2.1.0+repack-3 ii lsb-base 4.1+Debian12 Versions of packages cpufreqd recommends: ii acpid 1:2.0.20-1 Versions of packages cpufreqd suggests: ii cpufrequtils 008-1 -- no debconf information -- .''`. martin f. krafft <madduck@d.o> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systemsAttachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--- End Message ---
--- Begin Message ---
- To: 330409-done@bugs.debian.org,403428-done@bugs.debian.org,416618-done@bugs.debian.org,428249-done@bugs.debian.org,458012-done@bugs.debian.org,537219-done@bugs.debian.org,566528-done@bugs.debian.org,583663-done@bugs.debian.org,602032-done@bugs.debian.org,605643-done@bugs.debian.org,626852-done@bugs.debian.org,627265-done@bugs.debian.org,627649-done@bugs.debian.org,647713-done@bugs.debian.org,684446-done@bugs.debian.org,733545-done@bugs.debian.org,883009-done@bugs.debian.org,966620-done@bugs.debian.org,1012736-done@bugs.debian.org,1039156-done@bugs.debian.org,1044574-done@bugs.debian.org,933160-done@bugs.debian.org,
- Cc: cpufreqd@packages.debian.org
- Subject: Bug#1056251: Removed package(s) from unstable
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Wed, 29 Nov 2023 18:30:32 +0000
- Message-id: <[🔎] E1r8PKS-0036bV-7x@fasolo.debian.org>
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 ---