From owner-freebsd-current@FreeBSD.ORG Fri May 20 19:44:50 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 F0D3416A4CE for ; Fri, 20 May 2005 19:44:50 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C151E43D6E for ; Fri, 20 May 2005 19:44:50 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id B3E9972DD9; Fri, 20 May 2005 12:44:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id B1DBF72DD4; Fri, 20 May 2005 12:44:50 -0700 (PDT) Date: Fri, 20 May 2005 12:44:50 -0700 (PDT) From: Doug White To: Jens Schweikhardt In-Reply-To: <20050519190129.GA1048@schweikhardt.net> Message-ID: <20050520122944.B8229@carver.gumbysoft.com> References: <20050516113420.GA786@schweikhardt.net> <20050518150346.S87264@carver.gumbysoft.com> <20050519190129.GA1048@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.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: Fri, 20 May 2005 19:44:51 -0000 On Thu, 19 May 2005, Jens Schweikhardt wrote: > # Are you running with kern.hz or HZ set to something other than the > # default? > > No, > $ sysctl -a | grep hz > kern.clockrate: { hz = 1000, tick = 1000, profhz = 666, stathz = 133 } > debug.psm.hz: 20 > > is the same on both systems. > ... > # the lapic timer values should run about 2*hz. > > Then something is out of whack... this is from the strange system: > > $ vmstat -i > interrupt total rate > irq1: atkbd0 211 8 > irq13: npx0 1 0 > irq14: ata0 63 2 > irq15: ata1 109 4 > irq18: em0 17 0 > irq24: ahd0 4511 187 > irq25: ahc0 16 0 > lapic0: timer 190869 7952 > lapic1: timer 176174 7340 > Total 371971 15498 > > 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? When did you pull sources for the original working kernel and the new broken kernel? > 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. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org