Date: Tue, 21 Jun 2005 21:45:49 +0200 From: Jens Schweikhardt <schweikh@schweikhardt.net> To: Chris Gilbert <Chris@LainOS.org> Cc: freebsd-current@freebsd.org Subject: Re: Timekeeping gone whack in 6-CURRENT Message-ID: <20050621194549.GA840@schweikhardt.net> In-Reply-To: <200506210053.34204.Chris@LainOS.org> References: <20050617180321.GA1131@tarc.po.cs.msu.su> <42B5D82E.2090509@pop.agri.ch> <20050620130609.GA917@tarc.po.cs.msu.su> <200506210053.34204.Chris@LainOS.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 21, 2005 at 12:53:34AM +0200, Chris Gilbert wrote: # I've noticed since updating my machine from 5.3 to 6-CURRENT that the # timekeeping on the system goes out of sync very quickly. # # After about a day, the clock is out of sync up to 12 hours! # # This is strange as on 5.3/5.4 the timekeeping on my machine was much more # reasonable (+/- ~1 second a day) # # Is there something with 6-CURRENT that needs to be configured to keep this # from going nuts? # # If any other diagnostic information is needed please let me know! This looks like the same problem mentioned in the thread with subject "Timekeeping hosed by factor 3, high lapic[01] interrupt rates". See there for what file/revision to backout. Currently there is no solution known, but we're working on it. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050621194549.GA840>