From owner-freebsd-stable@FreeBSD.ORG Sat Jun 9 19:57:16 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18B1016A400 for ; Sat, 9 Jun 2007 19:57:16 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 02BB813C448 for ; Sat, 9 Jun 2007 19:57:15 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.8/8.13.7) with ESMTP id l59JvDDm026823; Sat, 9 Jun 2007 12:57:13 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.13.8/8.13.4/Submit) id l59JvDWR026822; Sat, 9 Jun 2007 12:57:13 -0700 (PDT) Date: Sat, 9 Jun 2007 12:57:13 -0700 (PDT) From: Matthew Dillon Message-Id: <200706091957.l59JvDWR026822@apollo.backplane.com> To: Dmitry Morozovsky References: <20070606153542.Y76617@woozle.rinet.ru> <20070606231940.T91939@woozle.rinet.ru> <200706062127.l56LRYTe090137@apollo.backplane.com> <20070608111809.U97287@woozle.rinet.ru> <200706090809.l5989Mkj020033@apollo.backplane.com> <20070609163329.P4850@woozle.rinet.ru> Cc: freebsd-stable@freebsd.org, Ivan Voras Subject: Re: calcru: runtime went backwards, RELENG_6, SMP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2007 19:57:16 -0000 :Well, I can of course shut the kernel up, but kernel time stability is still my :concern. I run ntpd there and while sometimes it seems stable (well, sorta: :drift are within several seconds...) there are cases of half-a-minute time :steps. : :Sincerely, :D.Marck [DM5020, MCK-RIPE, DM3-RIPN] I think the only hope you have of getting the issue addressed is to run FreeBSD current. If you can reproduce the time slips under current the developers should be able to track the problem down and fix it. The code is so different between those two releases that they are going to have a hard time working the problem in FreeBSD-6. If you don't want to do that, try forcing the timer to use the 8254 and see if that helps. You may also have to reduce the system tick to ~100-200 hz. -Matt Matthew Dillon