Bug#592662: cpufrequtils: Cannot set frequency range of policy to full hardware frequency range
Jonathan Nieder schrieb: Thanks for the update. It would be interesting to hear whether a current squeeze kernel is affected, too (it should be possible to test that on sid or wheezy without trouble) and what the latest affected version and first unaffected versions you remember trying were. I'll check this. Unfortunately, I'm currently writing on my dissertation and a little short on time, but it's on my list and will be done. Hopefully sooner than squeeze is done for. Thanks for your time, and best regards, Steve -- Steve Wolter ( Würzburg Univ.) | Web page: http://swolter.sdf1.org | vCard:http://swolter.sdf1.org/swolter.vcf A witty saying proves nothing. | Schedule: http://swolter.sdf1.org/sched.cgi -- Voltaire (1694-1778) | E-mail: swol...@sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592662: cpufrequtils: Cannot set frequency range of policy to full hardware frequency range
Hi Jonathan, Jonathan Nieder schrieb: Ben Hutchings wrote: On Wed, Aug 11, 2010 at 10:35:15PM +0200, Steve Wolter wrote: When using cpufrequtils or the kernel interface to the acpi-cpufreq module on my VIA Eden 1.5 GHz CPU, I cannot set the frequency range for the governor to the full hardware range. Trying to do so produces weird frequency settings. Any of the two single frequencies offered by the hardware can be included in a range, but not both at once. [...] Since you have reproduced this in Linux 2.6.35, please report this upstream at https://bugzilla.kernel.org under product 'ACPI', component 'Power-Processor'. Let us know the bug number or URL so that we can track it. So, now I'm in suspense. I'm very sorry this took so long. I do appreciate your work. Did you report this upstream? Did the problem stop happening with later kernels? I didn't report this upstream. The problem did stop with a later kernel, though I'm not sure when. I couldn't reproduce it with the currently running stock Debian kernel 3.0.0-1-486. I'm also curious about one detail from the original report: was this the first time you tried this, or was it a regression? Was the first time. Thanks for your help and best regards, Steve Wolter -- Steve Wolter ( Würzburg Univ.) | Web page: http://swolter.sdf1.org | vCard:http://swolter.sdf1.org/swolter.vcf A witty saying proves nothing. | Schedule: http://swolter.sdf1.org/sched.cgi -- Voltaire (1694-1778) | E-mail: swol...@sdf.lonestar.org signature.asc Description: Digital signature
Bug#592662: cpufrequtils: Cannot set frequency range of policy to full hardware frequency range
Version: 3.0.0-4 tags 592662 - moreinfo # ?? found 592662 linux-2.6/2.6.32-5 quit Steve Wolter wrote: Jonathan Nieder schrieb: Did you report this upstream? Did the problem stop happening with later kernels? I didn't report this upstream. The problem did stop with a later kernel, though I'm not sure when. I couldn't reproduce it with the currently running stock Debian kernel 3.0.0-1-486. Thanks for the update. It would be interesting to hear whether a current squeeze kernel is affected, too (it should be possible to test that on sid or wheezy without trouble) and what the latest affected version and first unaffected versions you remember trying were. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592662: cpufrequtils: Cannot set frequency range of policy to full hardware frequency range
Hi Steve, Ben Hutchings wrote: On Wed, Aug 11, 2010 at 10:35:15PM +0200, Steve Wolter wrote: When using cpufrequtils or the kernel interface to the acpi-cpufreq module on my VIA Eden 1.5 GHz CPU, I cannot set the frequency range for the governor to the full hardware range. Trying to do so produces weird frequency settings. Any of the two single frequencies offered by the hardware can be included in a range, but not both at once. [...] Since you have reproduced this in Linux 2.6.35, please report this upstream at https://bugzilla.kernel.org under product 'ACPI', component 'Power-Processor'. Let us know the bug number or URL so that we can track it. So, now I'm in suspense. Did you report this upstream? Did the problem stop happening with later kernels? I'm also curious about one detail from the original report: was this the first time you tried this, or was it a regression? Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592662: cpufrequtils: Cannot set frequency range of policy to full hardware frequency range
Hi Matthia, Mattia Dongili schrieb: On Wed, Aug 11, 2010 at 10:35:15PM +0200, Steve Wolter wrote: Package: cpufrequtils Version: 007-1 Severity: normal When using cpufrequtils or the kernel interface to the acpi-cpufreq module on my VIA Eden 1.5 GHz CPU, I cannot set the frequency range for the governor to the full hardware range. Trying to do so produces weird frequency settings. Any of the two single frequencies offered by the hardware can be included in a range, but not both at once. well, if writing values directly to the /sys/devices/system/cpu*/cpufreq files produces the same results I'm afraid this is a kernel bug. You don't seem to be using a stock debian kernel do you? Well, I do, at least it came right from ftp.de.debian.org. I've tried the 2.6.32-5 package in the meantime and the 2.6.35 from experimental, without the issue changing (interestingly, however, the 600 MHz cap was raised to 900 MHz). If you are (or you can reproduce the bug with a stock debian kernel) we can reassign the bug to the kernel package otherwise your best bet is trying to seek help on the cpufreq mailing list but you'll need to try using 2.6.35 at least. Well, it's not very urgent for me, so reassign might be the best option. I'll do the reassign (if I can, I'll try now :-). Thanks and best regards, Steve -- Steve Wolter (Bielefeld Univ.) | Web page: http://swolter.sdf1.org | vCard:http://swolter.sdf1.org/swolter.vcf A witty saying proves nothing. | Schedule: http://swolter.sdf1.org/sched.cgi -- Voltaire (1694-1778) | E-mail: swol...@sdf.lonestar.org signature.asc Description: Digital signature
Bug#592662: cpufrequtils: Cannot set frequency range of policy to full hardware frequency range
On Mon, 2010-08-16 at 16:04 +0200, Steve Wolter wrote: Hi Matthia, Mattia Dongili schrieb: On Wed, Aug 11, 2010 at 10:35:15PM +0200, Steve Wolter wrote: Package: cpufrequtils Version: 007-1 Severity: normal When using cpufrequtils or the kernel interface to the acpi-cpufreq module on my VIA Eden 1.5 GHz CPU, I cannot set the frequency range for the governor to the full hardware range. Trying to do so produces weird frequency settings. Any of the two single frequencies offered by the hardware can be included in a range, but not both at once. well, if writing values directly to the /sys/devices/system/cpu*/cpufreq files produces the same results I'm afraid this is a kernel bug. You don't seem to be using a stock debian kernel do you? Well, I do, at least it came right from ftp.de.debian.org. I've tried the 2.6.32-5 package in the meantime and the 2.6.35 from experimental, without the issue changing (interestingly, however, the 600 MHz cap was raised to 900 MHz). [...] Since you have reproduced this in Linux 2.6.35, please report this upstream at https://bugzilla.kernel.org under product 'ACPI', component 'Power-Processor'. Let us know the bug number or URL so that we can track it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#592662: cpufrequtils: Cannot set frequency range of policy to full hardware frequency range
Package: cpufrequtils Version: 007-1 Severity: normal When using cpufrequtils or the kernel interface to the acpi-cpufreq module on my VIA Eden 1.5 GHz CPU, I cannot set the frequency range for the governor to the full hardware range. Trying to do so produces weird frequency settings. Any of the two single frequencies offered by the hardware can be included in a range, but not both at once. Example transcript (lines replaced by [...] where identical to previous output): sudo cpufreq-set --governor ondemand --min 400MHz --max 1500MHz; cpufreq-info cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@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: 400 MHz - 1.50 GHz available frequency steps: 1.50 GHz, 400 MHz available cpufreq governors: powersave, conservative, userspace, ondemand, performance current policy: frequency should be within 400 MHz and 600 MHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 400 MHz. sudo cpufreq-set --governor ondemand --min 401MHz --max 1500MHz; cpufreq-info [...] current policy: frequency should be within 401 MHz and 1.50 GHz. [...] current CPU frequency is 1.50 GHz. sudo cpufreq-set --governor ondemand --min 400MHz --max 500MHz; cpufreq-info [...] current policy: frequency should be within 400 MHz and 500 MHz. [...] current CPU frequency is 400 MHz. sudo cpufreq-set --governor ondemand --min 400MHz --max 700MHz; cpufreq-info [...] current policy: frequency should be within 400 MHz and 600 MHz. [...] current CPU frequency is 400 MHz. sudo cpufreq-set --governor userspace --min 400MHz --max 1500MHz; cpufreq-info [...] current policy: frequency should be within 400 MHz and 600 MHz. The governor userspace may decide which speed to use within this range. current CPU frequency is 400 MHz. cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 13 model name : VIA Eden Processor 1500MHz stepping: 0 cpu MHz : 400.000 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce apic sep mtrr pge cmov pat clflush acpi mmx fxsr sse sse2 tm nx pni est tm2 xtpr rng rng_en ace ace_en ace2 ace2_en phe phe_en pmm pmm_en bogomips: 799.71 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 32 bits virtual power management: Thanks for your efforts. If you need any more information, let me know. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-486 Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cpufrequtils depends on: ii debconf [debconf-2.0] 1.5.33 Debian configuration management sy ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcpufreq0 007-1 shared library to deal with the cp ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip cpufrequtils recommends no packages. cpufrequtils suggests no packages. -- debconf information: cpufrequtils/enable: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592662: cpufrequtils: Cannot set frequency range of policy to full hardware frequency range
Hi Steve, On Wed, Aug 11, 2010 at 10:35:15PM +0200, Steve Wolter wrote: Package: cpufrequtils Version: 007-1 Severity: normal When using cpufrequtils or the kernel interface to the acpi-cpufreq module on my VIA Eden 1.5 GHz CPU, I cannot set the frequency range for the governor to the full hardware range. Trying to do so produces weird frequency settings. Any of the two single frequencies offered by the hardware can be included in a range, but not both at once. well, if writing values directly to the /sys/devices/system/cpu*/cpufreq files produces the same results I'm afraid this is a kernel bug. You don't seem to be using a stock debian kernel do you? If you are (or you can reproduce the bug with a stock debian kernel) we can reassign the bug to the kernel package otherwise your best bet is trying to seek help on the cpufreq mailing list but you'll need to try using 2.6.35 at least. ... Kernel: Linux 2.6.32-trunk-486 Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) regards, -- mattia :wq! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
