From: Ingo Molnar <mingo@elte.hu>
To: Mark Knecht <markknecht@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc3-rt9 - a few xruns misses
Date: Thu, 6 Oct 2005 10:30:43 +0200 [thread overview]
Message-ID: <20051006083043.GB21800@elte.hu> (raw)
In-Reply-To: <5bdc1c8b0510051615hfd77ba8pab7ee07bde13ffd4@mail.gmail.com>
* Mark Knecht <markknecht@gmail.com> wrote:
> Hi,
> This is nothing particularily new. I'm just presenting it to
> represent what I'm seeign and get some guidance about how to find out
> what's going on.
lets first check whether all the RT priorities are set up correctly for
your audio setup. Could you send me your /proc/interrupts, your .config
and the output of:
ps -eo pid,pri,rtprio,cmd
there are lots of built-in methods in the -rt kernel to figure out the
source of latencies. If the default methods do not show anything then
worst-case we can activate the kernel's latency tracer to record the
actual xrun critical path.
Ingo
next prev parent reply other threads:[~2005-10-06 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 23:15 Mark Knecht
2005-10-06 8:30 ` Ingo Molnar [this message]
2005-10-06 16:00 ` Mark Knecht
2005-10-06 16:26 ` Lee Revell
2005-10-06 16:30 ` Mark Knecht
2005-10-06 17:06 ` Mark Knecht
2005-10-06 17:38 ` Lee Revell
2005-10-06 17:44 ` Mark Knecht
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=20051006083043.GB21800@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
/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
all inboxes | Powered by JetHome®