Problems with clock on 1.1-CURRENT

[H.Miyamoto]

Hello.

My DragonFly 1.1-CURRENT system have same clock problems too, since
1.0-RELEASE that upgraded from FreeBSD 4.10-STABLE. I had updated
(buildkernel && installkernel) after reading these mails but problems
was not fixed.

$ uname -a
DragonFly humming.***.net 1.1-CURRENT DragonFly 1.1-CURRENT #5: Thu Jul 29 01:31:38 JST 2004     kazane at humming.***.net:/usr/obj/usr/home/df/src/sys/Humming  i386
$ dmesg | fgrep clock
TSC clock: 497850056 Hz, i8254 clock: 1193216 Hz
$ ./sysctlclockrate
hw.i8254.timestamp: 88f70b74 0000007cbf636d6f
hw.i8254.timestamp: 88f72b08 0000007cbf7d27d3
hw.i8254.timestamp: 88f74502 0000007cbf925409
hw.i8254.timestamp: 88f7606a 0000007cbfa8a9b6
hw.i8254.timestamp: 88f778f2 0000007cbfbca723
hw.i8254.timestamp: 88f78e86 0000007cbfce3b8c
hw.i8254.timestamp: 88f7ab7a 0000007cbfe5d3f6
hw.i8254.timestamp: 88f7c3b2 0000007cbff9904c
hw.i8254.timestamp: 88f7de74 0000007cc00f5f1c
hw.i8254.timestamp: 88f7f4e2 0000007cc021a54b
hw.i8254.timestamp: 88f80fac 0000007cc0377a49
hw.i8254.timestamp: 88f82af6 0000007cc04db866
hw.i8254.timestamp: 88f84184 0000007cc06018a8
hw.i8254.timestamp: 88f85a8c 0000007cc0747f56
hw.i8254.timestamp: 88f86f98 0000007cc085a5b9
hw.i8254.timestamp: 88f881de 0000007cc094896c
hw.i8254.timestamp: 88f89878 0000007cc0a6f565
hw.i8254.timestamp: 88f8abdc 0000007cc0b6c29d
hw.i8254.timestamp: 88f8c368 0000007cc0c9f2be
hw.i8254.timestamp: 88f8d688 0000007cc0d987a1
hw.i8254.timestamp: 88f8ed90 0000007cc0ec4e96
hw.i8254.timestamp: 88f904fa 0000007cc0ff6278
hw.i8254.timestamp: 88f91bde 0000007cc112090c
hw.i8254.timestamp: 88f92e1c 0000007cc120e74f
hw.i8254.timestamp: 88f94352 0000007cc1323135
hw.i8254.timestamp: 88f955e2 0000007cc14150ad
hw.i8254.timestamp: 88f96b6a 0000007cc152dc64
hw.i8254.timestamp: 88f980c8 0000007cc164474d
hw.i8254.timestamp: 88f99464 0000007cc1743fe4
hw.i8254.timestamp: 88f9ad12 0000007cc1885ef4
hw.i8254.timestamp: 88f9ce68 0000007cc1a38948
hw.i8254.timestamp: 88f9e484 0000007cc1b58aee
hw.i8254.timestamp: 88f9f76a 0000007cc1c4f281
hw.i8254.timestamp: 88fa0d9a 0000007cc1d7061f
hw.i8254.timestamp: 88fa21c8 0000007cc1e779dc
hw.i8254.timestamp: 88fa3680 0000007cc1f85afc
hw.i8254.timestamp: 88fa4c04 0000007cc209e27e
hw.i8254.timestamp: 88fa6376 0000007cc21cff96
hw.i8254.timestamp: 88fa7862 0000007cc22e0b0e
hw.i8254.timestamp: 88fa9076 0000007cc241aad3
hw.i8254.timestamp: 88faab36 0000007cc25777a1
hw.i8254.timestamp: 88fac3d6 0000007cc26b884b
hw.i8254.timestamp: 88fada28 0000007cc27db7c6
hw.i8254.timestamp: 88faf112 0000007cc2906412
hw.i8254.timestamp: 88fb0682 0000007cc2a1dd09
hw.i8254.timestamp: 88fb1df4 0000007cc2b4f9a0
hw.i8254.timestamp: 88fb3292 0000007cc2c5c616
hw.i8254.timestamp: 88fb4824 0000007cc2d75aa8
hw.i8254.timestamp: 88fb5f44 0000007cc2ea318a
hw.i8254.timestamp: 88fb7744 0000007cc2fdc09a

The 'sysctlclockrate' is the Matthew's shell script.
What can I do against this problems ?

Regards.
-- 
H.Miyamoto (aka "Yuukis"). <Ys at xxxxxxxxxxxxxx>
           http://wids.net/ - Enjoy Your Computing ?