From owner-freebsd-stable@FreeBSD.ORG Thu Dec 21 12:33:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53B4D16A87B for ; Thu, 21 Dec 2006 12:33:46 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 98B8D13C45E for ; Thu, 21 Dec 2006 12:33:36 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id kBL4bZA3063379; Thu, 21 Dec 2006 07:37:35 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id kBL4bY2B063377; Thu, 21 Dec 2006 07:37:34 +0300 (MSK) (envelope-from yar) Date: Thu, 21 Dec 2006 07:37:33 +0300 From: Yar Tikhiy To: V??clav Haisman Message-ID: <20061221043733.GA63112@comp.chem.msu.su> References: <45886C87.8020405@sh.cvut.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45886C87.8020405@sh.cvut.cz> User-Agent: Mutt/1.5.9i Cc: freebsd-stable@freebsd.org Subject: Re: negative runtime etc., the story continues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 12:33:46 -0000 On Tue, Dec 19, 2006 at 11:49:43PM +0100, V??clav Haisman wrote: > Hi, > I wrote about how FreeBSD 6.1 RC1, with latest RELENG_6 kernel, prints loads > of "calcru: runtime went backwards..." and "calcru: negative runtime..." > messages when the FreeBSD runs as virtual server under Microsoft Virtual > Server 2006 R2. When I wrote this I was compiling and installing lots of > packages, setting up the OS. Now that it is idle I have noticed one quite bad > thing. Any process that sleeps on timer or sleep() call will wake up much > later than it should. For example, when I start top there should be two > seconds delay between updates of the screen. It takes up to 20 seconds! But > when there is compilation running or something else CPU intensive, the timer > seems to work fine. > > I even tried setting different kern.timecounter.hardware (TSC, ACPI-safe, > i8254) and kern.hz (to lower than the default 1000) but that did not help a bit. > > Is there anything I can do to get rid of the calcru messages apart from > reinstalling to real hardware? Last time I was trying to run FreeBSD as a guest OS in MS VS, I found that TSC would work the best, but only if I made sure that the TSC frequency was correct. For some weird reason, the frequency initially detected by the kernel was totally bogus and changing from one boot to another, so I just estimated it from cpu-z output in the host OS, and it fairly worked. I still couldn't get rid of the annoying warnings, especially when under load. -- Yar