public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: David Ford <david+challenge-response@blue-labs.org>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	wiggly@wiggly.org, dnarnold@yahoo.com, matt@mattcaron.net,
	seymour@astro.utoronto.ca
Subject: Re: cdrom: dropping to single frame dma
Date: Tue, 3 Aug 2004 12:02:18 +0200	[thread overview]
Message-ID: <20040803100218.GK23504@suse.de> (raw)
In-Reply-To: <20040803095935.GA1929@ime.usp.br>

On Tue, Aug 03 2004, Rogério Brito wrote:
> On Aug 02 2004, Jens Axboe wrote:
> > On Sun, Jul 25 2004, David Ford wrote:
> > > I got a single "cdrom: dropping to single frame dma" message which 
> > > according to my research is part of the culprit.
> > > 
> > > I'm guessing that Jens' patch for this didn't make it into the kernel.
> > 
> > Try this.
> 
> I was having the same problems that David did.
> 
> In fact, I noticed that after I received the message "dropping to single
> frame dma", everything that the CD drive ripped from that point on was just
> digital silence.
> 
> With the patch sent by Jens, things seem to work well (just tried
> extracting something that *did* generate the "single frame dma" message and
> tried ripping another track and this latter track is, happily, not digital
> silence).
> 
> I'm using an almost plain vanilla 2.6.7 kernel here (with a one-liner patch
> to the USB hub controller).
> 
> Thanks Jens. I hope that this is included in the final 2.6.8.

Thanks for testing, the patch is in current -BK so it will be in 2.6.8.

-- 
Jens Axboe


  reply	other threads:[~2004-08-03 10:02 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 [this message]
2004-08-04  0:36   ` David N. Arnold
2004-08-04  5:31     ` Jens Axboe
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=20040803100218.GK23504@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