public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jpiszcz <jpiszcz@lucidpixels.com>
To: vishwas@india.hp.com
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Question about DMA and cd burning.
Date: Wed, 26 Feb 2003 10:56:34 -0500	[thread overview]
Message-ID: <3E5CE3B2.6010003@lucidpixels.com> (raw)
In-Reply-To: 3E5CA785.8010801@india.hp.com

Yes, hdparm -d1 /dev/hd{b,c} did not work on older kernels for me, but 
2.4.20 appears to work successfully.

However, second question, both of my Plextors support UDMA2, and both 
are on 80 PIN/IDE cables, when I enabled -d1 -X66, the kernel, it 
crashed the kernel.

Feb 26 10:30:55 war kernel: hdc: drive_cmd: status=0x41 { DriveReady Error }
Feb 26 10:30:55 war kernel: hdc: drive_cmd: error=0x04
Feb 26 10:30:59 war kernel: hdc: drive_cmd: status=0x41 { DriveReady Error }
Feb 26 10:30:59 war kernel: hdc: drive_cmd: error=0x04
Feb 26 10:31:02 war kernel: hdc: drive_cmd: status=0x41 { DriveReady Error }
Feb 26 10:31:02 war kernel: hdc: drive_cmd: error=0x04
Feb 26 10:32:22 war kernel: scsi : aborting command due to timeout : pid 
11206, scsi1, channel 0, id 1, lun 0 Read (10) 00 00 00 00 00 00 00 02 00
Feb 26 10:32:22 war kernel: hdc: timeout waiting for DMA
Feb 26 10:32:22 war kernel: ide_dmaproc: chipset supported 
ide_dma_timeout func only: 14
Feb 26 10:32:22 war kernel: hdc: status timeout: status=0xd8 { Busy }
Feb 26 10:32:22 war kernel: hdc: drive not ready for command

After this, X froze and the keyboard lights were blinking, I could not 
change to console or anything to see the kernel messages.

1] Why does the kernel turn DMA off by default?
     config: http://installkernel.tripod.com/config-2.4.20.txt
2] Why does the kernel crash when I try to enable UDMA2 on the cdrw?


vishwas@india.hp.com wrote:

> use: hdparam -d1 /dev/<hdX>
>
> to enable DMA, if it still says it cannot enable DMA.
> try enabling the xfermode,which gives me the same
> performace as DMA enabled.
>
> hdparam -X<num> /dev/<hdX>
>     put num greater than 32..like 33,34 etc  (for multiword DMA)
>     OR  greater that 64....like 65 66 etc.   (for UltraDMA)
>
> -vvp
>
>
>
>
>
>
>
>
>
>
>



  reply	other threads:[~2003-02-26 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  5:21 Question about DMA and cd burning jpiszcz
2003-02-26 11:39 ` vishwas
2003-02-26 15:56   ` jpiszcz [this message]
2003-02-26 17:02     ` Richard B. Johnson
2003-02-26 17:08       ` John W. M. Stevens
2003-02-26 17:42         ` Richard B. Johnson
2003-02-26 19:38       ` Alan Cox
2003-02-26 14:11 ` Alan Cox

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=3E5CE3B2.6010003@lucidpixels.com \
    --to=jpiszcz@lucidpixels.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vishwas@india.hp.com \
    /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