On Wed, 2004-06-16 at 16:53, Reuben D. Budiardja wrote:
> On Wednesday 16 June 2004 10:14 am, you wrote:
> > > hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > > hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >
> > BadCRC errors are cable faults 99.9% of the time.
> > THe disk sends data with checksum, and when it gets to the controller it
> > no longer matches that checksum. So either your cable is broken,
>
> If it's broken, shouldn't I be having trouble all the time, not just during
> booting ?
well the kernel will slow down the bus speed after such errors, so it
could well be that the initial bus speed is estimated too high, and
after the errors it scales down.
(but note: there comes a speed, eg sub udma, where there no longer is
CRC's with the data but just silent corruption instead)
Attachment:
signature.asc
Description: This is a digitally signed message part