From: "David N. Arnold" <dnarnold@yahoo.com>
To: Jens Axboe <axboe@suse.de>
Cc: David Ford <david+challenge-response@blue-labs.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
wiggly@wiggly.org, matt@mattcaron.net, seymour@astro.utoronto.ca
Subject: Re: cdrom: dropping to single frame dma
Date: Thu, 05 Aug 2004 21:43:38 -0400 [thread overview]
Message-ID: <4112E24A.3060309@yahoo.com> (raw)
In-Reply-To: <20040804053134.GA10340@suse.de>
Jens Axboe wrote:
> On Tue, Aug 03 2004, David N. Arnold wrote:
>
>>I don't know if it's a result of upgrading to 2.6.8-rc2 (from 2.6.5) or
>>from the patch, but it has changed things. I still get
>>
>>hdd: DMA timeout retry
>>hdd: timeout waiting for DMA
>>hdd: status timeout: status=0xd0 { Busy }
>>hdd: status timeout: error=0x00
>>hdd: drive not ready for command
>>hdd: ATAPI reset complete
>>cdrom: dropping to single frame dma
>>
>>but ripping stays at its normal speed (5.0x instead of 0.6x) and the
>>file produced is correct instead of skipping/silence.
>>
>>It doesn't fix the true issue of why I'm getting DMA timeouts, but it
>>does make ripping useable.
>
>
> After the 'dropping to single frame' message, does it work reliably
> after that? And when does the above occur, initially or after some time?
> Details, please.
>
After the single frame message it completes the CD rip without any other
timeouts. I can't tell if single frame mode impairs the speed, because
sound-juicer doesn't rip at full CD speed anyway. The DMA timeout
usually happens in the first few tracks (it's nondeterministic even on
the same CD). The only annoying issue left is that the initial ATAPI
reset freezes the system for a few seconds until it completes.
I don't know if you're interested, but the DMA timeout only happens in
certain usage patterns. If you grab the data one frame at a time with
pauses in between (for example linking an ogg encoder directly to the
data stream) it will trigger the DMA timeout. If you rip the CD at full
drive speed (like ripping to WAV) or batch the read requests together,
it doesn't have any problems. Also, if you slow the max speed of the
drive down with 'hdparm -E' so that the drive is operating at max
(because it's now slower than the encoder) it works fine.
This is all on a JLMS XJ-HD163D DVD drive on the latest firmware.
Thanks,
Dave Arnold
prev parent reply other threads:[~2004-08-06 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 19:30 cdrom: dropping to single frame dma David Ford
2004-08-02 13:24 ` Jens Axboe
2004-08-03 9:59 ` Rogério Brito
2004-08-03 10:02 ` Jens Axboe
2004-08-04 0:36 ` David N. Arnold
2004-08-04 5:31 ` Jens Axboe
2004-08-06 1:43 ` David N. Arnold [this message]
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=4112E24A.3060309@yahoo.com \
--to=dnarnold@yahoo.com \
--cc=axboe@suse.de \
--cc=david+challenge-response@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@mattcaron.net \
--cc=seymour@astro.utoronto.ca \
--cc=wiggly@wiggly.org \
/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