From owner-freebsd-current@FreeBSD.ORG Wed Jun 22 15:24:20 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 36A3616A420 for ; Wed, 22 Jun 2005 15:24:19 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D5ED43D58 for ; Wed, 22 Jun 2005 15:24:18 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.41.231] (Not Verified[65.202.103.25]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Wed, 22 Jun 2005 11:37:50 -0400 From: John Baldwin To: Jens Schweikhardt Date: Wed, 22 Jun 2005 10:57:47 -0400 User-Agent: KMail/1.8 References: <20050516113420.GA786@schweikhardt.net> <200506201344.10176.jhb@FreeBSD.org> <20050621195113.GB840@schweikhardt.net> In-Reply-To: <20050621195113.GB840@schweikhardt.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506221057.48595.jhb@FreeBSD.org> 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: Wed, 22 Jun 2005 15:24:20 -0000 On Tuesday 21 June 2005 03:51 pm, Jens Schweikhardt wrote: > John, > > # > See > http://lists.freebsd.org/pipermail/freebsd-current/2005-May/050210.html # > > for the whole thread. > # > # I did glance over it, but I don't really have time to read every e-mail > on # current@ in detail. :( Do you have verbose dmesg's for both cases? > If so, # can you get the 'lapic: Divisor' lines from each boot? > > Sure, they are the same: > lapic: Divisor 2, Frequency 99829738 hz > > It appears Chris Gilbert has the same problem, see "Timekeeping gone > whack in 6-CURRENT" on this list. Ok, this is weird. Does this happen if you disable SMP via 'kern.smp.disabled=1' from the loader? UP has more timecounters available for use, so I'm curious if this is a problem with the 8254 timecounter code for some reason. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org