From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
"Tarte, Robert" <Robert_Tarte@adaptec.com>
Subject: Re: [RFC] aic94xx: attaching to the sas transport class
Date: Thu, 2 Mar 2006 15:13:23 -0800 [thread overview]
Message-ID: <20060302231323.GA12869@us.ibm.com> (raw)
In-Reply-To: <1141339085.3238.80.camel@mulgrave.il.steeleye.com>
James Bottomley <James.Bottomley@SteelEye.com> wrote:
> This fairly minimal patch correctly attaches the aic94xx driver to the
> SAS transport class (The driver is available from
>
> www.kernel.org/git/jgarzik/sas-2.6
>
> ). Unfortunately, the driver itself still has the following critical
> issues
>
> 1. Discovery order is non-deterministic (it starts one thread per port,
> so the threads race for discovery)
>
The issue also results in the device discovery not completing by the time
the module load completes resulting in the initrd not finding the boot
disk
http://bugzilla.kernel.org/show_bug.cgi?id=6045
I agree that we need a solution for this. Should the solution be in the
LLDDs.I thought previous comments was that we wanted this fixed outside
the kernel in user space. Though I have not seen any enabled support in
initrds or support in the initrd bins.
This appears to not only be an issue with aic94xx as it appears this could
happen with some of the fc transport LLDDs.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2006-03-02 23:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 22:38 [RFC] aic94xx: attaching to the sas transport class James Bottomley
2006-03-02 23:13 ` Mike Anderson [this message]
2006-03-03 2:16 ` Mark Rustad
2006-03-03 4:04 ` Randy.Dunlap
2006-03-03 16:51 ` Mark Rustad
2006-03-03 15:51 ` Stefan Richter
2006-03-03 18:24 ` Luben Tuikov
2006-03-03 4:34 ` James Bottomley
2006-03-04 1:47 ` Alexis Bruemmer
2006-03-03 10:26 ` Luben Tuikov
2006-03-03 16:12 ` Stefan Richter
2006-03-03 18:26 ` Luben Tuikov
2006-03-03 10:14 ` Luben Tuikov
2006-03-03 15:23 ` James Bottomley
2006-03-03 15:58 ` Stefan Richter
2006-03-03 16:26 ` James Bottomley
2006-03-03 17:03 ` Mike Anderson
2006-03-03 17:28 ` Jeff Garzik
2006-03-06 18:30 ` Douglas Gilbert
2006-03-03 18:20 ` Luben Tuikov
2006-03-06 8:26 ` Mike Anderson
2006-03-06 15:13 ` James Bottomley
2006-03-06 16:37 ` Jeff Garzik
2006-03-18 1:45 ` [PATCH] " Alexis Bruemmer
2006-03-18 2:05 ` Alexis Bruemmer
2006-03-18 15:24 ` James Bottomley
2006-03-20 5:53 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2006-03-03 16:39 [RFC] " Robert Tarte
2006-03-04 3:01 Tarte, Robert
2006-03-04 4:09 ` James Bottomley
2006-03-04 8:50 ` Luben Tuikov
2006-03-06 19:35 ` Mike Anderson
2006-03-06 19:50 ` James Bottomley
2006-03-07 0:44 ` Alexis Bruemmer
2006-03-08 15:15 ` James Bottomley
2006-03-09 17:06 ` Alexis Bruemmer
2006-03-09 18:05 ` Mike Anderson
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=20060302231323.GA12869@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Robert_Tarte@adaptec.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;
as well as URLs for NNTP newsgroup(s).