Date: Thu, 12 Jul 2007 00:14:43 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-current@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Re: Debugging times Message-ID: <f73koj$a13$1@sea.gmane.org> In-Reply-To: <20070711132202.GA95487@walton.maths.tcd.ie> References: <f6u94s$v6o$1@sea.gmane.org> <20070709214216.GA72912@walton.maths.tcd.ie> <f6ucs8$d6t$1@sea.gmane.org> <20070711132202.GA95487@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
David Malone wrote: > 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.) I've got interesting results (in the bad sense of the phrase): I do get the message "Invalid time in real time clock. Check and reset the time immediately" (the i386 message) BUT my time gets reset to 0 (midnight 1970.) I see your patch and it shouldn't do that. Could it be a compiler bug, so the effects change after trivial code has been changed?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f73koj$a13$1>