HI, I sent a message about this to questions to no avail. So sorry if this is an inappropreate place but here is the problem. Dec 3 Upgared machine to FreeBSD 4.2 (i386) Dec 6 - Jan 2 away from machine. I logged in to find that the value of date was way out (-6 Days), at this point the machie was not running any type of time peering it was essentually stand-alone. I corrected the time manually using date. The next day I noticed the time was wrong again, and decided to run ntp to track the time on our master. It tried very hard to keep time but finally gave up and syslogged me that a manual time change would be necessary. This moring I find that the drift is -50% . I don't know much about how kernel time relates to bios time but I guess that there's a pashe locked loop in the software that is not getting feedback from the HW clock, but I'm just guessing. Can anybody explain what is happening? Thanks. Tom Brown To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
