On May 4, 2011 08:20:51 pm you wrote:
Weird, CLOCK_REALTIME does it too.
Only CLOCK_PROCESS_CPUTIME_ID does not.
Been reading, according to places like this:
CLOCK_MONOTONIC and CLOCK_MONOTONIC_RAW are not supposed to go backwards
but apparently CLOCK_MONOTONIC just might and CLOCK_MONOTONIC_RAW is better,
and CLOCK_REALTIME is less reliable than that.
However on that second page it mentions a kernel fix, more recent than mine.
Mine also doesn't seem to have CLOCK_MONOTONIC_RAW.
I am going to chalk it up to this older kernel, and test on my newer machine
and hope it vanishes...
In the meantime, I can make the code I'm working on tolerant.
I'm just not sure how this affects the rest of the existing app code -
could this be the source of occasional bugs or have we just been lucky or
is it already tolerant...
Linux-audio-dev mailing list