On Mon, 2007-07-23 at 23:41 +0100, Mark Fortescue wrote: > Hi James, > > Can you point me in the direction of any documentation to aid me in > identifing what debugging I need to work out what is going on? they're all in include/scsi/scsi.h The code is divided into four bytes (from LSB): status, message, host and driver. The status is what the SCSI command actually returned (if anything) the message is what the transport said (least used of the status codes). The host byte signals an error condition with the card and the driver byte with the driver (plus an optional suggestion of what to do about it). > For targets without any connected disk, I get scan responses of: > scsi scan: INQUIRY failed with code 0x40000 > after app 417ms. That's host byte 0x04 which is DID_BAD_TARGET. > For targets with a disk connected, I get scan responses of: > scsi scan: INQUIRY failed with code 0x8000002 > after app 170ms. Thats SCSI status 0x02 (which is CHECK_CONDITION) and driver byte of 0x08, which is DRIVER_SENSE (as in the device returned a sense code). This is really strange, because the INQUIRY command isn't supposed to be allowed to return a sense code for precisely this initial scan reason. This tends to point to a device failure. James - 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
