Your message dated Sun, 23 May 2021 04:54:50 -0700 (PDT) with message-id <60aa428a.1c69fb81.71d3d.6432@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #890365, regarding linux-image 4.14 messing up with CPU frequency 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.) -- 890365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890365 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-image 4.14 messing up with CPU frequency
- From: Eduardo Guerras Valera <ngc6720@gmail.com>
- Date: Tue, 13 Feb 2018 20:47:38 -0600
- Message-id: <CACErFUoCw3aKg=o2OsdpTmXSNy+sELCV06vV65cHZOsBjWjNYw@mail.gmail.com>
- Reply-to: ngc6720@gmail.com
Package: linux-image-4.14.0-0.bpo.3-amd64Distro: Debian 9 StretchWhen I try to set CPU frequency to the minimum, it doesn't work. This works perfectly with kernel 4.9.5 (but with 4.9.5 I cannot hibernate).Steps to reproduce the bug:Have this in your grub: GRUB_CMDLINE_LINUX_DEFAULT="intel_pstate=disable"sucpufreq-set -c 0 -g userspacecpufreq-set -c 0 -f 400MHzWith kernel 4.9 this resulted in the cpu running cold and silently at 400 MHz (check with cpufreq-info or with mate indicator applet).After updating to 4.14 (linux-image-4.14.0-0.bpo.3-amd64 and corresponding linux-header) the above mentioned use of cpufreq-set sets a variable frequency policy.Remark: this is happening too in Ubuntu 16.04 with kernel 4.10 and 4.13, so probably the bug was introduced in 4.10.Please send further instructions to provide any kind of log you need.(remark: reportbug is crashing in my system and that is why I send an email. See screen capture at https://unix.stackexchange.com/questions/424037/how-do-i-report-a-bug-to-debian-when-reportbug-crashes-because-it-has-itself-an)Thanks.----------------------------------------------------------------------------------Eduardo Guerras ValeraHomer L. Dodge Department of Physics and Astronomy440 W. Brooks St. - Norman, OK 73019-0225 - USA--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
- To: 890365-done@bugs.debian.org
- Cc: 890365-submitter@bugs.debian.org
- Subject: Closing this bug (BTS maintenance for src:linux bugs)
- From: carnil@debian.org
- Date: Sun, 23 May 2021 04:54:50 -0700 (PDT)
- Message-id: <60aa428a.1c69fb81.71d3d.6432@mx.google.com>
Hi This bug was filed for a very old kernel or the bug is old itself without resolution. If you can reproduce it with - the current version in unstable/testing - the latest kernel from backports please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore
--- End Message ---