Ar Mer, 2006-11-01 am 12:02 -0800, ysgrifennodd Andrew Morton: > Dunno if this is a scsi thing or an Alan thing. But it is certainly a > thing! > > and driver hangs in a non-functional state (neither removed nor active) > > HOWEVER, > > going to /sys/bus/scsi/devices/X:0:0:0/ and echo'ing 1 to delete triggers the > > same BUG; the drive disappears from the system correctly(!) and pata_cmd64x can > > be removed from system without further problems. It actually looks like a refcounting problem - could be in the SCSI code or in the libata code or in the AHCI code. I don't think it's in the driver however as the drivers don't carry custom code in that area > > On a subsequent docking, the drive affected by the above bug appears to be > > confused and kernel complains about not being able to identify the drive, > > however, after a few attempts it manages to reset the drive. > > That I think I understand assuming the first time you booted with the drive plugged in ? Alan - 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
