Darrick J. Wong wrote: > Andy Warner wrote: > > > So you are seeing legitimate REQ_TASK_ABORT values, but need to look > > at the remaining data to see what the chip is trying to tell you. > > For REQ_TASK_ABORT, status_block[1..2] is the transaction context, > > and status_block[3] is the reason (TC_NO_ERROR etc from aic94xx_sas.h) > > Funny, I've been trying to write at least a REQ_TASK_ABORT handler all > week. I'm having a bit of trouble using the transaction context... > mostly because the value I'm getting doesn't correspond to any ascb. > Assuming, of course, that ascb->scb->header.index/ascb->tc_index are > indeed transaction contexts. Check you're actually getting REQ_TASK_ABORT, and not REQ_DEVICE_RESET or SIGNAL_NCQ_ERROR, where the same field is a connection handle, and not a transaction context. -- andyw@xxxxxxxxx Andy Warner Voice: (612) 801-8549 Fax: (208) 575-5634 - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
