On Wed, 10 Apr 2013, Frederic Weisbecker wrote: > I don't know which tree you are using. But if you have that patch in:
This is tip timers/nohz > http://git.kernel.org/cgit/linux/kernel/git/frederic/linux-dynticks.git/commit/?h=3.9-rc1-nohz1&id=451128553e5e827dccc6cbcd24238470ec693d90 > looking at the traces on that CPU may give you a few hints. Then you can > dig deeper by looking at the sched_switch, timers, irq, ... events The last time when I checked this before testing this rev it turned out that nr_running was always > 1. Traces did only show that the timer interrupt was still on. I added printks to figure out what was up at that time which was a bit awkward since the kernel is a bit sensitive about doing printks in these functions. Sadly, I am suffering from manageritis these days and probably wont have the time to get into this again for the next two weeks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
