Weird dahdi_test output

I have run dahdi_test on a server I was asked to fix a Meetme() problem. The output is far beyond what is a realistic output. The server runs and the Dahdi version that comes with it. Any idea what is happening and any clue what might be a solution?

If you need any other info please let me know. Thanks in advance.

root@salt:~# dahdi_test
Opened pseudo dahdi interface, measuring accuracy…
-800.110% -800.102% -800.109% -800.109% -800.121% -800.098% -800.110% -800.110%
-800.109% -800.106% -800.109% -800.110% -800.109% -800.108% -800.109% -800.109%
-800.111% -800.106% -800.109% -800.109% -800.108% -800.115% -800.103% -800.109%
-800.109% -800.176% -800.039% -

The box working well gives RTC as source

meetmecall:/home/peter# cat /proc/dahdi/1
Span 1: DAHDI_DUMMY/1 “DAHDI_DUMMY/1 (source: RTC) 1” (MASTER)

The box with the problem has HRtimer as source

root@pepper:/etc/dahdi# cat /proc/dahdi/1
Span 1: DAHDI_DUMMY/1 “DAHDI_DUMMY/1 (source: HRtimer) 1” (MASTER)

What is difference between these sources and can the timer on the “problem server” be changed so RTC will be source (and the problem will be fixed in the proces)

The kernel has been changed and there is a change in the outpu of dahdi_test. first it was -800 or close to that and now it is -200 or close to that. It is still not working.

Any suggestion?

We also use HRTimer but our results are “normal”:
99.998% 99.992% 99.902% 99.896% …

Couple of suggestions - check what is output of
Then you can check running processes. May be you should check hardware also. Meaning if computer is too old and powerless - then may be you should change timer.