Date: Tue, 19 Sep 2000 20:30:25 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> 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: <92160.969388225@critter> In-Reply-To: Your message of "Wed, 20 Sep 2000 05:23:03 %2B1100." <Pine.BSF.4.21.0009200514520.2289-100000@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.21.0009200514520.2289-100000@besplex.bde.org>, Bruce Eva ns writes: >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. Yes, we are royally hosed right now with respect to interrupt service. It's a testimony to the robustness of the majority of our drivers that they don't explode more often than they do. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?92160.969388225>