On Thu, May 23, 2002 at 04:27:39PM +0200, Martin Dalecki wrote:
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Since this error can be expected to be quite common.
> Its an installation error. I will just make the corresponding
> error message more intelliglible to the average user:
> hda: checksum error on data transfer occurred!
BTW, I have a particular setup that spits out such errors,
and I somehow thinks the cable is good.
I have IBM DTLA-307030 drive and Seagate Barracuda IV drive (last one purchased
only recently).
IBM drive is connected to far end of 80-wires IDE cable and Barracuda is
connected to the middle of this same wire.
Before I bought IBM drive, everything was ok.
But now I see BadCRC errors on hdb (only on hdb, which is barracuda drive)
usually when both drives are active.
If I disable DMA on IBM drive (or if kernel disables it by itself for some
reason, and it actually does it sometimes), these errors seems to go away.
This is all on 2.4.18, but actually I think this is irrelevant.
If that's a bad cable, why it is only happens when both drives are working
in DMA mode?
Thank you.
Bye,
Oleg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/