From owner-freebsd-current Thu Oct 5 18:30:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id DF73737B503 for ; Thu, 5 Oct 2000 18:30:26 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e961UCi23836; Thu, 5 Oct 2000 18:30:12 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e961RlU43037; Thu, 5 Oct 2000 18:27:47 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001004140250.H5060@yoko.hsc.fr> Date: Thu, 05 Oct 2000 18:27:47 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Alain Thivillon Subject: RE: -CURRENT clock deviation Cc: current@FreeBSD.ORG 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'm about to commit some changes to the clock interrupt code on the x86, try again once those are in place. > 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. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message