From owner-freebsd-questions Tue Jun 25 6:44:20 2002 Delivered-To: freebsd-questions@freebsd.org Received: from PHSEXCHICI.MGH.HARVARD.EDU (phsexchici.mgh.harvard.edu [132.183.126.51]) by hub.freebsd.org (Postfix) with ESMTP id 458C237B43A for ; Tue, 25 Jun 2002 06:43:54 -0700 (PDT) Received: by phsexchici.mgh.harvard.edu with Internet Mail Service (5.5.2650.21) id ; Tue, 25 Jun 2002 09:43:38 -0400 Message-ID: <375F68784081D511908A00508BE3BB1701EF1BF4@phsexch22.mgh.harvard.edu> From: "Morse, Richard E." To: 'Aaron Burke' , FreeBSD-Questions Subject: RE: microuptime() went backwards Date: Tue, 25 Jun 2002 09:43:35 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Aaron Burke [mailto:aburke@nullplusone.com] wrote: > I am encountering a new problem with my primary unix machine. In > the last two weeks, I have been getting the error "microuptime() > went backwards (49869.438718 -> 49869.-694941947)". The numbers > do change with each message. Hi! You should do a search through the list for this, but as I recall, the error has something to do with AMD specific hardware (a motherboard issue, I think?). I think that there is a syscntl setting you can use to correct this. As I don't have any hardware this manifests on, I've never had to do it myself, but it has shown up frequently on the list... HTH, Ricky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message