Hi all,

I have noticed some strange behavior of real-time application that has very long period. Result from kernel and scheduler traces in particular suggests that the maximum length that you can set as resume time for the one-shot timer is roughly 7500000. I come to this conclusion as I watch the trace log and see the scheduler was executed at that interval (~7500000) although task has not reached the resume time yet. Has anyone noticed this before? Is there anyway to work around this or fix it?

You can repeat this result by set the period in the measurement example to bigger than 10000000.

 

Hai Quang Nguyen

 

Reply via email to