hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }

markstoe · 09-08-2001, 01:20 PM

Hi to everyone,..

I am one of many with the same problem...
After installing Redhat 7.1 I get these errors;
-----------------------------
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
-----------------------------
After I Disabled DMA, the message disappears but...... so does DMA.. see the problem?!!
I've noticed more people have the same problem and some of them have the same motherboard as I have: ABIT KT7-RAID with an 800 Mhz Duron processor..
Could it be a "VIA chipset" problem? I've tried multible harddrives but the problem occurs on all (Maxtor 40 GB, Seagate 30,7 GB), I've UDMA100 Cables shorter than 17" in length.., the newest BIOS update etc..
System specs:
------------------------------
ABIT KT7-RAID mobo
800 Mhz Duron processor (Unlocked)
Creative Geforce2 MX graphics card
Creative Soundblaster Live! soundcard
Sony CDRW
Aopen DVD
384 MB RAM
------------------------------

Please HELP!!!

chomicz · 10-23-2002, 10:21 AM

Did anybody ever contact you about this problem as I have a pretty similar spec:
*850 MHz Athlon
*Abit KT7-RAID
*512MB SDRAM
*6GB HDD
*20GB HDD
*52x CDRom

crashmeister · 10-24-2002, 04:25 AM

I did have the same error - after a power failure.
From the info I gathered it is normally a sign of the hdd becoming flaky.
But there is also a bug in older kernels that can trigger this error message.Try upgrading to the newest stable kernel first and see if that works - don't remember up ro which kernel the bug was a problem but 2.4.19 is ok.
In my case the hdd was fine.Seems like some part of my kernel got wacked by the power failure.Everything worked fine after a reinstall.

markstoe · 10-24-2002, 10:07 AM

Nobody ever contacted me about this problem.
It also was never solved.
In the end I got another mobo (MSI) and now everything works fine..
I guess the disk controller on the mobo was malfunctioning..

thanks anyway

mcleodnine · 10-24-2002, 08:56 PM

ehhh... What kernel were you running? There were a few I/O issues with kernels <2.4.16.

crashmeister · 10-25-2002, 04:09 AM

moses · 10-25-2002, 04:38 AM

You might also look into rebuilding your kernel and making sure the
via chipset workarounds are enabled.
Under the
ATA/IDE/MFM/RLL support
section, you'll find a lot of workarounds for various chipsets, look for yours.

dnar · 11-14-2002, 04:21 AM

Are these workarounds still applicable for the 2.4.19 kernel?