From owner-freebsd-current Tue Sep 19 11:23:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E506237B422 for ; Tue, 19 Sep 2000 11:23:23 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id FAA23924; Wed, 20 Sep 2000 05:23:07 +1100 Date: Wed, 20 Sep 2000 05:23:03 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: <20000919184043.A346@nagual.pp.ru> 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 Tue, 19 Sep 2000, Andrey A. Chernov wrote: > With very latest kernel I got lots of > > microuptime() went backwards (1.3624050 -> 1.998840) > > messages just before > > Mounting root from ufs:/dev/da0s1a 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message