dma_intr: error=0x84 DriveReady SeekComplete Error

From: Eric (erick_at_cook.rm-this-word.met.edu)
Date: 04/26/03


Date: Sat, 26 Apr 2003 09:26:55 -0400

During boot and during disk reads (like doing "cd /disk;find .") I get
error messages referring to a DMA issue. I've searched groups, but all
posts so far seem to say that these messages are due either to an
unsupported controller or dying disks. The disks are a couple months
old. Could it be the cables, I wonder? They are the flat-ribbon type
and I am pretty sure at *least* one is ATA100 capable. (It came with
a Tyan 2466 MB.) Data seems to transfer fine on and off the disk (so
far).

The disks: Maxtor 6Y200P0, one on each controller, in a SuperMicro X5DA8.
The drives are each consumed by one partition, hda1 & hdc1, which are
smushed into a Raid0 device. (The hdc drive (jumpered as master) shares
its channel with a DVD-ROM (hdd, jumpered as slave).)

# grep dma /var/log/messages
Apr 26 08:21:35 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:21:35 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:21:35 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:21:35 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:40 bering kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:40 bering kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:40 bering kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:40 bering kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:40 bering kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:40 bering kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:40 bering kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:40 bering kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:45 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:45 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:45 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:45 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:46 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:46 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:46 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:46 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:51 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:51 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:51 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:51 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:52 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:52 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 08:50:52 bering kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 08:50:52 bering kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 09:02:22 bering kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 09:02:22 bering kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 09:02:22 bering kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 09:02:22 bering kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 09:02:22 bering kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 09:02:22 bering kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Apr 26 09:02:22 bering kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 26 09:02:22 bering kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
#
(Sorry about the long lines.)

# dmesg|grep -i ide
Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz
system bus speed for PIO modes; override with idebus=xx PIIX4: IDE
controller on PCI bus 00 dev f9
    ide0: BM-DMA at 0x24a0-0x24a7, BIOS settings: hda:DMA, hdb:pio ide1:
    BM-DMA at 0x24a8-0x24af, BIOS settings: hdc:DMA, hdd:DMA
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
[snip]
ide1: reset: success
ide1: reset: success
ide0: reset: success
#

TIA,

-Erik



Relevant Pages

  • Re: DMA settings
    ... "Dick Snow" wrote in message ... > I was having some problems recently writing to DVD+RW disks for my ... > I was able to make DVD-R disks OK and the CD-RW drive was functioning OK ... > DMA if Available, but the current transfer mode is always showing PIO ...
    (microsoft.public.windowsxp.setup_deployment)
  • bad blocks... random death
    ... this continues discussions about bad disk blocks not really bad and redhat ... we're now a few on this list experiencing various symptoms (dma errors, ... blocks on disks, system freeze or death) that look like hardware problems. ... we've been advised to change dma disks settings. ...
    (RedHat)
  • Re: dma problems with Serverworks CSB5 chipset
    ... Just want to report that after changing the disks to two Maxtor 6Y160P0 ... > same DMA timeout error and often it locks up completely. ... > If i disable DMA with hdparm the system works fine. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: HighPoint 374
    ... >> drivers that come with the kernel. ... > I have tried these versions in the past as well without success. ... The disks are four Seagate ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Extending Exch 5.5 hard disk on RAID 5
    ... Suppose, i successfully performed the offline backup, tested the restore ... with success and ready to remove the existing 3x18gb disks. ... and pull the disks out just like that. ...
    (microsoft.public.exchange.admin)