From owner-freebsd-current Thu Oct 5 18:39:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id B111B37B502; Thu, 5 Oct 2000 18:39:43 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e961fTh03854; Thu, 5 Oct 2000 18:41:34 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010060141.e961fTh03854@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: Alain Thivillon , current@FreeBSD.ORG Subject: Re: -CURRENT clock deviation In-reply-to: Your message of "Thu, 05 Oct 2000 18:27:47 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Oct 2000 18:41:29 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 04-Oct-00 Alain Thivillon wrote: > > > > I have noticed that -CURRENT (build last week) is subject to a very high > > clock deviation: > > I run -CURRENT on a laptop, it seems that last commit in idle loop (the > > one replacing loop by HLT and lowering temperature) broke the clock. > > Hmm, this shouldn't really break it. I'm also a little surprised about that, but the whole "idle thread" concept is up for some major revision soon anyway, with APCI promising to substantially change the way we view "idleness" in a lot of cases. -- ... 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