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: Thu, 08 Feb 2007 15:32:02 -0800 [thread overview]
Message-ID: <45CBB2F2.5030504@us.ibm.com> (raw)
In-Reply-To: <89FD792A883D4B47AD469FEA2E5D1F9B0F59E8@aime2k302.adaptec.com>
Wu, Gilbert wrote:
> Hi Darrick,
>
> We can duplicate the problem here. The aic94xx with V28 passed IO
> testing overnight if we apply IO directly to /dev/sd?. But it fails
> very quickly when we create a partition and format it as ext3. The V17
> sequencer works fine with both cases. We are looking into it and find
> the root cause ASAP.
This may be fairly self evident by now, but it looks like the sequencer
for the link (LSEQ, I think?) is somehow locking up, which explains why
the scsi_cmnds start timing out and after that all commands (stp, phy
control, etc) time out as well. The other drives continue operating
normally, so I don't think the central sequencer isn't borked up.
Then again, you guys at Adaptec have the sequencer source code works and
I don't, so I can't do much more than make vague guesses. Oh well :(
--D
next prev parent reply other threads:[~2007-02-08 23:32 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 [this message]
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=45CBB2F2.5030504@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