From owner-freebsd-current@FreeBSD.ORG Wed Jul 11 13:22:04 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 7003F16A477; Wed, 11 Jul 2007 13:22:04 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.freebsd.org (Postfix) with SMTP id 9BB1313C4CC; Wed, 11 Jul 2007 13:22:03 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 11 Jul 2007 14:22:02 +0100 (BST) Date: Wed, 11 Jul 2007 14:22:02 +0100 From: David Malone To: Ivan Voras Message-ID: <20070711132202.GA95487@walton.maths.tcd.ie> References: <20070709214216.GA72912@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Debugging times 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: Wed, 11 Jul 2007 13:22:04 -0000 On Tue, Jul 10, 2007 at 12:29:26AM +0200, Ivan Voras wrote: > Yes, I'll test them. > > The problem is - the same kernel works when booted off a hard drive, so > unless the VMWare BIOS is very messed up (it's the first time I see such > problems) it may not help. Please, scatter debug printf's around so I > can see what's going on :) Try the patch at: http://www.maths.tcd.ie/~dwmalone/clock.patch It checks the return values of the various clock reading functions in the kernel and prints an error message if it finds that it can't set the clock OK. Some machines have a BIOS that doesn't count the day-of-week correctly, and recently FreeBSD has started treating this as an error on some platforms. (This patch won't fix anything, but might produce a more informative error message.) David.