From owner-freebsd-sparc64@FreeBSD.ORG Sun Oct 24 22:52:39 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86EB916A4CE for ; Sun, 24 Oct 2004 22:52:39 +0000 (GMT) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1F5643D39 for ; Sun, 24 Oct 2004 22:52:38 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) i9OMqVAZ020871; Mon, 25 Oct 2004 00:52:35 +0200 (CEST) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.10/8.12.10/Submit) id i9OMqPSQ020870; Mon, 25 Oct 2004 00:52:25 +0200 (CEST) (envelope-from marius) Date: Mon, 25 Oct 2004 00:52:25 +0200 From: Marius Strobl To: Kris Kennaway Message-ID: <20041025005225.A20538@newtrinity.zeist.de> References: <20041023231454.GA11787@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20041023231454.GA11787@xor.obsecurity.org>; from kris@obsecurity.org on Sat, Oct 23, 2004 at 04:14:54PM -0700 X-AntiVirus: checked by AntiVir Milter (version: 1.1; AVE: 6.28.0.7; VDF: 6.28.0.34; host: newtrinity.zeist.de) cc: sparc64@freebsd.org Subject: Re: ntpdate unable to repair clock X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2004 22:52:39 -0000 On Sat, Oct 23, 2004 at 04:14:54PM -0700, Kris Kennaway wrote: > A sparc64 machine I'm using was consistently failing to set the date > properly when updated across the recent RELENG_5 changes that required > date to be reset. ntpdate claimed to be setting the date correctly, > but date(1) still returned a bogus value. > > Setting the date manually and then rerunning ntpdate gave another > bogus offset message, but in fact set it correctly. > You have to use `ntpdate -b` for such transitions so the time is also written to the clock chip. Your problems when not using the '-b' switch seem similar to what I also see on other architectures including i386 in this case. But there could be additional 64bit bugs in this path, e.g. the genclock clock isn't 64bit time_t clean, yet.