From owner-freebsd-current@FreeBSD.ORG Mon May 23 17:56:33 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 26CB416A41C for ; Mon, 23 May 2005 17:56:33 +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 C166443D49 for ; Mon, 23 May 2005 17:56:31 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id B3EFD3B921; Mon, 23 May 2005 19:56:29 +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 j4NHu9gw001141; Mon, 23 May 2005 19:56:09 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.13.3/8.13.3/Submit) id j4NHu93f001140; Mon, 23 May 2005 19:56:09 +0200 (CEST) (envelope-from schweikh) Date: Mon, 23 May 2005 19:56:09 +0200 From: Jens Schweikhardt To: Doug White Message-ID: <20050523175609.GA779@schweikhardt.net> References: <20050516113420.GA786@schweikhardt.net> <20050518150346.S87264@carver.gumbysoft.com> <20050519190129.GA1048@schweikhardt.net> <20050520122944.B8229@carver.gumbysoft.com> <20050521092857.GA847@schweikhardt.net> <20050522112845.S27009@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050522112845.S27009@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.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: Mon, 23 May 2005 17:56:33 -0000 ... # Lets try this: # 0. If you're overclocking your CPU, don't. Never did. # 1. Boot with ACPI enabled and print the two kern.timecount sysctls above. # I'm curious if its picking up the ACPI timecounter. Isn't APIC enabled unless I disable it with hint.acpi.0.disabled="1"? # 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. This is my home machine, which I turn off at night. The BIOS clock looks good. And this would not explain why it's the same system that works with a different kernel. # 3. Backout rev 1.218 of src/sys/i386/isa/clock.c so the irq0 interrupt # handler is reactivated and the RTC fiddled. Will do so next. I've nailed the change between March 6 and March 30. 1.218 is from 2005/03/24 21:34:16, which would fit. # > 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. It's puzzling, but dammit, these are deterministic machines :-) I'm sure in the end we'll find the cause. Thanks for your patience. # Are you running ntpd? Yes. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)