![](https://seccdn.libravatar.org/avatar/55325b2dec7811006ffd06aa7c37565a.jpg?s=120&d=mm&r=g)
On Wed, 2007-07-25 at 13:47 +0200, Dieter Jurzitza wrote:
Dear Thomas, dear listmembers, I know I owe answers (specifically to Thomas), so here you go:
"Stock" kernel 2.6.21-185 (not in use any more, stem from kernel repositories at that time: Backlight full power, ipw3945 full power mode: 15,7 Watts power consumption (average)
"Modified" kernel 2.6.21-190 (derived from above, only the following options activated: CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_USB_SUSPEND=y CONFIG_TIMER_STATS=y
Backlight full power, ipw3945 full power mode: 12,6 Watts.
Backlight full power, ipw3945 in low power consumption mode: 11,4 Watts.
Backlight totally dimmed and ipw3945 in low power mode: 9,5 Watts
so yes, you were right, the kernel options are not _that_ effective. But three Watts still remain an impressive value. What you say about stability of the kernel options - well, I can tell for my laptop only that since the day I switched to this kernel including the options mentioned above I haven't seen a single crash - the issues I had been facing before were mainly related to suspend issues. Nevertheless from my limited scope of view these options seem to do no harm - and a commenter in the wiki said that Ubuntu and Fedora would acitvate them by default.
What regards the loading induced by zen-updater and opesuseupdater I will provide a follow-up soon.
And, sorry, it would take tons of time to rebuild the kernel with each option activated separately to distinguish what contributes how much. If there is no urgent need for this I would be glad if you can survive without that information. Come back to me if you really really need it - and tell me the activation sequence you'd want to see. Dieter, thanks a lot. Such values are really helpful and cost a lot of time to do...
Just one question: Have you used an USB device while doing this? Hmm, you could have some built in USB device... What I like to find out: USB suspend works, AFAIK: if an USB suspend capable device is unused for a specific time, it's suspended (after 2 seconds per default). The kernel does not need to poll it every some micro seconds (yes USB is stupid) and therefore the C-states are much more efficient. It wakes up itself if it gets used again by an interrupt. E.g. if you do not use your (new enough) mouse for 2 seconds, it's suspend and not functional any more. If you hit a specific button (the one in the middle normally), the mouse generates an interrupt, the device gets polled again and works, but the processor consumes more power (because it's not going to C-states that often anymore). Could you somehow find out whether it was the USB autosuspend kicking in, suspending a device or whether it's the NO_HZ option? Maybe you can simply use your low energy kernel (I expect you use it by default :) ) and disable autosuspend (find /sys |grep autosuspend) and echo -1 > into the found files..., then autosupend should not kick in for sure. Hmm, I doubt a USB device got suspended, if you don't find the time to do this, then just don't care... Maybe you have another idea to find out or if anything additional comes to your mind about these values, I'd be happy to know. BTW: Maybe you've already noticed, CONFIG_TIMER_STATS is enabled in our very recent kernels (Alpha6 should already be compiled with that one). Ahh yes, how many C-states does your processor support? Could you post /proc/acpi/processor/*/power Thanks, Thomas
Dieter
Am Dienstag, 10. Juli 2007 19:54 schrieb Thomas Renninger: ****
Could you give us a pointer what kind of events happen how often, pls. And how they keep loading the battery. Through not going into Cx state Is it really that much? What have you modified? Simply booting the one or the other kernel saves you that much (-> I doubt that)? Do you use an USB mouse/keyboard that gets autosuspended with the other kernel?
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-mobile+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mobile+help@opensuse.org