From: "Darrick J. Wong" <djwong@us.ibm.com>
To: "Wu, Gilbert" <Gilbert_Wu@adaptec.com>
Cc: 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, 07 Feb 2007 01:11:32 -0800 [thread overview]
Message-ID: <45C997C4.1010705@us.ibm.com> (raw)
In-Reply-To: <89FD792A883D4B47AD469FEA2E5D1F9B0F59E7@aime2k302.adaptec.com>
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....)
--D
next prev parent reply other threads:[~2007-02-07 9:11 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 [this message]
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
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=45C997C4.1010705@us.ibm.com \
--to=djwong@us.ibm.com \
--cc=Gilbert_Wu@adaptec.com \
--cc=James.Bottomley@SteelEye.com \
--cc=alexisb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox