Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Andrew Patterson <andrew.patterson@hp.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: "Moore, Eric" <Eric.Moore@lsil.com>,
	Christoph Hellwig <hch@infradead.org>,
	linux-scsi@vger.kernel.org
Subject: RE: [PATCH] Optionally disable QAS in MPT Fusion spi driver
Date: Thu, 15 Jun 2006 11:28:09 -0600	[thread overview]
Message-ID: <1150392489.12760.153.camel@bluto.andrew> (raw)
In-Reply-To: <1150388463.3143.47.camel@mulgrave.il.steeleye.com>

On Thu, 2006-06-15 at 09:21 -0700, James Bottomley wrote:
> On Thu, 2006-06-15 at 09:31 -0600, Moore, Eric wrote:
> > James said it was okay for having this done in lld, instead
> > of transport.  I'm sure both me and Andrew would be happy 
> > the same if the transport handled this.  
> > Is that possible for you to look into this, or James?
> 
> Before we go the lld route, could someone just assure me this is a
> fusion specific problem.  Andrew, could you attach the same drives to
> another QAS LLD, like aic79xx and verify the problem doesn't recur?

We can only reproduce this problem at a specific site which we no longer
have access to.  At that site, we had problems with both HP OEM'd Maxtor
and Fujitsu drives.  I also don't have any other u320 cards to try this
on other than Fusion.  Eric? Have you been able to reproduce this
problem on Linux at LSI?

> 
> If it's something drive specific, we probably need more of a blacklist
> in the spi transport class.

My guess is this is a drive/fusion interaction problem. 

Andrew



  reply	other threads:[~2006-06-15 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15 15:31 [PATCH] Optionally disable QAS in MPT Fusion spi driver Moore, Eric
2006-06-15 16:21 ` James Bottomley
2006-06-15 17:28   ` Andrew Patterson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-15 18:21 Moore, Eric
2006-06-14 23:16 Moore, Eric
2006-06-02 21:14 Andrew Patterson
2006-06-15 15:12 ` Christoph Hellwig

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=1150392489.12760.153.camel@bluto.andrew \
    --to=andrew.patterson@hp.com \
    --cc=Eric.Moore@lsil.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=hch@infradead.org \
    --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