|
Bugzilla – Full Text Bug Listing |
| Summary: | CPU throttling not applied | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Michael Stather <kontakt> |
| Component: | Mobile Devices | Assignee: | Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michael Stather
2005-09-25 13:25:35 UTC
are you sure you are not mixing things up? Throttling has nothing to do with "performance", "powersave" and "dynamic", but with - erm - throttling. It works additionally to cpu frequency scaling. So do the following when on AC and when on battery (probably waiting some seconds to let the throttling timeout jump in): powersave -c # shows cpufreq policy powersave -t # shows throttling info powersave -x # shows the active scheme and report back what the results are. Sorry I really mixed thigs up. I only know of "frequency scaling", this is what doesn´t work here. What´s throttling BTW? The output of the powersave info is: With AC: michael@michilap:~> powersave -c PERFORMANCE michael@michilap:~> powersave -t Throttling not supported michael@michilap:~> powersave -x Performance active AC_default_scheme Powersave battery_default_scheme michael@michilap:~> With battery: michael@michilap:~> powersave -c PERFORMANCE michael@michilap:~> powersave -t Throttling not supported michael@michilap:~> powersave -x Performance AC_default_scheme Powersave active battery_default_scheme So the cpufreq change fails and throttling isn´t supported at all. ok. so what does "grep CPUFREQ /etc/sysconfig/powersave/scheme_*" say? what cpufreq module are you using? (should be in the log from powersaved start, "grep "CPUFREQD_MODULE" /var/log/messages"). If you are using speedstep-smi, please watch out for the following message: "Try CPUFREQ_CONTROL=userspace in /etc/sysconfig/powersave/cpufreq." in /var/log/messages. michael@michilap:~> grep CPUFREQ /etc/sysconfig/powersave/scheme_* /etc/sysconfig/powersave/scheme_performance:CPUFREQUENCY="performance" /etc/sysconfig/powersave/scheme_powersave:CPUFREQUENCY="dynamic /var/log/messages contains the following messages related to CPUFREQ Sep 26 16:20:40 michilap rcpowersaved: enter 'speedstep_ich' into CPUFREQD_MODULE in /etc/sysconfig/powersave/cpufreq. Sep 26 16:20:40 michilap rcpowersaved: this will speed up starting powersaved and avoid unnecessary warnings in syslog. Sep 26 16:20:40 michilap kernel: bootsplash: status on console 0 changed to on Sep 26 16:20:40 michilap [powersave]: ERROR (CPUFreq_Kernel:21) Can not set ondemand governor, maybe your cpufreq driver is too slow. Sep 26 16:20:40 michilap [powersave]: ERROR (CPUFreq_Kernel:23) Try CPUFREQ_CONTROL=userspace in /etc/sysconfig/powersave/cpufreq. Sep 26 16:20:40 michilap [powersave]: WARNING (setConfig:126) Problems with ondemand governor, could not write up_threshold. (In reply to comment #4) > Sep 26 16:20:40 michilap [powersave]: ERROR (CPUFreq_Kernel:21) Can not set > ondemand governor, maybe your cpufreq driver is too slow. > Sep 26 16:20:40 michilap [powersave]: ERROR (CPUFreq_Kernel:23) Try > CPUFREQ_CONTROL=userspace in /etc/sysconfig/powersave/cpufreq. Well, this log message is there for a reason... :-) > Sep 26 16:20:40 michilap [powersave]: WARNING (setConfig:126) Problems with > ondemand governor, could not write up_threshold. This is only the consequence. Short: duplicate. If userspace does not work, please reopen. *** This bug has been marked as a duplicate of 113615 *** |