public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: safemode <safemode@speakeasy.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.17-pre2 having dma problems with atapi devices
Date: 01 Dec 2001 00:28:39 -0500	[thread overview]
Message-ID: <1007184520.408.0.camel@psuedomode> (raw)

I'm trying to write to a cd at 8x, which i could do in prior kernels
(2.4.15-prex and before), but now i'm getting cdrecord errors and
sometimes dma timeouts.  Seems that data is being corrupted somewhere
again.  I got this kind of performance when i had it on the promise
controller and when i moved it back to my via controller it worked
perfectly.  

Ide controller:  
 VIA vt82c686a (rev 22) IDE UDMA66 controller

CDR : CREATIVE CD-RW RW8438E, ATAPI CD/DVD-ROM drive 
(set as master and DMA set by kernel)

setting to a lower write speed allows successful writes.  


cdrecord error:
/usr/bin/cdrecord: Input/output error. send opc: scsi sendcmd: no error
CDB:  54 01 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 17.724s timeout 60s
/usr/bin/cdrecord: Resource temporarily unavailable. OPC failed.
/usr/bin/cdrecord: fifo had 64 puts and 0 gets.
/usr/bin/cdrecord: fifo was 0 times empty and 0 times full, min fill was
100%.

The dma errors weren't very special,  same old dma timeout and reset
messages.    The cds are perfectly fine, i use the same one that errored
at 4x and it reads fine after burn.   




                 reply	other threads:[~2001-12-01  5:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1007184520.408.0.camel@psuedomode \
    --to=safemode@speakeasy.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