Date: Sun, 19 Aug 2001 13:00:06 +0930 From: Greg Lehey <grog@FreeBSD.org> To: Sean Davis <dive-fb@endersgame.net> Cc: freebsd-questions@freebsd.org Subject: Re: microuptime() oddness Message-ID: <20010819130006.C35750@wantadilla.lemis.com> In-Reply-To: <20010813032537.A10782@endersgame.net>; from dive-fb@endersgame.net on Mon, Aug 13, 2001 at 03:25:37AM -0400 References: <20010813032537.A10782@endersgame.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 13 August 2001 at 3:25:37 -0400, Sean Davis wrote: > Hello, I have a machine (AMD Athlon 1.2ghz, 256MB ram) running > FreeBSD-stable, and have been noticing a lot of weird kernel debug messages > like: > > microuptime() went backwards (7467.677311 -> 7467.-694689197) > microuptime() went backwards (7718.041075 -> 7718.-695325418) > calcru: negative time of -1984434482 usec for pid 365 (setiathome) > calcru: negative time of -1984434287 usec for pid 365 (setiathome) > calcru: negative time of -1984434107 usec for pid 365 (setiathome) > calcru: negative time of -1984433927 usec for pid 365 (setiathome) > <repeat many, many times> > > Does anyone have any idea whats causing this? It's a bug which seems to be triggered by something to do with AMD processors, though we're not sure whether it's the processor or (more likely) the BIOS. If you disable APM, it should go away. I have four AMD processors here, and they all showed it with APM enabled. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010819130006.C35750>