On Tue, Jul 05, 2005 at 02:18:56PM -0700, Jeremy C. Reed wrote:
> On Tue, 5 Jul 2005, Manuel Bouyer wrote:
> 
> >>6450 ms can't be correct and the negative number is wrong too.
> >
> >It looks like your system clock is not behaving properly. From your dmesg
> >output, this system should have a CPU cycle counter. Maybe it's one
> >of these CPU with a broken TSC ? If so, running a 'while (1);' loop (or
> >anything else that will keep the CPU 100% busy) may help.
> 
> I see that it does help. I do a while loop in one shell and the ping in 
> another console and now it behaves correctly. It is basically same speed 
> as on my workstation. Thanks for the workaround.
> 
> Any fix? Not a big deal, as I am replacing this hardware soon.

There has been a discussion about this on port-i386:
"when to change microtime_func from i8254_microtime to cc_microtime"

I think if you rebuild a kernel with
options NO_TSC_TIME
it should work

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--