summaryrefslogtreecommitdiffstats
path: root/etc
diff options
context:
space:
mode:
authorphk <phk@FreeBSD.org>2010-05-15 10:31:11 +0000
committerphk <phk@FreeBSD.org>2010-05-15 10:31:11 +0000
commit32096493f0746736dc1e939a5c2184f3bf666178 (patch)
tree5e69274ea88e7cbe318b3682cff6f8594e6dbd39 /etc
parent0d79835fcf4f07a7a5049f8117ad7b2f4d850f89 (diff)
downloadFreeBSD-src-32096493f0746736dc1e939a5c2184f3bf666178.zip
FreeBSD-src-32096493f0746736dc1e939a5c2184f3bf666178.tar.gz
Apply a patch that has been lingering in my inbox for far too long:
On a soekris Net5501, if you do a watchdog -t 16, followed by a watchdog -t 0 to disable the watchdog, and then after some time (16s) re-enable the watchdog the box reboots immediatly. This prevents also to stop and restart watchdogd(8). This is because when you stop the watchdog, the timer is not stoped, only the hard reset is disabled. So when the timer has elapsed, the C2 event of the timer is set. But when the hard reset is re-enabled, the event is not cleared and the box reboots. The attached patch stops and resets the counter when the watchdog is disabled and do not disable the hard reset of the timer (if the timer has elapsed it's too late). Submitted by: Patrick Lamaizière
Diffstat (limited to 'etc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud