As discovered by a Phoronix reader, there is a patch in the Linux 220.127.116.11 kernel that can partially improve the system's power performance. The patch by a Nokia engineer is entitled "cpuidle: menu: fixed wrapping timers at 4.294 seconds" and initial reports have said that it will lower the power consumption compared to the stock 2.6.39 kernel.
"Cpuidle menu governor is using u32 as a temporary datatype for storing nanosecond values which wrap around at 4.294 seconds. This causes errors in predicted sleep times resulting in higher than should be C state selection and increased power consumption. This also breaks cpuidle state residency statistics."
This patch was then brought up in LaunchPad Bug #760131, which is the Ubuntu bug report tracking this upstream kernel problem. Those that have tested this patch / the Linux 18.104.22.168 have reported their power consumption has dropped along with lower operating temperatures now that the CPUs are switching properly to their lower C-states and staying there. However, this does not address the complete Linux kernel problem.
A round of Phoronix power tests were carried out today to see the impact of the 22.214.171.124 kernel. While the power consumption on 126.96.36.199 is now lower than in the bugged Linux 2.6.38 release, it is still off. The Linux 188.8.131.52 power consumption is still elevated from its Linux 2.6.37 levels, which is the release before the big Linux kernel power regression. This suggests that this might not even be a fix for the real regression in the 2.6.38 merge window but rather just a power management improvement that is now landing. There is also at least one other Linux kernel power regression affecting a great number of systems. The average power consumption with the Linux 184.108.40.206 kernel is still up by an approximate 18~20% over older (Linux 2.6.34 era) kernels or over 22% for a system that's not affected by the Linux 2.6.35 power bug. While this 220.127.116.11 reduced power consumption is a nice improvement, there is still regressions left to bisect.
Discuss this article in our forums, IRC channel, or email the author. You can also follow our content via RSS and on social networks like Facebook, Identi.ca, and Twitter (@Phoronix and @MichaelLarabel). Subscribe to Phoronix Premium to view our content without advertisements, view entire articles on a single page, and experience other benefits.