At Fri, 6 Oct 2000 22:00:23 +0000 (UTC), jhb wrote:
JB> The problem was that the interrupt threads for the clk interrupt introduced
JB> enough latency that occasionally (mostly during a heavy load of interrupts)
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? ;|
JB> clock interrupts not be threaded fixes this problem.
Oh, well, I understand now that scheduling is nesessary to be run early
because interrupts are implemented as kernel threads even when kernel
is in phase of hardware detection.;(
/netch
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
