Ok - there are a lot of issues around about this (googled). It all depends on whether your motherboard has the old RTC (Real Time Clock) timer or the newer HPET (High Precision Event Timer). On top of that, if it has HPET, is it enabled. Does the OS kernel support it ? Even IF the kernel supports it, was the kernel built with it enabled and correct options ? But wait, there's more. Are things like asterisk, the ztdummy compiled/recompiled for it ?
On top of that, there are a bunch of 'fixes' that disable the HPET and use the old RTC, change the max-user-freq, turn ACPI off
As the HPET is supposed to be a move forward and supported in kernel 2.6.22, I'm not sure we should be going backwards.
http://en.wikipedia.org/wiki/High_Precision_Event_TimerAs I'm not a programmer, a lot of this is way above me.
But i found this interesting, recent, asterisk thread.
http://forums.digium.com/viewtopic.php?t=22387&highlight=rtc+lost+interruptsWhere, at the bottom, is said:-
"Okay... I fixed it!
Still I'm getting a delay in a meetme room when I'm sitting next to someone else trying, but I'm blaming that on the default meetme operations.
Right, what I did was:
1. Recompile the default Debian kernel with a timer of 1000Hz instead of 256Hz. (Needed for Zaptels timing).
2. Commented out the defines for the RTC from ztdummy.c
3. Recompiled zaptel & installed it (not the init scripts though).
4. Recompiled asterisk and installed it.
5. Ran modprobe ztdummy
6. Activated a meetme conference.
Will something like this also work for you?"