From owner-freebsd-current@FreeBSD.ORG Tue Jun 21 19:51:31 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06D8616A41F for ; Tue, 21 Jun 2005 19:51:31 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id A59E443D48 for ; Tue, 21 Jun 2005 19:51:27 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 537353B8C7; Tue, 21 Jun 2005 21:51:23 +0200 (CEST) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) by hal9000.schweikhardt.net (8.13.3/8.13.3) with ESMTP id j5LJjn5t001164; Tue, 21 Jun 2005 21:45:49 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.13.3/8.13.3/Submit) id j5LJjn83001163; Tue, 21 Jun 2005 21:45:49 +0200 (CEST) (envelope-from schweikh) Date: Tue, 21 Jun 2005 21:45:49 +0200 From: Jens Schweikhardt To: Chris Gilbert Message-ID: <20050621194549.GA840@schweikhardt.net> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200506210053.34204.Chris@LainOS.org> User-Agent: Mutt/1.5.9i Cc: freebsd-current@freebsd.org Subject: Re: Timekeeping gone whack in 6-CURRENT 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: Tue, 21 Jun 2005 19:51:31 -0000 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)