If you want to unload your hba driver, you should make
sure your hba device has no child in the device tree via
"prtconf -D"

And if there are some sd instance under your hba, you
can try "rem_drv sd" to unload the sd driver firstly, and
then unload your hba driver.  But before you unload sd
driver, please make sure your boot system is not a SCSI
disk, that means it is not drived by sd driver.

Thanks,
Ada

Steve Chang wrote:
> Hello,
> Here is another question about driver unload.
> I've tried to unload the driver by "rem_drv mydriver"
> but it always reports "Device Busy" and if do it one more
> time, it said driver is removed but you need to reboot
> the system to take effect. From debugging trace, I didn't
> see "detach" routine is called?
>
> At this moment, there is no I/O activity but HBA firmware
> naturally will keep interrupting HBA for service even it is
> a null interrupt. In this case, how to handle that so my driver
> can stop the interrupt first, then remove system resources
> when users want to remove the driver.
>
>
> Thanks
> Steve
>   
>
> _______________________________________________
> driver-discuss mailing list
> driver-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>   
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to