Re: Updated on UDMA BadCRC errors + subsequent problems (was: Is it safe to ignore UDMA BadCRC errors?)

[Jonathan Kamens]

John Bradford writes:
 > Quote from Jonathan Kamens <jik@xxxxxxxxxxxxxxxxxxxxxx>:
 > > ... hde: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
 > > ... hde: drive_cmd: error=0x04 { DriveStatusError }
 > 
 > The drive doesn't seem to understand the command it was sent.

I'm not sure what this means, but assuming that it's going to happen
again at some point, what do I need to do to my kernel/configuration
now to be able to capture additional debugging information the next
time it happens?

Thanks,

  jik
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/