From owner-freebsd-current@FreeBSD.ORG Sun May 22 18:34:45 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 58B1A16A41C for ; Sun, 22 May 2005 18:34:45 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A63D43D49 for ; Sun, 22 May 2005 18:34:45 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id D304372DD9; Sun, 22 May 2005 11:34:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id D0ACE72DD4; Sun, 22 May 2005 11:34:44 -0700 (PDT) Date: Sun, 22 May 2005 11:34:44 -0700 (PDT) From: Doug White To: Jens Schweikhardt In-Reply-To: <20050521092857.GA847@schweikhardt.net> Message-ID: <20050522112845.S27009@carver.gumbysoft.com> References: <20050516113420.GA786@schweikhardt.net> <20050518150346.S87264@carver.gumbysoft.com> <20050519190129.GA1048@schweikhardt.net> <20050520122944.B8229@carver.gumbysoft.com> <20050521092857.GA847@schweikhardt.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Sun, 22 May 2005 18:34:45 -0000 On Sat, 21 May 2005, Jens Schweikhardt wrote: > 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.hardware: i8254 > kern.timecounter.choice: TSC(-100) i8254(0) dummy(-1000000) > > working: > kern.timecounter.hardware: i8254 > kern.timecounter.choice: TSC(-100) i8254(0) dummy(-1000000) Okay, no change there. > # 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) Lets try this: 0. If you're overclocking your CPU, don't. 1. Boot with ACPI enabled and print the two kern.timecount sysctls above. I'm curious if its picking up the ACPI timecounter. 2. Shutdown and unplug the machine for about 20 minutes or overnight if convenient. Plug it back in, go into BIOS Setup and check the clock. If its off or dead then the CMOS battery is dead. 3. Backout rev 1.218 of src/sys/i386/isa/clock.c so the irq0 interrupt handler is reactivated and the RTC fiddled. > 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... This would imply the source of the problem is not in the timecounter, which doesn't make sense. Are you running ntpd? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org