On Wed, 2010-07-07 at 17:48 -0400, Jacob Ritorto wrote:
> Well, OK, but where do I find it?
>
> I'd still expect some problems with FCODE - vs. - BIOS issues if it's
> not SPARC firmware.
Ah, only if you are using the device to boot from. And in that case,
the low level boot code *should* be on a prom that might not be
upgradeable. (That boot code is essentially a device driver, whether in
BIOS form or in Fcode form...)
The operational firmware is probably located in a different region of
flash, and gets updated more frequently. That said, I don't know for
sure whether this is the case or not.
- Garrett
>
> thx
> jake
>
>
> On 07/07/10 17:46, Garrett D'Amore wrote:
> > On Wed, 2010-07-07 at 17:33 -0400, Jacob Ritorto wrote:
> >> Thank goodness! Where, specifically, does one obtain this firmware for
> >> SPARC?
> >
> > Firmware is firmware -- it should not be host-cpu specific. (At least
> > one *hopes* not, although I *suppose* it is possible to have endian
> > specific interfaces in the device... ugh that would be a very bad idea.)
> >
> > - Garrett
> >
> >>
> >> On 07/07/10 17:04, Daniel Bakken wrote:
> >>> Upgrade the HBA firmware to version 1.30. We had the same problem, but
> >>> upgrading solved it for us.
> >>>
> >>> Daniel Bakken
> >>>
> >>>
> >>> On Wed, Jul 7, 2010 at 1:57 PM, Joeri Vanthienen
> >>> <m...@joerivanthienen.be<mailto:m...@joerivanthienen.be>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> We're using the following components with snv134:
> >>> - 1068E HBA (supermicro)
> >>> - 3U SAS / SATA Expander Backplane with dual LSI SASX28 Expander
> >>> Chips (supermicro)
> >>> - WD RE3 disks
> >>>
> >>> We've got the following error messages:
> >>>
> >>> Jul 7 10:09:12 sanwv01 scsi: [ID 107833 kern.warning] WARNING:
> >>> /p...@0,0/pci8086,3...@7/pci15d9,a...@0/s...@b,0 (sd2):
> >>>
> >>> Jul 7 10:09:12 sanwv01 incomplete read- retrying
> >>>
> >>> Jul 7 10:09:17 sanwv01 scsi: [ID 243001 kern.warning] WARNING:
> >>> /p...@0,0/pci8086,3...@7/pci15d9,a...@0 (mpt0):
> >>>
> >>> Jul 7 10:09:17 sanwv01 mpt_handle_event_sync:
> >>> IOCStatus=0x8000, IOCLogInfo=0x31123000
> >>>
> >>> Jul 7 10:09:17 sanwv01 scsi: [ID 243001 kern.warning] WARNING:
> >>> /p...@0,0/pci8086,3...@7/pci15d9,a...@0 (mpt0):
> >>>
> >>> Jul 7 10:09:17 sanwv01 mpt_handle_event: IOCStatus=0x8000,
> >>> IOCLogInfo=0x31123000
> >>>
> >>> Jul 7 10:09:19 sanwv01 scsi: [ID 365881 kern.info
> >>> <http://kern.info>] /p...@0,0/pci8086,3...@7/pci15d9,a...@0 (mpt0):
> >>>
> >>> Jul 7 10:09:19 sanwv01 Log info 0x31123000 received for
> >>> target 21.
> >>>
> >>> Jul 7 10:09:19 sanwv01 scsi_status=0x0, ioc_status=0x804b,
> >>> scsi_state=0xc
> >>>
> >>> Jul 7 10:09:19 sanwv01 scsi: [ID 365881 kern.info
> >>> <http://kern.info>] /p...@0,0/pci8086,3...@7/pci15d9,a...@0 (mpt0):
> >>>
> >>> Jul 7 10:09:19 sanwv01 Log info 0x31123000 received for
> >>> target 21.
> >>>
> >>> Jul 7 10:09:19 sanwv01 scsi_status=0x0, ioc_status=0x804b,
> >>> scsi_state=0xc
> >>>
> >>> Jul 7 10:09:19 sanwv01 scsi: [ID 365881 kern.info
> >>> <http://kern.info>] /p...@0,0/pci8086,3...@7/pci15d9,a...@0 (mpt0):
> >>>
> >>> Jul 7 10:09:19 sanwv01 Log info 0x31123000 received for
> >>> target 21.
> >>>
> >>> Jul 7 10:09:19 sanwv01 scsi_status=0x0, ioc_status=0x804b,
> >>> scsi_state=0xc
> >>>
> >>> Jul 7 10:09:19 sanwv01 scsi: [ID 365881 kern.info
> >>> <http://kern.info>] /p...@0,0/pci8086,3...@7/pci15d9,a...@0 (mpt0):
> >>>
> >>> Jul 7 10:09:19 sanwv01 Log info 0x31123000 received for
> >>> target 21.
> >>>
> >>> Jul 7 10:09:19 sanwv01 scsi_status=0x0, ioc_status=0x804b,
> >>> scsi_state=0xc
> >>>
> >>> Jul 7 10:09:21 sanwv01 smbsrv: [ID 138215 kern.notice] NOTICE:
> >>> smbd[WINDVISION\franz]: testshare share not found
> >>>
> >>> Jul 7 10:09:26 sanwv01 scsi: [ID 243001 kern.warning] WARNING:
> >>> /p...@0,0/pci8086,3...@7/pci15d9,a...@0 (mpt0):
> >>>
> >>> Jul 7 10:09:26 sanwv01 SAS Discovery Error on port 0.
> >>> DiscoveryStatus is DiscoveryStatus is |SMP timeout|
> >>> Jul 7 10:10:20 sanwv01 scsi: [ID 107833 kern.warning] WARNING:
> >>> /p...@0,0/pci8086,3...@7/pci15d9,a...@0 (mpt0):
> >>>
> >>> Jul 7 10:10:20 sanwv01 Disconnected command timeout for
> >>> Target 21
> >>>
> >>> After this message, the pool is unavailable over iscsi. We can't run
> >>> the format command or zpool status command anymore. We have to
> >>> reboot the server. This happens frequently for different Targets.
> >>> The stock firmware on the HBA is 1.26.01
> >>> --
> >>> This message posted from opensolaris.org<http://opensolaris.org>
> >>> _______________________________________________
> >>> zfs-discuss mailing list
> >>> zfs-discuss@opensolaris.org<mailto:zfs-discuss@opensolaris.org>
> >>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> zfs-discuss mailing list
> >>> zfs-discuss@opensolaris.org
> >>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> >>
> >> _______________________________________________
> >> zfs-discuss mailing list
> >> zfs-discuss@opensolaris.org
> >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> >>
> >
> >
>
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
