Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#8674 - cpufrequtils on Core Duo - only one cpu scales on boot
Attached to Project:
Arch Linux
Opened by Peter Booth (ploub) - Saturday, 17 November 2007, 08:02 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 17 November 2007, 12:25 GMT
Opened by Peter Booth (ploub) - Saturday, 17 November 2007, 08:02 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 17 November 2007, 12:25 GMT
|
DetailsDescription:
Using T2300 Centrino Duo. I have acpi-cpufreq cpufreq_ondemand in rc.conf modules array and cpufreq in daemons. On boot only cpu0 goes in to 'ondemand', cpu1 starts in 'performance' mode. I have to manually set cpu1 to 'ondemand'. I believe this behaviour occurred only after upgrade to kernel 2.6.23. Additional info: * package version(s): cpufrequtils-002-1 * config and/or log files etc: cpufreq-info on startup: cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to linux@brodo.de, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 996 MHz - 1.66 GHz available frequency steps: 1.66 GHz, 1.33 GHz, 996 MHz available cpufreq governors: powersave, ondemand, performance current policy: frequency should be within 996 MHz and 1.66 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 996 MHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 1 hardware limits: 996 MHz - 1.66 GHz available frequency steps: 1.66 GHz, 1.33 GHz, 996 MHz available cpufreq governors: powersave, ondemand, performance current policy: frequency should be within 996 MHz and 1.66 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.66 GHz. /etc/conf.d/cpufreq: #configuration for cpufreq control # valid governors: # ondemand, performance, powersave, # conservative, userspace governor="ondemand" # governor="powersave" # governor="performance" # valid suffixes: Hz, kHz (default), MHz, GHz, THz max_freq="1.66GHz" min_freq="996MHz" Steps to reproduce: |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Saturday, 17 November 2007, 12:25 GMT
Reason for closing: Not a bug
Saturday, 17 November 2007, 12:25 GMT
Reason for closing: Not a bug
FS#64401. Omitting the -c or --cpu argument is equivalent to setting it to zero
it's not a bug it's normal