The watchdog is "off" by default, meaning that you have to have something actually start resetting the watchdog before it will start running. That's why you are seeing this behavior. There is a start_now option that will start the watchdog when it is loaded, but then it will reset the system unless something resets the watchdog periodically, and you have a limited time to start this operation. On a panic, the IPMI driver attempts to preserve the state of the watchdog and (if running) increase the timeout time to allow a kdump or something like that to occur. That's the purpose of the code you reference. It is not to start a reset operation on any panic. It used to start a reset on every panic, but that cause problems for many users. -corey Andrew Morton wrote:-
| H. Peter Anvin | Re: [rft] s2ram wakeup moves to .c, could fix few machines |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Ingo Molnar | [patch] PID namespace design bug, workaround |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Eric Dumazet | Re: Multicast packet loss |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
