On Tue, Jun 12, 2012 at 11:22:02AM -0400, Prarit Bhargava wrote: > [This seems to have been missed ... sending again] > > On a large system with a large number of tasks, the output of > > echo t > /proc/sysrq-trigger > > can take a long period of time. If this period is greater than the period > of the current clocksource, the clocksource watchdog will mark the > clocksource as unstable and fail the clocksource over.
A lot of our customers are running into this issue (especially the big boxes). This is patch solves their problem nicely. The approach is a little heavier than the current approach, but it allows a useful feature like sysrq-t to work reliably. Acked-by: Don Zickus <[email protected]> -- 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/
