From: Lee Revell <rlrevell@joe-job.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Overruns are killing my recordings.
Date: Fri, 28 Oct 2005 14:43:25 -0400 [thread overview]
Message-ID: <1130525006.4363.44.camel@mindpipe> (raw)
In-Reply-To: <5bdc1c8b0510280752y5b7a665cpfdd512d15f896482@mail.gmail.com>
On Fri, 2005-10-28 at 07:52 -0700, Mark Knecht wrote:
> On 10/27/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > On Thu, 2005-10-27 at 17:00 -0700, Avuton Olrich wrote:
> > > aggh. Sorry for all the noise,
> > >
> > > I have all my drives on a linear raid and I had hdparm set to put my
> > > IDE drives to sleep after a while, I didn't put it together because it
> > > was happening in the middle of recording.
> >
> > Hey, I think it's a testament to the progress that has been made in the
> > past year and a half that people now consider audio dropouts in a "known
> > good" app like ecasound to be a kernel bug. For the longest time the
> > answer was "linux isn't an RTOS, deal with it".
> >
> > Lee
>
> Lee, et. all,
> Could this possibly be part of what is causing my xrun problems? I
> had a huge rash of xruns yesterday. I seem to run into issues after
> longer times of inactivity. I hadn't considered this possibility
> before.
I really doubt it. It's more likely that the xruns are caused by a bug
in the new ktimers system. I am seeing "xruns" here too with -rt1, but
the latency tracer does not report anything over ~120 usecs. Previous
to all the ktimers/HRT stuff going in, I was xrun free for months.
The reason I think it's a ktimers bug is because sometimes JACK reports
an xrun of negative length which I'd NEVER seen before.
I suspect this might all be fixed in the latest -rt patch but I have not
had time to build it.
Lee
next prev parent reply other threads:[~2005-10-28 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 19:12 Overruns are killing my recordings Avuton Olrich
[not found] ` <200510271528.28919.diablod3@gmail.com>
2005-10-27 19:57 ` Avuton Olrich
2005-10-27 21:06 ` Lee Revell
2005-10-28 0:00 ` Avuton Olrich
2005-10-28 3:40 ` Lee Revell
2005-10-28 14:52 ` Mark Knecht
2005-10-28 18:43 ` Lee Revell [this message]
2005-10-28 18:55 ` Mark Knecht
2005-10-28 21:15 ` William Weston
2005-10-28 23:07 ` 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=1130525006.4363.44.camel@mindpipe \
--to=rlrevell@joe-job.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.