From owner-freebsd-current Tue Jan 9 3:10:51 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 A4B0537B401 for ; Tue, 9 Jan 2001 03:10:34 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA98886; Tue, 9 Jan 2001 12:10:33 +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: current@freebsd.org Subject: bogus microuptime() warnings? From: Dag-Erling Smorgrav Date: 09 Jan 2001 12:10:32 +0100 Message-ID: Lines: 12 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 I regularly get "microuptime() went backwards" warnings on my desktop box. The funny thing about them is that the reported timevals have the same seconds part, but the microseconds part of the second timeval is so large that it's wrapped around to a negative number (causing the signed comparison to report that it went backwards). This suggests that the current process has been running uninterrupted for several seconds, which seems unlikely - or that the timecounter was adjusted upwards while the process was running (could ntp cause that?) 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