Jan Kiszka wrote:
> Hi,
> I'm hitting that bug check in __xnpod_schedule after
> xnintr_clock_handler issued a xnpod_schedule like this:
>       if (--sched->inesting == 0) {
>               __clrbits(sched->status, XNINIRQ);
>               xnpod_schedule();
>       }
> Either the assumption behind the bug check is no longer correct (no call
> to xnpod_schedule() without a real need), or we should check for
> __xnpod_test_resched(sched) in xnintr_clock_handler (but under nklock then).
> Comments?

You probably have a real bug. This BUG_ON means that the scheduler is
about to switch context for real, whereas the resched bit is not set,
which is wrong.


Xenomai-core mailing list

Reply via email to