From: Jens Axboe <axboe@suse.de>
To: Nigel Rantor <wiggly@wiggly.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cdrom ripping / dropping to dingle frame dma
Date: Tue, 15 Jun 2004 22:38:31 +0200 [thread overview]
Message-ID: <20040615203828.GA12504@suse.de> (raw)
In-Reply-To: <40CF594C.30109@wiggly.org>
On Tue, Jun 15 2004, Nigel Rantor wrote:
>
> Hi all,
>
> Sorry if this is a completely redundant post but I have not been
> subscribed recently and missed the thread on this.
>
> I have had cdparanoia ripping blank sound off of my cdrom, looking in
> the syslog gives the following just before stuff goes weird.
>
> kernel: cdrom: dropping to single frame dma
>
> Whilst trying to find others with the same problem I have seen an
> archived LKML thread where Jens Axboe provided a patch against 2.6.4-rc1
>
> I am currently running 2.6.5 and am wondering if this patch made it in
> or not, and if not, where I can grab it from.
>
> Alternatively, if this patch should be in 2.6.5 then I have a machine
> that still fails with it, if so I'll be happy to post system specs etc
> and try to find a test CD that exhibits the problem for testing.
It did not, and it didn't fix the issue completely. My plan is to add a
counter just checking if we succeeded doing some dma ripping already,
in which case there's no point to falling back to lesser methods. That
should be way more reliable than checking sense and making up our on
rules based on that.
I'll get a patch out tomorrow.
--
Jens Axboe
next prev parent reply other threads:[~2004-06-15 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 20:17 cdrom ripping / dropping to dingle frame dma Nigel Rantor
2004-06-15 20:38 ` Jens Axboe [this message]
2004-06-15 20:47 ` Nigel Rantor
2004-06-15 20:49 ` Jens Axboe
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=20040615203828.GA12504@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.