From owner-freebsd-current Tue Sep 19 14:26:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 0223037B422 for ; Tue, 19 Sep 2000 14:26:52 -0700 (PDT) Received: (qmail 7001 invoked from network); 19 Sep 2000 21:26:51 -0000 Received: from acs-24-154-11-27.zoominternet.net (24.154.11.27) by scully.zoominternet.net with SMTP; 19 Sep 2000 21:26:51 -0000 Date: Tue, 19 Sep 2000 17:26:50 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-11-27.zoominternet.net To: Bruce Evans Cc: "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, Bruce Evans wrote: > On Tue, 19 Sep 2000, Andrey A. Chernov wrote: > > > microuptime() went backwards (1.3624050 -> 1.998840) > It really does go backwards. This is caused by the giant lock preventing > the clock interrupt task from running soon enough. The giant lock can > also prevent the clock interrupt task from running often enough even > after booting. E.g., "dd if=/dev/random of=/dev/null bs=large" does > several bad things. I've noticed that, every time I do ntpdate, my clock loses about 5-11 seconds per hour. At first I thought it may have been my CMOS battery, but maybe it's that microuptime() thing that's causing it. (I've got a UP machine.) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message