All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Dodd <phil.lists@two-towers.net>
To: Jens Axboe <axboe@suse.de>
Cc: Daniele Bernardini <db@sqbc.com>, linux-kernel@vger.kernel.org
Subject: Re: dma ripping
Date: Sun, 16 May 2004 17:26:44 +0200	[thread overview]
Message-ID: <40A78834.1030605@two-towers.net> (raw)
In-Reply-To: <20040515211901.GG24600@suse.de>

Jens Axboe wrote:
8<
> You are not being stupid, I think we have a leak in there some where.
> PIO should work just fine. Slower than DMA of course, but it should work
> perfectly of course.

Hi All,

Just a quick "me too" here - though symptoms don't appear to be 
identical.  Running 2.6.6 on Debian Sid and using nvidia binary modules. 
  My system doesn't hang, but when I get the log message "cdrom: 
dropping to single frame dma" ripping stops working.  It still rips but 
I get silence - it will rip the track OK, as in read through the correct 
track length, but I get silence on the resulting wav file.

Please let me know if I can let you have any information about this problem.

Kind regards,

Phil

  reply	other threads:[~2004-05-16 15:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14 15:29 dma ripping Daniele Bernardini
2004-05-15 10:14 ` Jens Axboe
2004-05-15  8:45   ` Daniele Bernardini
2004-05-15 14:58     ` Jens Axboe
2004-05-15 10:13       ` Daniele Bernardini
2004-05-15 14:03       ` Daniele Bernardini
2004-05-15 21:19         ` Jens Axboe
2004-05-16 15:26           ` Philip Dodd [this message]
2004-05-16 15:39             ` Hugo Mills
2004-05-17 22:06               ` Philip Dodd
2004-05-20  2:31                 ` Philip Dodd
2004-05-20 13:34                 ` Jens Axboe
2004-05-30 17:36                   ` Philip Dodd
2004-05-31  5:19                     ` Tvrtko A. Uršulin
2004-05-17 22:12         ` Bill Davidsen

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=40A78834.1030605@two-towers.net \
    --to=phil.lists@two-towers.net \
    --cc=axboe@suse.de \
    --cc=db@sqbc.com \
    --cc=linux-kernel@vger.kernel.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 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.