[Bug 233063] New: powersaved: changes concerning crufreq are ignored on restart
https://bugzilla.novell.com/show_bug.cgi?id=233063 Summary: powersaved: changes concerning crufreq are ignored on restart Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jo@feuersee.de QAContact: qa@suse.de No matter what settings are made to /etc/sysconfig/powersave/cpufreq, they are ignored when restarting powrsaved. The SYSV init script say about this topic: # Should start contains acpid apmd and cpufreqd, so that I can check # whether they are running and whether this script should fail # apmd and cpufreqd should never run together with this service Yes, this is correct. But w/ openSUSE 10.2 there isn't any cpufreqd etc. so changes made must be honored.Settings made to /etc/sysconfig/powersave/cpufreq (like CONSIDER_NICE) must not be ignored on powersaved restart -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |hmacht@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Comment #1 from hmacht@novell.com 2007-01-12 08:22 MST ------- As long as gnome-power-manager or kpowersave are running, they are in charge of caring about cpufreq. So this works as designed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 jo@feuersee.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Comment #2 from jo@feuersee.de 2007-01-12 08:39 MST ------- Both gnome-power-manager and kpowersave require X11 and a running user gnome/kde session -> not my topic here. Consider a backup server: it won't have much to do all the time, exept when backups are made or restored. In order to save power, it makes sense to let the CPU freq. scale down when idle, scale up when needed. Note: no X11 session involved here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 ------- Comment #3 from hmacht@novell.com 2007-01-12 09:45 MST ------- (In reply to comment #2)
Both gnome-power-manager and kpowersave require X11 and a running user gnome/kde session -> not my topic here.
Consider a backup server: it won't have much to do all the time, exept when backups are made or restored. In order to save power, it makes sense to let the CPU freq. scale down when idle, scale up when needed.
Note: no X11 session involved here.
Ok, sorry, I made the assumption that you are using a desktop. So which setting are you trying to adjust? If you set CONSIDER_NICE in /etc/powersave/cpufreq, you have to remove it from the scheme_* files, because the settings made there have higher priority and overwrite the settings made in the general config files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 ------- Comment #4 from jo@feuersee.de 2007-01-12 10:25 MST ------- If settings in /etc/powersave/cpufreq have lower prioritys than the scheme_* settings anyway, which purpose do they have? Most likeley, they will get overwritten by the scheme_* settings? The reason I opened this report was that I tried to tweak the settings for a server. To get some significant data, I tweaked 1 param every 24h (then reloaded powersaved), and came to the wrong assumption that CONSIDER_NICE doesn't affect anything. However, after a reboot, the server behaved quiet different. The CONSIDER_NICE="yes" was still active. AFAICS CONSIDER_NICE was introduced to /etc/powersave/cpufreq with openSUSE 10.2 (there is no such setting in 10.1). Why is this setting honord on reboot, but not by eg. powersaved restart? From you last post, I would expect that the scheme_* settings always rule over cpufreq. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME ------- Comment #5 from hmacht@novell.com 2007-01-26 03:28 MST ------- (In reply to comment #4)
If settings in /etc/powersave/cpufreq have lower prioritys than the scheme_* settings anyway, which purpose do they have? Most likeley, they will get overwritten by the scheme_* settings?
By default, there shouldn't be any duplicate settings in cpufreq and scheme_*, and if so, only for documentation purposes.
The reason I opened this report was that I tried to tweak the settings for a server. To get some significant data, I tweaked 1 param every 24h (then reloaded powersaved), and came to the wrong assumption that CONSIDER_NICE doesn't affect anything. However, after a reboot, the server behaved quiet different. The CONSIDER_NICE="yes" was still active.
AFAICS CONSIDER_NICE was introduced to /etc/powersave/cpufreq with openSUSE 10.2 (there is no such setting in 10.1).
There was, at least in scheme_* files.
Why is this setting honord on reboot, but not by eg. powersaved restart? From you last post, I would expect that the scheme_* settings always rule over cpufreq.
Works here just fine without kpowersave or gnome-power-manager running. Sorry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 ------- Comment #6 from jo@feuersee.de 2007-01-26 05:43 MST ------- Could you clarify what excactly "works" for you? 1) Setting CONSIDER_NICE="yes" in /etc/powersave/cpufreq and reloading powersaved (resulting to powersaved considers nice'd processes when dynamically assigning CPU freq) or 2) Changing the value of CONSIDER_NICE in the scheme_* files and reloading powersaved (resulting to the same) ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 ------- Comment #7 from hmacht@novell.com 2007-01-26 05:56 MST ------- (In reply to comment #6)
Could you clarify what excactly "works" for you?
1) Setting CONSIDER_NICE="yes" in /etc/powersave/cpufreq and reloading powersaved (resulting to powersaved considers nice'd processes when dynamically assigning CPU freq)
This works if I remove the config variable CONSIDER_NICE from the scheme file which is active on boot (either scheme_performance or scheme_powersave). Otherwise the setting included int the scheme_* file would be taken into account.
2) Changing the value of CONSIDER_NICE in the scheme_* files and reloading powersaved (resulting to the same) ?
Yes, this always works, no matter if there is a CONSIDER_NICE option in /etc/powersave/cpufreq or not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 ------- Comment #8 from jo@feuersee.de 2007-01-26 06:08 MST ------- THX for clarifying. For future releases IMHO there should at least be a hint in the the comments of cpufreq that the CONSIDER_NICE setting will be overwritten by the current scheme if avail. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=233063 ------- Comment #9 from hmacht@novell.com 2007-01-26 06:15 MST ------- The strange thing is that you have a CONSIDER_NICE variable in /etc/powersave/cpufreq at all. This shouldn't be there. It definitely shouldn't be there in future releases. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com