From: "Darrick J. Wong" <djwong@us.ibm.com>
To: dougg@torque.net, Tarjei Huse <tarjei@scanventure.no>,
linux-scsi@vger.kernel.org, "Wu,
Gilbert" <Gilbert_Wu@adaptec.com>,
"Chim, Ed" <ed_chim@adaptec.com>,
Alexis Bruemmer <alexisb@us.ibm.com>
Subject: Re: Adaptect 9405w: What is the best solution?
Date: Thu, 11 Jan 2007 11:30:53 -0800 [thread overview]
Message-ID: <45A6906D.3040805@us.ibm.com> (raw)
In-Reply-To: <45A6570C.3090308@torque.net>
[cc'ing a few contacts at adaptec]
Douglas Gilbert wrote:
> Tarjei Huse wrote:
>> Hi, I'm working on getting Linux to use my SATA drives on an IBM x306
>> running a HostRaid controller that uses the adaptech 9405w chipset.
<snip>
>> c) In the thread Darrick Wong refers to another branch[1] that contains
>> (according to him) a lot of fixes for this chipset. Is that branch
>> confirmed to work with my chipset?
Yes. I'd also strongly recommend consideration of patches #23 and #26
from here:
http://sweaglesw.net/~djwong/docs/sas_ata-patches/
I create my kernel tree by cloning the linux-2.6 git tree and then
applying scsi-misc-2.6, scsi-rc-fixes-2.6 and aic94xx-sas-2.6 patches
atop that. And then the giant long slew of patches atop *that*.
>> I have also tried to compile the latest rc of the 2.6.20 kernel and
>> loaded up the aic94xx driver + firmware. I then ended up getting the
>> same errors that started the above mentioned thread on this list.
Yes, because you need the changes that are in aic94xx-sas that add SATA
support. Ideally that message would have printed something less
cryptic, such as "SATA device found but not supported in this driver!",
but that's water under the bridge at this point.
> it was too old) showed the same problems (tmf timeouts). Then
The TMF timeout problems (and several other bugs) were fixed in v18 of
the sequencer firmware blob. Alexis, Ed, and Gilbert are currently
working to have the firmware blob posted on Adaptec's web site. I think
the sequencer is up to v28 now?
(Vaporware, I know, but hopefully we can nip this one in the bud soon.)
> Luben Tuikov sent me a version of his driver with a "use_msi"
> related fix in it. My 48300 has been rock solid since. The last
> time I tried "Darrick's" driver (about a week ago) it failed in
> the fashion unto which I have become accustomed.
I'm not certain that I'm completely aware of the failures that you're
seeing with the driver. Can you send me the BIOS firmware level, the
sequencer version (probably v17 since that's the only one that I know of
that's available on the 'net), and a dmesg output?
> I have encouraged people to talk amongst themselves about the
> use_msi patch, but I don't believe that I should be reverse
> engineering that patch. There are other issues. As you may
> understand from the above, I am walking on a bit of a tight rope
> here.
Are you enabling MSI mode? There is a known bug where one needs to kick
one of the CHIMINTEN bits if a certain flag is set, though none of the
IBM boxes require MSI (and at the moment it isn't working anyway...).
>> 2. http://www.jimmy.co.at/weblog/?p=71
Egad.
Anyway, patches are forthcoming.
--D
next prev parent reply other threads:[~2007-01-11 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 11:02 Adaptect 9405w: What is the best solution? Tarjei Huse
2007-01-11 15:26 ` Douglas Gilbert
2007-01-11 19:30 ` Darrick J. Wong [this message]
2007-01-11 19:48 ` Tarjei Huse
2007-01-11 20:08 ` Darrick J. Wong
[not found] ` <45A6C33C.8060900@scanventure.no>
2007-01-12 23:37 ` Darrick J. Wong
2007-01-14 15:30 ` Tarjei Huse
[not found] ` <45AA4A7B.7070607@scanventure.no>
2007-01-15 20:50 ` Darrick J. Wong
2007-01-16 14:12 ` Tarjei Huse
2007-01-16 23:14 ` Alexis Bruemmer
2007-01-17 10:51 ` Tarjei Huse
2007-01-17 16:32 ` Mark Rustad
2007-01-17 16:54 ` James Bottomley
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=45A6906D.3040805@us.ibm.com \
--to=djwong@us.ibm.com \
--cc=Gilbert_Wu@adaptec.com \
--cc=alexisb@us.ibm.com \
--cc=dougg@torque.net \
--cc=ed_chim@adaptec.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tarjei@scanventure.no \
/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).