cpu-timer rate
Peter Jeremy
PeterJeremy at optushome.com.au
Wed Dec 7 10:25:03 PST 2005
On Wed, 2005-Dec-07 03:51:47 -0800, Ed wrote:
>I certainly do not have a full understanding of the interactions between
>the various FreeBSD software timers and i386 hardware clocks, but I do know
>this is not the first time we've seen a problem with the APIC/ACPI
>timers/clocks.
You have a totally different problem. In your case the system is not
keeping correct time - this is because VMware does not provide stable
clock interrupts - probably due to interactions between VMware and the
host OS. In kama's case, the interrupt rate reported by vmstat -i
does not match the numbers reported by kern.clockrate. There is no
indication that the system is not keeping correct time.
>Again, I'm no expert, but clock problems do keep cropping up here on
>the -STABLE list, and the explanations for them to date have not been
>consistent.
AFAIR, all the problems reported here have been related to VMware
clients. And as someone stated "VMware plays fast and loose with
clocks".
>I'm sure I'm not the only end-user who would appreciate it if the core team
This is nothing to do with the core team.
--
Peter Jeremy
More information about the freebsd-stable
mailing list