On Sat, 2013-06-29 at 19:44 -0400, Dave Jones wrote: > Yeah, this is running as a user. Those don't sound like things that should > be possible. What instrumentation could I add to figure out why > that kthread got awakened ?
trace-cmd record -e sched_wakeup -f 'comm ~ "migrati*"' Add "-O stacktrace" to see where they got woken up too. -- Steve -- 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/
