This looks like a garbage collector always running when no more memory is available. But that would only be possible if you use Java (or Mono/DotGnu).
Regards,
H. Keller
as far as i can remember, i had similar problems with interaction userland-app and i2c-driver. decrease the i2c-clock fixed this problem.
Quote from "hwmbabe"The program is written in C, so there should be no garbage-collection(?)... any further suggestions?
No specific ideas from me anymore. Try to strip down your program more and more until this effect vanishes. Then the problem must be in the last block that you removed.
Regards,
H. Keller
This might be the only way... divide and conquer 
Could a real-time-extension be a proper solution?
Regards,
Patrick
I think this is no regular behaviour, therefore just try to locate and remove the problem, then everything should be fine. And by the way, a real-time-extension is not so easy to handle as you might think.
Regards,
H. Keller
