From owner-freebsd-current Tue Jan 9 3:52:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id EE46637B400 for ; Tue, 9 Jan 2001 03:52:12 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA99038; Tue, 9 Jan 2001 12:49:40 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: bogus microuptime() warnings? References: <15658.979038875@critter> From: Dag-Erling Smorgrav Date: 09 Jan 2001 12:49:39 +0100 In-Reply-To: Poul-Henning Kamp's message of "Tue, 09 Jan 2001 12:14:35 +0100" Message-ID: Lines: 18 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > No, this is either a problem reading the i8254 timecounter reliably > or an interrupt latency problem. Given that this is -CURRENT, interrupt latency is a likely explanation... Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... > If you sysctl's indicate that you are running on the TSC timecounter > and you can reproduce this there is some chance we can create a workaround. I'll check. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message