[Bug 223986] New: [regression] power management does not work /at all/
https://bugzilla.novell.com/show_bug.cgi?id=223986 Summary: [regression] power management does not work /at all/ Product: openSUSE 10.2 Version: RC 1 Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de I have a Dell 2650 Inspiron laptop which has seen SuSE 9.1 through 10.1 and now openSUSE 10.2 RC1. Power management worked *great* in 10.0 and 10.1, and now doesn't work at all in 10.2 RC2. None of the modules get loaded (none of the cpudyn* modules), and neither kpowersaved nor the gnome applet seem to be able to do anything about it. If I load the modules by hand and restart powersaved *sometimes* it works. This is very frustrating - it makes my expected battery lifetime about 26 minutes! -- 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=223986 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jnelson-suse@jamponi.net ------- Comment #1 from mhorvath@novell.com 2006-11-27 15:05 MST ------- Please attach your yast log files, the /var/log/messages, boot.log, and boot.msg . http://en.opensuse.org/Bugs/YaST Thank you. -- 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=223986 jnelson-suse@jamponi.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jnelson-suse@jamponi.net | ------- Comment #2 from jnelson-suse@jamponi.net 2006-11-27 18:57 MST ------- I did some investigation and got it working, although it leads to some action items: The file /etc/sysconfig/powersave/cpufreq allowed the specification of the kernel module to load. This was a fallback mechanism which did not work for me. Apparently, powersave no longer uses this item in this file (I cannot speak for any other items in this file), it says acpid does. So I check out acpid and acpid claims that *it* no longer supports loading this information (it *does* source the file and does nothing with the information therein, which is IMO a small bug). The responsibility falls on HAL. Thus, item no. 1 is to document that the responsibility for loading the module is now HAL's job and neither powersave nor acpid's. Item no. 2 is to remove the erroneous include line in acpid's init script. There may be other files that are sourced as well that are not used. Item no. 3 is to have HAL get the parameter from a config file (/etc/sysconfig/powersve/cpufreq would be nice) but failing that to include p4-clockmod *which was not included in the list*. The static compilation of that list seems a little brittle to me but in any case the list is missing p4-clockmod (and p4_clockmod for the GREP line). Adding this information has allowed my powermanagement to work again. 2. CPUFREQD_MODULE="" -- 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=223986 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |hmacht@novell.com |screening@forge.provo.novell| |.com | Status|ASSIGNED |NEW -- 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=223986 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #3 from hmacht@novell.com 2006-11-28 10:04 MST ------- (In reply to comment #2)
I did some investigation and got it working, although it leads to some action items:
The file /etc/sysconfig/powersave/cpufreq allowed the specification of the kernel module to load. This was a fallback mechanism which did not work for me. Apparently, powersave no longer uses this item in this file (I cannot speak for any other items in this file), it says acpid does. So I check out acpid and acpid claims that *it* no longer supports loading this information (it *does* source the file and does nothing with the information therein, which is IMO a small bug). The responsibility falls on HAL.
Thus, item no. 1 is to document that the responsibility for loading the module is now HAL's job and neither powersave nor acpid's.
Yes, that's a bug. We were forced to move the loading of these modules to HAL at a late time in the process, so this variable didn't get removed although it's needless.
Item no. 2 is to remove the erroneous include line in acpid's init script. There may be other files that are sourced as well that are not used.
Ok, will have a look at that.
Item no. 3 is to have HAL get the parameter from a config file (/etc/sysconfig/powersve/cpufreq would be nice) but failing that to include p4-clockmod *which was not included in the list*. The static compilation of that list seems a little brittle to me but in any case the list is missing p4-clockmod (and p4_clockmod for the GREP line). Adding this information has allowed my powermanagement to work again.
No! Don't use p4_clockmod. It doesn't do frequency scaling but throttling. And throttling doesn't save you power, it only skips timer ticks making your system slow without any gain. p4_clockmod pretends to do scaling, but doesn't. That's the reason why it is not included in the list. In the initial comment you're writing that it saves you 26 minutes of battery life but I doubt that. Please come up with concrete figures if you are sure that's the case. Nevertheless, I will have a look at the remaining issues. -- 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=223986 ------- Comment #4 from jnelson-suse@jamponi.net 2006-11-28 11:26 MST ------- (In reply to comment #3)
(In reply to comment #2)
..
Item no. 3 is to have HAL get the parameter from a config file (/etc/sysconfig/powersve/cpufreq would be nice) but failing that to include p4-clockmod *which was not included in the list*. The static compilation of that list seems a little brittle to me but in any case the list is missing p4-clockmod (and p4_clockmod for the GREP line). Adding this information has allowed my powermanagement to work again.
No! Don't use p4_clockmod. It doesn't do frequency scaling but throttling. And throttling doesn't save you power, it only skips timer ticks making your system slow without any gain. p4_clockmod pretends to do scaling, but doesn't. That's the reason why it is not included in the list. In the initial comment you're writing that it saves you 26 minutes of battery life but I doubt that. Please come up with concrete figures if you are sure that's the case.
Well, I could watch my CPU frequency go from 1600 MHz to 200 MHz (and a couple of variable stops in between) while on battery (ie, 'dynamic' or 'powersave' schemes) and stick at 1600 MHz while plugged in ('performance' scheme). Furthermore, it's the *only* module that works with that machine, and it's recommended everywhere that I can google for it. According to this: (2.6.3 changelog) http://lwn.net/Articles/71228/ p4-clockmod does a 'variant' of frequency scaling while the others also do voltage scaling. I'd love it if the other modules (centrino or ich) worked with my machine but they don't - something is better than nothing.
Nevertheless, I will have a look at the remaining issues.
Thanks! -- 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=223986 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #5 from hmacht@novell.com 2007-01-22 07:26 MST ------- Fixed. An updated package will be out soon. -- 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=223986 ------- Comment #6 from ast@novell.com 2007-01-29 02:49 MST ------- released -- 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=223986 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED -- 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