From: Mark Knecht <markknecht@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, Lee Revell <rlrevell@joe-job.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: 2.6.15-rt2 - repeatable xrun - no good data in trace
Date: Tue, 10 Jan 2006 05:55:20 -0800 [thread overview]
Message-ID: <5bdc1c8b0601100555k7538924cx7a17b3e405771691@mail.gmail.com> (raw)
In-Reply-To: <1136900950.6197.33.camel@localhost.localdomain>
On 1/10/06, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 2006-01-10 at 11:05 +0100, Ingo Molnar wrote:
> > * 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.)
>
> Hmm, this reminds me. This system isn't a SMP machine is it? SMP has
> threads that run at priority 99 to handle things like swapping tasks
> from one CPU to another. These will never show up in the tracer since
> they are the highest priority. But I have seen these threads cause
> latencies in some of my own code.
>
> -- Steve
Steven,
No, this specific machine is UMP although I do have an HT machine I
use once in awhile that might fall prey to what you are mentioning.
While I have to agree that *if* cdrecord is running at a higher
priority then Jack would get trumped, I'm not positive yet that we
know that's true in this specific case. I have not yet received any
response from the developer of k3b, and while cdrecord is listed in
the setup of k3b I'm not sure how to test that it is really causing
the specific failure I saw.
NOTE: I'm sure cdrecord probably is causing this. I just don't want to
believe it is without some technical confirmation and assume there's
nothing that could be improved in the kernel.
NOTE 2: This case is pathological as I would never start writing a CD
when doing important audio work that requires zero xruns. I reported
it only to learn more myself.
Thanks,
Mark
next prev parent reply other threads:[~2006-01-10 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 20:52 Mark Knecht
2006-01-08 21:04 ` Michal Schmidt
2006-01-08 21:49 ` Jan Engelhardt
2006-01-08 22:04 ` Mark Knecht
2006-01-08 22:11 ` Michal Schmidt
2006-01-08 22:21 ` Mark Knecht
2006-01-10 10:05 ` Ingo Molnar
2006-01-10 13:49 ` Steven Rostedt
2006-01-10 13:55 ` Mark Knecht [this message]
2006-01-10 14:04 ` Michal Schmidt
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=5bdc1c8b0601100555k7538924cx7a17b3e405771691@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=rostedt@goodmis.org \
--cc=xschmi00@stud.feec.vutbr.cz \
/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®