On 02/04/2016 05:48 AM, Timur Tabi wrote:
Guenter Roeck wrote:
Also, if panic is enabled, the timeout needs to be adjusted accordingly
(to only panic after the entire timeout period has expired, not after
half of it). We can not panic the system after timeout / 2.
It's a debugging feature, not an actual watchdog timeout panic. That's why it's disabled by default.
"* When the first stage(the half timeout) is reached, WS0 interrupt is
* triggered, at this moment the second watch period starts;
* In the WS0 interrupt routine, panic will be triggered for saving the
* system context.
* If the system is getting into trouble and cannot be reset by panic or
* restart properly by the kdump kernel(if supported), then the second
* stage (the timeout) will be reached, system will be reset by WS1."
That doesn't sound like debugging to me.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
