On Mon, 4 Feb 2013, Austin Hendrix wrote: > I gave the 3.4.28-rt40 stable release a try today, and so far I > haven't seen the problems that I was seeing with 3.4.4-rt13. I'd still > like to know more about how the debug the problems I'm seeing on > 3.4.4-rt13 so that I can do a better job of debugging if problems like > this come up in the future. One possibility would be to use the kernel tracer and modify latencytop in the kernel to issue a tracing_off() call when a certain latency treshold is reached. That way you freeze the kernel trace on the spot where the latency is detected and you can analyze what happened right before that point in the system. Thanks, tglx -- 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
