> us who have via chipset motherboards, suggesting that it is limited
> to that chipset, that chipset is ubiquitous, or via chipset
> motherboard owners are generally the complaining type. no idea which
> applies there, either.
Or there are a lot of them. 90% of scsi bug reports I get are adaptec 29xx
driver. Thats not because the adaptec 29xx is the most sucky driver 8)
Firstly there are numerous reasons for CRC errors. At ATA100 even the track
length and the capacitance of the connectors becomes an issue. It is quite
possibly a driver issue. It could even be that specific combination of drives
and ide controller is right on the edge of the spec limits and just slightly
dipping over. It might be the odd power spike.
Providing the code is working sanely the odd CRC error shouldnt be a
problem and should be causing a command retry. The CRC checking used in ATA
is very robust so unlike scsi parity errors which couldnt be ignored ATA
ones on occassion are probably fine
ATA100 is another testimony to the fact that pigs can be made to fly given
sufficient thrust (to borrow an RFC)
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jan 15 2001 - 21:00:30 EST