NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/46623: iscsi failure to enumerate bus



The following reply was made to PR kern/46623; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: martin%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost
Subject: Re: kern/46623: iscsi failure to enumerate bus
Date: Sat, 23 Jun 2012 18:50:05 +0200

 On Sat, Jun 23, 2012 at 01:20:05PM +0000, Martin Husemann wrote:
 > The following reply was made to PR kern/46623; it has been noted by GNATS.
 > 
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: kern/46623: iscsi failure to enumerate bus
 > Date: Sat, 23 Jun 2012 15:17:53 +0200
 > 
 >  On Sat, Jun 23, 2012 at 01:05:03PM +0000, Michael L. Hitch wrote:
 >  >     I think this is because the NetBSD probe will stop scanning when the 
 >  >  probe for an lun doesn't show a device.  So if lun 0 doesn't exist, the 
 >  >  scan stops.  See scsi_probe_bus() in sys/dev/scsipi/scsiconf.c.
 >  
 >  Oh, obvious once you look there ;-)
 >  Is this realy needed?
 >  
 >  I see how it is usefull if the failure to probe the device involves a
 >  timeout of some sorts, but can we tell those cases apart via different
 >  return values from the inquiry?
 
 Isn't lun 0 supposed to always exist ?
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --
 


Home | Main Index | Thread Index | Old Index