NMI watchdog works correctly on intel family of processors. KGDB is hooked to nmi watchdog so that infinite loops with interrupts disabled can be caught.
Since this doesn't seem to help this case, it's probably the case of a double fault or something similar. An NMI trick (isa cards etc) won't work in that case. good old printk may help you to track a trace of where it's going. -Amit On Thursday 18 May 2006 01:46, George Anzinger wrote: > Florian Beier wrote: > > Hi, > > I am trying to debug a system freeze caused by our own kernel module... > > I am using a serial interface and kgdb. > > When the system freezes, the only possibility in the remote gdb is to > > stop the debugging session because I cannot press 'ctrl c' anymore > > (because the test machine is dead). > > So how am I supposed to get a kernel stack or any helpfull information? > > It is hardly possible to set a breakpoint because the module functions > > are called serveral times a second and the system runs sometimes hours > > without problems... > > The best off the self solution is the NMI watchdog. Failing that, there > are ways to generate NMIs manually using a switch to directly send a signal > to the backplane. > > You might check out http://www.microsoft.com/whdc/system/CEC/dmpsw.mspx for > PCI card sets or the attached for ISA machines. > > (This info should be part of the kgdb documentation...) ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
