Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 166310 - CPU stuck on lowest speed when starting from battery
Summary: CPU stuck on lowest speed when starting from battery
Status: VERIFIED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-11 09:40 UTC by Erik
Modified: 2009-08-11 10:27 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik 2007-02-11 09:40:39 UTC
When I start my laptop from battery, I notice horrible performance. I look at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq and see that it is stuck at 600000 (lowest), no matter how much is needed. (/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq shows 1600000 and the scheduler is ondemand.) I have a compile running so it should be 1600000 (highest). Attaching it to power does not help, it has to be rebooted.

This makes the system almost unusable as a laptop. I can not take it with me somewhere, start it and work with it. What I have to do is to connect it to power somewhere, start it, disconnect it and take it with me. But this limits the usefulness greatly.

Reproducible: Always

Steps to Reproduce:




# grep -r "" /sys/devices/system
/sys/devices/system/clocksource/clocksource0/available_clocksource:acpi_pm jiffies tsc pit
/sys/devices/system/clocksource/clocksource0/current_clocksource:acpi_pm
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load:0
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold:80
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate:80000
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate_min:40000
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate_max:40000000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1600000 1600000 1600000 1400000 1200000 1000000 800000 600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:ondemand performance
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:centrino
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:ondemand
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:600000
# cat /proc/version
Linux version 2.6.18-gentoo-r6 (root@localhost) (gcc version 4.1.1 (Gentoo 4.1.1-r1)) #1 Thu Dec 28 15:19:30 CET 2006
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-02-11 10:08:29 UTC
Please, try w/ 2.6.19-r6 (and latest vanilla-sources if it still doesn't work) and report back. Thanks.
Comment 2 Erik 2007-02-16 15:55:42 UTC
I have tested to start from battery with 2.6.19-r5 and it went up to 1600000 when needed. But I tried again with 2.6.18-r6 and it worked there too this time. So it is not always reproducible (I have observed the bug a few times in the past). I will let you know if I make any more interesting observations about this.
Comment 3 Erik 2007-02-17 11:04:18 UTC
Now the bug has happened with 2.6.19-r5:
# grep -r "" /sys/devices/system
/sys/devices/system/clocksource/clocksource0/available_clocksource:acpi_pm jiffies tsc pit
/sys/devices/system/clocksource/clocksource0/current_clocksource:acpi_pm
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias:0
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load:0
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold:80
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate:80000
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate_min:40000
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate_max:40000000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1600000 1600000 1600000 1400000 1200000 1000000 800000 600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:ondemand performance
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:centrino
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:ondemand
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:600000
localhost ~ # cat /proc/version
Linux version 2.6.19-gentoo-r5 (root@localhost) (gcc version 4.1.1 (Gentoo 4.1.1-r3)) #1 Sun Feb 11 13:09:03 CET 2007
Comment 4 Erik 2009-08-11 10:27:26 UTC
Seems to work nowadays.