-- On Wed, 31 Oct 2007, Arjan van de Ven wrote: > On Wed, 31 Oct 2007 11:00:56 -0400 (EDT) > Steven Rostedt <[EMAIL PROTECTED]> 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...
Could be just a development glitch on my part, but there were times (IIRC) I would not get a dump from a fault inside the interrupt handler, but I would get the report of the killing of the interrupt handler. Seems that I need to start recording the issues I've had with a kernel bug not dumping a stack and doing a panic (which did nothing). And then I can get back to you ;-) -- Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
