Messages in this thread | | | Date | Thu, 10 Jul 2003 17:12:31 +0200 | From | Stephan von Krawczynski <> | Subject | Re: 2.4.22-pre3 and reiserfs boot problem |
| |
On Thu, 10 Jul 2003 16:44:28 +0200 Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net> wrote:
> > I have currently nmi_watchdog=1 which works (NMI interrupts show up during > > normal operation), but there is no backtrace visible or producable during > > the freeze, sorry. > > How is that possible? If the NMI watchdog works but doesn't fire, the > lockup should respond to SysRq-T. Could you please try SysRq-T *before* > the hang just to verify that it would work?
Well, the thing I don't really understand about SysRq-X is that the output is visible by dmesg-command, but I cannot see anything on the console (single user tested). This means it may well work in the hang-case, but as I cannot execute dmesg I will never see it...
Regards, Stephan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |