Date: Tue, 2 Oct 2001 17:20:15 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Mike Smith <msmith@freebsd.org> Cc: Warner Losh <imp@harmony.village.org>, <current@freebsd.org> Subject: Re: whups, I lied Message-ID: <20011002171953.C4030-100000@wonky.feral.com> In-Reply-To: <20011002171721.C4030-100000@wonky.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It also mostly seems to be happening during boot probing- probably when my FC kernel thread is running. That may be a clue. On Tue, 2 Oct 2001, Matthew Jacob wrote: > > I dunno. It's an STL2 board with 2 1GHz processors and 1GB of memory. > It doesn't always happen. I'm running ntp. > > > > On Tue, 2 Oct 2001, Mike Smith wrote: > > > > > yes, with acpi timer disabled this seems to have gone away > > > > > > Nope, even with the change Mike mentioned, I still get: > > > > > > microuptime() went backwards (50013.3990440 -> 50012.321555) > > > microuptime() went backwards (50013.3990440 -> 50012.406351) > > > > This looks really bad; like time is actually stepping forwards a second > > or so accidentally. > > > > One misread I'd put down to a glitch, but this looks like our idea of > > "now" goes forward too fast and then "real time" takes a while to catch > > up. > > > > -- > > ... 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] > > V I C T O R Y N O T V E N G E A N C E > > > > > > > > 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?20011002171953.C4030-100000>