Date: Sat, 23 Jun 2001 00:10:36 +0100 From: j mckitrick <jcm@FreeBSD-uk.eu.org> To: Matthew Jacob <mjacob@feral.com> Cc: scsi@freebsd.org Subject: Re: how to invalidate scsi connection to driver module Message-ID: <20010623001035.A67153@dogma.freebsd-uk.eu.org> In-Reply-To: <20010622140800.F20923-100000@wonky.feral.com>; from mjacob@feral.com on Fri, Jun 22, 2001 at 02:10:20PM -0700 References: <20010622220719.A64495@dogma.freebsd-uk.eu.org> <20010622140800.F20923-100000@wonky.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
here is what i did so far:
xpt_async(AC_LOST_DEVICE, vpo->path, NULL);
xpt_free_path(vpo->path);
xpt_bus_deregister(cam_sim_path(vpo->sim));
cam_sim_free(vpo->sim, TRUE);
It pretty much works, meaning the module unloads and can be reloaded without
crashing. However, something odd happens. When you first attach, as
expected it says "vpo0... da0..." which is fine. But on each subsequent
reattach, it allocates da0 and da1... then da0, da1, and da2. And so on.
When i detach, it detaches the entire list. Everything still works, but it
should *not* attach /n/ devices for every /nth/ attach.
How do i force only one instance of the drive for each attach?
Jonathon
--
Microsoft complaining about the source license used by
Linux is like the event horizon calling the kettle black.
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?20010623001035.A67153>