The above also occurred with no SMP.
I backed out Changeset 1.606 which did this in kernel/sched.c:
- if (unlikely(in_interrupt()))
+ if (unlikely(in_atomic()))
and 2.5.34-mm2 was able to boot with CONFIG_PREEMPT=y.
Obviously, this is not a fix of any kind, but shows that the scheduler
may be being called with a preemption lock.
Steven
-
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/