From: Douglas Gilbert <dougg@torque.net>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
James.Bottomley@SteelEye.com
Subject: Re: aic94xx driver woes
Date: Sat, 31 Mar 2007 15:05:52 -0400 [thread overview]
Message-ID: <460EB110.8060706@torque.net> (raw)
In-Reply-To: <460EA211.2060501@us.ibm.com>
Darrick J. Wong wrote:
> Douglas Gilbert wrote:
>
>> So that is almost 12 months that I have been reporting
>> this driver as broken. Is it just me or my hardware?
>
> I seem to recall you saying that the LSI Fusion card was plugged into
> the same expander as the 48300? If so, does unplugging the Fusion card
> from the expander make it work?
Darrick,
There is a LSI Fusion card in the adjacent PCI-X
slot but it wasn't connected to anything so it
should not have been interfering.
I have another Fusion card in a second machine
which was off. I'll turn the second machine on
now to show the topology of my SAS domain.
Topology (seen from the second machine's MPT Fusion
phy which is both an initiator and a target):
# smp_discover -mb
Device <500605b0000033ef>, expander (only connected phys shown):
phy 3:S:attached:[500605b00006f260:00 i(SSP+STP+SMP) t(SSP)] 3 Gbps
phy 5:T:attached:[500605b000000af0:02 exp t(SMP)] 3 Gbps
phy 6:T:attached:[50000d10002dc000:00 i(SSP+STP+SMP)] 3 Gbps
phy 9:T:attached:[5000c500005208ee:01 t(SSP)] 3 Gbps
phy 11:T:attached:[5000c50001b0213a:01 t(SSP)] 3 Gbps
# smp_discover -mb -s 0x500605b000000af0
Device <500605b000000af0>, expander (only connected phys shown):
phy 2:S:attached:[500605b0000033ef:05 exp t(SMP)] 3 Gbps
phy 10:T:attached:[5000c50001b02139:00 t(SSP)] 3 Gbps
phy 11:T:attached:[5000c500005208ed:00 t(SSP)] 3 Gbps
James, note the SAS address of the first expander.
So with the second machine off, the expander entry
on 0x500605b0000033ef phy_id 3 is not there. [The
mainline aic94xx driver fails the same way with the
second machine off or on.]
>> aic94xx: Found sequencer Firmware version 1.1 (V17/10c6)
>
> Have you tried the V30 sequencer?
No. But I note that Luben's driver is still using
V17/10c6 successfully (in lk 2.6.21-rc4).
How would I know that the official driver needs firmware,
where to get it and what was the recommended version
with a Kconfig entry like this:
config SCSI_AIC94XX
tristate "Adaptec AIC94xx SAS/SATA support"
depends on PCI
select SCSI_SAS_LIBSAS
select FW_LOADER
help
This driver supports Adaptec's SAS/SATA 3Gb/s 64 bit PCI-X
AIC94xx chip based host adapters.
config AIC94XX_DEBUG
bool "Compile in debug mode"
default y
depends on SCSI_AIC94XX
help
Compiles the aic94xx driver in debug mode. In debug mode,
the driver prints some messages to the console.
??
Is there some useful documentation somewhere else?
If so perhaps I link to it could be placed in the
Kconfig entry.
Doug Gilbert
next prev parent reply other threads:[~2007-03-31 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 16:48 aic94xx driver woes Douglas Gilbert
2007-03-31 17:28 ` James Bottomley
2007-03-31 18:01 ` Darrick J. Wong
2007-03-31 19:05 ` Douglas Gilbert [this message]
2007-03-31 23:17 ` James Bottomley
2007-04-01 20:29 ` Douglas Gilbert
2007-04-02 17:52 ` James Bottomley
2007-04-02 23:36 ` Douglas Gilbert
2007-04-03 0:37 ` 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=460EB110.8060706@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@SteelEye.com \
--cc=djwong@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