I think that you can get this if you have an MP kernel compiled without
"Enhanced Real Time Clock" support. The default clock driver apparently
isn't MP-safe.
Ken Seefried, CISSP
Przemyslaw Wegrzyn writes:
>
> Look at this:
>
> czajnik@earth:~$ ping 156.17.209.1
> PING 156.17.209.1 (156.17.209.1): 56 data bytes
> 64 bytes from 156.17.209.1: icmp_seq=0 ttl=247 time=5427.7 ms
> 64 bytes from 156.17.209.1: icmp_seq=1 ttl=247 time=23.2 ms
> 64 bytes from 156.17.209.1: icmp_seq=2 ttl=247 time=429492829.5 ms
> ^^^^^^^^^^^^^^^^^^^
> 64 bytes from 156.17.209.1: icmp_seq=3 ttl=247 time=429492907.1 ms
> 64 bytes from 156.17.209.1: icmp_seq=4 ttl=247 time=16.5 ms
> 64 bytes from 156.17.209.1: icmp_seq=5 ttl=247 time=21.4 ms
>
> What the hell can it be ?!? Every ping comes back in few milisecounds...
>
> We've recently added second CPU to this machine, can it (failed CPU) be
> the reason ? Overall stability is good...
>
> -=Czaj-nick=-
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
