Date: Fri, 8 Sep 2000 10:10:02 +0930 From: Greg Lehey <grog@lemis.com> To: John Baldwin <jhb@pike.osd.bsdi.com> Cc: Steve Ames <steve@virtual-voodoo.com>, freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards Message-ID: <20000908101001.G83632@wantadilla.lemis.com> In-Reply-To: <200009080028.RAA26021@pike.osd.bsdi.com>; from jhb@pike.osd.bsdi.com on Thu, Sep 07, 2000 at 05:28:02PM -0700 References: <20000907191913.A93124@virtual-voodoo.com> <200009080028.RAA26021@pike.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 7 September 2000 at 17:28:02 -0700, John Baldwin wrote: > Steve Ames wrote: >> Just upgraded to -CURRENT as of about noon (EST) today. At reboot >> I got a lot of these: >> >> microuptime() went backwards (1.7682417 -> 1.997434) >> >> I recall reading in -current earlier this week that someone was >> looking for victims getting this. What further information can I provide? > > This is a SMPng issue on UP machines. Yes, but it's not the only cause. We've also seen it on pre-SMPng stuff, and Athlons seem to be particularly capable of doing it. phk is looking at it at the moment, and he has an idea what's causing it. I'd guess, however, that this *is* the SMPng problem. It's subtly different from other manifestations in that the first time typically has 7 digits after the decimal point. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000908101001.G83632>