public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: Bernd Schubert <bs_lists@aakef.fastmail.fm>
Cc: "Desai, Kashyap" <Kashyap.Desai@lsi.com>,
	Michael Reed <mdr@sgi.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	"Prakash, Sathya" <Sathya.Prakash@lsi.com>,
	"Moore, Eric" <Eric.Moore@lsi.com>,
	Jeremy Higdon <jeremy@sgi.com>, Robin Holt <holt@sgi.com>
Subject: Re: [PATCH 1/1] fusion: hold off error recovery while alternate ioc is initializing
Date: Thu, 11 Feb 2010 13:01:24 -0500	[thread overview]
Message-ID: <1265911284.13197.6.camel@mulgrave.site> (raw)
In-Reply-To: <201002111853.12306.bs_lists@aakef.fastmail.fm>

On Thu, 2010-02-11 at 18:53 +0100, Bernd Schubert wrote:
> Shouldn't we create a similar patch for scsi and sas as well? This issue might 
> explain why any hard-reset (for scsi systems of my former employer) always 
> caused a complete failure of both ports.

It can't really be done generically.  Firstly, the attachments look like
two separate hosts, the mid layer won't even know if they're related,
and secondly, even if we work out they are different functions of the
same PCI device, depending on how the device is implemented, there may
not be this problematic interdependency ... in fact it's more the
exception than the norm.

James



  reply	other threads:[~2010-02-11 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 20:32 [PATCH 1/1] fusion: hold off error recovery while alternate ioc is initializing Michael Reed
2010-02-11  9:27 ` Desai, Kashyap
2010-02-11 17:53   ` Bernd Schubert
2010-02-11 18:01     ` James Bottomley [this message]
2010-02-11 18:11       ` Bernd Schubert
  -- strict thread matches above, loose matches on Subject: below --
2009-12-16 21:20 Michael Reed

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=1265911284.13197.6.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=Eric.Moore@lsi.com \
    --cc=Kashyap.Desai@lsi.com \
    --cc=Sathya.Prakash@lsi.com \
    --cc=bs_lists@aakef.fastmail.fm \
    --cc=holt@sgi.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