We're seeing something similar on our dual core AMD system here. After a reboot, it worked fine. We rebooted it when Luke first posted this message.

Now, roughly 30 days later, the latency numbers are very unreliable. Honestly, we've not looked at it since the problem started getting bad (that happened on March 6th after a reboot on February 20th), so we've not yet had a chance to troubleshoot what's going on here. Since the 6th, though, the "drift" has been increasing - with the average latency going from 105ms on the 6th to 2009ms right now. Luke's clock problems are drifting the opposite direction from ours - here, it seems like our latency is growing rather than getting negative latency numbers.

The ping command is returning the same thing - 150ms, then 2200ms, then 145, then 2300. It's not a latency problems because it doesn't take 2200ms to get the response - those come back immediately - very evident that it's a clock problem.

I'll see if I can look for any patterns later today (like maybe the reporting times from the different CPU cores, if that's the problem). Maybe I can put together a little utility that shows the drift between the cores.

I'm assuming that we're just having time drift problems between the clock cores, and the cores are just not synchronized.

Interesting stuff...

- Pete