driver removal problems with mptsas?

driver removal problems with mptsas?

[Scott O'Connor]

Hello,

I have noticed that if I 'rmmod mptsas', the scsi_eh_<n> kernel
thread is not stopped.  If I 'modprobe mptsas' a new scsi_eh_<n>
is started.  If I put the above in a loop, a new scsi_eh_<n>
is started for each modprobe of mptsas.

I also believe that mptsas is not cleaning up properly
when removed.  I have a 1068 and during probe, sas_phy_alloc()
is called for each of the 8 phys.  During mptsas_remove() I
would expect to see those 8 allocated sas_phy structures
freed by calls to sas_phy_delete()/sas_phy_free().  Or are they
removed elsewhere?

I'm running 2.6.16.18 and using LSISAS1068 card.

-Scott.

Re: driver removal problems with mptsas?

[Alexis Bruemmer]

Hi Scott,

Your right this was a problem, but was addressed with a recent patch
in scsi-misc:
http://www.kernel.org/git/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commitdiff;h=92aab6464be735139f9ea38fd039c3b84c722630

--Alexis


On Thu, 2006-05-25 at 15:17 -0400, Scott O'Connor wrote:
> Hello,
> 
> I have noticed that if I 'rmmod mptsas', the scsi_eh_<n> kernel
> thread is not stopped.  If I 'modprobe mptsas' a new scsi_eh_<n>
> is started.  If I put the above in a loop, a new scsi_eh_<n>
> is started for each modprobe of mptsas.
> 
> I also believe that mptsas is not cleaning up properly
> when removed.  I have a 1068 and during probe, sas_phy_alloc()
> is called for each of the 8 phys.  During mptsas_remove() I
> would expect to see those 8 allocated sas_phy structures
> freed by calls to sas_phy_delete()/sas_phy_free().  Or are they
> removed elsewhere?
> 
> I'm running 2.6.16.18 and using LSISAS1068 card.
> 
> -Scott.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html