From owner-freebsd-current@FreeBSD.ORG Tue Jul 10 12:21:52 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D87216A41F for ; Tue, 10 Jul 2007 12:21:52 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from ns.trinitel.com (186.161.36.72.static.reverse.layeredtech.com [72.36.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id E720A13C4C2 for ; Tue, 10 Jul 2007 12:21:51 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from proton.local (209-163-168-124.static.twtelecom.net [209.163.168.124]) (authenticated bits=0) by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id l6ACLoUq099588; Tue, 10 Jul 2007 07:21:51 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <469379DE.2030605@freebsd.org> Date: Tue, 10 Jul 2007 07:21:50 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Victor Snezhko References: <46934301.5080302@fer.hr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com Cc: freebsd-current@freebsd.org Subject: Re: Debugging time X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2007 12:21:52 -0000 Victor Snezhko wrote: > Ivan Voras writes: > >>> For about half a year I have another weirdness with time on my >>> -current box without vmware, maybe it's somehow has common origins >>> with your behaviour. When I boot FreeBSD, ntpdate (which is set up to >>> run via rc.conf) often reports huge time offsets: >>> 10 Jul 12:04:34 ntpdate[51761]: step time server ntp.server.name offset 234456.074166 sec >>> >>> I have so far only noticed that the value of the the offset is roughly >>> equal to the amount of time when FreeBSD isn't running (this is a >>> dual-boot box with windows). The box is pretty old, 600-MHz Celeron >> Is the above number correct (i.e. ~~ 65 hours)? > > Yes, sometimes my FreeBSD is not running for several days - in this > case ntpdate prints such numbers. It looks like kernel stores date and > time values somewhere and then re-reads them. I still don't rule out > some stupidity on my part - the behaviour I'm observing is very > illogic. Maybe I should try installing current from a fresh snapshot > when it's released. > >> I noticed there can be a consistent "shift" of duration equal to >> your timezone when VMWare sets the RTC to the host's local time and >> FreeBSD thinks it's UTC. But if the difference is not constant, it's >> not it. > > When I just reboot FreeBSD, offset doesn't exceed one or two seconds > (notably, bios takes longer to boot, about 5-10 seconds). When BSD is > inactive for several hours, number is much bigger. > > I neglected to debug this deeply before - I assumed I have overlooked > something simple, but now that you have reported another issue in the > similar area, I'll try to collect full information. > When you say 'inactive', do you mean that you have suspended the machine in vmware, or it is 'powered off'? Eric