From: Lee Revell <rlrevell@joe-job.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: Fernando Lopez-Lezcano <nando@ccrma.stanford.edu>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
dwalker@mvista.com, david singleton <dsingleton@mvista.com>
Subject: Re: 2.6.14-rc4-rt1
Date: Wed, 12 Oct 2005 14:38:02 -0400 [thread overview]
Message-ID: <1129142282.11410.7.camel@mindpipe> (raw)
In-Reply-To: <1129141547.11297.4.camel@mindpipe>
On Wed, 2005-10-12 at 14:25 -0400, Lee Revell wrote:
> On Wed, 2005-10-12 at 11:00 -0700, Mark Knecht wrote:
> > On 10/12/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > > Sounds like an application bug (some JACK client doing something not RT
> > > safe). Can you reproduce the xruns if you just run jackd with no
> > > clients?
> >
> > I don't know. These xruns take hours to generate. I'd probably have to
> > dedicate a whole day of doing nothing on the machine to try, and then
> > if I didn't produce anything I'm not sure what it proves. If I do get
> > one then we get to see if there's data.
>
> A much easier solution is to recompile JACK with the
> --enable-preemption-check option. This activates the in-kernel
> debugging mechanism that causes a stack dump when an RT task schedules.
> It has been used to find tricky bugs in Hydrogen and Freqtweak already.
I should also remind you that if you pursue the
--enable-preemption-check option, then we'll be well outside of kernel
land so you might want to take it up on the JACK list.
Lee
next prev parent reply other threads:[~2005-10-12 18:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 11:14 2.6.14-rc4-rt1 Ingo Molnar
2005-10-11 16:03 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 20:55 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-11 21:08 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 21:13 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 21:21 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-11 22:23 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 16:37 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 17:48 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 18:00 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 18:25 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 18:38 ` Lee Revell [this message]
2005-10-12 19:11 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 19:41 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 19:45 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 19:52 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 6:14 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 6:16 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 6:33 ` 2.6.14-rc4-rt1 Steven Rostedt
2005-10-12 22:08 ` 2.6.14-rc4-rt1 George Anzinger
2005-10-12 23:41 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-12 23:52 ` 2.6.14-rc4-rt1 George Anzinger
2005-10-14 4:04 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 7:10 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-13 22:29 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 2:28 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 4:56 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 6:15 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 8:53 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 18:01 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 18:35 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 19:05 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 3:56 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 16:42 ` 2.6.14-rc4-rt1 Badari Pulavarty
2005-10-14 6:22 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 9:57 ` 2.6.14-rc4-rt1 Andi Kleen
2005-10-14 13:12 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 19:24 ` 2.6.14-rc4-rt1 Badari Pulavarty
2005-10-14 6:22 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-13 21:14 ` 1.6ms jitter in rtc_wakeup (Re: 2.6.14-rc4-rt1) Esben Nielsen
2005-10-14 3:45 ` Ingo Molnar
2005-10-14 21:32 ` Esben Nielsen
2005-10-19 7:52 ` Esben Nielsen
2005-10-19 16:04 ` Petr Vandrovec
2005-10-19 18:07 ` ktimer hiccup in rt11 David Singleton
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=1129142282.11410.7.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=dsingleton@mvista.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=mingo@elte.hu \
--cc=nando@ccrma.stanford.edu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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