From owner-freebsd-current Fri Sep 8 12:38:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 461EF37B446 for ; Fri, 8 Sep 2000 12:38:03 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id WAA01815; Thu, 7 Sep 2000 22:43:11 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009080543.WAA01815@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Lehey Cc: Kenneth Wayne Culver , John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-reply-to: Your message of "Fri, 08 Sep 2000 13:54:33 +0930." <20000908135433.V83632@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 22:43:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121)y > > > > this is bad.. right ? :-) > > Well, at any rate it looks very funny. If this is a laptop, try > building a kernel without apm and see if that helps. It only helps "hide" the problem. There's either *extremely* bogus data coming in, or an arithmetic or sequencing error that's allowing a corrupt timecounter to be seen. It might help to see the negative number as hex... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message