Re: 2.6.19-rc6-rt8: alsa xruns

Fernando Lopez-Lezcano
2006-11-29T18:38:24Z

On Wed, 2006-11-29 at 14:43 +0100, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
>
> > > > > ( japa-4096 |#0): new 17 us maximum-latency wakeup.
> > > > > ( beagled-3412 |#1): new 19 us maximum-latency wakeup.
> > > > > ( IRQ 18-1081 |#1): new 26 us maximum-latency wakeup.
> > > > > ( snd-4040 |#1): new 1107 us maximum-latency wakeup.
> > > > > ( japa-4096 |#0): new 1445 us maximum-latency wakeup.
> > > > > ( japa-4096 |#0): new 2110 us maximum-latency wakeup.
> > > > > ( qjackctl-4038 |#1): new 2328 us maximum-latency wakeup.
> > > > > ( japa-4096 |#0): new 2548 us maximum-latency wakeup.
> > > > > ( IRQ 18-1081 |#0): new 10291 us maximum-latency wakeup.
>
> ok, i reproduced something similar on one of my boxes and it turned out
> to be a tracer bug. I've uploaded -rt10, could you try it? (The xruns
> will likely remain, but at least the tracer should be more usable now to
> find out the reason for the xruns.)

I'm testing -rt10 right now (your binary rpm). Looks like the number and
length of the xruns went down, at least for now. All below 2mSec - jack
is running 128x2 @ 48000Hz. I'll let it run for a while and report the
traces (I have a script that collects all traces above 60us, but not all
xruns trigger a trace).

-- Fernando