On Sat, 22 Apr 2000, Piotr Wilkin wrote:
> booting with 2.2.14:
> Apr 22 18:28:51 debian kernel: Partition check:
> Apr 22 18:28:51 debian kernel: hda: hda1
> Apr 22 18:28:51 debian kernel: hdb: hdb1 hdb2
> Apr 22 18:28:51 debian kernel: hdc:hdc: dma_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> Apr 22 18:28:51 debian kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Apr 22 18:28:51 debian kernel: hdc: DMA disabled
You have cable crosstalk or another error that faults DMA CRC retry.
I am working on code that will address the detection of this problem and
respeed the system actively to try can keep UDMA alive. If we wall below
UDMA 0, it will default to disable DMAing........
I will add an override config option to continue the performance down
grade, but beyond UDMA 0 we lose the CRC safety net........
> Apr 22 18:28:51 debian kernel: ide1: reset: success
> Apr 22 18:28:51 debian kernel: [PTBL] [1561/128/63] hdc1 hdc2
> Is it something I have to worry about?
> CONFIG_BLK_DEV_IDEPCI=y
> CONFIG_IDEPCI_SHARE_IRQ=y
> CONFIG_BLK_DEV_IDEDMA_PCI=y
> # CONFIG_BLK_DEV_OFFBOARD is not set
> CONFIG_IDEDMA_PCI_AUTO=y
> CONFIG_BLK_DEV_IDEDMA=y
> CONFIG_IDEDMA_PCI_EXPERIMENTAL=y
> CONFIG_BLK_DEV_PIIX=y
> CONFIG_PIIX_TUNING=y
> CONFIG_IDEDMA_AUTO=y
> CONFIG_BLK_DEV_IDE_MODES=y
Andre Hedrick
The Linux ATA/IDE guy
-
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 : Sun Apr 30 2000 - 21:00:07 EST