Gilles Chanteperdrix wrote: > 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.
This happened over my 2.6.35 port - maybe some spurious IRQ enabling. Debugging further... Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux _______________________________________________ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core