Re: Timekeeping hosed by factor 3, high lapic[01] interrupt rates

Jens Schweikhardt wrote:
> ...
> # # 3. Backout rev 1.218 of src/sys/i386/isa/clock.c so the irq0 interrupt
> # # handler is reactivated and the RTC fiddled.
> # 
> # Will do so next. I've nailed the change between March 6 and March 30.
> # 1.218 is from 2005/03/24 21:34:16, which would fit.
> 
> We have a winner. Backing out 1.218 from a 2005/03/24 system does the trick,
> as well as a CURRENT without 1.218 (but 1.219-220 in there) bring back irq0
> and time dilation is gone. All clocks work correctly.
> 
> Now the question is: what is so special in my system so that I appear
> to be the only one to notice the problem?
> 
> Regards,
> 
> 	Jens

I see this too, backing out 1.218 of clock.c did not help here but my system is 
overclocked and it's pretty old (Abit BP6) so the battery may very well be dead.

This is with the 1.218 change backed out.
# vmstat -i
interrupt                          total       rate
irq0: clk                       82734023       1000
irq4: sio0                             2          0
irq6: fdc0                            10          0
irq16: fxp1                        10347          0
irq17: fxp0                        29339          0
irq19: ahc0                       187220          2
lapic0: timer                  165447117       2000
lapic1: timer                  165430135       1999
Total                          413838193       5002

I'll check the battery and step it back down to 366Mhz (now at 510).

-- 
Pawel