Date: Wed, 11 Jul 2007 14:22:02 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: Ivan Voras <ivoras@fer.hr> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Debugging times Message-ID: <20070711132202.GA95487@walton.maths.tcd.ie> In-Reply-To: <f6ucs8$d6t$1@sea.gmane.org> References: <f6u94s$v6o$1@sea.gmane.org> <20070709214216.GA72912@walton.maths.tcd.ie> <f6ucs8$d6t$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070711132202.GA95487>