Timer problem?

Matthew Dillon dillon at apollo.backplane.com
Tue Feb 3 23:24:53 PST 2004

:Something is seriously whacked up with the timer on my box. This started
:recently (cant exactly pin down when)..
:uname output:
:DragonFly dragon.bsdtech.com 1.0-CURRENT DragonFly 1.0-CURRENT #0: Tue Feb
:3 05:38:29 CET 2004
:for example, "date" is jumping about 17 seconds every second..
:another example:
:[erik at dragon:~]$ time fetch
:Receiving epic4.tgz (699615 bytes): 100% (ETA 00:00)
:699615 bytes transferred in 1444.8 seconds (484.24 Bps)
:real    27m20.950s
:user    0m0.769s
:sys     0m2.304s
:This actually took about 3 minutes..
:Any ideas on how I can track this down?
:- Erik

    Hmm.  Well, the time keeping code was changed recently, that's probably
    the event.  But there's something very wrong here... it kinda sounds
    like something in the kernel has taken over 8254 Timer 2 rather then
    the system clock being off.

    If you have any sound drivers or special console features loaded try
    turning them off.

    Boot with -v to see what the system reports the 8254's frequency
    to be.  If it is wildly off from 1193182 Hz try building a kernel
    with the CLK_USE_I8254_CALIBRATION option.  If it isn't wildly off
    then something is messing with Timer2.

					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>

More information about the Bugs mailing list