From owner-freebsd-current@FreeBSD.ORG Sat May 21 09:29:20 2005 Return-Path: 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 0ACD016A4D4 for ; Sat, 21 May 2005 09:29:20 +0000 (GMT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF34743DB1 for ; Sat, 21 May 2005 09:29:15 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 7CF3E3B8CD; Sat, 21 May 2005 11:29:13 +0200 (CEST) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) j4L9SvdH001366; Sat, 21 May 2005 11:28:57 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.13.3/8.13.3/Submit) id j4L9Sv60001365; Sat, 21 May 2005 11:28:57 +0200 (CEST) (envelope-from schweikh) Date: Sat, 21 May 2005 11:28:57 +0200 From: Jens Schweikhardt To: Doug White Message-ID: <20050521092857.GA847@schweikhardt.net> References: <20050516113420.GA786@schweikhardt.net> <20050518150346.S87264@carver.gumbysoft.com> <20050519190129.GA1048@schweikhardt.net> <20050520122944.B8229@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050520122944.B8229@carver.gumbysoft.com> 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.1 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: Sat, 21 May 2005 09:29:20 -0000 On Fri, May 20, 2005 at 12:44:50PM -0700, Doug White wrote: ... # > Note that there's no # > irq0: clk 745029 1000 # > appearing. I'm not an expert, but that's unexpected to my eyes. # # Not totally (I don't have irq0 on any of my -current machines after the # lapic change), but it being there before and then going away implies the # kernel is choosing a different timecounter than before, and the new one # may be bogus. # # Can you get the output of 'sysctl kern.timecounter' for both working and # broken kernels? broken: kern.timecounter.stepwarnings: 0 kern.timecounter.nbinuptime: 221327 kern.timecounter.nnanouptime: 0 kern.timecounter.nmicrouptime: 640 kern.timecounter.nbintime: 951 kern.timecounter.nnanotime: 22 kern.timecounter.nmicrotime: 929 kern.timecounter.ngetbinuptime: 410 kern.timecounter.ngetnanouptime: 76 kern.timecounter.ngetmicrouptime: 3599 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetnanotime: 0 kern.timecounter.ngetmicrotime: 5 kern.timecounter.nsetclock: 2 kern.timecounter.hardware: i8254 kern.timecounter.choice: TSC(-100) i8254(0) dummy(-1000000) kern.timecounter.tick: 1 kern.timecounter.smp_tsc: 0 working: kern.timecounter.stepwarnings: 0 kern.timecounter.nbinuptime: 630606 kern.timecounter.nnanouptime: 0 kern.timecounter.nmicrouptime: 1220 kern.timecounter.nbintime: 127348 kern.timecounter.nnanotime: 58801 kern.timecounter.nmicrotime: 68578 kern.timecounter.ngetbinuptime: 1983 kern.timecounter.ngetnanouptime: 423 kern.timecounter.ngetmicrouptime: 34313 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetnanotime: 0 kern.timecounter.ngetmicrotime: 5 kern.timecounter.nsetclock: 1 kern.timecounter.hardware: i8254 kern.timecounter.choice: TSC(-100) i8254(0) dummy(-1000000) kern.timecounter.tick: 1 kern.timecounter.smp_tsc: 0 # When did you pull sources for the original working kernel and the new # broken kernel? Working: around March 5 (I always cvsup before compiling a system) Broken: May 17 (after the ATA hangs at boot were fixed) # > pcib0: pcibus 0 on motherboard # # Is ACPI disabled on purpose? It should work on such a new system. ACPI # provides a couple of timecounters of its own that we'd prefer to use. Some time in the past, the system would hang at boot with acpi enabled. So I kept a hint.acpi.0.disabled="1" in /boot/device.hints. But even without that hint, the time dilation effect (hey, it's the Einstein Year!) is the same... Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)