The USB code should recover from that , if it doesnt report it to the USB
folks.
> I was not sure if the VIA82CXXX option should be set with the via kt133
> chipset , but setting it results in hundreds of
> hda: dma_intr:status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr:error=0x84 { DriveStatusError BadCRC }
> mesages along with the uhci: errors mentioned above.
> Again , the directory was copied correctly.
That indicates cable problems. The CRC will avoid bad transfers as it will
do retries
Alan
-
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/