watchdogs and kdump
dzickus at redhat.com
Thu Oct 27 16:30:29 EDT 2011
I was assisting a customer the other day debugging a kdump problem, when we
noticed the real problem was the hardware watchdog was firing and
rebooting the box.
Of course, this can be inconvienant if the panic happens right before the
watchdog is supposed to be kicked, leading to a spontaneous reboot before
the second kernel finishes booting and loading the watchdog module.
I was trying to think of a way to solve this and thought, one way to
minimize the problem is to kick the watchdog before we jump into the kdump
kernel. Another way is to disable the watchdog entirely, but that doesn't
work on all hardware I believe.
Anyway, I was posting on the watchdog mailing list to see if anyone had any
ideas that might help. And if my above idea to kick the watchdog before
jumping into the kdump kernel seems ok, then an api would need to be
I am willing to do any coding and testing necessary, but before I did, I
wanted help to get a direction to go in first.
 - I am ignorantly assuming everyone knows what kdump is. Kdumping is
the ability to jump into a previously loaded kernel in the case of a
panic. This kdump (second) kernel would run in reserved memory, copy the
first kernel's memory to a file and save it to a pre-determined location.
There is no system reboot in between the first and second kernel, so no
chance for the watchdog to disarm itself.
More information about the kexec