* Steven Rostedt <[EMAIL PROTECTED]> wrote:
> So it is probably stuck in some spinning "yield" loop, which was the
> reason I was writing this test to begin with! It's most likely also
> waiting for kjournald to do some work, and is starving it in a
> schedule or yield loop never actually going to sleep letting kjournald
> do the real work.
actually, what priorities do the yielding tasks have? sched_yield() does
not guarantee that the CPU will be given up, of if a highest-prio
SCHED_FIFO task is in a yield() loop it will livelock the system.
Ingo
-
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/
