On Tue, Sep 19, 2000 at 08:30:25PM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, 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.
It seems it was SCSI driver in my case waiting for SCSI device settle (or
in some another state, I am not sure).
BTW, could you please summarize this diagnostic? I.e. istead of tons of
messages effectively overflowing dmesg buffer and maybe cause backwards by
time consumed by themselfs put only one message summarizing all of them,
something like "went backwards N times".
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
