The oopses scrolling by all starts with
init exited with preempt-count xx
where xx increase by 3 for each oops.
The call trace is longer each time.
The scrolling stops when this counter reach 63 or 66,
probably running out of some resource such as kernel stack.
I haven't written down the last oops assuming it is the first
one that is interesting, but I can reproduce and write
down details if someone thinks it makes a difference.
The kernels are compiled with preempt, vesafb, devfs.
Recompiling without preempt gives me a kernel
that works fine.
This preempt problem seems to have existed at least
since 2.5.12-dj1, it took some time before I figured
out it was a preempt problem.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/