On 02/19/2014 04:27 PM, Steven Rostedt wrote: > Hmm, I wonder if this is because msleep() sets the tasks state to > TASK_UNINTERRUPTIBLE, and hrtimer_nanosleep sets it to > TASK_INTERRUPTIBLE. No, it is because freezable_schedule() is called via do_nanosleep() in hrtimer call path and msleep() calls schedule() without it. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
