From: Jens Axboe <axboe@suse.de>
To: Daniele Bernardini <db@sqbc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dma ripping
Date: Sat, 15 May 2004 23:19:01 +0200 [thread overview]
Message-ID: <20040515211901.GG24600@suse.de> (raw)
In-Reply-To: <1084629809.4612.51.camel@linux.site>
On Sat, May 15 2004, Daniele Bernardini wrote:
> On Sat, 2004-05-15 at 16:58, Jens Axboe wrote:
> > On Sat, May 15 2004, Daniele Bernardini wrote:
> > >
> > > On Sat, 2004-05-15 at 12:14, Jens Axboe wrote:
> > > > On Fri, May 14 2004, Daniele Bernardini wrote:
> > > > > Hi Folks,
> > > > >
> > > > > I am trying to get cd ripping to work on a freshly installed SuSE 9.1 on
> > > > > IBM thinkpad R50 with dvdram drive.
> > > > >
> > > > > It works for a while and then hangs. At this point nothing short of a
> > > > > reboot works. Ripping stop working when the message
> > > > > cdrom: dropping to single frame dma
> > > > > comes up. The system feels slow for a couple of seconds and then is back
> > > > > to normal, but no ripping until next reboot
> > > > >
> > > > > I am running the 2.6.4 compiled by SuSE.
> > > >
> > > > Can you retest with this small debug patch applied.
> > > >
> > > > --- drivers/cdrom/cdrom.c~ 2004-05-15 12:12:24.770228291 +0200
> > > > +++ drivers/cdrom/cdrom.c 2004-05-15 12:13:25.101720866 +0200
> > > > @@ -1987,6 +1987,7 @@
> > > > struct request_sense *s = rq->sense;
> > > > ret = -EIO;
> > > > cdi->last_sense = s->sense_key;
> > > > + printk("rip failed, sense %x/%x/%x\n", s->sense_key, s->asc, s->ascq);
> > > > }
> > > >
> > > > if (blk_rq_unmap_user(rq, ubuf, bio, len))
> > >
> > > I did it and started ripping a cd it froze after 9 tracks, though did
> > > not see your message. I was looking at /var/log/messages (see below).
> > > BTW the system got instable and then froze had to power down. It
> > > happened before always after the ripping problem.
> > >
> > > Should I aswitch on debug for the cdrom?
> >
> > Just an idea - can you log vmstat 5 info while doing this burn? Maybe
> > there's still a little leak in there, so watch the ram usage
> > (used/free/swap/cache).
> >
> > Does your drive have dma enabled?
>
> dma was off. I turned it on and now everything is fine I am through the
> third cd without a glitch...
>
> Thanks and sorry for being so stupid :)
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.
I'll check up on this...
--
Jens Axboe
next prev parent reply other threads:[~2004-05-15 21:19 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 [this message]
2004-05-16 15:26 ` Philip Dodd
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=20040515211901.GG24600@suse.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox