On Sat, Nov 09, 2013 at 12:32:06PM +0400, Alexander Beregalov wrote: > Hi, > It first appeared some time after 3.9 or 3.10 and still persist. > I guess bisect is not required? > > WARNING: CPU: 1 PID: 6 at kernel/time/tick-sched.c:187 > can_stop_full_tick+0x8d/0x9a() > NO_HZ FULL will not work with unstable sched clock
Right, it's not a bug, just a warning we've put to make sure that users of full dynticks are aware of limitations when the sched clock is unstable. That's something we want to fix in the long run as it seems that quite a lot of people have unstable tsc. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
