Tejun Heo wrote:
quoted text
> Yeap, the SG command is fine.  The drive is being weird tho.  The
> allocation length field says 10 bytes, so it should just have
> transferred 10 bytes without causing HSM violation.
> 
> Can you please apply the attached patch and report what the kernel says
> after triggering the error condition?

Thanks for looking at this, the kernel now says:

<4>ata2.00: HSM violation: eh_analyze_tf: BUSY|DRQ
<3>ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
<3>ata2.00: cmd a0/00:00:00:0a:00/00:00:00:00:00/a0 tag 0 cdb 0x5a data 
10 in
<4>         res 58/00:02:00:0a:00/00:00:00:00:00/a0 Emask 0x2 (HSM 
violation)
<3>ata2.00: status: { DRDY DRQ }
<6>ata2: soft resetting link
<6>ata2.00: configured for UDMA/33
<6>ata2: EH complete

Daniel
-
unsubscribe notice
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/