Messages in this thread | | | Date | Fri, 14 Oct 2005 10:53:21 +0200 | From | Ingo Molnar <> | Subject | Re: 2.6.14-rc4-rt1 |
| |
* Ingo Molnar <mingo@elte.hu> wrote:
> > could you try: > > > > strace -o log sleep 10 > > > > and wait for a failure, and send us the log? Is it perhaps nanosleep > > unexpectedly returning with -EAGAIN or -512? There's a transient > > nanosleep failure that happens on really fast boxes, which we havent > > gotten to the bottom yet. That problem is very sporadic, but maybe > > your box is just too fast and triggers it more likely :-) > > is nanosleep returning -ERESTART_RESTARTBLOCK (-516) perhaps?
ok, i fixed the -ERESTART_RESTARTBLOCK bug that fast systems were exhibiting. But this bug is limited to HIGH_RES_TIMERS kernels, so it cannot explain your problems i think.
in any case, could you try the -rc4-rt3 patch i just uploaded - it also includes more ktimer debugging code, perhaps one of them triggers on your box.
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |