Date: Fri, 11 May 2007 11:17:21 +0200 (CEST) From: Martin Dieringer <martin.dieringer@gmx.de> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-stable@freebsd.org Subject: Re: clock problem Message-ID: <20070511110759.L700@thinkpad.dieringer.dyndns.org> In-Reply-To: <20070510.225237.1159134316.imp@bsdimp.com> References: <200705081429.l48ETYYr087578@lurza.secnetix.de> <20070508164234.L839@thinkpad.dieringer.dyndns.org> <20070510.225237.1159134316.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 May 2007, M. Warner Losh wrote: > In message: <20070508164234.L839@thinkpad.dieringer.dyndns.org> > Martin Dieringer <martin.dieringer@gmx.de> writes: > : well now it works without "restrict": > : # ntpq -p > : remote refid st t when poll reach delay offset jitter > : ============================================================================== > : *time 192.53.103.108 2 u 19 64 77 91.454 301.926 860.104 > : > : > : and the clock is "only" 3 seconds late now... > > only 300ms late, or .3s you mean. Well it says so, but I meant 3 seconds, compared by eye to a radio clock. This is NOT a hardware problem. 1. I have this on 2 machines, 2. the problem is solved by switching to ACPI instead of APM m.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070511110759.L700>