On Thu, Oct 03, 2013 at 04:07:31PM -0400, Rich wrote: > I, and a few others, have scripted the hell out of sas2ircu and a few > other things on various platforms. > Been there, done that :) I was mostly wondering if there are other tools so I could evaluate if it makes sense to continue wrapping sas2ircu with custom scripts, or if there are better tools out there.. > I haven't had time to clean up mine and post it publicly yet (it's all > in VCS, I use it a lot, on Windows + Linux + Solaris...), but > https://github.com/swacquie/DiskMap is an example on Solaris. > > I may take some time this weekend and clean up the bleeding edges > remaining and make my repo public for people to use... > That'd be nice! Looking forward to it.. -- Pasi > - Rich > > On Thu, Oct 3, 2013 at 3:11 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote: > > On Mon, Sep 02, 2013 at 05:44:35PM +0300, Pasi Kärkkäinen wrote: > >> On Sun, Sep 01, 2013 at 08:13:02PM +0300, Pasi Kärkkäinen wrote: > >> > On Fri, Aug 30, 2013 at 05:38:04PM -0400, Rich wrote: > >> > > Apparently, only about 4 months. > >> > > P17 firmware is out. > >> > > Tested on a card which was demonstrating the incorrect behavior before, of > >> > > model 9201-16i. > >> > > It does appear to contain the fixes for this problem. > >> > > >> > This is great news, finally! > >> > Thanks for testing and reporting! > >> > > >> > >> Hmm, I checked the P17 firmware changelog PDFs for LSI 9211-8i, 9207-8i and 9201-16i, > >> and I can't see anything about this issue being fixed.. > >> > >> But if you say it's now fixed, then I guess it means LSI doesn't list every change in the changelog.. > >> > > > > I just had some time today to test the new P17 IT firmware with LSI 9211-8i SAS HBAs. > > > > It seems also the "LOCATE" function of LSI sas2ircu tool now actually works and makes > > the red/failure leds blink on the Supermicro passive (direct-attach) backplane! Finally.. > > > > Btw do you guys have any scripts/tools to control the LEDs on these passive backplanes? > > smp_read_gpio/smp_write_gpio isn't the most userfriendly interface ;) Should I try ledmon/ledctl? > > > > I can probably hack something myself too.. but there are many other tasks on the todo-list before this :) > > > > Thanks, > > > > -- Pasi > > > >> > >> > > >> > > - Rich > >> > > > >> > > On Mon, Apr 22, 2013 at 8:39 PM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote: > >> > > > >> > > On Mon, Apr 22, 2013 at 08:28:58PM -0400, Rich wrote: > >> > > > I'm told that the fix won't actually be in until P17, because it > >> > > involved > >> > > > touching a large number of codepaths, but that it will be in P17. > >> > > > > >> > > > >> > > That's unfortunate.. so another 5-6 months. > >> > > > >> > > Thanks for the info! > >> > > > >> > > -- Pasi > >> > > > >> > > > - Rich > >> > > > > >> > > > On Mon, Apr 22, 2013 at 8:19 PM, Pasi KÃ*rkkÃ*inen > >> > > <[1][2]pasik@xxxxxx> > >> > > > wrote: > >> > > > > >> > > > On Wed, Dec 19, 2012 at 09:41:42PM +0200, Pasi KÃ*rkkÃ*inen > >> > > wrote: > >> > > > > On Wed, Dec 19, 2012 at 02:35:02PM -0500, Rich wrote: > >> > > > > >   Nope, I'm wrong. > >> > > > > > >> > > > > :( > >> > > > > > >> > > > > >   I flashed P15 on a machine, and the same behavior > >> > > persisted, > >> > > > right up to > >> > > > > >   and including the "groups of 3 devices light up when I > >> > > do my > >> > > > own > >> > > > > >   smp_write_gpio". > >> > > > > >   Whereas if I flash the experimental blob I was handed by > >> > > > support to try > >> > > > > >   and confirm they had resolved the issue, it does the > >> > > correct > >> > > > thing. > >> > > > > >   I wonder why this change didn't make it into P15. > >> > > > > > >> > > > > Hmm.. if you have open contact channel with LSI support please > >> > > ask > >> > > > them.. > >> > > > > it'd be nice to get the fix for wider audience.. > >> > > > > > >> > > > > >> > > > It seems LSI P16 firmware has been released.. in the FW changelog > >> > > I can > >> > > > see at least this: > >> > > > > >> > > > "Disable SGPIO Group ID support in Channel NVDATA XML's. This > >> > > allows the > >> > > > use of manufacturing page 7 or default slot mapping setting for > >> > > direct > >> > > > connected drive slots." > >> > > > > >> > > > -- Pasi > >> > > > > >> > > > > > >> > > > > >   - Rich > >> > > > > > > >> > > > > >   On Wed, Dec 19, 2012 at 2:00 PM, Rich > >> > > > <[1][2][3]rercola@xxxxxxxxxxx> wrote: > >> > > > > > > >> > > > > >    From the LSI P15 F/W release notes: > >> > > > > >    SCGCQ00342805 (DFCT) Ã* - SlotStatus updates to SES > >> > > managed > >> > > > Enclosure may > >> > > > > >    update incorrect slots > >> > > > > >    "Modified FW to use SES diag page 0Ah mapping only if > >> > > SMP > >> > > > Discover > >> > > > > >    DeviceSlotNum is used for Encl PhyÃ* Slot > >> > > enumeration." > >> > > > > >    SCGCQ00345867 (DFCT) Ã* - Channel NVDATA internal Phy > >> > > > reverse setting for > >> > > > > >    9207-4i4e 9207-8i 9217-4i4eÃ* 9217-8i and 9201-16i > >> > > > > >    "ISSUE DESC:Ã* Internal PHY orders are reversed for > >> > > the > >> > > > channel boards > >> > > > > >    above." > >> > > > > >    So I would submit this is likely fixed by this FW > >> > > rev. > >> > > > > >    - Rich > >> > > > > > > >> > > > > >    On Fri, Dec 7, 2012 at 8:46 AM, Pasi > >> > > KÃ*â*¬rkkÃ*â*¬inen > >> > > > <[2][3][4]pasik@xxxxxx> > >> > > > > >    wrote: > >> > > > > > > >> > > > > >     On Thu, Nov 01, 2012 at 11:55:25AM -0400, Rich > >> > > wrote: > >> > > > > >     > On Sun, Oct 21, 2012 at 8:46 AM, Pasi > >> > > > KÃ*â*¬rkkÃ*â*¬inen <[3][4][5]pasik@xxxxxx> > >> > > > > >     wrote: > >> > > > > >     > > On Mon, Sep 10, 2012 at 07:13:15PM +0300, Pasi > >> > > > KÃ*â*¬rkkÃ*â*¬inen wrote: > >> > > > > >     > >> On Mon, Sep 10, 2012 at 12:07:45PM -0400, > >> > > Rich > >> > > > wrote: > >> > > > > >     > >> > On Mon, Sep 10, 2012 at 12:04 PM, Pasi > >> > > > KÃ*â*¬rkkÃ*â*¬inen > >> > > > > >     <[4][5][6]pasik@xxxxxx> wrote: > >> > > > > >     > >> > > On Mon, Sep 10, 2012 at 06:01:42PM +0200, > >> > > > Emmanuel Florac > >> > > > > >     wrote: > >> > > > > >     > >> > >> Le Mon, 10 Sep 2012 16:47:11 +0300 > >> > > > > >     > >> > >> Pasi KÃ*â*¬rkkÃ*â*¬inen > >> > > <[5][6][7]pasik@xxxxxx> > >> > > > Ã*©crivait: > >> > > > > >     > >> > >> > >> > > > > >     > >> > >> > Any replies from Supermicro/LSI ? > >> > > > > >     > >> > >> > > >> > > > > >     > >> > >> > >> > > > > >     > >> > >> Only loosely related, but Supermicro > >> > > replaced > >> > > > recently my > >> > > > > >     846E26 (dual > >> > > > > >     > >> > >> expander backplane) with 846E16 (single > >> > > > expander). > >> > > > > >     Apparently they > >> > > > > >     > >> > >> gave up getting the E26 to work properly > >> > > or > >> > > > something: LSI > >> > > > > >     expander > >> > > > > >     > >> > >> firmware problem. > >> > > > > >     > >> > >> > >> > > > > >     > >> > >> In another (very large scale, high end) > >> > > setup, > >> > > > many > >> > > > > >     different 60 slots > >> > > > > >     > >> > >> 5 LSI expanders chassis had a general > >> > > failure > >> > > > of the 5th > >> > > > > >     drawer. > >> > > > > >     > >> > >> Another LSI SAS-2 expander firmware > >> > > problem. > >> > > > > >     > >> > >> > >> > > > > >     > >> > >> I could start a rant about the evil of > >> > > > proprietary firmware, > >> > > > > >     etc. You > >> > > > > >     > >> > >> get my meaning :) > >> > > > > >     > >> > >> > >> > > > > >     > >> > > > >> > > > > >     > >> > > Yeah, this is a good example why we're > >> > > trying to > >> > > > get the LEDs > >> > > > > >     working with > >> > > > > >     > >> > > direct attach (non-expander) backplanes > >> > > :) > >> > > > > >     > >> > > > >> > > > > >     > >> > > -- Pasi > >> > > > > >     > >> > > > >> > > > > >     > >> > > >> > > > > >     > >> > I don't have anything useful for people, > >> > > other > >> > > > than that they > >> > > > > >     have > >> > > > > >     > >> > shown me an HBA firmware that fixes the LED > >> > > > problem but has > >> > > > > >     other > >> > > > > >     > >> > problems they're still debugging. > >> > > > > >     > >> > > >> > > > > >     > >> > So there does exist code for this firmware > >> > > which > >> > > > will fix this > >> > > > > >     problem. > >> > > > > >     > >> > > >> > > > > >     > >> > >> > > > > >     > >> That's good to know! Let's hope the fix ends > >> > > up in > >> > > > an official > >> > > > > >     > >> LSI HBA firmware update in not-so-distant > >> > > future. > >> > > > > >     > >> > >> > > > > >     > > > >> > > > > >     > > Btw what was the version number of the > >> > > LED-fixed LSI > >> > > > firmware? > >> > > > > >     > > I'm just wondering in which firmware series > >> > > the fix > >> > > > might end up > >> > > > > >     being included.. > >> > > > > >     > > > >> > > > > >     > > Also: Any updates on this? > >> > > > > >     > > > >> > > > > >     > > Thanks, > >> > > > > >     > > > >> > > > > >     > > -- Pasi > >> > > > > >     > > > >> > > > > >     > > >> > > > > >     > The fixed FW I had demonstrated for me was still > >> > > > 14.0.0.0 - I've > >> > > > > >     been > >> > > > > >     > told it'll be rolled into the FW release > >> > > currently on > >> > > > the site and > >> > > > > >     > posted at some point, but that they have no ETA > >> > > for > >> > > > that. > >> > > > > >     > > >> > > > > > > >> > > > > >     I can now see P15 firmware available on LSI's > >> > > website for > >> > > > 9211-8i > >> > > > > >     (SAS2008 based HBA). > >> > > > > >     Sadly it's missing the releasenotes/changelogs for > >> > > both > >> > > > the LSI bios > >> > > > > >     and firmware.. > >> > > > > >     -- Pasi > >> > > > > > > >> > > > > > References > >> > > > > > > >> > > > > >   Visible links > >> > > > > >   1. mailto:[7][8]rercola@xxxxxxxxxxx > >> > > > > >   2. mailto:[8][9]pasik@xxxxxx > >> > > > > >   3. mailto:[9][10]pasik@xxxxxx > >> > > > > >   4. mailto:[10][11]pasik@xxxxxx > >> > > > > >   5. mailto:[11][12]pasik@xxxxxx > >> > > > > -- > >> > > > > To unsubscribe from this list: send the line "unsubscribe > >> > > linux-scsi" > >> > > > in > >> > > > > the body of a message to [12][13]majordomo@xxxxxxxxxxxxxxx > >> > > > > More majordomo info at > >> > > >  [13][14]http://vger.kernel.org/majordomo-info.html > >> > > > > >> > > > References > >> > > > > >> > > > Visible links > >> > > > 1. mailto:[15]pasik@xxxxxx > >> > > > 2. mailto:[16]rercola@xxxxxxxxxxx > >> > > > 3. mailto:[17]pasik@xxxxxx > >> > > > 4. mailto:[18]pasik@xxxxxx > >> > > > 5. mailto:[19]pasik@xxxxxx > >> > > > 6. mailto:[20]pasik@xxxxxx > >> > > > 7. mailto:[21]rercola@xxxxxxxxxxx > >> > > > 8. mailto:[22]pasik@xxxxxx > >> > > > 9. mailto:[23]pasik@xxxxxx > >> > > > 10. mailto:[24]pasik@xxxxxx > >> > > > 11. mailto:[25]pasik@xxxxxx > >> > > > 12. mailto:[26]majordomo@xxxxxxxxxxxxxxx > >> > > > 13. [27]http://vger.kernel.org/majordomo-info.html > >> > > > >> > > References > >> > > > >> > > Visible links > >> > > 1. mailto:pasik@xxxxxx > >> > > 2. mailto:pasik@xxxxxx > >> > > 3. mailto:rercola@xxxxxxxxxxx > >> > > 4. mailto:pasik@xxxxxx > >> > > 5. mailto:pasik@xxxxxx > >> > > 6. mailto:pasik@xxxxxx > >> > > 7. mailto:pasik@xxxxxx > >> > > 8. mailto:rercola@xxxxxxxxxxx > >> > > 9. mailto:pasik@xxxxxx > >> > > 10. mailto:pasik@xxxxxx > >> > > 11. mailto:pasik@xxxxxx > >> > > 12. mailto:pasik@xxxxxx > >> > > 13. mailto:majordomo@xxxxxxxxxxxxxxx > >> > > 14. http://vger.kernel.org/majordomo-info.html > >> > > 15. mailto:pasik@xxxxxx > >> > > 16. mailto:rercola@xxxxxxxxxxx > >> > > 17. mailto:pasik@xxxxxx > >> > > 18. mailto:pasik@xxxxxx > >> > > 19. mailto:pasik@xxxxxx > >> > > 20. mailto:pasik@xxxxxx > >> > > 21. mailto:rercola@xxxxxxxxxxx > >> > > 22. mailto:pasik@xxxxxx > >> > > 23. mailto:pasik@xxxxxx > >> > > 24. mailto:pasik@xxxxxx > >> > > 25. mailto:pasik@xxxxxx > >> > > 26. mailto:majordomo@xxxxxxxxxxxxxxx > >> > > 27. http://vger.kernel.org/majordomo-info.html > >> > -- > >> > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in > >> > the body of a message to majordomo@xxxxxxxxxxxxxxx > >> > More majordomo info at http://vger.kernel.org/majordomo-info.html > >> -- > >> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in > >> the body of a message to majordomo@xxxxxxxxxxxxxxx > >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
