public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott O'Connor <soconnor@sanblaze.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: driver removal problems with mptsas?
Date: Thu, 25 May 2006 15:17:25 -0400	[thread overview]
Message-ID: <447602C5.10007@sanblaze.com> (raw)

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.


             reply	other threads:[~2006-05-25 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 19:17 Scott O'Connor [this message]
2006-05-25 21:04 ` driver removal problems with mptsas? Alexis Bruemmer

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=447602C5.10007@sanblaze.com \
    --to=soconnor@sanblaze.com \
    --cc=linux-scsi@vger.kernel.org \
    /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