> 2.4.0-test3-pre2 + ide.2.4.0-t3-2.0629
>
> Jul 1 15:34:07 vortex kernel: hdf: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Jul 1 15:34:07 vortex kernel: hdf: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Jul 1 15:34:07 vortex kernel: hdf: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Jul 1 15:34:07 vortex kernel: hdf: dma_intr: error=0x84 { DriveStatusError BadCRC }
BadCRC is just a report that your drive/controller believe your ide cable
is bogus. nothing more or less. it's not harmful, since Linux retries
such failed transactions. and the solution is just to fix the cabling
(ie, <=18", both ends plugged in, and use the new 80-conductor cable for
udma66 (doesn't hurt on lower modes, either))
it seems like BadCRC reports most often result from people running udma66
with normal 40-conductor cables. this can happen when a driver update
adds udma66 functionality...
regards, mark hahn.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jul 07 2000 - 21:00:11 EST