mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Liu <richliu@ite.techarea.org>
To: Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: ATAPI CDROM at  DMA mode problem
Date: Wed, 26 Jun 2002 10:08:12 +0800	[thread overview]
Message-ID: <20020626095000.0B09.RICHLIU@ite.techarea.org> (raw)

Hi.
  I have some problem about use DMA mode transfer data .
when I use "hdparm -d1 /dev/hdd" to setting cdrom to DMA mode

my built-in VIA chipset VT82C868B IDE work fine.
but
PROMISE Ultra66(PDC20262) and CMD649 also have problem.
system will hang on. 
and if I use PIO mode to transfer data, the system is fine, no problem.
beside some kernel message will log in file "message"

does anyone can give me a suggestion? 
maybe I want to patch kernel or other?
or linux kernel's IDE CDROM DMA mode have problem, still developing ?


kernel version ,
=======================
# uname -a
Linux mdk82 2.4.18-6mdk #1 Fri Mar 15 02:59:08 CET 2002 i686 unknown
=======================

kernel message about IDE
=======================
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:04.1
    ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:pio, hdd:pio
CMD649: IDE controller on PCI bus 00 dev 40
PCI: Found IRQ 11 for device 00:08.0
PCI: Sharing IRQ 11 with 01:00.0
CMD649: chipset revision 2
CMD649: not 100% native mode: will probe irqs later
    ide2: BM-DMA at 0xa000-0xa007, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xa008-0xa00f, BIOS settings: hdg:pio, hdh:pio
hda: IBM-DTLA-307030, ATA DISK drive
hdf: ASUS DVD-ROM E608, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xb400-0xb407,0xb002 on irq 11
hda: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(33)
hdf: ATAPI 40X DVD-ROM drive, 128kB Cache
=============================
P.S My CDROM is ASUS 8x DVD-ROM


strange message
=============================
hdf: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdf: packet command error: error=0x04
hdf: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdf: request sense failure: error=0x04
hdf: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdf: packet command error: error=0x04
hdf: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdf: request sense failure: error=0x04
hdf: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdf: packet command error: error=0x04
hdf: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdf: request sense failure: error=0x04
hdf: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hdf: task_in_intr: error=0x04
hdf: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hdf: task_in_intr: error=0x04
hdf: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hdf: task_in_intr: error=0x04
hdf: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hdf: task_in_intr: error=0x04
hdf: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdf: packet command error: error=0x04
hdf: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdf: request sense failure: error=0x04
hdf: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdf: packet command error: error=0x04
hdf: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdf: request sense failure: error=0x04
=============================

--
Richard Liu

                 reply	other threads:[~2002-06-26  2:08 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=20020626095000.0B09.RICHLIU@ite.techarea.org \
    --to=richliu@ite.techarea.org \
    --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

all inboxes | Powered by JetHome®