From: Scott Long <scott_long@adaptec.com>
To: Luke Rosenthal <lists@luko.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Adaptec 39160 RAID ?!
Date: Tue, 10 Feb 2004 19:33:15 -0700 [thread overview]
Message-ID: <4029946B.7040003@adaptec.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402111215260.21666-100000@gw.luko.org>
Luke Rosenthal wrote:
>>>Yes, but doesn't the card ship with "fake RAID"?
>>
>>No, it's just a plain old Ultra160 Dual Channel SCSI Host Adapter.
>
>
> I just purchased one actually, have hooked it up to a Quantum Atlas 10K2
>
> and can't seem to get them talking in Ultra160 mode. Here's the proc
> output:
>
>
> Adaptec AIC7xxx driver version: 6.2.8
> aic7899: Ultra160 Wide Channel B, SCSI Id=0, 32/253 SCBs
>
> Serial EEPROM:
> 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
> 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0x43bb
> 0xb8f4 0x5d5c 0x2800 0x0010 0xffff 0xffff 0xffff 0xffff
> 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0xf4c7
>
> Channel A Target 0 Negotiation Settings
> User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
> [snip snip Targets 1-14, nothing hooked up]
> Channel A Target 15 Negotiation Settings
> User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
> Goal: 40.000MB/s transfers (20.000MHz, offset 127, 16bit)
> Curr: 40.000MB/s transfers (20.000MHz, offset 127, 16bit)
> Channel A Target 15 Lun 0 Settings
> Commands Queued 438859
> Commands Active 0
> Command Openings 32
> Max Tagged Openings 32
> Device Queue Frozen Count 0
>
>
> The drive has a SCA connector on the back, with a sticker on the
> connector
> stating "Ultra160/LVD/SE". To connect this drive I've used an adapter
> which converts the SCA connection into a regular 68-pin internal one,
> then
> used a terminated cable with Ultra160/LVD/SE marked on both the
> connectors
> (there's 4 of them) AND the terminator. I've tried turning the internal
>
> terminator in the Adaptec BIOS on and off with no change. There's no
> other devices on this bus other than the drive & the host adapter.
>
For whatever reason, the bus is running in single ended mode. I don't
have a guide to the 10k2 handy (and google is turning up empty), but it
might either be jumpered wrong, or you might have a cabling issue. You
might also want to check that the SCA<->68 pin coverter isn't
responsible.
> Is this normal? What do "User", "goal" and "curr" mean?
User is what the BIOS is set to
Goal is the best that we think that we can get
Curr is what we are actually running at
> Why are there so many commands queued?
This is just a cummulative count since the system booted.
Scott
next prev parent reply other threads:[~2004-02-11 2:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S263491AbUBKAtC/20040211004902Z+28@vger.kernel.org>
2004-02-11 1:36 ` Adaptec 39160 RAID ?! Luke Rosenthal
2004-02-11 2:33 ` Scott Long [this message]
2004-02-11 4:18 ` Guy
2004-02-10 18:24 Rechenberg, Andrew
2004-02-10 20:18 ` Jeff Garzik
2004-02-10 20:33 ` Scott Long
2004-02-10 20:43 ` Paul Clements
-- strict thread matches above, loose matches on Subject: below --
2004-02-10 13:13 Thomas Graham
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=4029946B.7040003@adaptec.com \
--to=scott_long@adaptec.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@luko.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).