Your message dated Tue, 30 Dec 2014 11:43:24 +0100 with message-id <1419936204.5686.37.camel@decadent.org.uk> and subject line Re: Bug#774199: linux-image-3.16.0-0.bpo.4-amd64: most cpufreq governors newly unavailable has caused the Debian Bug report #774199, regarding linux-image-3.16.0-0.bpo.4-amd64: most cpufreq governors newly unavailable 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.) -- 774199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774199 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-image-3.16.0-0.bpo.4-amd64: most cpufreq governors newly unavailable
- From: Ian Zimmerman <itz@buug.org>
- Date: Mon, 29 Dec 2014 21:59:58 -0800
- Message-id: <[🔎] 20141229215958.7f79b168.itz@buug.org>
Package: src:linux Version: 3.16.0-0.bpo.4 On my other system, which is a laptop, with linux-image-3.2.0-4-amd64 cpufrequtils starts correctly out of the box, and the contents of /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors is: powersave userspace conservative ondemand performance But with linux-image-3.16.0-0.bpo.4 booted on the same machine, I get the dreaded message "Setting ondemand CPUFreq governor...disabled, governor not available" and indeed, scaling_available_governors contains just powersave performance So this looks on the face as a kernel regression, although many other suspects come to mind as well. The machine is a Dell XPS with a 4-way Intel Core i7-3571U. Let me know if I can provide any more useful information. -- Please *no* private copies of mailing list or newsgroup messages. Rule 420: All persons more than eight miles high to leave the court. Local Variables: mode:claws-external End:
--- End Message ---
--- Begin Message ---
- To: 774199-done@bugs.debian.org
- Subject: Re: Bug#774199: linux-image-3.16.0-0.bpo.4-amd64: most cpufreq governors newly unavailable
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Tue, 30 Dec 2014 11:43:24 +0100
- Message-id: <1419936204.5686.37.camel@decadent.org.uk>
- In-reply-to: <[🔎] 20141229215958.7f79b168.itz@buug.org>
- References: <[🔎] 20141229215958.7f79b168.itz@buug.org>
On Mon, 2014-12-29 at 21:59 -0800, Ian Zimmerman wrote: > Package: src:linux > Version: 3.16.0-0.bpo.4 > > On my other system, which is a laptop, with linux-image-3.2.0-4-amd64 > cpufrequtils starts correctly out of the box, and the contents of > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors is: > > powersave userspace conservative ondemand performance > > But with linux-image-3.16.0-0.bpo.4 booted on the same machine, > I get the dreaded message > "Setting ondemand CPUFreq governor...disabled, governor not available" > and indeed, scaling_available_governors contains just > > powersave performance > > So this looks on the face as a kernel regression, although many other > suspects come to mind as well. > > The machine is a Dell XPS with a 4-way Intel Core i7-3571U. Let me know > if I can provide any more useful information. This is expected behaviour on systems where the intel_pstate driver is used. Some background: http://www.phoronix.com/scan.php?page=news_item&px=MTM3NDQ Ben. -- Ben Hutchings It is easier to write an incorrect program than to understand a correct one.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---