Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Sep 2000 15:02:17 +0200
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        John Baldwin <jhb@FreeBSD.ORG>
Cc:        Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG, "Andrey A. Chernov" <ache@nagual.pp.ru>, smp@FreeBSD.ORG
Subject:   Re: recent kernel, microuptime went backwards 
Message-ID:  <96419.969454937@critter>
In-Reply-To: Your message of "Wed, 20 Sep 2000 00:44:24 PDT." <XFMail.000920004424.jhb@FreeBSD.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <XFMail.000920004424.jhb@FreeBSD.org>, 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-smp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96419.969454937>