Kaya, Sinan wrote:
Hello all,
My realtime system experiences periodic bursts every 4 hours. How can
i find the reason for this ? I know the traceit tool but it dumps
so much data and it is useless under this case. I need to find what
happened at the exact time of burst.
The trace-it tool is a demo, you need to adopt it to your scenario,
specifically make it trigger the stop once you detected some burst.
Means, you need to put its code into your application. Did you do this?
I use rtai_smi module to disable SMI interrupts
Then you will probably like this tool even more:
http://www.rts.uni-hannover.de/rtaddon/#smictrl
and set my network interface driver priorities to 99. So it should be
something non maskable but what ?
Out-of-the-box NIC drivers are generally not suited for more than
soft-RT. They allocate memory (skbs) from global pools which takes
varying time (or may even fail if your are short on memory), sometimes
they try to pile up packets first before they raise an IRQ, and they
often contain hardware/link state watchdogs that can inject latencies
right at the wrong time. If you need low latency by design, more work is
required.
In any case, understanding this particular problem comes first, and
collecting the right traces will help.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
-
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
