summaryrefslogtreecommitdiffstats
path: root/sys/kern
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>2015-02-05 01:43:21 +0000
committerpeter <peter@FreeBSD.org>2015-02-05 01:43:21 +0000
commitbf625afa44d0d15e87e805ea5abe991328acc988 (patch)
treef91d7b0908f28d840ecb2dbcaa0912d9fd7b6690 /sys/kern
parentaba31cb69187d41c37c7fa832eb9c8270b8b7227 (diff)
downloadFreeBSD-src-bf625afa44d0d15e87e805ea5abe991328acc988.zip
FreeBSD-src-bf625afa44d0d15e87e805ea5abe991328acc988.tar.gz
Initialize ticks so that it wraps 10 minutes after boot to increase the
chances of finding problems related to wraparound sooner. This comes from P4 change 167856 on 2009/08/26 around when we had problems with the TCP stack with ticks after 24 days of uptime.
Diffstat (limited to 'sys/kern')
-rw-r--r--sys/kern/kern_clock.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/sys/kern/kern_clock.c b/sys/kern/kern_clock.c
index 6aa3523..fdf2271 100644
--- a/sys/kern/kern_clock.c
+++ b/sys/kern/kern_clock.c
@@ -410,6 +410,11 @@ initclocks(dummy)
#ifdef SW_WATCHDOG
EVENTHANDLER_REGISTER(watchdog_list, watchdog_config, NULL, 0);
#endif
+ /*
+ * Arrange for ticks to wrap 10 minutes after boot to help catch
+ * sign problems sooner.
+ */
+ ticks = INT_MAX - (hz * 10 * 60);
}
/*
OpenPOWER on IntegriCloud