It looks like nohz_ratelimit will be reverted for 2.6.35, which is essentially the change included in the power2 kernel. But the power2 kernel also includes changes scheduled for 2.6.36. So to ensure that the revert alone is enough to solve the problem, I'm uploading a power3 kernel with only the revert.
If the power3 kernel is fine, then this will be solved in the final 2.6.35 kernel and therefore Maverick. Now the bad news: this fix can't be backported to Lucid's 2.6.32 because it's simply the removal of something added after 2.6.32. In other words, Lucid suffers from this problem for a different reason. On the bright side, it's apparently something that was fixed later, so it should be possible to look at post-2.6.32 scheduler changes and find a fix. -- Tens of wakes per second in "[kernel scheduler] Load balancing tick" on Core 2 Duo even with only 1 core enabled https://bugs.launchpad.net/bugs/524281 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
