Messages in this thread | | | From | Jonathan Kamens <> | Date | Thu, 15 Jan 2004 22:47:44 -0500 | Subject | Re: Updated on UDMA BadCRC errors + subsequent problems (was: Is it safe to ignore UDMA BadCRC errors?) |
| |
The drive which stopped reporting BadCRC errors for weeks when I transferred it from the Promise PDC20262 Ultra66 controller to the SIIG SIi680 Ultra133 controller just reported this:
Jan 15 22:03:13 jik kernel: hde: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 15 22:03:13 jik kernel: hde: drive_cmd: error=0x04 { DriveStatusError } Jan 15 22:03:20 jik kernel: hde: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 15 22:03:20 jik kernel: hde: drive_cmd: error=0x04 { DriveStatusError }
I don't know whether it's relevant that these errors are tagged "drive_cmd" and the BadCRC errors were tagged "dma_intr".
Are the errors above close enough to the BadCRC errors I was getting, i.e.:
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
for me to now start suspecting a problem with the drive, given that two different controllers with two different chipsets are reporting problems with it?
Thanks,
Jonathan Kamens - 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/
| |