Re: 2.6.15-rt2 - repeatable xrun - no good data in trace

[Ingo Molnar <mingo@elte.hu>]

* Mark Knecht <markknecht@gmail.com> wrote:

> > cdrecord does run with SCHED_RR/99 when started with proper privileges.
>
> Ah, then it's likely that this isn't a real problem and it would be 
> expected to cause an xrun?
> 
> Anyway, it seems strange that the trace doesn't show anything. I 
> suppose that's because cdrecord just grabs a lot of time at a higher 
> priority than Jack and Jack ends up not getting serivces at all for 
> 5-10mS?

the tracer will only detect undue delays in the 'highest prio' task in 
the system - but it cannot detect whether all priorities in the system 
are given out properly. In this particular case it was cdrecord that had 
the highest priorities, and the delays you saw in Jackd were due to 
cdrecord trumping Jackd's priority.

One way to make such scenarios easier to notice & debug would be for 
jackd to warn if there are tasks in the system that have higher
priorities. (maybe it could even do it at xrun time, from a lower-prio 
thread.)

	Ingo