> On Thu, 16 Jul 1998, Andi Kleen wrote:
>
> > Umm, no. The paths that sends signals to processes (SIGSEGV, SIGBUS etc.)
> > have their own handlers and are not dispatched through the usual do_IRQ().
> > You'll see that if you follow the interrupt entry code in entry.S.
>
> I' ll take a look... What I need to know is _why_ my kernel locked
> yesterday.
a missed 'current->counter -= ticks', and infinitly running user-space
code? Since the need_resched flag is detected after returning from
do_IRQ(), schedule() never sees the decrement and will always select that
process, causing a 'soft hang', where you can ping the box but nothing
really works. Does this describe your hang?
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html