From owner-freebsd-stable@FreeBSD.ORG Tue Jun 12 09:33:35 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 966D516A400 for ; Tue, 12 Jun 2007 09:33:35 +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 1D9FC13C457 for ; Tue, 12 Jun 2007 09:33:34 +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 l5C9XP5G042387; Tue, 12 Jun 2007 13:33:25 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Tue, 12 Jun 2007 13:33:25 +0400 (MSD) From: Dmitry Morozovsky To: Matthew Dillon In-Reply-To: <200706120213.l5C2DlkO055522@apollo.backplane.com> Message-ID: <20070612132917.I71178@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> <20070610175748.L88437@woozle.rinet.ru> <20070610193708.W88437@woozle.rinet.ru> <200706120213.l5C2DlkO055522@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]); Tue, 12 Jun 2007 13:33:25 +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: Tue, 12 Jun 2007 09:33:35 -0000 On Mon, 11 Jun 2007, Matthew Dillon wrote: MD> MD> :============================================================================== MD> : cs3661.rinet.ru 192.38.7.240 2 u 354 1024 377 5.305 -66314. 4321.47 MD> : ns.rinet.ru 130.207.244.240 2 u 365 1024 377 6.913 -66316. 4305.33 MD> : whale.rinet.ru 195.2.64.5 2 u 358 1024 377 7.939 -66308. 4304.90 MD> : MD> :Any directions to debug this? MD> : MD> :Sincerely, MD> :D.Marck [DM5020, MCK-RIPE, DM3-RIPN] MD> MD> Since you are running on HEAD now, could you also kgdb the live kernel MD> and print cpu_ticks? I believe the sequence is (someone correct me if MD> I am wrong): MD> MD> kgdb /kernel /dev/mem MD> print cpu_ticks s,/kernel,/boot/kernel/kernel, ;-) well, strange enough result for me: (kgdb) print cpu_ticks $1 = (cpu_tick_f *) 0xffffffff8036cef0 Does this mean that kernel uses tsc? sysctl reports kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-1000000) kern.timecounter.hardware: ACPI-fast MD> As for further tests... try building a non-SMP kernel (i.e. one that MD> only recognizes one cpu) and see if the problem occurs there. That MD> will determine whether there is a basic problem with time keeping or MD> whether it is an issue with SMP. As I'd reported in the first mail, at least RELENG_6/amd64/GENERIC (SMP is on by default only on HEAD) behaves similarly. There may be some hardware issues with this particular mobo though... Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------