The first, 2.6.35-0unpatched+18.24~lucid, is essentially just maverick's 2.6.35-18.24 built for lucid. Note that despite the name 'unpatched', it still has the patch for this bug because that has been included in maverick's standard kernel.
The second kernel, 2.6.35-power+18.24~lucid, should be identical except that CONFIG_LATENCYTOP, CONFIG_SCHED_DEBUG, and CONFIG_SCHEDSTATS have been removed from the configuration.
Does anyone else observe the same thing as devsk, that on a kernel with the latencytop and scheduler statistics options disabled, wakes per second are lower? Or do they remain the same?
(BTW, I also uploaded a 'power' kernel for maverick, which can be compared against 2.6.35-18.24.)
Based on devsk's comment, I've uploaded two kernels for lucid to my power-saving PPA: /launchpad. net/~brian- rogers/ +archive/ power
https:/
The first, 2.6.35- 0unpatched+ 18.24~lucid, is essentially just maverick's 2.6.35-18.24 built for lucid. Note that despite the name 'unpatched', it still has the patch for this bug because that has been included in maverick's standard kernel.
The second kernel, 2.6.35- power+18. 24~lucid, should be identical except that CONFIG_LATENCYTOP, CONFIG_SCHED_DEBUG, and CONFIG_SCHEDSTATS have been removed from the configuration.
Does anyone else observe the same thing as devsk, that on a kernel with the latencytop and scheduler statistics options disabled, wakes per second are lower? Or do they remain the same?
(BTW, I also uploaded a 'power' kernel for maverick, which can be compared against 2.6.35-18.24.)