From owner-freebsd-stable Wed Jun 28 7:32:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hq1.tyfon.net (hq1.tyfon.net [213.212.29.17]) by hub.freebsd.org (Postfix) with ESMTP id 7AFC637B87E; Wed, 28 Jun 2000 07:32:15 -0700 (PDT) (envelope-from dl@tyfon.net) Received: from enigmatic (dhcp1.intranet.tyfon.net [192.168.1.20]) by hq1.tyfon.net (Postfix) with SMTP id 963AA1C5C9; Wed, 28 Jun 2000 16:32:11 +0200 (CEST) From: "Dan Larsson" To: "Steve O'Hara-Smith" , "Bob Willcox" Cc: , , "Greg Lehey" Subject: RE: microuptime() going backwards Date: Wed, 28 Jun 2000 16:31:56 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | 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. Someone suggested that I should compile my kernel with the line 'device apm0' commented out. This worked for me, but may not be something to aim for on a laptop (FYI: FreeBSD-4.0 STABLE). | Regards ------------ Dan Larsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message