Re: 2.2.12, 2.2.10 lockups... VFAT? SCSI? Sound?

Mark Hahn (hahn@coffee.psychology.mcmaster.ca)
Tue, 28 Sep 1999 13:37:06 +0000 ( )


>| Sep 27 15:37:44 cb26038-a kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>| Sep 27 15:37:44 cb26038-a kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> A dejanews post said "disable Ultra DMA in BIOS"... which I did. So far
> so good. I had assumed hda was what was giving the file_cluster
> errors... it was not.

disabling udma is a REALLY bad idea if you're talking about udma33
and your drive and controller both support it. why? because udma
is telling you that your cable is too long or broken; disabling udma
means not using CRC's on each transfer, making the corruption invisible.
remember, IDE cables must be 18" or less, and you must have both ends
plugged in (no stub).

the real issue seems to be drives that power up in udma66 by default;
this doesn't work on most hardware, and at least some versions of Linux
aren't smart enough to tune to a supported mode. besides, no current disk is
too fast for udma33.

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/