From owner-freebsd-current@FreeBSD.ORG Thu Mar 2 06:13:35 2006 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 8203A16A420 for ; Thu, 2 Mar 2006 06:13:35 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6AFA43D4C for ; Thu, 2 Mar 2006 06:13:34 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so574531wra for ; Wed, 01 Mar 2006 22:13:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FD98+IU5gcjBlHDtx5MXOpeIar94X5bL17eByzPvyJpzoyNq2EiN8+EVfSWYXoHqBhSr5s9asCCPBBqIMi5WaT4mdWwBDtl8Jk9uYc/x+qITfhhRYcn83mcDlcIg6duPskCLXHRw5ZUDBT3Urcm495pU7oCHHza3WP13UcHPWao= Received: by 10.65.211.11 with SMTP id n11mr490617qbq; Wed, 01 Mar 2006 22:13:33 -0800 (PST) Received: by 10.65.211.12 with HTTP; Wed, 1 Mar 2006 22:13:33 -0800 (PST) Message-ID: <47d0403c0603012213o32b6d6d0m6ab4207de9134577@mail.gmail.com> Date: Thu, 2 Mar 2006 06:13:33 +0000 From: "Ben Kaduk" To: "Poul-Henning Kamp" In-Reply-To: <15841.1141279248@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200603011724.08214.jhb@freebsd.org> <15841.1141279248@critter.freebsd.dk> Cc: Mike Jakubik , freebsd-current@freebsd.org Subject: Re: Still seeing "calcru: runtime went backwards" messages 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: Thu, 02 Mar 2006 06:13:35 -0000 On 3/2/06, Poul-Henning Kamp wrote: > In message <200603011724.08214.jhb@freebsd.org>, John Baldwin writes: > > >Maybe we could make the dynamic flag for the tsc controllable via tunabl= e? > > Ideally ACPI would tell us the max TSC frequency and the TSC wouldn't nee= d > to be marked variable. Havn't had time to look at this yet though. > > >If I have a server machine without any fancy pentium-m cpufreq type stuf= f, > >then I would rather just use the tsc frequency snapshot taken at boot an= d > >just stick with that as the static frequency then have a bunch of warnin= gs > >on the console if the max freq changes sometime later. > > Right, I would actually prefer to try to make the calibration more precis= e > first, rather than add yet another knob for roots to remember to tweak. > > >Also, note that > >I am still getting a bunch of the backwards messages on my DS20 Alpha wh= ich > >is _not_ using the TSC. :) > > That's interesting... Alpha should be using the timecounter and that > is not marked "variable". > > My alpha hasn't been able to boot in a long time now :-( > > > (I should probably fix Alpha to use its own > >version of the TSC at some point, but for now I want to get it to stop > >spitting out the warnings when using the timecounters as that shouldn't > >be causing any warnings). > > I'd be tempted to just supress the warning if the negative delta is less > than 3usec (for some value of 3). Could not one put in a counter variable and only print the message every 50 times it happens (for some value of 50)? Ben Kaduk