public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Kristian <kristian.peters@korseby.net>
Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: [CFT] Bus mastering support for IDE CDROM audio
Date: 27 Jan 2002 14:54:21 -0500	[thread overview]
Message-ID: <1012161271.22707.50.camel@psuedomode> (raw)
In-Reply-To: <20020127111917.3c019701.kristian.peters@korseby.net>
In-Reply-To: <3C5119E0.6E5C45B6@zip.com.au> <000701c1a5d5$812ef580$6caaa8c0@kevin> <3C53711B.F8D89811@zip.com.au> <3C53A116.81432588@zip.com.au> <20020127101131.0f71e978.kristian.peters@korseby.net>  <20020127111917.3c019701.kristian.peters@korseby.net>

You might want to try sending your cdroms into sleep when dma mode wont
work anymore.  That usually fixes things for me.    hdparm -Y  ....the
kernel should wake them up immediately and things should work again.  


On Sun, 2002-01-27 at 05:19, Kristian wrote:
> Hello again.
> 
> Ok. Sorry. My fault. The second patch produces the same throughput... I didn't realized that the kernel disabled DMA during rebooting. My drives only went to DMA again after a cold boot. Don't know what's going on here. But after a normal reboot, my drives are in PIO only and don't support DMA.
> 
> cdparanoia on /dev/scd0 now gives the same result as with the first patch.
> real    1m8.055s
> user    0m6.740s
> sys     0m2.850s
> 
> *Kristian
> 
>   :... [snd.science] ...:
>  ::
>  :: http://www.korseby.net
>  :: http://gsmp.sf.net
>   :.........................:: ~/$ kristian@korseby.net :
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2002-01-27 19:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  8:40 [CFT] Bus mastering support for IDE CDROM audio Andrew Morton
2002-01-25 19:21 ` Kevin P. Fleming
2002-01-27  2:13   ` Dan Chen
2002-01-27  3:16   ` Andrew Morton
2002-01-27  6:41     ` Andrew Morton
2002-01-27  9:11       ` Kristian
2002-01-27 10:19         ` Kristian
2002-01-27 19:54           ` Ed Sweetman [this message]
2002-01-28  8:29             ` Andrew Morton
2002-01-28  9:51               ` benh
2002-01-28  9:51                 ` Andrew Morton
2002-01-28 15:50                   ` Ed Sweetman
2002-01-28 17:13                     ` Kristian
2002-01-28 13:51               ` Kristian
2002-01-28 19:21       ` Kevin P. Fleming
2002-01-26  8:43 ` Dan Chen
2002-01-26 12:03 ` Kristian
2002-01-27 21:21 ` Robert Love
2002-01-27 21:25   ` Jens Axboe
2002-01-27 21:36     ` Andrew Morton
2002-01-27 21:40     ` Robert Love

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=1012161271.22707.50.camel@psuedomode \
    --to=ed.sweetman@wmich.edu \
    --cc=akpm@zip.com.au \
    --cc=kristian.peters@korseby.net \
    --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