public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "David N. Arnold" <dnarnold@yahoo.com>
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: Wed, 4 Aug 2004 07:31:34 +0200	[thread overview]
Message-ID: <20040804053134.GA10340@suse.de> (raw)
In-Reply-To: <41102FAB.40701@yahoo.com>

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.

-- 
Jens Axboe


  reply	other threads:[~2004-08-04  5:31 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 [this message]
2004-08-06  1:43       ` David N. Arnold

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=20040804053134.GA10340@suse.de \
    --to=axboe@suse.de \
    --cc=david+challenge-response@blue-labs.org \
    --cc=dnarnold@yahoo.com \
    --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