>It fails to detected all the external scsi devices, and communicate with
>devices when there is a gap between lun numbers. If there is a gap, it
>omits devices from the absent lun number to the next 2 power # lun number,
>and I/O error after that.
>For example, if device /dev/scsi/host1/bus0/target1/lun7 is taken out
>from the system, the aic7xxx driver fails to detect disks from
>/dev/scsi/host1/bus0/target1/lun8
>to /dev/scsi/host1/bus0/target1/lun31, in stead jumps to ..../lun32,
>and fails to talk to the device ever since.
>
>Old aic7xxx driver is OK.
You'll need to enable additional SCSI logging to determine what is going
on here. The aic7xxx driver doesn't care about lun numbers really, and
doesn't have any code to "willy-nilly" reject some subset of luns just
because one was not probed. What I really need to see is what error
code was returned by the aic7xxx driver when the attempt to probe the
"not found" lun occurs. You should be able to instrument the non
"hardcoded" section of drivers/scsi/scsi_scan.c:scan_scsis() to get
this information.
-- Justin - 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/
This archive was generated by hypermail 2b29 : Fri Aug 31 2001 - 21:00:15 EST