From: Ingo Molnar <mingo@elte.hu>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: "Linux-Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc6-rt8: alsa xruns
Date: Wed, 29 Nov 2006 14:43:11 +0100 [thread overview]
Message-ID: <20061129134311.GA14566@elte.hu> (raw)
In-Reply-To: <1164747854.15887.48.camel@cmn3.stanford.edu>
* 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.)
Ingo
next prev parent reply other threads:[~2006-11-29 13:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 19:58 2.6.19-rc6-rt8: alsa xruns Fernando Lopez-Lezcano
2006-11-28 20:09 ` Ingo Molnar
2006-11-28 20:37 ` Fernando Lopez-Lezcano
2006-11-28 21:04 ` Fernando Lopez-Lezcano
2006-11-28 21:35 ` Fernando Lopez-Lezcano
2006-11-28 23:22 ` Fernando Lopez-Lezcano
2006-11-29 7:24 ` Ingo Molnar
2006-11-29 13:43 ` Ingo Molnar [this message]
2006-11-29 18:38 ` Fernando Lopez-Lezcano
2006-11-29 19:51 ` Ingo Molnar
2006-11-29 20:22 ` Fernando Lopez-Lezcano
2006-11-29 20:34 ` Fernando Lopez-Lezcano
2006-11-28 20:12 ` Lee Revell
2006-11-28 20:14 ` Ingo Molnar
2006-11-28 22:01 ` Daniel Walker
2006-11-29 7:21 ` Ingo Molnar
2006-11-29 16:24 ` Daniel Walker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061129134311.GA14566@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox