Re: NMI Watchdog detected LOCKUP on CPU1 (stext_lock)(2.4.0-test9-pre2)

From: Andrea Arcangeli (andrea@suse.de)
Date: Wed Sep 20 2000 - 10:18:04 EST

Next message: Steve Hill: "Kernel oops & panic in ISDN"
Previous message: J Brook: "[Oops] Unable to handle kernel NULL pointer dereference"
In reply to: Andrew Morton: "Re: NMI Watchdog detected LOCKUP on CPU1 (stext_lock)(2.4.0-test9-pre2)"
Next in thread: Anton Blanchard: "Re: NMI Watchdog detected LOCKUP on CPU1 (stext_lock)(2.4.0-test9-pre2)"
Reply: Anton Blanchard: "Re: NMI Watchdog detected LOCKUP on CPU1 (stext_lock)(2.4.0-test9-pre2)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Sep 21, 2000 at 12:42:25AM +1100, Andrew Morton wrote:
> What about the ALT-SYSRQ-P thing? I guess that wouldn't be necessary if
> handle_sysrq() did a show_stack(0), which it doesn't, and probably
> should.

Yes, SYSRQ+P should definetly show the stack trace.

Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Steve Hill: "Kernel oops & panic in ISDN"
Previous message: J Brook: "[Oops] Unable to handle kernel NULL pointer dereference"
In reply to: Andrew Morton: "Re: NMI Watchdog detected LOCKUP on CPU1 (stext_lock)(2.4.0-test9-pre2)"
Next in thread: Anton Blanchard: "Re: NMI Watchdog detected LOCKUP on CPU1 (stext_lock)(2.4.0-test9-pre2)"
Reply: Anton Blanchard: "Re: NMI Watchdog detected LOCKUP on CPU1 (stext_lock)(2.4.0-test9-pre2)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 21:00:23 EST