Date: Fri, 12 Feb 2010 13:25:48 +0100 From: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> To: freebsd-stable@freebsd.org Subject: Re: ntpd struggling to keep up - how to fix? Message-ID: <20100212132548.8aed4d16.torfinn.ingolfsen@broadpark.no> In-Reply-To: <E8F167BE-FD1E-4999-B5B9-7995E914592E@mac.com> References: <20100211190652.6a66c618.torfinn.ingolfsen@broadpark.no> <E8F167BE-FD1E-4999-B5B9-7995E914592E@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Feb 2010 10:25:59 -0800 Chuck Swiger <cswiger@mac.com> wrote: > The rate at which this machine is losing time is probably exceeding the ~50 seconds per day that NTPd is willing to correct without extreme measures (ie, it has to step time rather than drift-correct). > You might help it maintain a more sane idea of time by using at least 4 timeservers. Hmm, ok that iis something I can try. > You might take a look at 'vmstat -i' and look out for an interrupt storm, but it's possible your hardware's clock is simply busted. AFAICT, vmstat -i looks ok: root@kg-f2# uptime 1:23PM up 18:31, 3 users, load averages: 0.00, 0.00, 0.00 root@kg-f2# vmstat -i interrupt total rate irq1: atkbd0 36 0 irq6: fdc0 1 0 irq16: siis0 ohci0+ 408 0 irq22: atapci0 856338 12 cpu0: timer 133347678 1999 irq256: re0 234087 3 cpu1: timer 133337654 1999 Total 267776202 4016 -- Regards, Torfinn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100212132548.8aed4d16.torfinn.ingolfsen>