Page MenuHomeFreeBSD

dwwdt: make it actually useful
ClosedPublic

Authored by avg on Dec 17 2021, 11:28 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 19, 8:41 PM
Unknown Object (File)
Feb 6 2024, 6:58 PM
Unknown Object (File)
Dec 20 2023, 1:00 AM
Unknown Object (File)
Dec 12 2023, 11:44 PM
Unknown Object (File)
Nov 28 2023, 5:49 AM
Unknown Object (File)
Nov 27 2023, 7:10 PM
Unknown Object (File)
Nov 23 2023, 5:22 PM
Unknown Object (File)
Nov 22 2023, 9:01 PM
Subscribers

Details

Summary

Flip dwwdt_prevent_restart to false. What's the use of a watchdog if it
does not restart a hung system?

Add a knob for panic-ing on the first timeout, resetting on the second
one. This can be useful if interrupts can still work, otherwise a reset
recovers a system without any aid for debugging the hang.

The change also doubles the timeout that's programmed into the hardware.
The previous version of the code always had the interrupt on the first
timeout enabled, but it took no action on it. Only the second timeout
could be configured to reset the system. So, the hardware timeout was
set to a half of the user requested timeout. But now,we can take a
corrective action on the first timeout, so we use the user requested
timeout.

While here, define boolean sysctl-s as such.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable