Am Mittwoch 24 Mai 2006 22:05 schrieb George Anzinger: > Florian Beier wrote: > > The problem wasn't the watchdog, which was properly configured... > > I had to stop the syslog daemon which took the stacktrace so that I got > > nothing on the remote machine... > > Could you explain this further? The stack trace syslog took, for example.
Actually all I can say is that as long as the syslog daemon was started, no log messages appeared on the remote machine. So the stacktrace didn't show up on the remote machine, too. > > So the bug is fixed now. > > What did you do and what was the result? The bug was a double called spinlock, which was calles in some special cases. > If KGDB was entered at this > point, what is does bt and kgdbinfo show? I.e. we need to understand how > kgdb was entered and thus why what you did fixed it. I wasn't able to set a breakpoint, because the module was called several times per second, but the freeze occured after minutes... ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
