All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rustad <mrustad@gmail.com>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: "Wu, Gilbert" <Gilbert_Wu@adaptec.com>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	linux-scsi@vger.kernel.org, Alexis Bruemmer <alexisb@us.ibm.com>
Subject: Re: [PATCH] scsi: Update Aic94xx SAS/SATA Linux open source devicedriver for new sequence firmware.
Date: Wed, 7 Feb 2007 16:57:19 -0600	[thread overview]
Message-ID: <E933AE1E-B184-4421-B9A4-A2B0851BBC7F@gmail.com> (raw)
In-Reply-To: <45C997C4.1010705@us.ibm.com>

On Feb 7, 2007, at 3:11 AM, Darrick J. Wong wrote:

> Wu, Gilbert wrote:
>> Hi James,
>>
>>   We are investigating this issue here. We will update the status  
>> when
>> we can duplicate the problem here and root cause.
>
> FWIW,
>
> v17 looks good for both SAS/SATA load testing.  The 24-disk x260 seems
> to have crapped out after about 800 rounds of load/unload due to the
> phys reporting devices, then no devices about 10s later, and then  
> having
> the module unloaded before the dead SAS commands finished returning.
> Not sure what that's about, though I might also have borked the  
> x260 :(
>
> Though who really is going to reboot the machine 800 times in rapid- 
> fire
> succession???
>
> (I'm not trying to slam the v28 sequencer, I'm merely providing a
> baseline for comparison between the two.  It may very well be the case
> that all the bugs we used to observe with v17 were merely a result  
> of us
> poking the sequencer the wrong way....)

My understanding is that the new sequencer has moved some registers  
and so each version of the sequencer would have to be run with a  
driver coded for that particular version of the sequencer. If you are  
trying to use the same driver with both versions of the sequencer,  
bad things will happen unless you have a driver that can recognize  
both versions and handle each appropriately. I don't think that the  
aic94xx driver as it exists can do that.

Please excuse me if you were already aware of this, but if you  
weren't I wanted to try to short-circuit some of your head-banging.

-- 
Mark Rustad, MRustad@gmail.com



      parent reply	other threads:[~2007-02-07 22:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 23:31 [PATCH] scsi: Update Aic94xx SAS/SATA Linux open source device driver for new sequence firmware Wu, Gilbert
2007-01-31  9:56 ` Christoph Hellwig
2007-01-31 16:56   ` James Bottomley
2007-01-31 19:32     ` Luben Tuikov
2007-02-03 22:28 ` James Bottomley
2007-02-06 19:02   ` [PATCH] scsi: Update Aic94xx SAS/SATA Linux open source devicedriver " Wu, Gilbert
2007-02-07  9:11     ` Darrick J. Wong
2007-02-07 21:54       ` Wu, Gilbert
2007-02-08 23:32         ` Darrick J. Wong
2007-02-09  2:24           ` Wu, Gilbert
2007-02-07 22:57       ` Mark Rustad [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=E933AE1E-B184-4421-B9A4-A2B0851BBC7F@gmail.com \
    --to=mrustad@gmail.com \
    --cc=Gilbert_Wu@adaptec.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=alexisb@us.ibm.com \
    --cc=djwong@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.