From owner-freebsd-current@FreeBSD.ORG Thu Mar 2 06:00:50 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 DC78D16A420; Thu, 2 Mar 2006 06:00:50 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from pasmtp.tele.dk (pasmtp.tele.dk [193.162.159.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81CE343D45; Thu, 2 Mar 2006 06:00:50 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x535c0e2a.sgnxx1.adsl-dhcp.tele.dk [83.92.14.42]) by pasmtp.tele.dk (Postfix) with ESMTP id 694F91EC322; Thu, 2 Mar 2006 07:00:49 +0100 (CET) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.4/8.13.4) with ESMTP id k2260m30015842; Thu, 2 Mar 2006 06:00:48 GMT (envelope-from phk@critter.freebsd.dk) To: John Baldwin From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 01 Mar 2006 17:24:06 EST." <200603011724.08214.jhb@freebsd.org> Date: Thu, 02 Mar 2006 06:00:48 +0000 Message-ID: <15841.1141279248@critter.freebsd.dk> Sender: phk@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:00:51 -0000 In message <200603011724.08214.jhb@freebsd.org>, John Baldwin writes: >Maybe we could make the dynamic flag for the tsc controllable via tunable? Ideally ACPI would tell us the max TSC frequency and the TSC wouldn't need 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 stuff, >then I would rather just use the tsc frequency snapshot taken at boot and >just stick with that as the static frequency then have a bunch of warnings >on the console if the max freq changes sometime later. Right, I would actually prefer to try to make the calibration more precise 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 which >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). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.