linux-kernel - Re: 2.6.19-rc6-rt8: alsa xruns

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1164825498.18954.5.camel@cmn3.stanford.edu>
Date:	Wed, 29 Nov 2006 10:38:18 -0800
From:	Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	nando@...ma.Stanford.EDU,
	"Linux-Kernel," <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19-rc6-rt8: alsa xruns

On Wed, 2006-11-29 at 14:43 +0100, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <nando@...ma.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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/