|
Bugzilla – Full Text Bug Listing |
| Summary: | "Dynamic" CPU frequency policy in powersave does not work well | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Daniel Wolstenholme <daniel> |
| Component: | Basesystem | Assignee: | Thomas Renninger <trenn> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | venkatesh.pallipadi |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Daniel Wolstenholme
2005-09-29 05:14:01 UTC
Is Hyperthreading enabled?
Does it help if you set CPUFREQ_CONTROL="" to CPUFREQ_CONTROL="userspace" in
/etc/sysconfig/powersave/cpufreq and restart the powersave daemon ("rcpowersave
restart")?
If both is true, does it help if you disable hyperthreading in BIOS and use
CPUFREQ_CONTROL="kernel" -> do not forget to restart the powersave daemon again.
Hmmm, Pentium 4 3.6 GHz going down to 450 MHz seems to me as Intel is faking
speedstep with throttling through ACPI abstraction?!?
what cpufreq driver are you using? on boot, there should be a line like "rcpowersaved: enter 'speedstep_centrino' into CPUFREQD_MODULE in /etc/sysconfig/powersave/cpufreq." in /var/log/messages. (probably not speedstep_centrino, but the module used on your machine, just grep for CPUFREQD_MODULE in /var/log/messages). Probably p4-clockmod driver is getting used here today? I haven't seen P4 3.6GHz system running at 450 MHz with speedstep-centrino or acpi-cpufreq driver. The minimum frequency with those two drivers should be around 2.8GHz. OK, we should remove the p4-clockmod driver from our distri. People are getting confused and think it helps to save power, but it already is used through /proc/acpi/processor/.../throttling and there could happen bad things if both interfaces are used as it is probably the case here. I will close this one as invalid in case you have used the p4-clockmod driver. Reopen the bug if you have not. |