linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harri Olin <harri.olin@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Rich <rercola@pha.jhu.edu>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Odd behavior of a "SAS-2" backplane with SGPIO commands
Date: Sun, 19 Aug 2012 15:50:00 +0300	[thread overview]
Message-ID: <5030E0F8.5@gmail.com> (raw)
In-Reply-To: <20120819102531.GP19851@reaktio.net>

On 19.8.2012 13:25, Pasi Kärkkäinen wrote:
>> To be brief, the sas2ircu toolset works perfectly fine with IT mode
>> HBAs - just not with passive backplanes AFAICS [e.g. the 846A, versus
>> the 846EL2].
> Ok. So with an expander backplane (846EL*) with SES, sas2ircu is able to control leds?
> "LOCATE" command works? I haven't been able to try those commands with SES backplanes
> because in these systems I've been trying to avoid expanders :)

I think SGPIO control is disabled intentionally on LSI 9211-8i firmware, 
maybe others. When using expander, the expander controls LED's and SGPIO 
control lines from HBA are unused.

The thing is, on 9211-8i and 9240 and probably others, multilane 
connectors are wired backwards so that if you connect a normal 
ipass-ipass cable, backplane slots will appear in backwards order to the 
system. Firmware knows this and slot numbers will appear to be correct 
when checking serial numbers etc from bios or with sas2ircu, but I 
suspect this is related to SGPIO not working.

You can get the SGPIO working (using sas2ircu) with Supermicro-supplied 
SAS2008 firmware from 
ftp://ftp.supermicro.com/driver/SAS/LSI/2008/IT/Firmware/ but as 
Supermicro SAS2008 HBA's (AOC-USAS2-L8i) use correct lane order on 
multilane connector, SGPIO-controlled LOCATE LED will point to wrong 
slot if not used with Supermicro card. Note that Supermicro backplanes 
will not light the LED if no HDD is in slot.

Tested mainly with Supermicro 846A backplane I think.

I think I still have a support request open with LSI but haven't heart 
back for a long time about this issue..

Also I haven't yet tested the new SAS2308 based cards, great if finally 
fixed but I kind of doubt it before I see it :)

Quick summary about Supermicro backplane models:
T  - separate SATA connectors, no SGPIO and no locate LED's
TQ - separate SATA connectors for each slot, separate SGPIO header for 
each 4 slot group
A  - multilane connector for each 4 slots, SGPIO on multilane connectors
E1 - single expander
E2 - dual expander
E16 - single 6GB expander
E26 - dual 6GB expander

-- 
Harri.

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-08-19 12:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04  1:54 Odd behavior of a "SAS-2" backplane with SGPIO commands Rich
2012-08-18 23:52 ` Pasi Kärkkäinen
2012-08-19  0:10   ` Rich
2012-08-19 10:25     ` Pasi Kärkkäinen
2012-08-19 12:50       ` Harri Olin [this message]
2012-08-19 13:13         ` Pasi Kärkkäinen
2012-08-19 13:47           ` Rich
2012-08-19 13:56             ` Pasi Kärkkäinen
2012-08-19 14:01               ` Rich
2012-08-19 14:06                 ` Pasi Kärkkäinen
2012-09-10 13:47             ` Pasi Kärkkäinen
2012-09-10 16:01               ` Emmanuel Florac
2012-09-10 16:04                 ` Pasi Kärkkäinen
2012-09-10 16:07                   ` Rich
2012-09-10 16:13                     ` Pasi Kärkkäinen
2012-09-10 16:14                       ` Rich
2012-09-10 16:25                         ` Pasi Kärkkäinen
2012-10-21 12:46                       ` Pasi Kärkkäinen
2012-11-01 15:55                         ` Rich
2012-11-01 16:04                           ` Pasi Kärkkäinen
2012-12-07 13:46                           ` Pasi Kärkkäinen
     [not found]                             ` <CAOeNLuroRgZUvFWYTx7yr5ERtEpjiOwQgcy4COCLsm7Z9wWaKw@mail.gmail.com>
2012-12-19 19:40                               ` Pasi Kärkkäinen
     [not found]                               ` <CAOeNLuqVPQTsBs1eoizHBcEVbGgLrQOQBxqkV38cGwyKS4UTNA@mail.gmail.com>
2012-12-19 19:41                                 ` Pasi Kärkkäinen
2013-04-23  0:19                                   ` Pasi Kärkkäinen
     [not found]                                     ` <CAOeNLuo+Pti7LfshpOuzDSwWzdtXw0Ouph7ZAoJ9i7CyaUXiAA@mail.gmail.com>
2013-04-23  0:39                                       ` Pasi Kärkkäinen
     [not found]                                         ` <CAOeNLuqnX9r-jrmq0kV1=kU3XOzFEttDQktcD5338BzaBX3KHg@mail.gmail.com>
2013-08-30 21:42                                           ` Rich
2013-09-01 17:13                                           ` Pasi Kärkkäinen
2013-09-02 14:44                                             ` Pasi Kärkkäinen
2013-10-03 19:11                                               ` Pasi Kärkkäinen
2013-10-03 20:07                                                 ` Rich
2013-10-03 20:16                                                   ` Pasi Kärkkäinen
2013-10-04  0:07                                                 ` Douglas Gilbert

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=5030E0F8.5@gmail.com \
    --to=harri.olin@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pasik@iki.fi \
    --cc=rercola@pha.jhu.edu \
    /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).