From owner-freebsd-current Wed Sep 20 7:13:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 2B8CC37B422; Wed, 20 Sep 2000 07:13:45 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8KD2HN96421; Wed, 20 Sep 2000 15:02:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: Bruce Evans , current@FreeBSD.ORG, "Andrey A. Chernov" , smp@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: Your message of "Wed, 20 Sep 2000 00:44:24 PDT." Date: Wed, 20 Sep 2000 15:02:17 +0200 Message-ID: <96419.969454937@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: >As for the micruptime() >messages on boot, they only occur here on a UP kernel. On an SMP kernel I >don't get them. Also, they always occur during mi_switch() when an interrupt >thread is finishing and going back to sleep. The first such thread to be run >to generate thet error message is the irq0: clk ithread, so the clk ithread is >running fine. The microuptime() messages occur because the timecounters expect the i8254 clock interrupt to run "hz" times per second, and it doesn't. In particular it doesn't during then 10-20 seconds we probe/attach devices. -- 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