On Friday 08 February 2008 04:33:29 pm Stefan Richter wrote: > fw-sbp2 is unable to reconnect while performing __scsi_add_device > because there is only a single workqueue thread context available for > both at the moment. This should be fixed eventually. > > An actual failure of __scsi_add_device is easy to handle, but an > incomplete execution of __scsi_add_device with an sdev returned would > remain undetected and leave the SBP-2 target unusable. > > Therefore we use a workaround: If there was a bus reset during > __scsi_add_device (i.e. during the SCSI probe), we remove the new sdev > immediately, log out, and attempt login and SCSI probe again. > > Signed-off-by: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx> Now *this* does the trick. I get the 'READ CAPACITY failed' as before, then 'firewire_sbp2: fw1.0: error status: 0:4', followed by a new login and SCSI probe, both of which are successful this time, disk is available for use and all that good stuff. Signed-off-by: Jarod Wilson <jwilson@xxxxxxxxxx> -- Jarod Wilson jwilson@xxxxxxxxxx - 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
