Date: Tue, 19 Sep 2000 17:26:50 -0400 (EDT) From: Donn Miller <dmmiller@cvzoom.net> To: Bruce Evans <bde@zeta.org.au> Cc: "Andrey A. Chernov" <ache@nagual.pp.ru>, current@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards Message-ID: <Pine.BSF.4.21.0009191724370.333-100000@acs-24-154-11-27.zoominternet.net> In-Reply-To: <Pine.BSF.4.21.0009200514520.2289-100000@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009191724370.333-100000>