Re: [PATCH] dump_stack on panic

[Arjan van de Ven]

On Wed, 31 Oct 2007 11:00:56 -0400 (EDT)
Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> 
> I've had too many issues in development where I hit a panic and it
> gives me nothing to tell me why.
> 
> At the very least, we should have a dump_stack in areas that are
> usually caused by kernel bugs. For example, killing an interrupt
> handler.
> 

here's the deal.... the killing of an interrupt handler because of an
oops THEN causes a panic. If you dump stack AGAIN, you have 2 stack
traces, with the first one being the real good one, and the second one
being.. well more crappy... so you proposal just dropped the good
stacktrace off the screen in favor of a worse one...




-- 
If you want to reach me at my work email, use arjan@xxxxxxxxxxxxxxx
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/