From owner-freebsd-stable Wed Jun 28 7:21:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sohara.dyndns.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id A0D1137B87B; Wed, 28 Jun 2000 07:21:40 -0700 (PDT) (envelope-from steve@sohara.dyndns.org) Received: (from steve@localhost) by sohara.dyndns.org (8.9.3/8.9.3) id PAA08455; Wed, 28 Jun 2000 15:28:59 +0100 (IST) (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000628084749.A84134@luke.immure.com> Date: Wed, 28 Jun 2000 15:28:59 +0100 (IST) From: "Steve O'Hara-Smith" To: Bob Willcox Subject: Re: microuptime() going backwards Cc: freebsd-stable@FreeBSD.ORG, wilko@FreeBSD.ORG, Greg Lehey Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Jun-00 Bob Willcox wrote: > with a 700MHz Athlon CPU. Also, I have another system here with a > similar configuration (same Abit board but with a 800MHz CPU in it and > a SCSI disk vs. IDE) that doesn't suffer from this problem (with apm > installed). Just as a datapoint, I get the microuptime going backwards messages on rare occasions (maybe once a week) from my Compaq laptop. I rather assume that the cause (race hazard ?) affects my system but that I rarely see the symptom, I can easily imagine it being rare enough to be invisible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message