From: Mark Knecht <markknecht@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Overruns are killing my recordings.
Date: Fri, 28 Oct 2005 07:52:27 -0700 [thread overview]
Message-ID: <5bdc1c8b0510280752y5b7a665cpfdd512d15f896482@mail.gmail.com> (raw)
In-Reply-To: <1130470852.4363.26.camel@mindpipe>
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.
Unfortunately I don't know how to fix this for SATA drives? hdparm
doesn't say much and sdparm gives me info I don't understand:
lightning ~ # hdparm /dev/sda
/dev/sda:
IO_support = 0 (default 16-bit)
readonly = 0 (off)
readahead = 256 (on)
geometry = 30401/255/63, sectors = 250059350016, start = 0
lightning ~ #
lightning ~ # sdparm /dev/sda
/dev/sda: ATA ST3250823AS 3.03
Read write error recovery mode page:
AWRE 1 [ sav: 1]
ARRE 1 [ sav: 1]
PER 0 [ sav: 0]
Caching (SBC) mode page:
WCE 1 [ sav: 1]
RCD 0 [ sav: 0]
Control mode page:
SWP 0 [ sav: 0]
lightning ~ #
Drive performance seems good:
lightning ~ # hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 2200 MB in 2.00 seconds = 1100.12 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate
ioctl for device
Timing buffered disk reads: 198 MB in 3.03 seconds = 65.45 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate
ioctl for device
lightning ~ #
I'm still waiting for someone to address the problem where I cannot
build 2.4.16-rc5-rt7 so this is on -rt3.
Thanks,
Mark
next prev parent reply other threads:[~2005-10-28 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 19:12 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 [this message]
2005-10-28 18:43 ` Lee Revell
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=5bdc1c8b0510280752y5b7a665cpfdd512d15f896482@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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®