Mark Lord wrote: > Mark Lord wrote: >> >> ###### Test stuck DRQ on VIA-sata (disk): >> >> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen >> ata1.00: cmd ec/00:00:00:00:00/00:00:00:00:00/00 tag 0 cdb 0x0 data 0 >> res 58/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x2 (HSM violation) > > Why do we not always put a '\n' in front of that last line above ?? > Sometimes it seems to have it, and lots of times it does not have a '\n'. > Weird. > >> ###### Test stuck DRQ on VIA-pata (ATAPI DVD/RW): >> ###### Notice how the first "ata4.00: cmd ..." line is *missing*: >> >> res 58/00:02:00:00:02/00:00:00:00:00/40 Emask 0x2 (HSM violation) >> ata4: soft resetting port >> ata4.00: configured for UDMA/66 >> ata4: EH complete > > And in this case, the first line of diagnostics (the "cmd" line) > is always missing. Why? Hmmm... that's very weird. I've never seen such problems. The report messages are printed in ata_eh_report() and both the cmd and res lines are printed by single invocation to printk(). Is the log captured using serial console? I think it could be transmission error or buffer overflow on serial link. -- 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
