From: James Bottomley <James.Bottomley@SteelEye.com>
To: linux-scsi <linux-scsi@vger.kernel.org>
Cc: Alexis Bruemmer <alexisb@us.ibm.com>,
Mike Anderson <andmike@us.ibm.com>,
"Tarte, Robert" <Robert_Tarte@adaptec.com>
Subject: aic94xx status
Date: Sat, 08 Jul 2006 11:27:47 -0500 [thread overview]
Message-ID: <1152376067.12020.26.camel@mulgrave.il.steeleye.com> (raw)
The current status is this:
The biggest problem I've been pursuing all week was the hangs and
softlockups on driver insertion. This actually turns out to be all
caused by the generic timer code and have nothing to do with the actual
aic94xx (the pitfalls of working in Linus' git head, I'm afraid).
The only two remaining serious issues I can now find that need to be
fixed before it can go into scsi-misc are:
1) SATA support. We at least need this stubbed out so seeing a SATA
device won't cause nasty things to happen (IBM is working on this).
Ideally, we need to integrate this driver with Brian King's SATA/SAS
code, but no-one who has this board has a sata device and vice versa.
2) Error handling. I seem to have a somewhat flakey connection on my
SAS cage that seems to cause intermittent transport errors. The current
behaviour is for this driver to find the transport problem, clear the
nexus and then complete the command (i.e. fail it). So if this happens
at boot time in the initial INQUIRY (and it does for me about 25% of the
time) it never brings up my root disk, so the box panics. The error
handler needs to be taught to retry the commands for transport failures.
(I can look into doing this unless there are ready volunteers).
3) The wide port formation and deformation issues, which I've described
in a separate email.
Other than this, most of the remaining work is code refactoring, which I
think can be done in-tree, unless anyone else has critical issues to add
to the list.
James
next reply other threads:[~2006-07-08 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 16:27 James Bottomley [this message]
2006-07-10 16:09 ` aic94xx status Mike Anderson
2006-07-10 16:27 ` James Bottomley
2006-07-11 5:07 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2006-07-11 8:32 Robert Tarte
2006-07-20 14:39 ` Brian King
2006-07-20 18:39 ` Luben Tuikov
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=1152376067.12020.26.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=Robert_Tarte@adaptec.com \
--cc=alexisb@us.ibm.com \
--cc=andmike@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