On Sat, 7 Oct 2000, Valentin Nechayev wrote:
> At Fri, 6 Oct 2000 22:00:23 +0000 (UTC), jhb wrote:
> JB> tc_windup() wasn't called soon enough to update the timecounter. Making
>
> On my system _each_ boot causes hundreds of these messages.
> And as described, long offsets without updating are caused by some
> code in drivers, i.e. DELAY(1000000) in isa/fd.c. Is it nesessary to call
> tc_windup() between iterations in isa_configure? ;|
Not really. The timecounters overflow to bizarre values if the boot takes
a long time (more than about 4 seconds), but there is no problem unless
something looks at the time before tc_windup() is working and expects the
time to be monotonic. Previously mi_switch() looked at the time before
tc_windup() was called, and this was impossible to avoid because getting
to tc_windup() involved a context switch. Now the misbehaviour should
only be visible using a debugger or debugging code that prints the time.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
