From owner-freebsd-stable@FreeBSD.ORG Thu May 3 00:35:47 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6AA6B16A402 for ; Thu, 3 May 2007 00:35:47 +0000 (UTC) (envelope-from martin.dieringer@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id D305413C459 for ; Thu, 3 May 2007 00:35:46 +0000 (UTC) (envelope-from martin.dieringer@gmx.de) Received: (qmail invoked by alias); 03 May 2007 00:35:45 -0000 Received: from c-134-227-159.d.dsl.de.ignite.net (EHLO dieringer.dyndns.org) [62.134.227.159] by mail.gmx.net (mp031) with SMTP; 03 May 2007 02:35:45 +0200 X-Authenticated: #21464393 X-Provags-ID: V01U2FsdGVkX1/eYAoodC7ecI/hZorfirpNkVNeyz9OyK0sQ8x5BQ YU9iMxvOcWIeZm Received: (qmail 2055 invoked by uid 1001); 3 May 2007 00:35:40 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 May 2007 00:35:40 -0000 Date: Thu, 3 May 2007 02:35:40 +0200 (CEST) From: Martin Dieringer To: Doug Barton In-Reply-To: <4638C8FD.3060606@FreeBSD.org> Message-ID: <20070503022338.P839@thinkpad.dieringer.dyndns.org> References: <20070501204548.L860@thinkpad.dieringer.dyndns.org> <20070502020319.GB6419@SDF.LONESTAR.ORG> <20070502132330.U860@thinkpad.dieringer.dyndns.org> <4638C8FD.3060606@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: clock too slow - big time offset with ntpdate X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Dieringer List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 May 2007 00:35:47 -0000 On Wed, 2 May 2007, Doug Barton wrote: > Martin Dieringer wrote: > >> On Wed, 2 May 2007, John Walthall wrote: >> >>> On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote: >>>> I think it has to do with powerd, if I kill that, the time stays correct. >>> >>> With powerd enabled, are you able to maintain a "reasonably" >>> correct time with frequent NTP syncronizations? Sorry if it's just >>> me, but I am not quite clear about that, from what has been written >>> already. >> >> I would have to update every minute at least and would still be more >> than 5 seconds off. > > I think you misunderstand how ntpd works vs. how ntpdate works. > ntpd is a daemon, so you don't run it every minute, it runs in the > background and keeps the clock up to date. > Turn off all of the power management, and any other service that > might be affecting the clock, and then reboot. If your system is > able to maintain correct time under these circumstances, start > adding things in until you find the culprit and let us know. both laptops can keep the time without powerd. apm is enabled, but not acpi. as soon as I start powerd or change cpu speed, time gets a few seconds off. It doesn't matter whether I use ntpd or ntpdate. (ntpdate at system startup makes no sense as I have to dialup first). m.