public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: Michael Reed <mdr@sgi.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Jeremy Higdon <jeremy@sgi.com>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: Re: More FC Transport Issues
Date: Sat, 24 Dec 2005 20:02:31 -0500	[thread overview]
Message-ID: <43ADEFA7.8070204@emulex.com> (raw)
In-Reply-To: <43AB36BC.8000003@sgi.com>


Michael Reed wrote:
> Hello,
> 
> I installed 2.6.15-rc6-git3 on my ia64 test system and the system hung during
> startup.  There were "recursion depth exceeded" messages.
> 
> The fabric was coming online at the time of hba startup and the targets
> hadn't yet been discovered by the switch.  Consequently, the hbas saw
> loop up but no targets, then the switch generates a state change notification
> and the driver for the hbas discovers the targets in parallel.
> 
> So, there appears to be another recursion issue with the new fc transport.

FYI - you would not see the recursion issue with the lpfc driver. This is a
combination of the qla2xxx driver and the fc transport both using work queue
entries on add/delete.  The lpfc driver uses a background thread rather than
work queue entries.

I'll see if there's something similar to what I did before that could be
applied. Otherwise, we'll have to change either the calling rules or the api.
This is one of those things where the micro view looked simple and
straight-forward, but the macro view is showing the inefficiencies of
black-box design.

-- james s


      parent reply	other threads:[~2005-12-25  1:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 23:29 More FC Transport Issues Michael Reed
2005-12-23 19:47 ` Andrew Vasquez
2005-12-23 19:50 ` Andrew Vasquez
2005-12-23 22:44   ` Michael Reed
2006-01-03 17:30     ` Andrew Vasquez
2005-12-23 19:58 ` Andrew Vasquez
2005-12-25  1:02 ` James Smart [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=43ADEFA7.8070204@emulex.com \
    --to=james.smart@emulex.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=jeremy@sgi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdr@sgi.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