linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: "goggin, edward" <egoggin@emc.com>, James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: deadlock while cleaning up after transport timeout for target
Date: Wed, 21 Sep 2005 14:21:11 -0700	[thread overview]
Message-ID: <20050921212111.GA5492@us.ibm.com> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321ACC9@SRMANNING.eng.emc.com>

goggin, edward <egoggin@emc.com> wrote:
> Running with 2.6.13, an EMC Symmetrix target with lpfc and getting
> into a deadlock when the target port times out WHILE starting to scan
> the port via fc_scsi_scan_rport.
> 
> The lpfc_worker thread is stuck waiting for the scsi host's work_q to
> empty in scsi_flush_work.  But this work queue wont empty since the
> inquiry to LUN 0 initiated by the fc_scsi_scan_rport port scan is
> getting retried onto the scsi mid-level request queue, seemingly ad
> infinitum, since lpfc_queuecommand is returning
> SCSI_MLQUEUE_HOST_BUSY whenever a target port infrastructure
> is being dismantled.  This prevents the fc_scsi_scan_rport call from
> finishing which prevents the target's NODEV timeout from being
> completely serviced.  My boot up hangs as a result.
> 

I believe the lpfc driver in 2.6.13 is missing the latest update from
Emulex which is in 2.6.14-rc* (i.e., 8.0.29 vs. 8.0.30). Have you tried a
test run on 2.6.14-rc?

James S can better comment if this fix alone will solve your issue, but it
matches fairly close to the signature I was previously receiving on the
older version of the lpfc driver.

In my testing of port bounce runs, I could not complete a run until I
started using the updated version of the driver.

-andmike
--
Michael Anderson
andmike@us.ibm.com

      reply	other threads:[~2005-09-21 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21 20:47 deadlock while cleaning up after transport timeout for target goggin, edward
2005-09-21 21:21 ` Mike Anderson [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=20050921212111.GA5492@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Smart@Emulex.Com \
    --cc=egoggin@emc.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;
as well as URLs for NNTP newsgroup(s).