From owner-freebsd-current@FreeBSD.ORG Fri Jun 24 16:50:25 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 5074716A41C; Fri, 24 Jun 2005 16:50:25 +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 0F8A443D53; Fri, 24 Jun 2005 16:50:24 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 038B03B908; Fri, 24 Jun 2005 18:50:22 +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 j5OGo2cq001174; Fri, 24 Jun 2005 18:50:02 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.13.3/8.13.3/Submit) id j5OGo2x0001173; Fri, 24 Jun 2005 18:50:02 +0200 (CEST) (envelope-from schweikh) Date: Fri, 24 Jun 2005 18:50:02 +0200 From: Jens Schweikhardt To: John Baldwin Message-ID: <20050624165002.GA860@schweikhardt.net> References: <20050516113420.GA786@schweikhardt.net> <200506221057.48595.jhb@FreeBSD.org> <20050623205854.GA763@schweikhardt.net> <200506231714.40891.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200506231714.40891.jhb@FreeBSD.org> User-Agent: Mutt/1.5.9i Cc: freebsd-current@FreeBSD.org Subject: Re: Timekeeping hosed by factor 3, high lapic[01] interrupt rates 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: Fri, 24 Jun 2005 16:50:25 -0000 On Thu, Jun 23, 2005 at 05:14:39PM -0400, John Baldwin wrote: ... # Ok. What timecounter does your UP kernel use, and does your UP kernel break # if you change the timecounter to i8254? The UP uses the TSC: $ sysctl -a|grep timec kern.timecounter.stepwarnings: 0 kern.timecounter.nbinuptime: 136311 kern.timecounter.nnanouptime: 0 kern.timecounter.nmicrouptime: 664 kern.timecounter.nbintime: 1273 kern.timecounter.nnanotime: 36 kern.timecounter.nmicrotime: 1237 kern.timecounter.ngetbinuptime: 405 kern.timecounter.ngetnanouptime: 29 kern.timecounter.ngetmicrouptime: 2534 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetnanotime: 0 kern.timecounter.ngetmicrotime: 5 kern.timecounter.nsetclock: 2 kern.timecounter.hardware: TSC kern.timecounter.choice: TSC(800) i8254(0) dummy(-1000000) kern.timecounter.tick: 1 kern.timecounter.smp_tsc: 0 When I do $ sysctl kern.timecounter.hardware=i8254 on the UP the time dilation by factor 3 starts and the lapic rate increases. So yes, that breaks the UP kernel. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)