On Thu, 2005-08-25 at 16:09 +0530, Suparna Bhattacharya wrote: > On Fri, Aug 19, 2005 at 09:22:45AM -0400, James Bottomley wrote: > > On Fri, 2005-08-19 at 15:24 +0530, Suparna Bhattacharya wrote: > > > sda: > > > > Well, this line is identifying the root cause. It says that the > > partition code came up with no partitions for this device. Do any of > > your other devices come up with paritions? (as in could this be a simple > > device node transposition issue?) > > Yes, it looks like that. The ordering now seems to be id 9, 10, ... 14, 0, > 1, 2, instead of the default of id 0, 1, 2 ... Did you expect a change > in probe ordering ? > > When I switch back to the old AIC driver the ordering goes back to > default.
Er, boggle! I know of no change to the new driver that could affect the target scanning order (this is target, not lun, right?). Target scan should be handled sequentially in the mid-layer (scsi_scan.c) in a for loop that runs from 0 to 15 (well shost->max_id). There is a reverse_order flag, could that be set somehow? James - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
