public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	john stultz <johnstul@us.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.15-rc7-rt1
Date: Thu, 05 Jan 2006 19:46:33 -0500	[thread overview]
Message-ID: <1136508393.12482.3.camel@mindpipe> (raw)
In-Reply-To: <5bdc1c8b0601051643m1d8cf0b5k8abc6697e281ffb7@mail.gmail.com>

On Thu, 2006-01-05 at 16:43 -0800, Mark Knecht wrote:
> On 1/5/06, Mark Knecht <markknecht@gmail.com> wrote:
> > On 1/5/06, Lee Revell <rlrevell@joe-job.com> wrote:
> > > On Thu, 2006-01-05 at 11:33 -0800, Mark Knecht wrote:
> > > > I expect that I am probably still getting a low level of xruns. I
> > > > hope one day we can make that work a bit better.
> > >
> > > Were you ever able to get latency tracing to work on your box?
> > >
> > > Lee
> >
> > Not yet, due to the power failure and being off line. I'll give it a
> > shot this evening.
> >
> > Does anyone with an AMD64 platform have this working?
> >
> > Thanks,
> > Mark
> >
> 
> Hi Lee,
>    OK, I rebuilt the new kernel (2.6.15-rt2) with latency tracing
> enabled. I still get xruns when running Jack and Aqualung. The tracing
> doesn't show anything new although I do have the IRQ off tracing
> turned on and don't see the long timer delays that Iused to see.
> 
>    What the following shows is that I have a 14uS delay before

Yeah 14 usec is nothing, I think we've established that this isn't a
kernel problem.  We should take it to the JACK list.

Lee


  reply	other threads:[~2006-01-06  0:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28 17:26 2.6.15-rc7-rt1 Ingo Molnar
2005-12-28 18:21 ` 2.6.15-rc7-rt1 K.R. Foley
2005-12-29  8:50   ` 2.6.15-rc7-rt1 Ingo Molnar
2005-12-31 17:15 ` 2.6.15-rc7-rt1 Jan Engelhardt
2005-12-31 17:45   ` 2.6.15-rc7-rt1 Steven Rostedt
2005-12-31 18:48     ` 2.6.15-rc7-rt1 Steven Rostedt
2006-01-01 15:19       ` 2.6.15-rc7-rt1 Mark Knecht
2006-01-01 15:31         ` 2.6.15-rc7-rt1 Jan Engelhardt
2006-01-01 15:34         ` 2.6.15-rc7-rt1 Steven Rostedt
2006-01-02 12:41         ` 2.6.15-rc7-rt1 Steven Rostedt
2006-01-05 19:33           ` 2.6.15-rc7-rt1 Mark Knecht
2006-01-05 20:16             ` 2.6.15-rc7-rt1 Lee Revell
2006-01-05 20:58               ` 2.6.15-rc7-rt1 Mark Knecht
2006-01-06  0:43                 ` 2.6.15-rc7-rt1 Mark Knecht
2006-01-06  0:46                   ` Lee Revell [this message]
2006-01-06  1:58                     ` 2.6.15-rc7-rt1 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=1136508393.12482.3.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markknecht@gmail.com \
    --cc=mingo@elte.hu \
    --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