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.. Thanks! -- Pasi > - Rich > > On Wed, Dec 19, 2012 at 2:00 PM, Rich <[1]rerc...@pha.jhu.edu> 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]pa...@iki.fi> > 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]pa...@iki.fi> > 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]pa...@iki.fi> 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]pa...@iki.fi> é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:rerc...@pha.jhu.edu > 2. mailto:pa...@iki.fi > 3. mailto:pa...@iki.fi > 4. mailto:pa...@iki.fi > 5. mailto:pa...@iki.fi -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
