It seems that the commit that went into 2.6.27 can't be backported to .26. But, hrtick, what is causing the problem, can be disabled.
The patch to disable hrtick that applies on a vanila 2.6.26.2 kernel and should also apply to Ubuntu's kernel is below. That patch (or similar) should go into 2.6.26.3 or 2.6.26.4. See discussion here:
A full fix to hrtick went into 2.6.27
(31656519e132f6612584815f128c83976a9aaaef),
but that fix is too intrusive to backport. Henceforth, we default to
disable hrtick.
It seems that the commit that went into 2.6.27 can't be backported to .26. But, hrtick, what is causing the problem, can be disabled.
The patch to disable hrtick that applies on a vanila 2.6.26.2 kernel and should also apply to Ubuntu's kernel is below. That patch (or similar) should go into 2.6.26.3 or 2.6.26.4. See discussion here:
http:// lkml.org/ lkml/2008/ 8/19/311
-----------------
The hrtick implementation in 2.6.25 and .26 has been known to cause boot
problems with at least Intel GMA cards. see:
https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 15602 bugzilla. kernel. org/show_ bug.cgi? id=10892
http://
A full fix to hrtick went into 2.6.27 612584815f128c8 3976a9aaaef) ,
(31656519e132f6
but that fix is too intrusive to backport. Henceforth, we default to
disable hrtick.
Signed-off-by: Justin Madru <email address hidden>
Tested-by: Justin Madru <email address hidden>
Cc: Peter Zijlstra <email address hidden>
Cc: Ingo Molnar <email address hidden>
--- a/kernel/ sched_features. h sched_features. h FEAT(AFFINE_ WAKEUPS, 1) FEAT(CACHE_ HOT_BUDDY, 1) FEAT(SYNC_ WAKEUPS, 1) FEAT(DOUBLE_ TICK, 0) FEAT(NORMALIZED _SLEEPER, 1) FEAT(DEADLINE, 1)
+++ b/kernel/
@@ -4,7 +4,7 @@
SCHED_
SCHED_
SCHED_
-SCHED_FEAT(HRTICK, 1)
+SCHED_FEAT(HRTICK, 0)
SCHED_
SCHED_
SCHED_