Florian Beier wrote:
Am Freitag, 19. Mai 2006 00:57 schrieb George Anzinger:
Given this is an x86 box, I suspect a configuration problem around the NMI
rather than a double fault (which, I think, will force a reboot rather than
a hang). It is also possible that the system is not as frozen as you are
reporting...
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.
Really KGDB should have gotten this notify as part of the watchdog call. Me
thinks we are missing (or ignoring) a call to kgdb in this path.
So the bug is fixed now.
What did you do and what was the result? 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.
--
George Anzinger [EMAIL PROTECTED]
HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
-------------------------------------------------------
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
