Date: Fri, 22 Jun 2001 12:38:13 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: j mckitrick <jcm@freebsd-uk.eu.org> Cc: <scsi@freebsd.org> Subject: Re: how to invalidate scsi connection to driver module Message-ID: <20010622123714.R20923-100000@wonky.feral.com> In-Reply-To: <20010622203540.A62806@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> | > | > | On Fri, 22 Jun 2001, j mckitrick wrote: > | > | > > | > Here is the code for a scsi removable media drive. If this is to become a > | > module, the cam/scsi attachment must be removed. I have tried calling > | > cam_sim_free() and xpt_bus_deregister() but when the module is reloaded, the > | > cam system assigns the next higher minor device number, and then crashes > | > when accessed. Any ideas here how to reset cam to a state where it knows > | > nothing about the device? > | > | The xpt_bus_deregister is supposed to do an AC_LOST_DEVICE on all attached > | devices. I don't remember what is supposed to happen to recycle unit > | numbers.... > | > | Take a look at camperiphunit- it really should recycle unit numbers if the old > | ones have truly gone away. > > Hmmm. I'm new to cam/scsi code, so i'm not sure what i need to do here. > Apparently, the 2 functions i call *aren't* enough to make the unit number > go away. > Well, xpt_bus_deregister should invalidate all attached peripherals. But it's not clear to me whether it's your periph driver that's fielding (and swallowing) the AC_LOST_DEVICE, thus leaving things around. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010622123714.R20923-100000>