From: Alexis Bruemmer <alexisb@us.ibm.com>
To: Scott O'Connor <soconnor@sanblaze.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: driver removal problems with mptsas?
Date: Thu, 25 May 2006 14:04:31 -0700 [thread overview]
Message-ID: <1148591071.11298.0.camel@localhost.localdomain> (raw)
In-Reply-To: <447602C5.10007@sanblaze.com>
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
prev parent reply other threads:[~2006-05-25 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 19:17 driver removal problems with mptsas? Scott O'Connor
2006-05-25 21:04 ` Alexis Bruemmer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1148591071.11298.0.camel@localhost.localdomain \
--to=alexisb@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=soconnor@sanblaze.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox