Martin Michlmayr wrote: > Is this a bug in the VIA driver? > > Sample errors: > > ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 > ata3.00: (BMDMA stat 0x4) > ata3.00: cmd ca/00:08:08:80:04/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 out > res 53/84:00:0f:80:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) I doubt it's the driver's fault. It's more likely actual wiring problem. In the first two dmesgs, even UDMA/25 doesn't work. Errors stop only after it drops speed down to PIO4. The only thing driver can do to cause this PATA transmission errors I can think of is misprogramming the timing registers but transfer mode programming on vt6421 is as simple as telling the controller the index of the mode, so it's pretty hard to screw up there. The difference between the first two and the last one might be that the last one is just more tolerant about degraded signals. (e.g. some of latest PATA drives can do UDMA/100 on 40c cable w/o any problem). -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
