From owner-freebsd-sparc64@FreeBSD.ORG Fri Oct 16 19:55:18 2009 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FC771065695 for ; Fri, 16 Oct 2009 19:55:18 +0000 (UTC) (envelope-from carton@Ivy.NET) Received: from sakima.Ivy.NET (sakima.Ivy.NET [69.31.131.60]) by mx1.freebsd.org (Postfix) with ESMTP id 0A4288FC17 for ; Fri, 16 Oct 2009 19:55:17 +0000 (UTC) Received: from castrovalva.Ivy.NET (castrovalva.Ivy.NET [69.31.131.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sakima.Ivy.NET (Postfix) with ESMTP id DE0ECA80E7 for ; Fri, 16 Oct 2009 15:55:12 -0400 (EDT) Received: by castrovalva.Ivy.NET (Postfix, from userid 405) id B2DE212FD0E; Fri, 16 Oct 2009 15:55:12 -0400 (EDT) To: freebsd-sparc64@freebsd.org References: <3979a4b0910142324s5158a7f9g91ca45298738730c@mail.gmail.com> From: Miles Nordin MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Fri_Oct_16_15:55:11_2009-1"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 16 Oct 2009 15:55:11 -0400 In-Reply-To: <3979a4b0910142324s5158a7f9g91ca45298738730c@mail.gmail.com> (KOT MATPOCKuH's message of "Thu, 15 Oct 2009 10:24:30 +0400") Message-ID: User-Agent: T-gnus/6.17.2 (based on No Gnus v0.2) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.4 (alpha--netbsd) MULE/5.0 (SAKAKI) Subject: Re: FreeBSD/sparc64 on SunFire V215 - clock (?) problem X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 19:55:18 -0000 --pgp-sign-Multipart_Fri_Oct_16_15:55:11_2009-1 Content-Type: text/plain; charset=US-ASCII >>>>> "km" == KOT MATPOCKuH writes: km> The time in NVRAM's clock is not synced after reboot, km> and time difference increases after each system restart. km> 14 Oct 18:31:27 ntpdate[963]: step time server 192.168.2.1 km> offset 343.494018 sec [reboot] km> 15 Oct 10:22:53 ntpdate[962]: step time server 192.168.2.1 km> offset 345.509317 sec so you are finding two separate problems: 1. if NVRAM clock were synced after reboot, the step on 15 Oct would be close to zero, not 300. 2. accepting that bug exists, and the NVRAM time is never updated to system time, the step should be the same size on the 14th and 15th. Instead the nvram is gaining/losing two seconds in only 16 hours which is much worse accuracy than you expect from the battery chip. --pgp-sign-Multipart_Fri_Oct_16_15:55:11_2009-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (NetBSD) iQCUAwUAStjPn4nCBbTaW/4dAQIxMAPxAeVZ63UXCH6a1wpRPGrJaSX/Tng3Q9Hq aLFhRkfvqYDTF/BuTnNB0Yf0QZoHwRaMBbKse47SUetmcxRL8a0/r4smtK1+QTWD rvqf467iI09DBDr4v1BmvpMpweH2QTHbl18f1m6q4hQv8UjEd+Pv4q2+zBW2JDQq wqdUFkMO2A== =F/FB -----END PGP SIGNATURE----- --pgp-sign-Multipart_Fri_Oct_16_15:55:11_2009-1--