From owner-freebsd-stable@FreeBSD.ORG Mon Jun 11 12:53:42 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 99D2116A41F for ; Mon, 11 Jun 2007 12:53:42 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 0A7F413C45B for ; Mon, 11 Jun 2007 12:53:41 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.1/8.14.1) with ESMTP id l5BCraJv020817; Mon, 11 Jun 2007 16:53:36 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Mon, 11 Jun 2007 16:53:36 +0400 (MSD) From: Dmitry Morozovsky To: Matthew Dillon In-Reply-To: <200706091957.l59JvDWR026822@apollo.backplane.com> Message-ID: <20070611164121.J20351@woozle.rinet.ru> 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> <200706091957.l59JvDWR026822@apollo.backplane.com> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (woozle.rinet.ru [0.0.0.0]); Mon, 11 Jun 2007 16:53:37 +0400 (MSD) 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: Mon, 11 Jun 2007 12:53:42 -0000 On Sat, 9 Jun 2007, Matthew Dillon wrote: MD> :Well, I can of course shut the kernel up, but kernel time stability is still my MD> :concern. I run ntpd there and while sometimes it seems stable (well, sorta: MD> :drift are within several seconds...) there are cases of half-a-minute time MD> :steps. MD> MD> If you don't want to do that, try forcing the timer to use the 8254 MD> and see if that helps. You may also have to reduce the system tick MD> to ~100-200 hz. Does not help either: ct-new# sysctl kern.clockrate kern.clockrate: { hz = 200, tick = 5000, profhz = 133, stathz = 26 } ct-new# sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) ACPI-safe(1000) i8254(0) dummy(-1000000) kern.timecounter.hardware: i8254 kern.timecounter.nsetclock: 3 kern.timecounter.ngetmicrotime: 6118 kern.timecounter.ngetnanotime: 0 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetmicrouptime: 4741 kern.timecounter.ngetnanouptime: 30 kern.timecounter.ngetbinuptime: 485 kern.timecounter.nmicrotime: 1027 kern.timecounter.nnanotime: 96 kern.timecounter.nbintime: 1123 kern.timecounter.nmicrouptime: 804 kern.timecounter.nnanouptime: 0 kern.timecounter.nbinuptime: 60658 kern.timecounter.stepwarnings: 0 kern.timecounter.smp_tsc: 0 ct-new# ps calcru: negative runtime of -1322717 usec for pid 4 (g_down) calcru: negative runtime of -1322717 usec for pid 4 (g_down) PID TT STAT TIME COMMAND Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------