=============================================================================== Emulex FC Device Driver for Linux ===============================================================================
Device Driver Version: 11.2.209.7 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support
Device Driver Version: 10.2.375.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - ELS txcmplq list corruption cause crash during error injection - Cleaned up several issues around ExpressLane feature - Need a HAL workaround for upgrading 10.0 XE102/XE104 f/w to 10.2 - I/O hang on RHEL6.5 for small block (4K) random i/o on POWER8
Device Driver Version: 10.0.800.0 Supported On: IBM System x
Problems Fixed: - Low bi-di throughput seen on 1g ports of HS-23 LOM - Multiple performance improvements - Bonding driver takes approx 20 seconds to be ready
Incremental Interoperability: - RHEL 5.10 - RHEL 6.5 - XE-102 and XE-104 ASIC (OCx14xxx) - Support for set and get channels ethtool operation
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.4 and above 64-bit with KVM * SLES11 SP3 and above 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
Device Driver Version: 8.3.7.27 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Execution of internal loopback causes a crash - Issue which can cause multipath failover to not work properly
Incremental Interoperability: - IBM Flex System FC5052 2-port 16Gb FC Adapter - IBM Flex System FC5054 4-port 16Gb FC Adapter - IBM Tape unit interoperability - see SSIC for more information - SLES 11.3 on IBM System x and BladeCenter
Device Driver Version: 8.3.7.18 Supported On: IBM System x and BladeCenter
Problems Fixed: - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service - OXID Reused before RA_TOV without RRQ to recover - Intermittently storage paths will not recover after switch reboot
Device Driver Version: 8.3.6.4 Supported On: IBM Flex
Problems Fixed: - Fixed debug helper routine failed to dump CQ and EQ entries in non-MSI-X mode - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service - Fixed boot from san failure when SLI4 FC device presented on the same PCI bus - Fix ABTS recovery to be FC spec compliant - Fixed not reporting logical link speed to SCSI midlayer when QoS not enabled - Fix performance problem in pt2pt mode - Fixed SCSI host create showing wrong link speed on SLI3 HBA ports - Update text for misconfigured port messages - Fix discovery bug when swapping cables
Interoperability since previous release: - RHEL6.3 GA Kernel
Device Driver Version: 8.3.5.86 Supported On: IBM System x and BladeCenter
Problems Fixed: - Kernel panics with FCoE on HS23 in SLES 11.2 x86_64. Also requires a SLES11.2 kernel update - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service
Interoperability since previous release: - RHEL6.3 GA Kernel
Device Driver Version: 8.3.5.74 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Fixed system crash due to not providing SCSI error-handling host reset handler - Debug helper utility routines for dumping various SLI4 queues - Fix unsol abts xri lookup - Fixed issues with LPe16000 to LPe16000 discovery - Fix driver crash during back-to-back ramp events - Reregister VPI for SLI3 after cable moved to new Saturn port - Fix log message 2597 displayed when no error is detected - Fixed FCP LOG for easier Finisar trace correlation - Fix kernel panic when going into to sleep state - Fix error message displayed even when not an error - Fix Read Link status data - Fix unable to create vports on FCoE SLI4 adapter - Fix initiator sending flogi after acking flogi from target - Fix the case where an array controller does not apply FCP priority rules - Added support for handling SLI4-port XRI resource-provisioning profile change - Change default DA_ID support from disabled to enabled - Fix bug with driver unload leaving a scsi host for a vport around - Update copyright date for files modified in 2012 - Fix compilation errors on some kernels due to debugfs variable definitions - Used PCI configure space read to flush PCI function reset register write - Fixed system panic when extents enabled with large number of small blocks - Fixed system panic during EEH recovery - Fix resource leak when acc fails for received plogi - Fix SLI4 driver module load and unload test in a loop crashes the system - Fix missing CVL event causing round-robin FCF failover process to stop - Fix deadlock during adapter offline request - Fix same RPI registered multiple times after HBA reset
Device Driver Version: 8.3.5.66 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Fix SLI4 driver module load and unload test in a loop crashes the system - Fix missing CVL event causing round-robin FCF failover process to stop - Fix deadlock during adapter offline request - Fix same RPI registered multiple times after HBA reset - Fix driver handling of XRI Aborted CQE response - Fixed port and system failure in handling SLI4 FC port function reset - Fix bug with driver not sending a LOGO with vport delete - Make BA_ACC work on a fully qualified exchange - Fix for SLI4 Port delivery for BLS ABORT ACC - Fix KERNEL allocation while lock held - Incorrect usage of bghm for BlockGuard errors - Fix warning on i386 system - Fix ndlp nodelist not empty wait timeout during driver unloading - Fix mailbox and vpi memory leaks - Support character device to take a reference on the driver - Fix for FDISC failures after firmware reset or link bounce - Support debugfs for injecting T10 DIF errors - Fix SLI4 BlockGuard behavior when protection data is generated by HBA - Fix for driver using duplicate RPIs after 16Gb/s adapter port reset - Fix discovery problem when in pt2pt - Fixed failure in handling large CQ/EQ identifiers in an IOV environment - Fix Locking code raises IRQ twice - Fix driver not returning when bad ndlp found in abts error event handling - Support more driver logs in area of SLI4 port error attention and reset recovery - Fix bug with driver returning the wrong ndlp - Sync up with actual upstream lpfc driver code - Support SLI4 16Gb FC Adapter support for T10 DIF / BlockGuard - Merge from upstream: scsi: Fix up files implicitly depending on module.h inclusion - Fix driver behavior when receiving an ADISC - Fixed unbounded firmware revision string from port caused the system panic - Fix bug with driver processing dump command type 4 using 16Gb FC Adapter - Fix driver does not reset port when reset is needed during fw_dump - Fix ELS FDISC failing with local reject / invalid RPI - Changed SLI4 FC port internal loopback from outer serdes to inner internal - Fix REG_RPI fails on SLI4 HBA putting NPort into NPR state - Fix bug with driver processing an els command using 16Gb FC Adapter - Fix NMI seen due to CQE starvation - Fixed SLI4 FC port obtained link type and number dependent on link connection - Fixed SLI4 FC port internal loopback without SFP and external link/loopback plug - Fix driver incorrectly building fcpCdb during scsi command prep - Fixed FCP EQ memory check prevent initialize to single interrupt vector case - Fixed SLI4 16Gbit FC port internal and external diagnostic loopback tests - Fixed system panic during EEH recovery on SLI4 FC port - Fix FLOGI fails with invalid RPI (0x04) after connecting to a arbitrated loop - Fix ELS SCR failing with local reject / invalid RPI - Fix SLI4 port failures after firmware reset or dump - Fix port reset log messages indicate error when no error is seen - Fixed an issue where HBQ buffers are uninitialized in the base driver - Fixed missing shost lock protection on setting/clearing bit in vport->fc_flag - Fixed missing hbalock protection on setting/clearing bit in phba->link_flag - Fixed illegal state transition during driver unload - Fixed system crash on SLI4 FC port looopback diagnostic test with large buffers - Fixed a potential error path that might try to free DMA memory not allocated - Fixed SLI4 FC port Internal and External loopback diagnostic tests - Fix a crash while deleting 256 vports - Fix vport never finished discovery if switch runs out of resources - Fix kernel build warnings - Fix kernel panic when putting board in offline state twice - Fix memory leak when running hba resets to SLI-4 board - Fix driver message 3092 and 3116 to KERN_WARNING - Fix PCI read failure looks like a over temperature event - Fixed driver event reporting to mgmt on error attention due to forced dump - Fix not displaying firmware rev for BE UCNA boards - Fixed ABTS failure logic not rediscovering targets - Fix bug with driver not byte swapping extended mailbox data - Fix premature ndlp cleanup after second target LOGO - Fix Link pull causes I/O failures - Support loop for sli4 fc pass-through - No longer read fcoe parameters if board is not fcoe - Fix bug with driver passing a wrong count value - Support restore state and error log when sysfs board_mode attribute access failed - Fixed a typo in two of the log messages just introduced - Support for SLI4_CONFIG non-embedded COMN_GET_CNTL_ADDL_ATTR pass-through - Support for SLI4 FC port persistent linkdown through config region 23 - Fix for ABTS. Do not free original IOCB whenever ABTS fails - Fixed Linux driver inconsistency in reporting FC host port-state through OCM - Return an error if the mbox sysfs is called - Fix firmware upgrade attempt on unsupported adapter - Fix incomplete message number 2889 - Fix system crash when ASIC fails to initialize - Fix virtual fabrics bit set in FLOGI incorrectly - Fix bug with driver not returning extended mailbox data - Fix unsupported link speed accepted by SLI4 port - Incremented minor management version to reflect additional "protocol" sysfs attribute - Modify WQ handling to use entry_repost - Moved link type definitions to apply to all driver streams - Support a sysfs attribute "protocol" to report SLI4 port link protocol type - Support SLI4 INTF_TYPE and SLI_FAMILY as sub-field to the fwrev sysfs attribute - Support structure to support T10 DIF in SLI4 - Fix performance slowed due to too many register accesses - Fixed a warning when converting from simple_strtoul to strict_strtoul - Support Initial code to inject T10 DIF errors - Fixed a possible driver crash when cfg_fcp_eq_count is zero - Fixed non-embedded COMMON_GET_CNTL_ATTR mbox command failed with status 0x4 - Fixed null pointer dereference after clearing FCP policy rules - Changed the way of SLI4 device detecting physical port name - Fixed FCP policy exchange management rule parsing - Support check to lpfc_decode_firmware_rev to handle releases that have an 'X' - Fixed RPI leaks in ELS protocol handling - Fix kernel crash during boot with SLI4 card installed - Fixed NPIV FDISC failure on SLI4 if-type 2 ports - Fixed driver failed to follow IP reset procedure in SLI4 error attention handler - Fix sysfs lists fabric name for port that has been disconnected from fabric - Support FCP policy exchange management - Changed the timeout to 300 seconds for SLI_CONFIG (0x9B) mailbox command - Fixed fcp underrun reporting - Fixed a driver handling IP reset issue when PCI read return error - Fixed casting problem in calculating tx_words statistics - Support proper error code return for libdfc calling API to make proper decisions - Fix sli4 mailbox status code. Management software has dependencies - Fix compiler warning due to uninitialized local variable - Fix bus reset handler fails with bad failure code - Made proper error code return for libdfc calling API to make proper decisions - Made error log include PCI BAR bitmap from kernel when enable PCI device failed - Fixed sysfs API mismatch for building against SLES11 SP2 beta kernel - Fixed scsi midlayer queuecommand API mismatch for SLES11 SP2 beta kernel - Fixed ctlreg write bug not checking key string and limiting bytes to write - Fix default adapter name for the OCe15100 - Fixed incomplete scsi messages displayed - Fix cable pull failure on interface type 2 SLI-4 adapters - Fix enable_bg config parameter for SLI4 - Fixed not able to perform firmware reset through sysfs board_mode attribute - Fixed not recovering SLI port in handling error attention with RN bit set - Fixed two crash cases when unsolicted ELS ECHO_CMD is received - Fix direct connect does not come up for SLI4 FC ports - Fixed long wait when firmware reset to a SLI port without required privilege - Fix request firmware support for little endian systems - Fix driver firmware to match new firmware image format - Fixed SLI4 device firmware reset with SR-IOV virtual functions - Fix SLI4 CT handling for sequences > 4K - Fixed handling of unsolicited frames for vports - Fixed handling of CVL for vports - Fixed crash when aborting els IOs - Fix up CT and oxid/rxid for unsol rcv frames - Fixed mailbox double free panic - Support fcf priority record selection for fcf failover - Fixed compiler warning for putting large amount of memory on stack - Fixed driver build not building in debugfs even if kernel CONFIG_DEBUG_FS=y is set - Fix issue where the FC/FCoE Async Receive CQE did not scale for 16G FC adapters - FLOGI payload has Multiple N_port_ID set when lpfc_enable_npiv clear - Removed unused argument passed to the lpfc_bsg_diag_mode_enter routine - Fixed new ASIC device-mgmt BSG pass-through failed multi-buffer fw download - Support sysfs logging when writeable parameters are changed - Used PCI config space capability for sysfs get PF supported SR-IOV number of VFs - Support wait for SLI port status register for readyness following firmware reset - iDiag added SLI4 device PCI BAR memory mapped reigster access methods - Consolidated duplicating macro definitions - Fixed failure to enable PCIe AER prevent driver initialize and attach to device - Modified log messages for T10-PI processing - iDiag fixed mailbox capture and dump overlapping bitmap macro definition
Adapters Supported: ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481) ServeRAID M5110e SAS/SATA Controller for IBM System x ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478) ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304) ServeRAID M5115 SAS/SATA Controller for IBM Flex System (90Y4390) ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304) IBM Flex System Storage Expansion Node (Onboard 2208)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 23.34.0-0023 - High Impact/High Probability of Occurrence -------------------- FW PACKAGE: 23.34.0-0023 MR FW: 3.460.145-8209 iMR FW: 3.460.144-8208 BIOS: 5.50.03.0 UEFI: 0x06110200 HII: 03.17.14.04
Fixes: - Fixed an issue where malformed incoming host commands could cause card reset in DataCenter. (SCGCQ01240574) - Fixed an issue where iMR Montask while installing on degraded R5. (SCGCQ01165519) - Fixed an issue where MRS section in the DDF is not updated when a drive is moved from rebuilding to online state. (SCGCQ01255906) - Fixed an issue where IN FAILED ARRAY bit is not being set when a VD is cleared. (SCGCQ01287457) - Fixed an issue where cache windows of physical drives with invalid signatures were not being accounted properly which was lead to an infinite loop and ultimately kill adapter. (SCGCQ01260339 Port of Defect SCGCQ01058771) - Fixed an issue where Users can't change default access policy of SVD when it blocked by SSC removal. (SCGCQ01260344 Port of Defect SCGCQ00814937)
Version 23.34.0-0019 - High Impact/High Probability of Occurrence -------------------- FW PACKAGE: 23.34.0-0019 MR FW: 3.460.115-6465 iMR FW: 3.460.114-6464 BIOS: 5.50.03.0 UEFI: 0x06110200 HII: 03.17.14.04
Fixes: - Fixed an issue where copyback was being set to on after any reboot or OCR. (SCGCQ01157490) - Fixed an issue where copyback was not automatically initiated when manually setting drives to Unconfigured_Good (SCGCQ01181295) - Fixed an issue where foreign config import fails with DDF corruption (SCGCQ01172248) - Fixed an issue where firmware was not resetting learn cycle failed and learn cycle timeout fields when a new learn cycle starts and completes. (SCGCQ01174449) - Fixed an issue where system stall after sense key 04/c4/01 in HSP disk and controller reset repeatedly (SCGCQ01174450 Defect - SCGCQ01142402) - Fixed an issue where data mis-compare could occur during recovery of CacheCade pinned windows across OCR/Reboot or CacheCade pinned windows could be discarded while CacheCade degrade flush in progress (SCGCQ01163950 Defect - SCGCQ01118285) - Fixed an issue where virtual drive erase wouldn’t complete if VD ID number is changed while the task is ongoing. (SCGCQ01182611)
Version 23.34.0-0018 - High Impact/High Probability of Occurrence -------------------- FW PACKAGE: 23.34.0-0018 MR FW: 3.460.105-6456 iMR FW: 3.460.104-6455 BIOS: 5.50.03.0 UEFI: 0x06110200 HII: 03.17.14.04
Fixes: - Disabled further usage of PI due to a potential data issue (SCGCQ01128078, SCGCQ01105478) - Fixed an issue where MegaRAID firmware crashes or hangs on systems with ASPM enabled on the host and disabled on the controller. (SCGCQ01123931) - Fixed an issue where PI disabled before WJ flush (SCGCQ01135207) - Fixed an issue where virtual drive secure erase resets after a reboot and hangs at 0%. (SCGCQ01137940) - Fixed an issue where after reboot imported 4K drive R0 was not visible. (SCGCQ01156533) - Fixed an issue where patrol read on PD with medium errors could not be stopped by the stop command. (SCGCQ01137941)
Version 23.34.0-0016 - High Impact/High Probability of Occurrence -------------------- FW Package: 23.34.0-0016
Fixes: - Fixed an issue where enabling directpdmapping causes attached disk drives to be no longer be detected by storcli. (SCGCQ01063721) - Fixed an issue where storcli commands and MSM are very slow when migratation activties are occurring. (SCGCQ01086623) - Fixed an issue where Lenovo Info from storcli commands for bbu mismatches with the firmware log. (SCGCQ01041511)
Version 23.34.0-0009 - High Impact/High Probability of Occurrence -------------------- FW Package: 23.24.0-0009
HII: 03.17.14.02
UEFI Driver: 0x06110200
BIOS: 5.50.03.0
MR FW: 3.460.35-6104
iMR FW: 3.460.34-6103
Fixes:
- Fixed the potential of a data miscompare that was observed only at a vendor test facility under very heavy IO and abnormal practices (SCGCQ00995594, Port of SCGCQ00976904)
- Fixed an issue where error "Controller encountered fatal error and was reset" may occur under heavy IO and background operations (SCGCQ00894643)
- Fixed an issue where VMWare may crash when a Guest Operating System is powered off (SCGCQ00872121, Port of SCGCQ00854914)
- Fixed an issue where write-verify performance was lower than expected (SCGCQ00858151, SCGCQ00874193)
- Fixed an issue where "I2C 4 PID 10 SCL STUCK Low! while I2C Rx receiving data intStatus 00008000" may appear in firmware log (SCGCQ01007592)
- Fixed an issue where the Measured Voltage instead of Charging Voltage was displayed in event log (SCGCQ00876489)
- Fixed an issue where Supercap "Battery Not Present" error may occur after shutdown or reboot during a learn cycle (SCGCQ00917115)
- Fixed an issue where Write-through and Write-back cache policies can be changed via Windows Logical Disk Properties. (SCGCQ00856979)
- Fixed an issue where enclosures may go missing when connected in daisy-chain after multiple expander reset cycles (SCGCQ00840725, Port of SCGCQ00818569)
- Fixed an issue where MegaRAID Storage Mananger may display an error message if 'Schedule Consistency Check' is selected. (SCGCQ00852649, Port of SCGCQ00832908)
- Fixed an issue where Patrol Read Properties window does not pop up on MegaRAID Storage Manager (SCGCQ00862478, Port of SCGCQ00797676)
- Fixed an issue where MegaRAID Storage Manager shows messages with Error code 240 and no description (SCGCQ00970948, Port of SCGCQ00904466)
- Fixed an issue where Amber LED may turn on erroneously when an enclosure's slot numbers start with 0 but bay numbers start with 1 (SCGCQ01019622, Port of SCGCQ00903181)
- Fixed an issue where the Generic RAID1 profile option in HII is not greyed-out after creating 64 Virtual Drives (SCGCQ00826822, Port of SCGCQ00816137)
- Fixed an issue where firmware may hang until system is reset (SCGCQ00928869, Port of SCGCQ00923286)
- Fixed an issue where a Virtual Drive may disappear on reboot if it was created with drives from a previously-erased Virtual Drive (SCGCQ00937912, Port of SCGCQ00900237)
- Fixed an issue where Functional Level Reset was not supported (SCGCQ00854343, Port of SCGCQ00840253)
- Fixed an issue where an "L2 unrecoverable cache error" may occur when modifying Patrol read properties (SCGCQ00854668, Port of SCGCQ00847162)
- Fixed an issue where a Hot Spare disk may become Unconfigured Good on reboot (SCGCQ00862477, Port of SCGCQ00803341)
- Fixed an issue where SafeID may change on repeated queries using StorCLI (SCGCQ00949550, Port of SCGCQ00941577)
- Fixed an issue where error "MonTask: line 1272 in file ../../raid/1078dma.c" may occur while running IO in Virtual Machines (SCGCQ01016071, Port of SCGCQ00822403)
- Fixed an issue where incorrect connector information "connector: null x0" shows in MegaRAID Storage Manager (SCGCQ01016040, Port of SCGCQ00996578)
- Fixed an issue where a concurrent Consistency Check cannot be started after resetting adapter to factory defaults (SCGCQ00839437, Port of SCGCQ00838830)
- Fixed an issue where JBOD mode may be disabled if a Virtual Drives is offline (SCGCQ00871662, Port of SCGCQ00827731)
Enhancements:
- Added protection for clearing Foreign Configuration if preserved cache exists (SCGCQ00880783, Port of SCGCQ00842327)
- Enhanced cache restore operation for when restore data size is different than cache size (SCGCQ00860303, Port of SCGCQ00855038)
Version 23.33.0-0044 - High Impact/High Probability of Occurrence -------------------- Fixes: - Fixed an issue where controller may reset under heavy IO and background operations - (SCGCQ00894643) (RETAIN Tip H001154) - Fixed an issue where SuperCap "Battery Not Present" after shutdown and reboot during a learn cycle - (SCGCQ00917115) - Fixed an issue where a VD created with drives from a previously erased VD may disappear on next reboot - (SCGCQ00937912, Port of SCGCQ00900237) - Fixed an issue where firmware may incorrectly select backplane slots when updating drive status - (SCGCQ00980105) - Fixed an issue where MSM shows messages with Error Code 240 and no description - (SCGCQ00970948, Port of SCGCQ00904466) - Fixed an issue where SafeID may change with repeated queries using StorCLI - (SCGCQ00949550, Port of SCGCQ00941577) - Fixed an issue where a Foreign Configuration import may fail after reconstruction when using 4k sector drives - (SCGCQ00830109) - Fixed an issue where setting the Learn Cycle property of iBBU09 gives an I2C error - (SCGCQ00831315) - Fixed an issue where "Prepare for Removal" does not work on a PD when a drive erase is in progress - (SCGCQ00811219, Port of SCGCQ00703189) - Fixed an issue where EFI Driver Health fails when more than 64VDs are configured - (SCGCQ00831006, Port of SCGCQ00830918) - Fixed an issue where a controller may report Cache Memory size as 0 when no logical drives are present - (SCGCQ00837600, Port of SCGCQ00837162) - Fixed an issue where concurrent Consistency Checks cannot be started after issuing "setfactorydefaults" command - (SCGCQ00839437, Port of SCGCQ00838830) - Fixed an issue where Cache Memory size is not reporting 0 when there is no Cache Memory - (SCGCQ00838893, Port of SCGCQ00838193) - Fixed an issue where deleting a CacheCade VD can result in a firmware hang situation - (SCGCQ00838975, Port of SCGCQ00838953) - Fixed an issue where an incorrect error (MFI_STAT_PD_TYPE_WRONG (0x26) instead of MFI_STAT_LD_BLOCK_SIZE_MISMATCH (0x65)) is returned by the firmware when PDs with different block sizes are mixed - (SCGCQ00840251, Port of SCGCQ00836103) - Fixed an issue where BBU status reports Optimal but firmwre logs indicate the BBU has failed - (SCGCQ00838052, Port of SCGCQ00837834) - Fixed an issue where write-verify performance was lower than expected - (SCGCQ00858151) - Fixed an issue where Write-Through and Write-Back cache policies can be changed via Windows Logical Disk Properties - (SCGCQ00856979) - Fixed an issue where firmware reports no SMART error when a PFA (Predictive Failure) drive is attached - (SCGCQ00839455) - Fixed an issue where a status of 0xFF is erroneously returned from StoreLib - (SCGCQ00832673, Port of SCGCQ00827685) - Fixed an issue where an MSM displays an error message if "Schedule Consistency Check" is selected - (SCGCQ00852649, Port of SCGCQ00832908) - Fixed an issue where handling of Functional Level Reset (FLR) is not present - (SCGCQ00854343, Port of SCGCQ00840253)
Enhancements: - Changed the number of Sense Retry counts for a specific video application - (SCGCQ00841000) - Added ability to determine the revision ID for SuperCaps with no VPD programmed - (SCGCQ00828990) - Added support for SES RQST_OK deassertion - (SCGCQ00834321, Port of SCGCQ00817840) - Improved CPLD update capabilities - (SCGCQ00840631, Port of SCGCQ00758178) - Enhanced ability to flush cache with write-verify on RAID0 volumes with SATA drives - (SCGCQ00846777, Port of SCGCQ00842665)
Version 23.33.0-0043 - High Impact/High Probability of Occurrence ----------- Fixes: - Fixed an issue where hard drive slot amber LED not functioning correctly. - Fixed an issue in iMR mode where "Controller encountered fatal error and was reset" errors can occur under heavy IOs and background operations (SCGCQ00894643) (RETAIN Tip H001154) - Fixed an issue where BBU status says optimal but firmware logs indicate that the BBU has failed (SCGCQ00838052) (RETAIN Tip H214857) - Fixed an issue where importing a foreign configuration may fail after reconstruction on 4k sector drives (SCGCQ00830109) - Fixed an issue where the firmware may allow the OS to change VD cache settings (SCGCQ00842350) - Fixed an issue where MR firmware reports "no SMART" error when attaching a PFA drive (SCGCQ00839455) - Fixed an issue where the firmware may hang (enter MonTask) when a guest OS is powered on or off in VMWare (SCGCQ00854914) - Fixed an issue where setting the learn cycle property of iBBU09 gives an I2C error (SCGCQ00831315) - Fixed an issue where "Prepare for Removal" does not work on a PD when drive erase is in progress (SCGCQ00811219) - Fixed an issue where MSM displays "The requested command has invalid arguments" error message if 'Schedule Consistency Check' is selected (SCGCQ00852649) - Fixed an issue where cache memory size in iMR is not showing 0 (SCGCQ00838893) - Fixed an issue where an incorrect MFI_STAT_PD_TYPE_WRONG error is returned by the firmware when PDs with different block size are mixed (SCGCQ00840251) - Fixed an issue where the controller reports cache memory size as 0 when no logical drives are present (SCGCQ00837600) - Fixed an issue where concurrent consistency check cannot be started after issuing "setfactorydefaults" command (SCGCQ00839437) - Fixed an issue where uEFI may report LSI EFI driver "Unhealthy" or "Failed" when more than 64VDs are configured (SCGCQ00831006) - Fixed an issue where functional level reset was not properly showing as unsupported (SCGCQ00854343) - Fixed an issue where the legacy CTRL-H utility may report the wrong PCIe slot number (SCGCQ00799339) - Fixed an issue where the legacy OpROM may show an expander as a JBOD drive in POST (SCGCQ00809682) - Fixed an issue where an encrypted JBOD may be presented to the system in encrypted form even though password was entered incorrectly (SCGCQ00808086)
Enhancements: - Added ability to determine SuperCap revision ID when VPD is not programmed (SCGCQ00828990) - Added support for SES RQST_OK deassertion for customer proprietary JBOD SEP (SCGCQ00834321) - Added feature to enable support for detecting CPLD code version (SCGCQ00840631) - Added feature to enable drive fault LED to be lit when a known-bad drive is connected to the controller (SCGCQ00858142) - Added feature to turn on drive Fault LED when the controller detects a drive that was previously marked Bad (SCGCQ00858140)
Version 23.33.0-0018 - High Impact/High Probability of Occurrence ----------- Fixes: - Incorporated MegaRAID FW stack 5.13 - Fixed an issue where drive temperature cannot be displayed for a drive in Failed or Foreign state (SCGCQ00693959) - Fixed an issue where after creating an LD via StorCLI or MSM the firmware writes into saved power condition mode page (0x1a) of all PDs in the LD and enables their idle timers (SCGCQ00658701) - Fixed an issue where Patrol Read would sporadically correct the same defective LBA repeatedly (SCGCQ00729591) - Fixed an issue where importing a Foreign array onto a new controller may fail with "Cannot force emulate VD to 512E since enable512Esupport is false" error in firmware log (SCGCQ00721106) - Fixed an issue where the controller may enter MegaMon sporadically (SCGCQ00776409) - Fixed an issue where MSM may not report a Full Initialization Aborted error until system rebooted (SCGCQ00759100) - Fixed an issue where the firmware may allow the OS to change VD cache settings (SCGCQ00842350) - Fixed an issue where Link Speed may show UNKNOWN when attaching a 3G or 6G SATA drive (SCGCQ00803522) - Fixed an issue where StorLib may return 0x00ff (fail) code even though operation succeeds when creating a VD out of an existing drive group (SCGCQ00827685) - Fixed an issue where format process of SSD may take much longer than in previous firmware (SCGCQ00674388) - Fixed an issue where controller must have cleared config to enable 240VD unless existing config only included single-drive RAID0 VDs (SCGCQ00559643) - Fixed an issue where some commands would timeout with CDB=ff ff ff ff (SCGCQ00459760) - Fixed an issue where slot ordering in iMR mode might differ from slot numbering in MR mode (SCGCQ00559274) - Blocked CacheCade deletion when multiple CacheCade volumes are associated with Virtual Drives, preventing data issues (SCGCQ00830977) (RETAIN TIP H214323)
Features/enhancements: - Added support for 512e drives (SCGCQ00425363) Enhanced Event Log to include CVPM health details after every Learn Cycle to allow closer monitoring of CVPM health (SCGCQ00819877) - Implemented a retry for reads of CVPM data to avoid erroneous event 386 or 150 in the Event Log (SCGCQ00392439) - Added ability for firmware to report the temperature for all SAS/SATA HDD/SSD (SCGCQ00490819) - Implemented ability for firmware to read drive temperature immediately following SAS discovery (SCGCQ00602573) - Added ability to clear the MaintainPdFailHistory (SCGCQ00474559)
Version 23.29.0-0015 - Critical ------------------- Enhancement - Provide mechanism to disable PCIe backchannel training via SBR. Fixes: - Fixed an issue where the ‘cli set securitykey=Lsi@12345’ command fails with error code 1001 and error message invalid key. - Fixed an issue where foreign configuration import could fail. - Fixed an issue where storcli.exe /c0 show all command repeatedly prints to termlog with respect to upgradekey presence. - Fixed an issue where boot message ‘cached data was lost,’ even when there was no battery present. - Fixed an issue where the order of the first 64 VDs in the POST is not the same sequence as returned from the firmware. - Fixed storCLI adpfwflash option crash and adpallinfo option failure. - Reduced the bootblock Init time, which effectively reduces the configuration retry time to approximately 700 mS.
Version 23.22.0-0024 - Non-Critical ------------------- Enhancement(s): - Display the Native Command Queuing (NCQ) enabled/disabled status of every SATA disk drive in the output of StorCLI and MegaCLI. - Added support for ServeRAID M5100 Series 2GB Flash/RAID 5. Fix(es): - Disable PI CRC checking when the drive is not initialized during a CC. - Increased the SuperCap learn time out value for 2GB TMM-B solution. - Fixed an issue for 2GB memory modules where SuperCap does not get connected to the controller and hence cache offload fails. - Fixed an issue where cache policy of virtual drives(VD) does not change to write through(WT) mode even after detecting a bad supercap. - Fixed an issue where a RAID configuration created with physical disks in powersave mode could be lost after rebooting the system. - Fixed an issue where an invalid frame sent during a PIO-mode SATA passthrough command results in resetting the drive. - Fixed an issue where the system is not allocating memory correctly when MR and iMR controllers are in the same system. - Fixed an issue where deep learn does not start immediately when the relative state of charge (RSOC) is just equal to 95%. - Fixed an issue where performing a re-key operation in external key management (EKM) mode without doing a reboot, and then switching to local key management Mode(LKM) results in the Firmware logs showing that a drive security key was created but HII says the key is incorrect. - Fixed an issue where on a local key management (LKM) enabled controller, the user is asked to enter the security key to unlock and import a foreign drive, which is locked and has external key management (EKM) enabled.
Version 23.16.0-0027 - Critical ------------------- Fix(es): - Addressed data exposure issue when using CacheCade - Fixed issue where Supercap shows 0 Capacitance - Fixed iBBU09 battery issue that caused a VD cache policy to remain in write-through mode after a manual relearn - Fixed iBBU09 battery issue that caused a VD cache policy to periodically toggle between write-back/write-through mode - The limits for iBBU09 battery charging were not updating properly in a learn cycle - Ensures a single supercap pack is not supported on 2GB memory module. - Resolves a firmware crash seen while doing continuous sas cable pulls. - Ensures OpROM loads even if segment address is 0xC0000. - Fixed an issue where the adapter is running iMR machine checking after requesting host memory. - Fixed an issue where HII does not allow the user to make use of the remaining free capacity to configure additional VD for R50/R10. - Fixed an issue where an HII: empty warning prompt is given when creating a CacheCade VD with forced writeback option. - Fixed and issue where Windows cannot install without a VGA device on board. - Fixed and issue in EFI WebBIOS were consistency check is still shown in progress after 1 PD is removed from a R1 array.
Version 23.16.0-0018 - Suggested ------------------- Fix(es): - Fixed an issue where the adapter is running iMR machine checking after requesting host memory. - Fixed an issue where HII does not allow the user to make use of the remaining free capacity to configure additional VD for R50/R10. - Fixed an issue where an HII: empty warning prompt is given when creating a CacheCade VD with forced writeback option. - Fixed and issue where Windows cannot install without a VGA device on board. - Fixed and issue in EFI WebBIOS were consistency check is still shown in progress after 1 PD is removed from a R1 array.
Version 23.12.0-0016 - Suggested ------------------- Fix(es): - Added isync to prevent speculative execution while memory is being allocated. - Delayed enablement of POM until AFTER valid memory range is provided by host system.
Version 23.12.0-0011 - Suggested ------------------- Enhancement(s): - Support for 512e and 4k SAS/SATA hard drives added - Implemented Limited Band Charging for iBBU09 (RETAIN tip H21631) - Changed BIOS check to determine if running in HAMR, in order to ensure nothing gets broken when user has an iButton which is not programmed. - Changed controller status for safe mode to show controller status as safe mode and disable debug message logging in serial port.
Fix(es): - Addressed an issue where deeply discharged Cache Vault Power Modules would be prematurely be marked as failed. - Fixed an issue where HII hangs when trying to enter configuration management while in safe mode. Changed the safe mode warning message as below: "Controller is running in safe mode. Safe mode is used for diagnostic purposes only. Limited operations such as Configuration Preview, Clear Configuration and View/Change Controller Properties are allowed in this mode. Other operations such as Create Configuration, Import and Clear Foreign Configurations are not allowed. To exit safe mode, correct the fault, and reboot your computer." - Fixed an issue where having more than three adapters results in a calculation error for the offset to store physical disk info for fourth adapter, due to BIOS not clearing upper byte of AX (that is AH which is containing some non zero value). - Fixed an issue where the Wrong spanned drive group size is displayed by WebBIOS (Ctrl-H).
Version 23.7.1-0010 - Suggested ------------------- Fixes: - Fix an issue related to the where the TSOC (EEPROM) is not able to read or write from the firmware which will result in the message "Incompatible secondary iButton present." - Fix a HII broswer issue where Cachecade virtual drive can be selected as a boot device. - Fix a HII broswer issue where the user is unable to clear the controller configuration when there are no drives attached. - Fix an issue where the BIOS doesn't display the RAID level and VD size correctly at BIOS POST.
Version 23.7.1-0009 - Suggested ------------------- Fixes: - Fixed an issue where SoH is bad after a learn cycle but iBBUI shows good status. - Fixed an issue where hi-temp warning was not being displayed.
Version 23.7.0-0037 - Suggested ------------------- Fixes: - Corrected differential signals for Phys 2 and 3 that caused slot numbers in simple swap configurations to be incorrect. - Fixed an issue when 'maintain PD failed history' is enabled, and a cable is removed while a drive is added, the drives state goes to optimal instead of foreign unconfigured bad. - Fixed a problem where a capacity change is reported after a rebuild completes on a Cache Cade volume. - Fixed a controller firmware hang when the recovery of a medium error takes to long. - Fixed an issue where the SATA BBM (Bad Block Manager) list was being corrupted. - Fixed an issue where FoD (Feature on Demand) Options were being lost because of errors while accessing the TSOC. - Fixed a problem where the controller firmware would crash and drives would go offline when a bad block entry was created during a check consistency operation. - Fixed a problem where drives were being marked unconfigured bad (foreign) on reboot. - Fixed problem where a member of a CacheCade volume did not get marked as foreign when the drive was pulled with 'maintain PD failed history' enabled. - Fixed a problem where during a rebuild, a former hot spare that was now in a state of unconfigured good, moved back to the state hot spare, which then automatically started a copyback operation, causing the rebuild to restart. - Fixed a problem where a controller fault occurred during a reboot while a physical device was in progress of a PD Erase.
Version 23.7.0-0029 - Suggested ------------------- Enhancements: - Added support for Cache Cade 2.1 - Added Support for PI Drives
Fixes: - Fixed an issue where the firmware reports device initialization completion status to be greater than 100% at startup. - Fix an issue where when a secure foreign drive was present, VD creation fails because firmware becomes unresponsive - Added a check for the presence of PD before writing the data arms of a protected LD during BGI. - Fixed Firmware asserts in CacheMemAllocForPrebootApps() when memory was allocated twice by BIOS. - Fixed an issue with USB Cacheoffload restore fails after multiple power cycles onServeRAID M51xx controllers. - Fixed an issue where querying SMART / PFA Status returns "all zeros" in Sense Data. - Fixed an issue where the import of a config from MR to iMR resulted in a firmware crash. - Fixed an issue where iMR firmware crashed while creating 8/16/32 KB stripe size Lds. - Fixed background initialization watermark conversion to PD LBA. - Fixed write protected R1E data arms during initialization. - Fixed an issue where MR firmware crashed while discarding pinned cache. - Fixed an issue where a dirty LD dependency information of SSD pd has stale entries. - Corrected an issue during system booting from pinned cache, firmware goes to loop message BootMsgDcmd - Fixed an issue where a BGI was aborted and restarted, elapsed time was not reset. - Fixed an issue where the start ref for a shared cache line was not an indicator of the offset into the stripe. - Fixed an issue where the firmware hangs while running CC on a rebuilt R1 VD with SBBM. - Fixed an issue where the firmware was wrongly adding puncture entries. - Fixed an issue where rebuild was ran twice on a target drive with 100% full SBBM table. - Fixed an issue where the firmware was generating powersave change event when DS3 was not enabled, due to this application are not parsing the event. - Fixed an issue where recon from R0 to R1 using 3 TB drive causes firmware to report excessive unexpected sense events. - Fixed an issue, in which the bbuMode would revert to the factory default value of 5, when automatic learn cycle was enabled. - Fixed an issue where cache offload firmware reports unnecessary High Temp Event due to incorrect temp value. - Fixed an issue in which a Patrol Read may not start under certain conditions. - Fixed an issue where the firmware hits montask after discarding the cache when a snapshot VD was involved. - Fixed an issue where the firmware hangs during pin cache destage as dirty lines in that map never become zero. - Fixed an issue where CC fails to correct media error at 2TB location on 2 3TB SATA drives that support WU. - Fixed an issue where a new XML file was added to the nvdata, the buffer to hold the uncompressed nvdata overflowed. - Fixed an issue where an imported drive becomes unconfigured good when secure VD erase was running. - Fixed an issue where CC stops progressing on a R6 VD with media errors. - Fixed an issue where 3TB Hitachi HDD failed in immunity test (Electrostatic Noise test). - Fixed an issue where controller features are lost if RAID Key was not detected. - Fixed an issue where performance degraded in RAID 5 Sequential Writes due to command Out-of Ordering. - Fixed an issue where "Native configuration is no longer supported" message in post. - Fixed an issue where (DDR3) Initialization fails with fault 0x91a1 - initial DFIRL selected too low. - Fixed an issue where subsequent drives are dropped when all drives in the stagger spin up drives fails on boot sequence.
Version 23.2.1-0043 - Suggested ------------------- Fixes: - Fixed an issue where "Potential non-optimal configuration due to drive PD commissioned as emergency spare" alarm would trigger erroneously. - Fixed an issue where Copyback does not progress upon inserting drives. - Fixed an issue When allowMixInLD is Disabled, and causes Copyback Fails after Rebuild to Emergency Hot Spare. - Fixed an issue where the Firmware faults while flashing. - Fixed an issure where querying SMART / PFA Status to Return all zeros in Sense Data. - Fixed an issue where the Re-inserted Drives becomes Unconfigured_good causing auto rebuilds to fail to start.
Version 23.2.1-0033 ------------------- - Initial release ibm_fw_sraidmr_6gb-23_34_0-0023_linux_32-64_chg
IBM Online SAS/SATA HDD/SSD Update Program. Version 1.23.02 Build ID: IBM12302 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.23.02 - Update Utility release for IBM x86 servers.
SAS 3.5"
- ST1000NM0045, ST2000NM0045, ST4000NM0025 to LK85
- ST6000NM0095 to LC85
SAS 2.5"
-HUC101860CSS20E, HUC101890CSS20E, HUC101812CSS20E, HUC101830CSS20E to P2H6
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.23.01 Build ID: IBM12301 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.23.01 - Update Utility release for IBM x86 servers.
Note 1: *- Fix bug : Sweep seek not scheduled after forced power condition
- ST2000NM0043, ST4000NM0043 to EC5K/FC5E - see Note1 * above
- ST2000NM0054, ST4000NM0054, ST6000NM0054 to EC6J/FC6E -see Note1 * above
- ST2000NM0034, ST4000NM0034, ST6000NM0034 to BC6G -see Note1 * above
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.23.00 Build ID: IBM12300 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.23.00 - Update Utility release for IBM x86 servers.
Note 1: *- Add Lenovo Branded Part Number in supporting list
Note 2: *- Remove the legacy HDD/SSD in this Update program, the drives were out of production by 4Q2014 or no firmware changes since 1Q2014. There is a seperate update program to support these drives.
This package acknowledges support and may include updates for drives with product ID strings of:
SAS 3.5"
- ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to LC5H - See Note 1* above
- ST2000NM0043, ST4000NM0043 to FC5D - See Note 1* above
- ST2000NM0054, ST4000NM0054, ST6000NM0054 to FC6D - See Note 1 * above
- ST3300657SS, ST3600057SS to LA5A - See Note 1* above
- HUS724020ALS64, HUS724030ALS64, HUS724040ALS64 to K3LC - See Note 1 * above
- HUS724020ALS61, HUS724040ALS61 to P3LC - See Note 1* above
- WD1001FYYG-23S, WD2001FYYG-23S to XA39 - See Note 1 * above
- WD5003ABYX-23 to WC42 - See Note 1 * above
- ST1000NM0045, ST2000NM0045, ST4000NM0025 to LK84 - See Note 1* above
- ST6000NM0095 to LC84 - See Note 1* above
- MG04SCA60EE to TG45 - See Note 1* above
- ST2000NM0034, ST4000NM0034, ST6000NM0034 to BC6F
SAS 2.5"
- ST300MM0006, ST600MM0006, ST900MM0006 to L56R - See Note 1* above
- ST300MM0026, ST600MM0026, ST900MM0026 to F56F - See Note 1* above
- ST1200MM0007 to L57D - See Note 1* above
- ST1200MM0017 to F578 - See Note 1* above
- ST300MP0005, ST600MP0005 to L67J - See Note 1* above
- ST300MP0015 to F674 - See Note 1 * above
- ST9146853SS, ST9300653SS to L63M - See Note 1* above
- ST9500620SS, ST91000640SS to LD2L - See Note 1* above
- HUC156030CSS20, HUC156060CSS20 to K2GF - See Note 1* above
- HUC109030CSS60, HUC109060CSS60, HUC109090CSS60 to K2EK - See Note 1* above
- HUC109030CSS61, HUC109060CSS61, HUC109090CSS61 to P2EK - See Note 1* above
- AL13SEB300, AL13SEB600, AL13SEB900 to TB37 - See Note 1* above
- HUSMM1620ASS20, HUSMM1640ASS20, HUSMM1680ASS20, HUSMM1616ASS20 to K4CC - See Note 1* above
- HUSMM1640ASS20E, HUSMM1680ASS20E to P4CC - See Note 1* above
- ST1000NX0453 to LD48 - See Note 1* above
- HUC101860CSS20, HUC101890CSS20, HUC101812CSS20, HUC101830CSS20 to K2H9 - See Note 1* above
- HUC101860CSS20E, HUC101890CSS20E, HUC101812CSS20E, HUC101830CSS20E to P2H5 - See Note 1* above
- HUC101818CS420 to J5H9 - See Note 1* above
- HUC101818CS420E to N5H9 - See Note 1 * above
- ST1800MM0018 to L59B - See Note 1* above
- ST1800MM0068 to F594 - See Note 1* above
- AL14SEB180E to TL43 - See Note 1 * above
- USMR1625ASS20E to P4C9 - See Note 1* above
SATA 3.5"
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to LB5F - See Note 1* above
- WD1004FBYZ-23YC, WD2004FBYZ-23YC to WH03 - See Note 1 * above
- ST1000NM0055, ST2000NM0055, ST4000NM0035 to LJ84 - See Note 1* above
- ST6000NM0115 to LB83 - See Note 1* above
- MG04ACA600E to TJ42 - See Note 1* above
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NS to LE2B - See Note 1* above
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MC50 - See Note 1* above
- SSDSC2BB800G4I to D201NE40 - See Note 1* above
- ST1000NX0423 to LE45 - See Note 1* above
SATA 1.8"
- MTFDDAA480MBB, MTFDDAA800MBB to MC50 - See Note 1* above
Below drives are removed from the program - See Note 2* above
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.21.00 Build ID: IBM12100 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.21.00 - Update Utility release for IBM x86 servers.
This package acknowledges support and may include updates for drives with product ID strings of:
SAS 3.5"
- ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5K
- ST2000NM0043, ST4000NM0043 to EC5H
- ST2000NM0034, ST4000NM0034, ST6000NM0034 to BC6E
- ST2000NM0054, ST4000NM0054, ST6000NM0054 to EC6E
- HUS724020ALS64, HUS724030ALS64, HUS724040ALS64 to MPXSJ3LA
- HUS724020ALS61, HUS724040ALS61 to MPXSN3LA
- VPCA300900EST1, VPCA450900EST, VPCA600900EST1 to VCXSA810
SAS 2.5"
- HUC156030CSS20, HUC156060CSS20 to KFXSJ2G8
- HUC101212CSS60 to CPXSJ2MC
- HUC101212CSS61 to CPXSN2MC
- HUC109030CSS60, HUC109060CSS60, HUC109090CSS60 to CEXSJ2EL
- HUC109030CSS61, HUC109060CSS61, HUC109090CSS61 to CEXSN2EL
- HUSMM1620ASS20, HUSMM1640ASS20, HUSMM1680ASS20, HUSMM1616ASS20 to SPXSJ4CC
- HUSMM1620ASS20E, HUSMM1640ASS20E, HUSMM1680ASS20E, HUSMM1616ASS20E to SPXSN4CC
SATA 3.5"
- WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD40
- ST2000NM0024, ST4000NM0024, ST6000NM0024, ST5000NM0024 to BB67
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5G
SATA 2.5"
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB47
- MZ7GE240HMHP-000M3, MZ7GE480HMHP-000M3, MZ7GE960HMHP-000M3 to EXT0CA35
- STECM8PSB2 to 2864/SM08
SATA 1.8"
- MTFDDAA120MBB, MTFDDAA240MBB, MTFDDAA480MBB, MTFDDAA800MBB to MB47
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.20.00 Build ID: IBM12000 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.20.00 - Update Utility release for IBM x86 servers.
Note: *- Update the firmware on SAS/SATA SSDs to fix PSIRT issue with Intel SSD's.
This package acknowledges support and may include updates for drives with product ID strings of:
SATA 2.5"
- SSDSC2BB120G4I, SSDSC2BB240G4I, SSDSC2BB480G4I, SSDSC2BB800G4I to D201NE40.
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to 5DV1NA39.
- SSDSC2BB080G4I, SSDSC2BB160G4I, SSDSC2BB300G4I, SSDSC2BB600G4I, SSDSC2BB800G4I to D201NE40.
- SSDSC2BB012T4I, SSDSC2BB016T4I to G201NC34.
SATA 1.8"
- SSDSC1NB080G4I, SSDSC1NB240G4I, SSDSC1NB400G4I to D201NE40.
- SSDSC1NA200G3I, SSDSC1NA400G3I to 5DV1NA39.
- SSDSC1NB800G4I to D201NE40.
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.19.06 Build ID: IBM11906 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.19.06 - Update Utility release for IBM x86 servers.
This package acknowledges support and may include updates for drives with product ID strings of:
- Remove TXA2D20200GA6I, TXA2D20400GA6I, TXA2D20800GA6I, TXA2E21600GA6I from FW update utility for new code updating break Raid.
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.18.03 Build ID: IBM11803
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.18.03 - Update Utility release for IBM x86 servers.
Note: * - Fixed extremely low probable data compare error on I/O held in standby when followed by power cycle; extremely low probable data compare error due to nonvolatile cache(NVC) write data not getting written to disc. RETAIN TIP: H214784 - MIGR-5098277
Note: # - Fixed a block misalignment during a sequential read.
RETAIN TIP: H214635 MIGR-5098037
SAS 3.5"
- ST2000NM0034, ST4000NM0034, ST6000NM0034 to BC6B - similar to Note * above.
- ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5J - Enhance Dither Algorithm to prevent dwelling during Idle environments. - ST2000NM0043, ST4000NM0043 to EC5E - Enhance Dither Algorithm to prevent dwelling during Idle environments.
SAS 2.5"
- TXA2E21600GA6I to GB7P - add support in profile.
- HUC156030CSS20, HUC156060CSS20 to J2G6 - add support in profile.
SATA 3.5"
- ST2000NM0024, ST4000NM0024, ST5000NM0024, ST6000NM0024 to BB66 - similar to Note * above.
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5F - Enhance Dither Algorithm to prevent dwelling during Idle environments.
SATA 2.5"
- MTFDDAA120MBB, MTFDDAA240MBB, MTFDDAA480MBB, MTFDDAA800MBB to MB42 - add support in profile.
- SSDSC2BB080G4I, SSDSC2BB160G4I, SSDSC2BB300G4I, SSDSC2BB600G4I to D201NB39 - add support in profile.
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.17.01 - Update Utility release for IBM x86 servers.
Note: * - Fixed extremely low probable data compare error on I/O held in standby when followed by power cycle; extremely low probable data compare error due to nonvolatile cache(NVC) write data not getting written to disc. RETAIN TIP: H214784 - MIGR-5098277
Note: # - Fixed a block misalignment during a sequential read. RETAIN TIP: H214635 MIGR-5098037
This package acknowledges support of qualified devices and may include updates for drives with product ID strings of:
SAS 3.5"
- HUS724020ALS61, HUS724040ALS61 to N3L6 - internal updates.
- ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5H - See Note * above.
- ST2000NM0054, ST4000NM0054, ST6000NM0054 to EC66 - see Note * above.
- ST2000NM0043, ST4000NM0043 to EC5D - See Note * above.
- Other drive codes are present for support identification.
SAS 2.5"
- WD3001BKHG-23D, WD6001BKHG-23D, WD9001BKHG-23D to ZA34 - follow-on release. - WD3002BKTG-23E, WD6002BKTG-23E, WD9002BKTG-23E to ZC33 - follow-on release.
- HUC109030CSS60, HUC109060CSS60, HUC109090CSS60 to J2EH - follow-on release.
- TXA2D20200GA6I, STXA2D20400GA6I, TXA2D20800GA6I, TXA2E21600GA6I to GB7P - enhancements.
- ST300MM0006, ST600MM0006, ST900MM0006 to B56T - See Note * above.
- ST300MM0026, ST600MM0026, ST900MM0026 to E56E - See Note * above.
- ST2000NM0043, ST4000NM0043 to EC5D - See Note * above.
- ST1200MM0007 to B57E - See Note * above.
- ST1200MM0017 to E577 - See Note * above.
- HUSMM1620ASS20, HUSMM1640ASS20, HUSMM1680ASS20, HUSMM1616ASS20 to J4C8 - See Note # above - HUSMM1620ASS20E, HUSMM1640ASS20E, HUSMM1680ASS20E, HUSMM1616ASS20E to N4C8 - See Note # above
- Other drive codes are present for support identification.
SATA 3.5"
- MG04ACA200E, MG04ACA300E, MG04ACA400E, MG04ACA500E to SJ1D - performance inhancements.
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5C - See Note * above.
- ST2000NM0024, ST4000NM0024, ST5000NM0024, ST6000NM0024 to BB65 - See Note * above.
- WD2003FYYS-23W0B0 to WA36 - configuration additions.
- WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD39 - configuration additions.
- HUA723030ALA6 to MKAOA930 - enhancements. - HUA723020ALA6 to MK7OA930 - enhancements.
- Other drive codes are present for support identification.
SATA 2.5"
- MZ7GE240HMHP-000M3, MZ7GE480HMHP-000M3, MZ7GE960HMHP-000M3 to EXT0CA34 - ship level.
- Other drive codes are present for support identification.
SATA 1.8"
- Drive codes are present for support identification.
IBM Online SAS/SATA HDD/SSD Update Program. Version 1.16.05 Build ID: IBM11605
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.16.05 - Update Utility release for IBM x86 servers.
This package acknowledges support and may include updates for drives with product ID strings of:
SAS 3.5"
- ESXSST1000NM0001, ESXSST2000NM0001 to BC4B - ensures that after servicing an 03/11/00 error, an index for Parity Creations is calculated correctly after a power cycle, that would otherwise make the drive unresponsive.
- ESXSHUS724020ALS64, ESXSHUS724030ALS64, ESXSHUS724040ALS64 to J3L6 - Fixed unexpected 02/04/11 error; Fixed a drive logic self-initiated reset on read/write long commands; Fixed a problem with large write sequential transfers.
SAS 2.5"
- ESXSST9500620SS, ESXSST91000640SS to BD2K - ensures that after servicing an 03/11/00 error, an index for Parity Creations is calculated correctly after a power cycle, that would otherwise make the drive unresponsive.
SATA 2.5"
- SSDSC2BB012T4I, SSDSC2BB016T4I to G201NC32 - SCT WriteSame fix.
IBM Online SAS/SATA HDD/SSD Update Program. Version 1.16.04 Build ID: IBM11604
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.16.04 - Update Utility release for IBM System x servers.
This package acknowledges support and may include updates for drives with product ID strings of:
NOTE: Check notation under PCIe NVMe devices.
SATA 2.5"
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB42 - > A drop in host power supply may cause bad block growth > The bad block table may not properly increment > Background activity may continue after STANDBY, STANDBY IMMEDIATE, or SLEEP > ID173/202 may show incorrect value when the NAND erase count exceeds 3000 > Changed DRAM timing > Event log may be programmed when supply voltage from host is out of specification
- SSDSC2BB012I4I, SSDSC2BB016T4I to G201NC32 - SCT WriteSame fix that corrects a condition that may cause the drive to not respond.
PCIe NVMe 2.5"
- SSDPE2ME400G4I, SSDPE2ME800G4I, SSDPE2ME016G4I, SSDPE2ME020G4I to 8DV1ND34 - will require two update runs and system reboots for device fw update to complete--Please See the limitations in readme for details.
> Performance improvement on sub-4KB sequential write > Fix drive reports higher than actual data units read and write > Fix drive incorrectly counts unsafe power shutdown events on warm reboots
IBM Online SAS/SATA HDD/SSD Update Program. Version 1.16.03 Build ID: SAS11603
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.16.03 - Update Utility release for IBM System x servers.
This package acknowledges support and may include updates for drives with product ID strings of:
NOTE: Check notation under PCIe NVMe devices.
SAS 3.5"
- ESXSST2000NM0034, ESXSST4000NM0034, ESXSST6000NM0034 to BC67 - GA code. - ESXSST2000NM0054, ESXSST4000NM0054, ESXSST6000NM0054 to EC66 - GA code.
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to XA39 - issues fixed: slow performance with PI enabled; drive hang on uncorrectable rd error in reallocation track; PERSISTANT RESERVATION command not working correctly; reliability improvements around off-track write protection.
SAS 2.5"
- ESXSTXA2D20200GA6, ESXSTXA2D20400GA6, ESXSTXA2D20800GA6, ESXSTXA2E21600GA6 to GB7P - fixes implemented to support PI issues.
- ESXSST300MP0005 to B675 - GA code. - ESXSST300MP0025 to E671 - GA code.
- ESXSST300MP0035, ESXSST600MP0035 to B683 - GA code. - ESXSST300MP0045, ESXSST300MP0045 to E685 - GA code.
- ESXSST300MX0012, ESXSST600MX0052 to BH53 - GA code.
- ESXSWD3001BKHG-23D, ESXSWD6001BKHG-23D, ESXSWD9001BKHG-23DS to ZA34 - issues fixed: slow performance with PI enabled; drive hang on uncorrectable rd error in reallocation track; PERSISTANT RESERVATION command not working correctly; drive was reporting 0B/11 instead of 03/11. - ESXSWD3002BKTG-23E, ESXSWD6002BKTG-23E, ESXSWD9002BKTG-23E to ZC33 - issues fixed: slow performance with PI enabled; drive hang on uncorrectable rd error in reallocation track; PERSISTANT RESERVATION command not working correctly; reliability improvements around off-track write protection.
SATA 3.5"
- MG04ACA200E, MG04ACA300E, MG04ACA400E, MG04ACA500E to SJ1C - GA code
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NS to BE2B - Update configuration change.
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB34 - > Some Out of Range LBAs accepted by NCQ commands where they should be aborted. > SataDownShift.srt failed, Smart attribute Raw lost with perform dirty pwr cycle . > Low Power Entry Bug Identified from Marvell Code Review > Track Timeout, Marvel 373 sequencer issue > Unreasonable ECC count in SMART ID 195
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program for Linux. Version 1.16.00 Build ID: SAS11600
******************************************* IBM SAS/SATA HDD/SSD Update Program Version 1.16.00 - First Update Utility release for IBM System x servers.
This package acknowledges support and may include updates for drives with product ID strings of:
NOTE: Check notation under PCIe NVMe devices.
SAS 3.5"
- ESXSST1000NM0023, ESXSST2000NM0023, ESXSST3000NM0023, ESXSST4000NM0023 to BC5E
- ESXSST2000NM0043, ESXSST3000NM0043, ESXSST4000NM0043, ESXSST1000NM0043 to EC5A
- ESXSST3300557SS, ESXSST3450757SS, ESXSST3600957SS to EA54
- ESXSST3300657SS, ESXSST3450857SS, ESXSST3600057SS to BA5A
- ESXSST33000650SS to BC3E
- ESXSST1000NM0001, ESXSST2000NM0001 to BC4A
- ESXSHUS724020ALS64, ESXSHUS724030ALS64, ESXSHUS724040ALS64 to J3L5
- ESXSHUS724020ALS61, ESXSHUS724040ALS61 to N3L5
- ESXSHUS723020ALS64, ESXSHUS723030ALS64 to J3K8
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to XA38
SAS 2.5"
- ESXSTXA2D20200GA6I, ESXSTXA2D20400GA6I, ESXSTXA2D20800GA6I, ESXSTXA2E21600GA6I to GB7H
- ESXSST300MM0006, ESXSST600MM0006, ESXSST900MM0006 to B56M; - ESXSST300MM0026, ESXSST600MM0026, ESXSST900MM0026 to E56D
- ESXST1200MM0007 to B57B - ESXST1200MM0017 to E576
- ESXSST9300605SS, ESXSST9600205SS, ESXSST9900805SS to B55E - ESXSST9300505SS, ESXSST9600105SS, ESXSST9900705SS to E558
- ESXSST9146853SS, ESXSST9300653SS to B63K
- ESXSST9146753SS, ESXSST9300553SS to E638 - ESXSST9500620SS, ESXSST91000640SS to BD2J
- ESXSHUC101212CSS60 to J2MA - ESXSHUC101212CSS61 to N2M9
- ESXSHUC156030CS420, ESXSHUC156060CS420 to J5G2 - ESXSHUC156030CSS20, ESXSHUC156060CSS20 to J2G4
- ESXSHUC156030CS420E, ESXSHUC156060CS420E to N5G2
- ESXSHUC156030CSS20E, ESXSHUC156060CSS20E to N2G4
- ESXSHUC101860CS420, ESXSHUC101890CS420, ESXSHUC101812CS420, ESXSHUC101818CS420 to J5H2 - ESXSHUC101860CS420E, ESXSHUC101890CS420E, ESXSHUC101812CS420E, ESXSHUC101818CS420E to N5H2
- ESXSHUC109030CSS60, ESXSHUC109060CSS60, ESXSHUC109090CSS60 to J2EG - ESXSHUC109030CSS61E, ESXSHUC109060CSS61E, ESXSHUC109090CSS61E to N2EG
- ESXSAL13SXB300N, ESXSAL13SXB600N to SC36
- ESXSMBF2300RC, ESXSMBF2600RC to SB2F
- ESXSMK1401GRRB, ESXSMK3001GRRB to SC2E - ESXSMK1401GRRR, ESXSMK3001GRRR to SF23 - ESXSMK3001GRDB, ESXSMK6001GRDB, ESXSMK9001GRDB to SB35
- ESXSWD3001BKHG-23D, ESXSWD6001BKHG-23D, ESXSWD9001BKHG-23D to ZA33 - ESXSWD3002BKTG-23E, ESXSWD6002BKTG-23E, ESXSWD9002BKTG-23E to ZC32
- EXSXHUSMM1620ASS20, EXSXHUSMM1640ASS20, EXSXHUSMM1680ASS20, EXSXHUSMM1616ASS20 to J4C6 - EXSXHUSMM1620ASS20E, EXSXHUSMM1640ASS20E, EXSXHUSMM1680ASS20E, EXSXHUSMM1616ASS20E to N4C6
SATA 3.5"
- WD1003FBYX-23Y7B0, WD2003FYYS-23W0B0 to WA35
- WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD37 - Resolves drive initiated reset (DBS (Debug Stop event)) encountered under a narrow timing window (~1ns) for specific command/access patterns, due to the drive’s handling of command automation where it was possible for an internal hardware resource conflict to occur between two tasks.
- ST33000650NS to BB3A
- ST1000NM0011, ST2000NM0011 to BB4A
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5A
- HUA723020ALA640 to MK7OA930 - HUA723030ALA640 to MKAOA930
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NSto BE2A
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB33
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to 5DV1NA37
- MZ7GE240HMHP-000M3, MZ7GE480HMHP-000M3, MZ7GE960HMHP-000M3 to EXST0CA34
PCIe NVMe 2.5"
- SSDPE2ME400G4I, SSDPE2ME800G4I, SSDPE2ME016G4I, SSDPE2ME020G4I to 8DV1ND32 - will require a system reboot for device fw update to complete.
********************************************************************* SAS/SATA HDD/SSD Update Program Version 1.15.00 - First Update Utility release for IBM System x servers.
This package acknowledges support and may include updates for drives with product ID strings of:
SAS 3.5"
- ESXSST1000NM0023, ESXSST2000NM0023, ESXSST3000NM0023, ESXSST4000NM0023 to BC5E
- ESXSST2000NM0043, ESXSST3000NM0043, ESXSST4000NM0043, ESXSST1000NM0043 to EC5A
- ESXSST3300557SS, ESXSST3450757SS, ESXSST3600957SS to EA54
- ESXSST3300657SS, ESXSST3450857SS, ESXSST3600057SS to BA5A
- ESXSST33000650SS to BC3E
- ESXSST1000NM0001, ESXSST2000NM0001 to BC4A
- ESXSHUS724020ALS64, ESXSHUS724030ALS64, ESXSHUS724040ALS64 to J3L5
- ESXSHUS724020ALS61, ESXSHUS724040ALS61 to N3L5
- ESXSHUS723020ALS64, ESXSHUS723030ALS64 to J3K8
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to XA38
SAS 2.5"
- ESXSTXA2D20200GA6I, ESXSTXA2D20400GA6I, ESXSTXA2D20800GA6I, ESXSTXA2E21600GA6I to GB7H
- ESXSST300MM0006, ESXSST600MM0006, ESXSST900MM0006 to B56M; - ESXSST300MM0026, ESXSST600MM0026, ESXSST900MM0026 to E56D
- ESXST1200MM0007 to B57B - ESXST1200MM0017 to E576
- ESXSST9300605SS, ESXSST9600205SS, ESXSST9900805SS to B55E - ESXSST9300505SS, ESXSST9600105SS, ESXSST9900705SS to E558
- ESXSST9146853SS, ESXSST9300653SS to B63K
- ESXSST9146753SS, ESXSST9300553SS to E638 - ESXSST9500620SS, ESXSST91000640SS to BD2J
- ESXSHUC101212CSS60 to J2MA - ESXSHUC101212CSS61 to N2M9
- ESXSHUC156030CS420, ESXSHUC156060CS420 to J5G2 - ESXSHUC156030CSS20, ESXSHUC156060CSS20 to J2G4
- ESXSHUC156030CS420E, ESXSHUC156060CS420E to N5G2
- ESXSHUC156030CSS20E, ESXSHUC156060CSS20E to N2G4
- ESXSHUC101860CS420, ESXSHUC101890CS420, ESXSHUC101812CS420, ESXSHUC101818CS420 to J5H2 - ESXSHUC101860CS420E, ESXSHUC101890CS420E, ESXSHUC101812CS420E, ESXSHUC101818CS420E to N5H2
- ESXSHUC109030CSS60, ESXSHUC109060CSS60, ESXSHUC109090CSS60 to J2EG - ESXSHUC109030CSS61E, ESXSHUC109060CSS61E, ESXSHUC109090CSS61E to N2EG
- ESXSAL13SXB300N, ESXSAL13SXB600N to SC36
- ESXSMBF2300RC, ESXSMBF2600RC to SB2F
- ESXSMK1401GRRB, ESXSMK3001GRRB to SC2E - ESXSMK1401GRRR, ESXSMK3001GRRR to SF23 - ESXSMK3001GRDB, ESXSMK6001GRDB, ESXSMK9001GRDB to SB35
- ESXSWD3001BKHG-23D, ESXSWD6001BKHG-23D, ESXSWD9001BKHG-23D to ZA33 - ESXSWD3002BKTG-23E, ESXSWD6002BKTG-23E, ESXSWD9002BKTG-23E to ZC32
- EXSXHUSMM1620ASS20, EXSXHUSMM1640ASS20, EXSXHUSMM1680ASS20, EXSXHUSMM1616ASS20 to J4C6 - EXSXHUSMM1620ASS20E, EXSXHUSMM1640ASS20E, EXSXHUSMM1680ASS20E, EXSXHUSMM1616ASS20E to N4C6
SATA 3.5"
- WD1003FBYX-23Y7B0, WD2003FYYS-23W0B0 to WA35
- WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD37
- ST9500620NS, ST91000640NS to BE2A
- ST33000650NS to BB3A
- ST1000NM0011, ST2000NM0011 to BB4A
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5A
- HUA723020ALA640 to MK7OA930 - HUA723030ALA640 to MKAOA930
SATA 2.5"
- ST9500620NS, ST91000640NS
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB33
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to 5DV1NA36
- MZ7GE240HMHP-000M3, MZ7GE480HMHP-000M3, MZ7GE960HMHP-000M3 to EXST0CA34
NOTE TO SERVICE - Reference RETAIN TIP H29851 ******************************************* SAS Hard Disk Drive Update Program Version 1.14.04 Critical Release Reference RETAIN TIP H29851
This package includes updates to drives with product ID strings of:
SAS 2.5"
Initial code Release - SMK3001GRDB, SMK6001GRDB, SMK9001GRDB to SB35
SATA 2.5"
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to NA36 - SSDSC2BB120G4I, SSDSC2BB240G4I, SSDSC2BB400G4I, SSDSC2BB800G4I to NB37 - fix to prevent possible drive lock up during format.
SATA 1.8"
Initial Code Release - SSDSC1NA200G3I, SSDSC1NA400G3I to NA36 - SSDSC1NB080G4I, SSDSC1NB240G4I, SSDSC1NB400G4I to NB37 - fix to prevent possible drive lock up during format.
=================================================================== IBM Online SAS/SATA Hard Disk Drive Update Program Version 1.14.03-2 Build ID: SAS11403-2
NOTE TO SERVICE - Reference RETAIN TIPS H211424 & H211667 ******************************************* IBM SAS Hard Disk Drive Update Program Version 1.14.03-2 Critical Release Reference RETAIN TIP H211424 & H211667
This package includes updates to drives with product ID strings of:
SAS 3.5"
Initial Code Releases - ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5B - ST2000NM0043, ST4000NM0043 to EC59 - WD1001FYYG-23S, WD2001FYYG-23S, WD3001FYYG-23S, WD4001FYYG-23S to XA35
Other - ST1000NM0001, ST2000NM0001 to BC4A - support persistent reservation - HUS723020ALS64, HUS723030ALS64 to J3K8 - servo adjustments
SAS 2.5"
Initial Code Releases - ST300MM0006, ST600MM0006, ST900MM0006 to B56H - ST300MM0026, ST600MM0026, ST900MM0026 to E568 - TXA2D20200GA6I, TXA2D20400GA6I, TXA2D20800GA6I, TXA2D21600GA6I to GB76 - see Retain Tip H211424. - HUC101212CSS60 to J2M7 - HUC101212CSS61 to N2M7 - T1200MM0007 to B576 - T1200MM0017 to E574 - ST600MX0001 to BH13 - WD3002BKTG-23E, WD6002BKTG-23E, WD9002BKTG-23E to ZC31 - ST9500431SS to ED12 - ST9146703SS to E536 - ST973352SS to E625 - ST9300553SS to E636 - HUC109030CSS61E, HUC109060CSS61E, HUC109090CSS61E to N2EF - MK3001GRDB, MK6001GRDB, MK9001GRDB to SB35 - drive Que depth fix; see Retain Tip H211667. - HUC109030CSS60, HUC109060CSS60, HUC109090CSS60 to J2EF - HUC109030CSS61E, HUC109060CSS61E, HUC109090CSS61E to N2EF
Other - WD3001BKHG-23D, WD6001BKHG-23D, WD9001BKHG-23D to ZA32 - performance, non-critical fixes and robustness changes.
- ST9600204SS to B54A with maintainance fixes and performance improvements.
- MBD2147RC, MBD2300RC to SB1B - drive Que depth fix; - MBE2073RC, MBE2147RC to SC18 - drive Que depth fix; - MBF2300RC, MBF2600RC to SB2F - drive Que depth fix; - MK1401GRRB, MK3001GRRB to SC2E - drive Que depth fix; see Retain Tip H211667.
- ST9500620SS, ST91000620SS to BD2F - support persistent reservation and maintainance fixes.
SATA 3.5"
Initial Code Release - WD801ABYS-23C0A0, WD1601ABYS-23C0A0 to 06.06H05 - WD5003ABYX-23 to WC38 - added mfg. parameters. - WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD36 - ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB58
Other
SATA 2.5"
Initial Code Release - SG9XCS2D50GEIBM to SE6H - WD3000BLHX-23V7BV to YA31 - SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to NA34 - SSDSC2BB120G4I, SSDSC2BB240G4I, SSDSC2BB400G4I, SSDSC2BB800G4I to NB34
Other - ST9250610NS, ST9500620NS, ST91000640NS to BE29 - maintainance updates. - MTFDDAK064MAR-1J1AA, MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA, MTFDDAK512MAR-1K1AA to MA57 - added mfg. parameters.
SATA 1.8"
Initial Code Release - SSDSC1NA200G3I, SSDSC1NA400G3I to NA34 - SSDSC1NB080G4I, SSDSC1NB240G4I, SSDSC1NB400G4I to NB34
Other - MTFDDAA064MAR-1J1AB, MTFDDAA128MAR-1J1AB, MTFDDAA256MAR-1K1AB, MTFDDAA512MAR-1K1AB to MA57 - added mfg. parameters.
=================================================================== Version 1.13.01 Build ID: SAS_113
NOTE TO SERVICE - Reference RETAIN H207993
******************************************* IBM SAS Hard Disk Drive Update Program Version 1.13.01 Critical Release Reference RETAIN H207993
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- HUS723020ALS64 to J3K7 Additions to VPD information used by manufacturing and fixes for overall robustness.
- HUS723030ALS64 to J3K7 Initial Code Release
- ST31000424SS, ST32000444SS to BC2D - ST1000NM0001, ST2000NM0001 to BC49 Fixes for overall robustness.
- ST33000650SS to BC3E Initial Code Release
SAS 2.5"
- MK1401GRRB, MK3001GRRB to SC29 Fixes for overall robustness.
- MBF2300RC, MBF2600RC to SB2C Initial Code Release.
- ST9300605SS, ST9600205SS, ST9900805SS to B55D ST9146853SS, ST9300653SS to B63B ST9500620SS, ST91000640SS to BD2E ST9300505SS, ST9600105SS, ST9900705SS to E557 ST9146753SS to E636 Additions to VPD information used by manufacturing and fixes for overall robustness.
SATA 3.5"
- ST500NM0011, ST2000NM0011, ST1000NM0011 to BB4A ST3500514NS, ST31000524NS, ST32000644NS to BB2C Reliability improvements, Additions to VPD information used by manufacturing
- ST33000650NS to BB3A Initial Code Release
- WD5003ABYX-23 to WC36, WD1003FBYX-23Y7B0 to WB35, WD2003FYYS-23W0B0 to WA35 Reliability improvements, Additions to VPD information used by manufacturing
- HUA723020ALA640 to MK7OA910 Additions to VPD information used by manufacturing.
- HUA723030ALA640 to MKAOA910 Initial Code Release
- HUA722050CLA330, HUA722010CLA330 to A3PH Initial Code Release
SATA 2.5"
- TE22D10100GE8IBM to SR3B Initial Code Release
- MTFDDAK064MAR-1J1AA, MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA, MTFDDAK512MAR-1K1AA to MA55 Initial Code Release
- ST9250610NS, ST9500620NS, ST91000640NS to BE28 Fixes for overall robustness.
SATA 1.8"
- MTFDDAA064MAR-1J1AB, MTFDDAA128MAR-1J1AB, MTFDDAA256MAR-1K1AB, MTFDDAA512MAR-1K1AB to MA55 Initial Code Release
- TX21B10100GE8IBM, TX21B10200GE8IBM, TX21B10400GE8IBM to SP3A Initial Code Release
Version 1.12.01 Critical Release Reference RETAIN #H207740
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA450900EST1, VPCA600900EST1 to A3C4, Corrects firmware bug that may cause data corruption. For further information, please refer to Retain Tip H207740.
- ST3300657SS, ST3450857SS, ST3600057SS to BA5A VPCA300900EST1, VPCA600900EST1 to A3C2 Additions to VPD information used by manufacturing
- ST3750630SS, ST31000640SS to BC1I ST31000424SS, ST32000444SS to BC2C Mode Page change to address performance issues under certain system configurations
- ST33000650SS to BC3D ST1000NM0001, ST2000NM0001 to BC48 Protection Information Fix - see Retain Tip H206140
- HUS723020ALS64, HUS723030ALS64 to J26C Initial Code Release
SAS 2.5"
- ST9300603SS, ST9146803SS to B53E ST9600204SS to B549 Additions to VPD information used by manufacturing
- ST9300605SS, ST9600205SS, ST9900805SS to B55C ST9146853SS, ST9300653SS to B63A ST9500620SS, ST91000640SS to BD2C ST9300505SS to E555 ST9146753SS to E635 Protection Information Fix - see Retain Tip H206140
- ST9600105SS, ST9900705SS to E555 Inital Code Release
- HUC106030CSS60, HUC106060CSS60 to D3A6 Performance improvements, critical fixes for Protection Information (PI) operation - see Retain Tip H206140
- MK1401GRRB, MK3001GRRB to SC27 Additions to VPD information used by manufacturing
- WD9001BKHG-23D, WD6001BKHG-23D, WD3001BKHG-23D to ZA31 Initial Code Release
SATA 3.5"
- WD2502ABYS-23B7A0 to 02.03B08 WD1602ABYS-23B7A0 to 02.03B07 Critical fix to address premature drive failures.
- ST3500514NS, ST31000524NS, ST32000644NS to BB2A ST33000650NS to BB38 ST1000NM0011, ST2000NM0011, ST500NM0011 to BB47 Fixes a potential, but rare data corruption issue which requires a background reallocation that exceeds the error recovery timer.
- HUA723020ALA640 to MK70A900 HUA723030ALA640 to MKA0A900 Initial Code Release
SATA 2.5"
- ST9160511NS, ST9500530NS to BE1A - ST9250610NS, ST9500620NS, ST91000640NS to BE25 Fixes a potential, but rare data corruption issue which requires a background reallocation that exceeds the error recovery timer.
SSD
- TX21B10200GE1IBM, TX21B10400GE1IBM, TX21B10100GE8IBM to PRO6SP36 TE22D10100GE8IBM to PRO6SR36 Initial Code Release
- MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA to MA52 Initial Code Release
- MTFDDAA512MAR-1K1AB, MTFDDAK064MAR-1J1AA, MTFDDAK512MAR-1K1AA, MTFDDAA064MAR-1K1AB, MTFDDAA128MAR-1K1AB, MTFDDAA256MAR-1K1AB to MA52 Fixes SMART attribute 190 (Current Temp) which caused warning messages with some versions of Linux
- STEC MACH8 IOPS to 2804 STEC M8PSB2 T4 to SM06 Additions to VPD information used by manufacturing Fixes potential drive failure if power loss occurs during firmware update.
- ST33000650SS to BC3A ST1000NM0001, ST2000NM0001 to BC44 Additions and corrections to VPD information used by manufacturing
SAS 2.5"
- ST9300605SS, ST9600205SS, ST9900805SS to B559 ST9146853SS, ST9300653SS to B637 ST9500620SS, ST91000640SS to BD29 ST9300505SS to E553 SST9146753SS to E633 HUC106030CSS60, HUC106060CSS60 to D390 Additions and corrections to VPD information used by manufacturing
- MK1401GRRB, MK3001GRRB to SC23 Fixes a pottential data corruption bug if there is an unexpected power loss.
SATA 3.5"
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15 ST3500514NS, ST31000524NS, ST32000644NS to BB29 ST33000650NS to BB36 ST1000NM0011, ST2000NM0011, ST500NM0011 to BB46
SATA SSD
- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB6C SG9XCS2D200GEIBM to SA03SE6C Fix for potential hang during an unexpected power cycle
MTFDDAK128MAR-1JAAB, MTFDDAK256MAR-1JAAB to MA44 Initial Release
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA600900EST1 to A3C0 Correction to VPD information used by manufacturing
- ST31000424SS, ST32000444SS to BC2B Fixes to improve robustness from certain read errors due to encroachment
- ST33000650SS to BC37 Fixes to improve overall robustness.
- ST1000NM0001, ST2000NM0001 to BC42 Inital Release
SAS 2.5" (SFF)
- ST9300605SS, ST9600205SS, ST9900805SS to B556 - ST9146853SS, ST9300653SS to B635 Fixes to improve overall robustness.
ST9300505SS to E552 ST9146753SS to E632 Initial Release
- ST9500620SS, ST91000640SS to BD26 Improve general robustness and added support for DPICZ
- HUC106030CSS60, HUC106060CSS60 to D340 Improve general robustness
- MBF2300RC, MBF2600RC to SB28 Improves performance in certain benchmarks
SATA 3.5"
- ST33000650NS to BB34 Fixes to improve overall robustness.
- ST1000NM0011, ST2000NM0011, ST500NM0011 to BB45 Initial Release
- ST3500514NS, ST31000524NS, ST32000644NS to BB29 Fixes for intermittent drive hangs
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15 Added enhancement for improved robustness
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NS to BE24 Initial Release
- ST9160511NS, ST9500530NS to BE19 Fixes for overall robustness.
SATA 2.5" SSD
- STEC MACH8 IOPS to 2765 STEC M8PSB2 T4 to SM05 Fixes potential drive lock up during cold or warm boots Fixes issues with RHEL 6.x installation
- SG9XCS2D200GEIBM to SA03SE6C Fixes default drive VPD information for manufacturing, the default LED behavior on certain systems and fixes issues with client install thru VMWare 5.x
SATA 1.8" SSD
- STEC M8PSB1 to 0409 STEC M8PSB1 T4 to SM16 Fixes potential drive lock up during cold or warm boots Fixes issues with RHEL 6.x installation
- SG9XCS1B50GMIBM to SA03SB6C SASG9XCS1F200GEIBM to SA03SB6C Fixes potential drive lock up during cold or warm boots and the default LED behavior on certain systems and fixes issues with client install thru VMWare 5.x
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- ST31000424SS, ST32000444SS to BC28 Added enhancement for improved RV robustness
- MBE2073RC, MBE2147RC to SC17 - MBA3073RC, MBA3147RC, MBA3300RC to SA0A Added VPD changes for manufacturing
SAS 2.5" (SFF)
- ST9300603SS, ST9146803SS to B53C ST9600204SS to B548 SST973452SS, ST9146852SS to B62C CBRCA146C3ETS0, CBRCA300C3ETS0 to C610 Added fixes for overall drive robustness
- MBD2147RC, MBD2300RC to SB1A Added VPD changes for manufacturing Addresses issues seen with DSA HDD Diagnostic test.
- MBF2300RC, MBF2600RC to SB25 Addresses issues seen with DSA HDD Diagnostic test.
- ST9500620SS, ST91000640SS to BD22 HUC106030CSS60, HUC106060CSS60 to D2F8 Inital Release
SATA 3.5"
- WD2502ABYS-23B7A0 , WD1602ABYS-23B7A0 to 02.03B07 Addresses firmware issues that may cause a drive to be marked defunct prematurely under certain application workloads.
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB14 ST3500514NS, ST31000524NS, ST32000644NS to BB28 Added enhancement for improved robustness
- WD5003ABYX-23 to WC31 Initial Release
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V10 (Critical) Addresses firmware issues that may cause a drive to be marked defunct prematurely under certain application workloads.
- ST9250610NS, ST9500620NS, ST91000640NS to BE21 Initial Release
SATA 2.5" SSD
- STEC MAC8 IOPS to 2732 STEC M8PSB2 T4 to SM04 Addresses an issue installing RHEL 6.0 onto this drive.
SATA 1.8" SSD
- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB63 Addresses rare issue where the drive may not being seen on power up.
- STEC M8PSB1 to 0408 STEC M8PSB1 T4 to SM15 Addresses an issue installing RHEL 6.0 onto this drive.
- ST373455SS, ST3146855SS, ST3300655SS to BA2D - ST373355SS, ST3146755SS, ST3300555SS to BA38 - ST3146356SS, ST3300656SS, ST3450856SS to BA4C - ST3300657SS, ST3450757SS, ST3600057SS to BA58 - ST3750630SS, ST31000640SS to BC1G - ST31000424SS, ST32000444SS to BC26 (All Above Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- MBA3073RC, MBA3147RC, MBA3300RC to SA08 This code corrects a firmware bug that may cause the drive to not come ready on a cold boot.
SAS 2.5" (SFF)
- ST973402SS, ST9146802SS to B52B - ST936751SS, ST973451SS to B617 - ST9146803SS, ST9300603SS toB53B - ST9600204SS to B546 - ST973452SS, ST9146852SS to B629 - ST9300503SS to E536 - ST9146752SS to E625 - ST9500430SS to BD14 (All Above Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
SATA 3.5"
- ST3500514NS, ST31000524NS, ST32000644NS to BB26
- WD2003FYYS-23W0B0 to WA32 - WDC WD1003FBYX-23Y7B0 to WB31 Initial release
SATA 2.5" SSD
- STEC MACH8 IOPS to 2582 (Critical) Corrects firmware bug that may cause data corruption. For further information, please refer to retain tip H197650.
SATA 1.8" SSD
- STEC M8PSB1 to 0405 (Critical) Corrects firmware bug that may cause data corruption. For further information, please refer to retain tip H197650.
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA450900EST, VPCA600900EST1 to A3B8 Initial Release
- VPBPA300C3EST1 to A529 Initial Release
- ST3300657SS, ST3450757SS, ST3600057SS to BA56 (Critical) Performance improvements under certain workloads. Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST31000424SS, ST32000444SS to BC21 Initial Release
SAS 2.5" (SFF)
- ST9300603SS, ST9146803SS to B53A (Critical) Performance improvements under certain workloads. Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST9600204SS to B544 (Critical) Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST973452SS, ST9146852SS to B626 Performance improvements under certain workloads.
- ST9500430SS to BD13 Performance improvements under certain workloads
- ST9300503SS to E534 and ST9146752SS to E623 Performance improvements under certain workloads.
- MBD2147RC, MBD2300RC to SB19 (Critical) MBE2073RC, MBE2147RC to SC16 (Critical) Corrects a firmware bug that erroneously reported medium errors which may cause the drive to report PFA alerts and in some cases be marked offline
SATA 3.5"
- WDC WD2502ABYS-23B7A0, WD2502ABYS-23B7A0, WD802ABYS-23B7A0, WD1602ABYS-23B7A0 to 02.03B05 (Critical) Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST3500514NS, ST31000524NS, ST32000544NS to BB26 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB13 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- HUA722020ALA330 to JKAOA3GA HUA722050CLA330 to JP2OA3GB HUA722010CLA330 to JP4OA3GB Initial Release
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V09 (Critical) This code corrects an additional issue where the drive may be marked defunct.
- ST9160511NS, ST9500530NS to BE18 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382. Also improves performance under certain workloads.
SATA 2.5" SSD
- STEC MACH8 IOPS to 2366 (critical) Corrects firmware bug that may cause degraded performance and in some cases the drive may not come ready after a warm or old boot.
SATA 1.8" SSD
- STEC M8PSB1 to 0404 Turns the default for write cache off Initial Release
IBM SAS Hard Disk Drive Update Program Version 1.06 (Critical)
Added support for the following controllers:
- IBM ServeRAID BR10il SAS controller v2 (49Y4731) - IBM ServeRAID M1015 SAS controller (46M0831) - IBM ServeRAID M5015 SAS controller (46M0829) - IBM ServeRAID M5014 SAS controller (46M0916)
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- ST373455SS, ST3146855SS, ST3300655SS to BA2A ST373355SS, ST3146755SS, ST3300555SS to BA36 (Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
- ST3750630SS, ST31000640SS to BC1E ST3146356SS, ST3300656SS, ST3450856SS to BA4A This code address an issue where the drive may report an erroneous hardware error to the controller.
- MBA3073RC, MBA3147RC, MBA3300RC to SA07 This code improves sequential write performance under certain workloads when write cache is turned on.
- ST3300657SS, ST3450757SS, ST3600057SS to BA52 NOTE: This is the first code release to be included in the hard drive update package.
SAS 2.5" (SFF)
- ST973402SS, ST9146802SS to B52A ST936751SS, ST973451SS to B616 (Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
- MBB2073RC, MBB2147RC to SB07 MBD2147RC, MBD2300RC to SB17 MBE2073RC, MBE2147RC to SC14 CBRCA146C3ETS0, CBRCA300C3ETS0 to C370 This code improves sequential write performance under certain workloads when write cache is turned on.
- ST9500430SS to BD11 This is the first code release to be included in the hard drive update package.
SATA 3.5"
- WD2003FYYS-23T8B0 to 01.00D04 This is the first code release to be included in the hard drive update package.
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V08 (Critical) This code corrects an issue where the drive may generate a false PFA alert. It also corrects an issue where the drive may be marked defunct
- ST9160511NS, ST9500530NS to BE16 This is the first code releases to be included in the hard drive update package.
=============================================================== IBM SAS Hard Disk Drive Update Program Version 1.05
SAS 2.5" (SFF)
ST9xxxx51SS to B616 ST9xxxx02SS to B52A - This code improves the robustness of write cache operations.
ST9xxxx52SS to B624 ST9xxxx03SS to B536 - This code improves the robustness of write cache operations and sequential write performance when write cache is enabled
MBD2xxxRC to SB14 - Initial release
SAS 3.5"
ST3xxxxx6SS to BA49 ST3750630SS to BC1D - This code improves the robustness of write cache operations.
SATA 3.5"
WDC WD2502ABYSxxxxx tp 02.03B04 - Fixes incorrect VPD data
SATA 2.5"
WD3000xxxxx to 04.04V05 - Adjusted PHY setting for better signal quality margin.
SATA 2.5" SSD
STEC MACH8 IOPS to 2269 GBRL0xxxxx to 4.17 GBRLBxxxxx to 4.26 - The new firmware will correct a rare data error condition in the drives where invalid data may be passed to the system without any error condition flagged.
Due to the severity of this potential issue, IBM strongly recommends applying this firmware as soon as possible.
For further information, please refer to retain tip H195663. =================================================================
IBM SAS Hard Disk Drive Update Program Version 1.04
SAS 2.5" (SFF)
CBRBAxxxxxx to C49B - Modified VPD for JSxx Blades
MBBxxxxxx to SB05 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller
MBC2073RC to SC04 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller
SAS 3.5"
MBAxxxxxx to SA06 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller
ST3xxxxx6SS to BA48 - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632
ST3750630SS to BC1A - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632
- Fixes a hang condition during failover operation on a Bladecenter-S chassis with an RSSM controller.
BBAxxxxxx to BH0K - Fixes an issue where a drive may prematurely report a PFA trip
GNAxxxxxx to BH0J - Fixes an issue where a drive may prematurely report a PFA trip
SATA 3.5"
ST31000340NS, ST370330NS, ST3250310NS, ST3500320NS to BB12 - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632
- This code addresses a rare potential for data loss. After a power cycle, the drive will no longer be available and becomes unresponsive. Data will become inaccessible due to the drive not responding. For further information, please refer to retain tip H194623.
WDC WD2502ABYSxxxxx tp 02.03B04 - Fixes incorrect VPD data
SATA 2.5"
WD3000xxxxx to 04.04V04 - Fixes a Critical issue - IBM recommends a backup of the data on the drive before attempting to update the firmware. This is a fix for an issue where data required for spinup of the drive may be overwritten rendering the drive inoperable on a subsequent warm or cold system reboot.
- Fixes a issue with an internal timer that may cause drive to go offline when used in a non-raid environment.
IBM SAS Hard Disk Drive Update Program Version 1.03
Added support for the following controllers:
IBM ServeRAID MR10il SAS Controller IBM ServeRAID MR10is SAS Controller IBM ServeRAID BR10i SAS Controller IBM ServeRAID BR10il SAS/SATA Controller IBM SAS/SATA RAID Kit IBM SAS Expansion Card (CFFv) for IBM BladeCenter IBM SAS Connectivity Card (CFFv) for IBM BladeCenter
New updates to drives with product ID strings of:
SAS 2.5" (SFF)
ST9146802SS, ST973402SS to B529 - Added support for JS2x Blades in a Bladecenter-S chassis - Picked up the latest network roll of firmware fixes to address some unexpected system hangs,
ST936751SS, ST973451SS to B615 - Added support for JS2x Blades in a Bladecenter-S chassis - Picked up the latest network roll of firmware fixes to address some unexpected system hangs,
CBRBAxxxxxx to C495 - Initial release
MBBxxxxxx to SB04 - Initial release
MBC2073RC to SC03 - Initial release
SAS 3.5"
VPBAxxxxxx to A496 - Added support for JS2x Blades in a Bladecenter-S chassis
ST3146855SS, ST3300655SS, ST373455SS to BA29 - Added support for JS2x Blades in a Bladecenter-S chassis - Picked up the latest network roll of firmware fixes to address some unexpected system hangs,
ST3450856SS to BA47 - IBM was notified by our vendor that there is a defect in a level of firmware used in the IBM 450GB 15K SAS 3.5" HS HDD (PN 41Y8454) in option 42D0519, which under certain conditions may lead to data being written or read back incorrectly on the drive. IBM has worked closely with the vendor to identify the problem and developed a firmware fix to resolve the problem. Customers should upgrade to firmware level BA47
MBAxxxxxx to SA05 - Initial release
ST3750630SS to BC17 - Initial release
SATA 3.5"
ST3250620NS, ST3500630NS, ST3750640NS to 3.AEV
ST3250621NS, ST3500631NS, ST3750641NS to 4AEV
ST31000340NS, ST3750330NS, ST3250310NS, ST3500320NS to BB10 - Initial release
HUA721050KLA330, HUA721075KLA330, HUA721010KLA330, to AB4A - Initial Release
SATA 2.5" SSD
GBRL001xxx, GBRL0031xxx to 4.14 - corrects intermittent hangs during operations =============================================================
IBM SAS Hard Disk Drive Update Program Version 1.02
Support of ServeRaid 8s Raid controller Support of ServeRaid 10i Raid controller Support of ServeRaid 10k Raid controller Support of ServeRaid 10m Raid controller Support of LSI 1078 SAS controller Support of SATA drives attached to SAS controllers
Support and updates to drives with product ID strings of:
VPAxxxxxx to A650 Change to improve performance in sequential write workloads Improvements to internal drive logging and media checking. Critical Fix: This code addresses a rare potential for data loss This code update should be applied to prevent the event from occurring.
ST340XXXAS and ST380XXXAS to 3.48 Fix to address Read Log Command abort error.
ST340XXXAS, ST380XXXAS and ST3160XXXAS to 3.05 Fix to address intermittent hard drive no-shows after system comes out of hibernation.
ST3500641NS to 3.AES Changes to the refresh rate of the DRAM used on the drive.
ST3500640NS to 3.AEJ Initial release.
HDTXX... & HDSXX... codes go to Masked ROM version. HDS725050KLA360 to AQ1A to also Fix an issue that occurs while running in NCQ mode with write cache disabled.
ST3xxxx4SS to BA26 Improves intialization times with some ServeRaid controllers Performance improvements under some sequential workloads.
ST3xxxx5SS to BA35 Improves intialization times with some ServeRaid controllers
ST9xxx51SS to B612 Intial release of firmware
ST9xxxx2SS to B526 Improves intialization times with some ServeRaid controllers
MAUxxxx and MAXxxxx Added support for new SAS features required by new SAS controllers.
IBM SAS Hard Disk Drive Update Program Version 1.01 Please refer to RETAIN tip H186019.
Support of ServeRaid 8e Raid controller Support of ServeRaid 8k Raid controller Support of ServeRaid 8l Raid controller Support of on-board LSI 1064 controller IBM MegaRaid 8480 Raid Controller
Firmware updates to drives with Product ID strings:
GNAxxxx and BBAxxxx to BH0G Picks up the latest network roll of firmware fixes to improve performance under some sequential workloads and improvements to signal quality parameters.
ST9xxxx to B51D amd ST3xxxx to BA18 Picks the latest network roll of firmware fixes to address unexpected system hangs and some performance improvements.
MAVxxxx to S116 and MAYxxxx to T107 Picks up the latest network roll of firmware fixes and to improve signal quality parameters.
MAXxxxx to T904 Initial release ============================================================
IBM SAS Hard Disk Drive Update Program Version 1.00 Initial Release
Support of Adaptec 48xxx based controllers Support of ServeRaid 8i Raid controller Support and updates to drives with product ID strings of: ST936701SS ST973401SS ST336754SS ST373454SS GNAxxxxx BBAXXXXX
ibm_fw_hddlenovo_sas-1_23_02_linux_32-64_chg
ServeRAID M and MR10 Series SAS Controller Driver for Linux (also supports MegaRAID 8480 SAS Controller)
Adapters Supported: - ServeRAID M1215 SAS/SATA Controller for IBM System x (46C9114) - ServeRAID M5210e SAS/SATA Controller for IBM System x - ServeRAID M5210 SAS/SATA Controller - ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481) - ServeRAID M5110e SAS/SATA Controller for IBM System x - IBM Flex System Storage Expansion Node - ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478) - ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304) - ServeRAID M5115 SAS/SATA Controller for IBM System x (90Y4390) - ServeRAID M5015 SAS/SATA controller (46M0829) - ServeRAID M5014 SAS/SATA controller (46M0916) - ServeRAID M1115 SAS/SATA Controller for IBM System X (81Y4448) - ServeRAID M1015 SAS/SATA Controller (46M0831) - IBM ServeRAID MR10il SAS controller (44E8767) - IBM ServeRAID MR10is SAS controller (44E8695) - IBM ServeRAID MR10ie (CIOv) SAS controller (46C7167) - IBM ServeRAID MR10i SAS controller (43W4296) - IBM ServeRAID MR10k SAS controller (43W4280) - IBM ServeRAID MR10M SAS controller (43W4339) - MegaRAID 8480 SAS controller (39R8850)
Supported Kernels: SLES 12 3.12.28.4
NOTE TO SERVICE - Reference RETAIN #N/A
Version 6.812.08.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes: - Modified not to send outstanding IOs back to SML with DID_RESET host_byte but return IOs back with host_byte DID_REQUEUE before doing OCR. SCGCQ01278656 (Port Of Defect SCGCQ01231846)
Enhancement - Added support for SLES 12.2
Version 6.812.07.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes - Changed timeout value for DCMDs get_bios_data and get_pd_info 180 seconds to keep it aligned with other DCMDs' timeout value. (SCGCQ00884247) - Do not allow MFI frame to be freed from DCMD fire context when already an OCR is in progress. (SCGCQ00879190) - Fixed an issue where driver always worked in non RDPQ mode even the running firmware did not support RDPQ. (SCGCQ00872542) - Moved SCSI layer interaction code out of reset_mutex in AEN thread to prevent deadlock around “reset_mutex”. (SCGCQ00868731) - Convert supported JBOD count value returned by firmware in CPU format and then use the same value for further validation (SCGCQ00837088) - Fixed an issue where unevenSpan configuration of R1 would not have proper load balancing for FP READ. SCGCQ00646224 - Added timeout value for wait_event. (SCGCQ00249742) - Enabled hostlockless flag of SCSI host for RHEL6 and clones for async IO submission from SCSI mid layer. (SCGCQ00884242) - Fixed an issue where double freeing of MFI frame in case of MFI IO timeout in polled mode could occur. (SCGCQ00837932) - Added synchronization between OCR thread and AEN thread, so that there should not be any PCI write from AEN thread during OCR (SCGCQ00836410) - Added IO timeout value for SCSI management commands for JBOD. (SCGCQ00750452) - Fixed a JBOD performance issue due to incorrect MSI-x index set in request desc. (SCGCQ00619694) - Changed state machine of firmware crash dump collection to prevent file system on VD being set to Read-only mode after ECC error injection. (SCGCQ00608705) - Fixed an issue where incorrect messages such as “LSI SAS2.0” were printed for MR driver. (SCGCQ00298201_ - Fixed an issue where the driver sent an incorrect region type "REGION_LOCK_EXCLUSIVE" set to FW for RAID level >=5 - Changed error handling for DCMD failure cases to allow graceful exit for not fatal errors. (SCGCQ00868661) - Free task management frame after dumping the task management reply frame data to ensure that TM reply frame will have valid data returned by firmware. (SCGCQ00860038) - Release reset_mutex inside OCR function, if adapter is already killed to prevent a kernel panic. (SCGCQ00857740) - Increased timeout to 180 seconds for flush cache and shutdown controller DCMDs to prevent kernel panic when DCMDs fired during driver's shutdown. (SCGCQ00841491) - Fixed an issue where traversed LDs at multiple places up to maximum 256 were limited to 64. (SCGCQ00652795) - Fixed an issue where the driver crashed when msix_disable=1 was passed to the boot time parameter. (SCGCQ00383508) - Fixed an issue where kernel panic seen while deleting VD and background IOs running. (SCGCQ00803468) - Fixed an issue where the driver was not sending DCMD- MR_DCMD_CTRL_SET_CRASH_DUMP_PARAMS after OCR. (SCGCQ00601138) - Fixed an issue where the kernel panicked inside PCI subsystem because of IRQs not freed before disabling MSI-X interrupts (SCGCQ00827403) - Disabled SED drive JBOD support. (SCGCQ00751296) - Fixed multiple OCRs triggering hits Exception Core issue (SCGCQ00707592) - Fixed an issue where the firmware faulted due to invalid regionlock Flags set by Driver. (SCGCQ00796461) - Fixed an issue where subsequent reads of state value from hardware resulted different values and could lead to a timeout in and a non working adapter. (SCGCQ00709216) - Fixed an issue where Offline VD caused boot hangs in SLES 11 (SCGCQ00284564) - Disabled SPAN_DEBUG and set get_arm_from_strip to print if firmware supports UnevenSpan. (SCGCQ00365846) - Added check to validate “ldcount” exposed in firmware RAID map for legacy firmware. If ldcount is more than 64, fail RAID map validation. (SCGCQ00820349) - Fixed an issue where the Linux kernel crashed when AEN and LD Sync commands were issued frequently. (SCGCQ00712031) - Fixed an issue where duplicate disk(s) were seen on controller after loading Linux driver during OS installation, (SCGCQ00568992) - Fixed an issue where kernel panic could occur at driver load time on 3.0 kernels (i.e. SLES11 SP2, SLES11SP3). (SCGCQ00561505) - Changed driver to return SCSI command back to mid layer if the controller has any critical hardware errors. SCGCQ00362023 - Fixed an issue where the driver did not do Load balance for R1 READ due to wrong stats counters. (SCGCQ00677516 Port of Defect - SCGCQ00674872) - Fixed potential duplicate IOCinit frames being fired by VMware5 VF driver during OCR. (SCGCQ00571967 PORT OF SCGCQ00571679) - Fixed OS crash issue on SCSI IO timeout (SCGCQ00631210 PORT OF SCGCQ00625137) -Fixed an issue where the kernel panicked due to MFI/MPT pass-through command timeout and later finished from Interrupt context. (SCGCQ00307867 PORT OF - SCGCQ00302080) - Fixed an issue where megasas_poll_wait_aen was cleared before poll syscall returns causing to lose events (SCGCQ00575192 PORT OF SCGCQ00574787) -Fixed an issue where data corruption observed on JBODs while running IOs with 32k block size. (SCGCQ00530992 PORT OF SCGCQ00523780) - Fixed MPC kernel panic during chassis power cycle if AEN completes and detach is called before event workqueue runs. (SCGCQ00647390 PORT OF SCGCQ00645836) - Fixed an issue where kernel crashed in some cases, where megaraid_sas driver is loaded but controller is not present. (SCGCQ00282968 PORT OF SCGCQ00282067)
Enhancements: - Set queue depth for syspD based on interface type (SCGCQ00879700) - Updated module Meta data (module description and module author) with Avago replacing LSI. (SCGCQ00801961) - Set OS provided timeout value for sysPD non read-write IOs (SCGCQ00764795) - Performance tuning for SMP affinity is implemented for distros's which support irq_set_affinity_hint API. (SCGCQ00623697) - Optimized OCR path to enable interrupt and make HBA OPERATIONAL after driver has fired LD_MAP_GET_INFO DCMD. (SCGCQ00768402) - Added module parameter to turn on/off SMP affinity code. (SCGCQ00666706) - Driver will do load balance for N Drive Raid 1 volumes. (SCGCQ00634064) -Functionality in driver is added to differentiate between iMR and MR at firmware initialization time. (SCGCQ00361244) - Uneven Span support added in Driver. (SCGCQ00319104) - Driver code is updated such way that it can work for any block size drive, if the rest of the system has proper support for the same. (SCGCQ00259244) - Implemented online controller reset if controller is not responding at driver load time. (SCGCQ00820389) - Added SCSI residual bytes support to the megaraid_sas Linux driver (SCGCQ00347089) - Use sequence number for JBOD FastPath I/O’s to eliminate command block after drive replacement (SCGCQ00806534) - Big endian architecture support added for MR Linux driver (SCGCQ00526911) - Driver support is added for 3108 C0 chip combine reply queue ON (SCGCQ00354586) - Added support 240 VD feature (SCGCQ00622703) - Added Firmware crash dump collection support (SCGCQ00550369) - Added support for large I/O 1MB transfer size (SCGCQ00816313) - Changed the max sg table size to 64. Old setting was 70 (SCGCQ00653992) - Added driver support for task management for Jbod or VD (tmCapable) (SCGCQ00854635) - Added support for SED JBOD in MR Linux driver (SCGCQ00711555) - Changed code to complete IOCtl’s posted just before a kill adapter so user space applications do not hang. (SCGCQ00759916)
Version 6.810.09.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes:
- Fixed an issue where deadlock may occur when the Automatic Event Notification thread runs in parallel with error handler thread (SCGCQ00911332, Port of SCGCQ00868731)
- Fixed an issue where driver will operated in RDPQ mode regardless of whether firmware has advertised support or not (SCGCQ00872542)
- Fixed an issue where system may reset with error "BUG: unable to handle kernel NULL pointer dereference at 00000000000000d0" preceded by error "megasas: target reset FAILED!!" (SCGCQ00875223)
- Fixed an issue where driver MFI frames could be freed twice (SCGCQ00879190)
- Fixed an issue where some out-of-band commands had different timeouts than others (SCGCQ00884247)
- Fixed an issue where performance was lower on async IO submissions from the SCSI mid layer (SCGCQ00884242)
- Fixed an issue where a kernel panic may occur if the system is reset or fail to reboot (SCGCQ00859634, Port of SCGCQ00857740)
- Fixed an issue where Task Management frames were not being dumped after the Tast Management Reply frame data (SCGCQ00860038)
- Fixed an issue where a fatal error may occur when an out-of-band command times out during an Online Controller Reset (SCGCQ00882011, Port of SCGCQ00868661)
- Fixed an issue where kernel may hang when many commands are timing out or many Automatic Event Notifications are being processed (SCGCQ00857245)
- Fixed an issue where megaraid_sas module was not being included inside initrd/initramfs (SCGCQ00880965)
- Fixed an issue where kernel may panic if driver does not setup IRQs for non-MSI-x interrupt mode (SCGCQ00870263, Port of SCGCQ00867873)
- Fixed an issue where driver return code is based on command completion rather than command return code (SCGCQ00856103, Port of SCGCQ00856089)
- Fixed an issue where Tape drives may not be detected by the Operating System (SCGCQ00914385, Port of SCGCQ00911702)
- Fixed an issue where max_sectors per IO request may be set to more than firmware can handle (SCGCQ00917992, Port of SCGCQ00917399)
- Fixed an issue where an IERR may occurr on heavy IO with Failover (SCGCQ00864111, Port of SCGCQ00736612)
Enhancements:
- Enhanced queue depths in driver for physical disks based on interface type (SCGCQ00879700)
- Improved naming of internal functions (SCGCQ00866064)
- Enhanced reply queue to support queue depth greater than 1K (SCGCQ00853521)
- Added feature for driver to support Task Management for JBOD and Virtual Drives (SCGCQ00854635)
- Added module parameter to disable 1M IO support and set default to enable 1M IO support (SCGCQ00911362)
- Enhanced tasklet initialization so it would occur before setting up IRQs (SCGCQ00914393, Port of SCGCQ00911709)
- Simplified HB handling for SR-IOV (SCGCQ00864113, Port of SCGCQ00700580)
- Enhanced driver to update Online Controller Reset capability when it changes (SCGCQ00914389, Port of SCGCQ00908352)
- Added feature to print Critical, Fatal and Dead firmware events into system logs (SCGCQ00868723, SCGCQ00882010, Port of SCGCQ00866176)
- Enhanced HB handling to align with behavior on other Operating Systems (SCGCQ00864117, Port of SCGCQ00707323)
- Removed excess dead code (SCGCQ00850012)
Version 6.808.16.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes: - Fixed an issue where a deadlock may occur around reset_mutex when Automatic Event Notification threads run in parallel with error handlers - (SCGCQ00911332, Port of SCGCQ00868731) - Fixed an issue where scanning of Tape drives does not occur depending on whether the drive state is set to systemPD or not - (SCGCQ00914385, Port of SCGCQ00911702) - Fixed an issue where max_sectors may be set larger than what firmware can support - (SCGCQ00917992, Port of SCGCQ00917399) - Fixed an issue where kernel may panic due to driver not setting up IRQs for non MSI-x interrupt mode - (SCGCQ00870263, Port of SCGCQ00867873) - Fixed an issue where driver may halt firmware due to improper error handling for DCMD failure cases - (SCGCQ00882011, Port of SCGCQ00868661) - Fixed an issue where driver may hang kernel due to deadlock - (SCGCQ00857245) - Fixed an issue where system may crash due to timeout for flushing cache and shutting down controller DCMDs was not long enough - (SCGCQ00841491) - Fixed an issue where deadlock may occur between Online Controller Reset and Automatic Event Notification processing function - (SCGCQ00846933) - Fixed an issue where PCI writes from Automatic Event Notification thread were occurring during Online Controller Reset - (SCGCQ00836410) - Fixed an issue where MFI frames linked list may corrupt due to double-freeing of frame in the case of an MFI IO timeout - (SCGCQ00837932) - Fixed an issue where kernel may panic inside PCI subsystem due to IRQs not freed before disabling MSI-X interrupts - (SCGCQ00827403) - Fixed an issue where ldcount was not validated for non-240VD firmware - (SCGCQ00820349) - Fixed an issue where a command block would occur for JBODs with FastPath IOs after a drive is replaced - (SCGCQ00806534) - Fixed an issue where 1MB IO support was not supported controller-wide - (SCGCQ00816313)
Enhancements: - Set DMA alignment to 8 bytes for PI-enabled VDs - (SCGCQ00928796, Port of SCGCQ00928176) - Added a parameter to support disabling 1MB IO support - (SCGCQ00911362) - Added support for printing Critical, Fatal and Dead Firmware events into system logs - (SCGCQ00882010, Port of SCGCQ00866176) - Added support for driver to perform an Online Controller Reset at driver load time if the controller is not responding - (SCGCQ00820389)
Version 6.808.14.00 - Initial release -------------------
ibm_dd_sraidmr_6_812_08_00_sles12_32-64_chg
=============================================================================== Emulex NIC Device Driver for Linux ===============================================================================
Device Driver Version: 11.2.1193.31 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support
Device Driver Version: 10.2.363.0 Supported On: System x and BladeCenter
Problems Fixed: - Multiple performance improvements in virtualized environments (SR-IOV,UMC) - Resetting Transparent Vlan to Default Vlan is not working - Cleanup ethtool set settings code - ARI on IBM x3650M4: All functions are not displayed in Linux
Device Driver Version: 10.2.261.0 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Provide link state control for VFs - ethtool shows port as fibre though copper cable is connected. - Multi channel config should be determined via port resource descriptor - Showing WoL supported in ethtool for BE3 where it is not supported - be2net driver crash when umc enabled - ip link show command shows vlan for vfs although vlan creation is failed on the vfs - Emulex be2net driver does not support IOMMU pass through mode
Device Driver Version: 10.0.800.0 Supported On: IBM System x
Problems Fixed: - Low bi-di throughput seen on 1g ports of HS-23 LOM - Multiple performance improvements - Bonding driver takes approx 20 seconds to be ready
Incremental Interoperability: - RHEL 5.10 - RHEL 6.5 - XE-102 and XE-104 ASIC (OCx14xxx) - Support for set and get channels ethtool operation
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.4 and above 64-bit with KVM * SLES11 SP3 and above 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
Device Driver Version: 4.6.267.4 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 KVM configurations - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 SR-IOV configurations - SR-IOV configuration section of the Linux NIC Driver Documentation has been modified to improve clarity
Incremental Interoperability: - S3 Resume on IBM Flex - SLES 11.3 on IBM System x and BladeCenter
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.3 and 6.4 64-bit with KVM * SLES11 SP2 and SP3 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
- Use of SR-IOV with the XEN hypervisor is not supported at this time.
- Use of SR-IOV with the KVM hypervisor requires the use of macvlan network interfaces.
Device Driver Version: 4.6.148.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - Ethernet performance issues in a variety of workloads - VFs are not displayed after driver re-load when is VFs attached to VM - vLAN tagging in Switch Agnostic vNIC mode
Incremental Interoperability: - RHEL 5.9 - RHEL 6.4 - Network performance varies with workload. An ethernet driver tuning script and instructions is now included with the be2net driver. - Switch Independent Mode within hypervisor OS's
Known Issues: - Multi-channel is not supported in RHEL5.x XEN. This is a kernel limitation - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 KVM configurations - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 SR-IOV configurations - SR-IOV is not supported with RHEL5.x XEN
Device Driver Version: 4.4.180.0 Supported On: IBM Flex
Device Driver Version: 4.2.389.0 Supported On IBM System x and BladeCenter
Problems Fixed: - Unloading the driver hangs the system after running IPv6 traffic - Link status messages cleaned up when in Switch Agnostic mode - Miscellaneous network performance issues to improve throughput - Miscellaneous problems related to SRIOV to improve usability - Ethtool wol command displays wol enabled even when disabled - Ethtool speed reported as 10000Mb/s for disabled devices in Switch Agnostic mode
Incremental Interoperability: - RHEL6.3 GA Kernel - Increase default B/W for SRIOV vf's to 10Gb from 100Mb
Device Driver Version: 4.1.413.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - WOL changes for Linux NIC driver as mentioned in Bug# 24543 - SR IOV UE when attempt to do multiple (3 times) driver load/unload - Speed is 10000Mb/s for Disabled devices in UMC Mode - Incorrect Duplex value is shown for unconnected port of NC552m in Rhel6.1 32bit - SLES 11 SP2 GMC: Enable support for Lnx NIC Driver - SRIOV: When VGT is configured for a VF, ip link show doesn't display it for the VF configured. - RHEL 5.8 GA: Enable support for Lnx NIC Driver - ip link command with vlan = 4095 has toggling effect - ip link command with vlan =0 should remove guest VGT privilege
Device Driver Version: 4.1.334.39 Supported On: IBM System x and BladeCenter
Problems Fixed: - SR-IOV: Can't load be2net driver in a VM after the VM has been rebooted - SR-IOV: Unload PF driver with VF driver loaded causes system instability - SR-IOV: VF MAC always gets Emulex OUI - SR-IOV: Partition the limited per port VLAN entries across VFs and PFs - Non Member VLAN packets not received in interface promiscuous mode in BE3 - Avoid CQ full condition in HW - be2net: use RX_FILTER cmd to program multicast addresses - account for skb allocation failures in ethtool stats - Support 60 second delay to Linux NIC driver to allow FAT dump completion on recovery from EEH - Link status is up [ethtool and OCM] when the bandwidth is assign 0 for UMC configuration - Remove msix module parameter - Use V1 version of COMMON_NTWK_LINK_STATUS_QUERY for Lancer. - Emulex: Ethtool failing to update FW - Emulex: Panic in be2net driver in SLES11-SP2-B7 on adapter - TCP ACKs from different connections are getting received in single queue - Multicast filtering feature not working on PPC - Exit of mcast promiscous mode not working - VLAN promiscous mode cannot be set on Lancer - Can't communicate after changing MAC address via VLAN interface - Improper memory accounting in received packets - WOL changes for Linux NIC driver as mentioned in bug - Transparent VLAN tagging feature not working in SR-IOV
Note: An asterisk (*) following a version number represents a certified driver. Arrows (<<) between versions indicate the component has been updated from the previous released software kit.
Known Issues and Limitations ============================
Certified Drivers: Citrix and VMware uncertified drivers are provided for test on the alpha, beta, and RC-level CDs. They are removed from the gold CD releases, in lieu of certified drivers being downloaded from their respective owners.
CN4093: The following anomalies have been noted as third party isssues with the CN4093 switch: 1) While performing shut/no shut on the switch port, it was observed that all initiators and targets were logged out from the FCoE database of the FCF-enabled VLAN by CN4093 switch. 2) After switch reboot, sometimes initiator and targets are logged out from the FCoE database of the FCF-enabled VLAN by CN4093 switch. Switch reboot is required to recover from this state. 3) In some cases, the “Application Protocol State Machine Status” for the CN4093 switch port shows “Enable Operational” and “Enable Peer” status as “Disabled” for priority 3 resulting in inability to run the traffic with priority tag of “3”. This seems to be a switch issue which needs further investigation. 4) The “Default Port VLAN ID” of the CN4093 switch port connecting to the QLogic FCoE initiator must be configured as “1” for switch to respond to VLAN Request. When the PVID of the switch port is set to any value other than 1, then switch does not respond to the VLAN Request and initiator will not be able to login to the fabric.
DCB/DCBX: DCB/DCBX is required for proper FCoE operation. When configuring FCoE operation, enable DCB/DCBX through the HII menus.
Default to VLAN 1002 if VLAN discovery fails: The QLogic NX2 implementation requires VLAN Discovery to work, to be able to discover targets in an FCoE setting. There is a known problem in the CN4093 and EN4093 adapters, where untagged VLAN Discovery packets are dropped, causing VLAN Discovery to fail. Lenovo has requested an enhancement to have the controllers fall back to VLAN 1002 if VLAN Discovery fails (CQ68018). These changes are implemented for UEFI (preboot), Windows, and VMware as part of the T7.12 release. Changes for Linux have been submitted upstream and will be part of a later OpenFCoE release.
Diagnostic Driver: The first time diagnostics are run in a Windows environment on NX2 devices, the diagnostic driver must be installed. Windows will either automatically install the driver, in which case, no action is required by the user, or Windows will ask to be directed to the INF file for the diagnostic driver. If you are prompted to install the driver, please direct the Windows dialog to search for the driver in the directory where the QLogic driver package was unzipped. You may also search your hard drive for the file “bxdiag.inf.”
FCoE and MFW: FCoE is only supported using MFW, not legacy bootcode.
Flow Control Statistics: Flow control statistics (MAC Sent X-ON, MAC Sent X-OFF and MAC Rx with no Pause Command) are reported incorrectly within QCS for 57710-based adapters. There is no functional impact and device is working as expected.
Hyper-V: Manually enabling TCP Chimney Offload in the guest operating systems under Hyper-V is not supported on Windows Server 2008 R2.
iSCSI Boot from SAN: Lenovo only supports the following iSCSI boot from SAN methods: 1) QLogic Legacy Mode Hardware initiator iSCSI Offload (L4) 2) Lenovo uEFI Mode Software initiator iSCSI (L2) Please refer to the appropriate user guide for proper configuration.
iSCSI Initiator: 1) The Linux iSCSI VLAN tag dependent on L2 VLAN tag, and must also be on the same subnet. 2) Linux iSCSI Path MTU is not yet implemented. 3) No routing support for SLES 11.3 ISCSI.
Legacy FCoE boot: Lenovo does not support legacy FCoE boot to any operating system.
Legacy iSCSI boot: Lenovo does not support legacy iSCSI boot for Windows 2012 and beyond. This is due to Windows limiting support to UEFI boot only. Support for legacy iSCSI boot remains in the QLogic controllers, to allow support of operating systems where this is allowed.
Legacy iSCSI and PXE Firmware: Legacy firmware instances from various devices compete for limited memory resources in the system. If legacy iSCSI or PXE boot is not working, especially after a system BIOS or adapter firmware change, it may be caused by memory contention. The workaround for such issues is to disable boot on competing devices, or to completely disable unneeded devices. For example, disabling the storage RAID adapter will often free up memory to allow iSCSI or PXE boot.
Licensing: FCoE and iSCSI offload are only available in the presence of valid licenses in NVRAM.
NC-SI with IOMMU: There is a known problem using NC-SI with IOMMU enabled, that can cause link down/up under stress conditions. If this occurs, disable IOMMU in the BIOS.
QLASP: QLASP (QLogic Advanced Server Program) will appear to be bound to all adapters in the system once loaded. This binding is normal and is used only to determine compatibility with QLASP. The binding is not active, as indicated by the gray background of the selection box. This pre-binding will not interfere with bindings to other software protocols.
QLASP and RSS: QLASP with RSS enable can support a maximum of up to 4 processors.
RIS Drivers: When loading drivers through the PNP (Plug and Play) method, users can occasionally end up loading the RIS drivers accidentally. Generally this occurs when a user is asked to point to the proper driver for the device, and the user selects the folder containing the RIS drivers as the driver for the device. This can result in network connections that fail to communicate across the network, as the NDIS driver will fail to bind to the devices. The most obvious way to identify the problem scenario is to open QCS and look at the network adapters displayed. Adapters that have the RIS drivers installed will be grayed out. Observing the driver loaded for the System Device portion of the NX2 devices will show that the RIS driver is loaded. Additionally, attempts to load the drivers using the installer will result in NDIS drivers displaying a yellow bang, as they’re not able to bind to the VBD driver. The easiest way to correct the problem is to run add/remove programs on all installed QLogic devices, then re-run the installer.
TOE and RSS: Receive Side Scaling (RSS) on TCP offloaded connections require a minimum of 8 gigabytes of RAM and only works for the 64-bit version of Windows Server 2008 and Windows Server 2008 R2.
Tundra / Tacoma modes: Tundra was developed and limited to 2x10Gb operation. Tacoma was developed and is currently limited to 2x10Gb operation. The hardware design includes support for a I2C register notification to the IMM of a VPD configuration change; the hardware for this has been tested, but the firmware support for this is not implemented. It is planned for an unidentified future release to support 4x10Gb and 2x20Gb modes.
UCM overriding QCS settings: The QCS utility has some functionality for changing adapter parameters, but recently enhancements to the UCM logic in the blade BIOS will store adapter information, and override new values from QCS with previous UCM values. This is a limitation of the UCM architecture. The only workaround is for changes such as enabling/disabling NPar or UFP to be done through the HII ( setup) menus, or through a UCM utility such as ASU or Config Patterns.
UEFI SAN Boot: UEFI SAN boot is only supported on the root ports of the device. In pNIC mode this is not a problem but in vNIC2 mode that means the FCoE offload function under the operating system MUST be enabled on vNIC port PF0 or 1, otherwise the hand off to the kernel will not happen correctly.
UEFI FCoE BFS is in test for full support with the following operating systems: Windows 2008 R2 (SP1) x64 Windows 2012 x64 Windows 2012 R2 x64 SLES 11 SP2 SLES 11 SP3 UEFI FCoE BFS is in test for support with major caveats on the following operating systems: RHEL6.5 (boot time failover will not work) RHEL6.6 (boot time failover will not work) In MPIO configurations, RHEL6.x systems cannot tolerate failed paths during system boot.
One specific interface must be online for boot to proceed (namely the last one specified for FCoE on the kernel command line). For example, the kernel command line dictates FCoE on eth1,eth2,eth3,eth4. If eth4 is down, the system will fail to boot.
This issue is being addressed for future RHEL releases. Once the system is fully booted, any single path can go down, and multipathed will sustain failover.
The following operating systems do not presently support UEFI FCoE BFS; efforts are underway to introduce this support in future versions of ESX. ESXi 5.0 (all updates) ESXi 5.1 U2 and below ESXi 5.5 GA
UEFI FCoE BFS is not supported with any 32 bit OS.
Virtual Bus Driver Architecture: The NetXtreme II drivers have two parts, the VBD driver and the NDIS Client driver. This combination of drivers can be used for WinPE installations as long as the WinPE image is built with the /PnP option. WinPE images that are booted with the -miniNT option will only load the NDIS driver so NetXtreme II network devices will not be functional in this environment. Use the -winpe option instead of the -minint option to boot WinPE when using NetXtreme II devices or use the special RIS driver contained in the distribution package in the NX2_RIS_Driver directory of the unpacked files.
Wake on LAN with NPar: When using Wake on LAN (WoL) with NIC Partitioning, all of the devices that comprise a port must be shut down to cause the WoL configuration to be written to the controller during operating system shutdown. If only a single function is shut down, the WoL configuration might not be written to the controller, and the controller might not wake.
WinPE: Windows Pre-installation Environment (WinPE for short) does not contain native support for 5708, 5709, 5716, 57710 and 57711 devices on operating systems prior to Windows Server 2008 R2. In order to “inject” driver support into Windows PE, refer to the steps provided by Microsoft at: http://support.microsoft.com/kb/923834/en-us. The 5708 Network Controller support is available as a native driver package in the Windows Server 2008 OS.
SR-IOV on ESXi: 1. When 64-bit BAR enabled in BIOS, an issue has been observed with powering on VM that has a VF assigned to it. This appears to be due to vmkernel behavior. So the suggestion is to keep 64-bit BAR disabled when configuring SR-IOV on ESXi
2. When multiple adapters are present on a server and UFP mode is configured on one or more of the adapters, users should take into consideration the sequence in which PFs are enumerated before determining which PFs need to have max_vfs configured. It is recommended that max_vfs be configured on functions in the order of enumeration. The enumeration sequence can be determined by examining vmkernel logs.
Historical Information ====================== E1 PXE: E1 (57710/57711) devices are no longer support by the T7.4 or later PXE code. PXE updates on E1 devices must use 7.2.x-based PXE drivers or earlier (provided with this kit).
ESX: VMware SRIOV support is limited to ESX 5.5 and above, and not supported on ESX 5.1 or prior.
Flow Control: The default Flow Control setting in the Linux drier for 5771x 10Gb fiber devices is now set to disabled. In some previous releases, the default was set to enabled.
FoD: General support for Features on Demand (FoD) was added in T7.8b for Tundra, but no FoD keys were defined or tested.
Hyper-V: No Windows 2012 inbox driver support in VM / Guest-OS.
Hyper-V TOE: Windows Server 2008 R2 was expected to support the ability to utilize the TCP Offload Engine (TOE) on child partitions for supported Guest operating systems. However, the stack supporting this feature was not fully matured upon the completion of the T7.8 driver release. As a result, we did not recommend enabling this capability with these drivers until an update to resolve these issues are released. This is now understood to be a third-party issue.
Inbox: The current inbox iSCSIUIO does not support Linux BFS with UFP on RHEL 6.5, RHEL 6.6, RHEL 7.0, and SLES 11.3. You will need to upgrade to the latest released driver during installation.
RPL: The 10Gb MBA PXE driver no longer supports the RPL protocol. This support was removed around the T7.4 timeframe.
Split / Rebranding: The split of NX1 and NX2 support, and the rebranding from Broadcom to QLogic, was done in the T7.12 timeframe.
Storage: Support was added in T7.10 for Tundra only.
Windows 2003: Support was discontinued as of the T7.0 program. This includes preventing driver install, preventing enumeration of iSCSI HBA, and removing support for installation of iSCSI boot drivers.
Legal Notices ============= Third-party trademarks and copyrights are property of their respective owners.
For FCoE, QLogic only officially supports the FCoE and DCB feature set on adapters that are licensed for FCoE, and for which EMC e-Labs certification is already complete or in progress. QLogic will *not* provide field support for unqualified platforms. Please refer to the EMC e-Labs certification matrix for existing support matrix postings, or contact your QLogic contact to inquire about configurations currently in the qualification queue for eventual support. Exercising either FCoE or DCB on an unsupported platform may lead to unpredictable results.
qlgc_fw_nic_7_13b_4_1c_linux_32-64_chg
IBM HBA/LSI 12Gb SAS/SATA/SSD Driver for SUSE Linux Enterprise Server 12
NOTE TO SERVICE - Reference RETAIN N/A
Supported Controllers: - IBM N2215 SAS/SATA HBA for IBM System x (47C8676)
Version 14.00.00.00 - Moderate Impact/Low Probability of Occurrence ------------------ Fixes: - Fixed an issue where the OS would crash after installing device driver. (SCGCQ01123902) - Fixed an issue where only 8 MSIX vectors were enabled for SAS3 HBAs on a 32 core machine even though 32 msix vectors could be enabled on the card, since it has RDPQ enabled firmware. (SCGCQ01106942)
Enhancements: - Updated initial ref tag with correct value for 4K PI drives in kernels less than 3.18. (SCGCQ01066189) - Set sas_phy's negotiated_linkrate sysfs attribute to 12Gbps if corresponding device is 12Gbps device. (SCGCQ01100134) - Set maximum transfer length per IO to 4MB for VDs (SCGCQ01072659, SCGCQ01100150 Port of SCGCQ01072631)
Version 13.00.02.00 - Moderate Impact/Low Probability of Occurrence ------------------- Fixes: - fixed an issue where the initial ref tag was incorrect with 4K sector size drives when PI is enabled for kernel v3.18 and onwards. (SCGCQ01015654) - Fixed an issue where partial driver message is displayed when active cable power consumption exception occurs.(SCGCQ01025061) - Merged mpt2sas driver in to mpt3sas driver module. (SCGCQ00955258)
Enhancement - Set sas_phy's negotiated_linkrate sysfs attribute to 12Gbps if corresponding device is 12Gbps device (SCGCQ01100134) - Added support for RHEL6.8. (SCGCQ01093683) - Active cable exception handling in mpt3sas driver (SCGCQ01008402) - Set maximum transfer length per IO to 4MB for VDs (SCGCQ01100150) - Fixed issue where OS not discovering all drives in dual node configuration (SCGCQ01026842 PORT of SCGCQ00776162) - Updated MPI Headers from 2.00.39 to 2.00.42 (SCGCQ01015128)
Version 12.00.00.00-1 - Moderate Impact/Low Probability of Occurrence ------------------- Fixes: - Fixed potential protection fault due to sas device list corruption (SCGCQ00933587) - Fixed potential protection fault due to fw event list corruption (SCGCQ00933591) - Fixed memory leak occuring with failed firmware event data (SCGCQ00881682)
Enhancements: - Make use of additional HighPriorityCredit number of message frames for sending SCSI IO's (SCGCQ00899842) - Add support for configurable Chain Frame Size. (SCGCQ00933600, Port of SCGCQ00929253)
Version 10.00.02.00 - Moderate Impact/Low Probability of Occurrence ------------------ Fixes: - Enabled polling for detecting of SMART SATA drives (SCGCQ00791340)
Note: Installed version number is 10.00.02.00
Version 8.00.00.00 - Initial release ------------------
ibm_dd_mpt3sas_14_00_00_00_sles12_32-64_chg
IBM Online SAS/SATA HDD/SSD Update Program. Version 1.22.01 Build ID: IBM12201 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.22.01 - Update Utility release for IBM x86 servers.
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.22.00 Build ID: IBM12200 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.22.00 - Update Utility release for IBM x86 servers.
Note: *- Only keep the legacy HDD/SSD in this Update program, the drives were out of production by 4Q2014 or no firmware changes since 1Q2014. No FW update for below legacy drives in this version.
This package acknowledges support and may include updates for drives with product ID strings of:
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.21.00 Build ID: IBM12100 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.21.00 - Update Utility release for IBM x86 servers.
This package acknowledges support and may include updates for drives with product ID strings of:
SAS 3.5"
- ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5K
- ST2000NM0043, ST4000NM0043 to EC5H
- ST2000NM0034, ST4000NM0034, ST6000NM0034 to BC6E
- ST2000NM0054, ST4000NM0054, ST6000NM0054 to EC6E
- HUS724020ALS64, HUS724030ALS64, HUS724040ALS64 to MPXSJ3LA
- HUS724020ALS61, HUS724040ALS61 to MPXSN3LA
- VPCA300900EST1, VPCA450900EST, VPCA600900EST1 to VCXSA810
SAS 2.5"
- HUC156030CSS20, HUC156060CSS20 to KFXSJ2G8
- HUC101212CSS60 to CPXSJ2MC
- HUC101212CSS61 to CPXSN2MC
- HUC109030CSS60, HUC109060CSS60, HUC109090CSS60 to CEXSJ2EL
- HUC109030CSS61, HUC109060CSS61, HUC109090CSS61 to CEXSN2EL
- HUSMM1620ASS20, HUSMM1640ASS20, HUSMM1680ASS20, HUSMM1616ASS20 to SPXSJ4CC
- HUSMM1620ASS20E, HUSMM1640ASS20E, HUSMM1680ASS20E, HUSMM1616ASS20E to SPXSN4CC
SATA 3.5"
- WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD40
- ST2000NM0024, ST4000NM0024, ST6000NM0024, ST5000NM0024 to BB67
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5G
SATA 2.5"
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB47
- MZ7GE240HMHP-000M3, MZ7GE480HMHP-000M3, MZ7GE960HMHP-000M3 to EXT0CA35
- STECM8PSB2 to 2864/SM08
SATA 1.8"
- MTFDDAA120MBB, MTFDDAA240MBB, MTFDDAA480MBB, MTFDDAA800MBB to MB47
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.20.00 Build ID: IBM12000 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.20.00 - Update Utility release for IBM x86 servers.
Note: *- Update the firmware on SAS/SATA SSDs to fix PSIRT issue with Intel SSD's.
This package acknowledges support and may include updates for drives with product ID strings of:
SATA 2.5"
- SSDSC2BB120G4I, SSDSC2BB240G4I, SSDSC2BB480G4I, SSDSC2BB800G4I to D201NE40.
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to 5DV1NA39.
- SSDSC2BB080G4I, SSDSC2BB160G4I, SSDSC2BB300G4I, SSDSC2BB600G4I, SSDSC2BB800G4I to D201NE40.
- SSDSC2BB012T4I, SSDSC2BB016T4I to G201NC34.
SATA 1.8"
- SSDSC1NB080G4I, SSDSC1NB240G4I, SSDSC1NB400G4I to D201NE40.
- SSDSC1NA200G3I, SSDSC1NA400G3I to 5DV1NA39.
- SSDSC1NB800G4I to D201NE40.
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.19.06 Build ID: IBM11906 ************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.19.06 - Update Utility release for IBM x86 servers.
This package acknowledges support and may include updates for drives with product ID strings of:
- Remove TXA2D20200GA6I, TXA2D20400GA6I, TXA2D20800GA6I, TXA2E21600GA6I from FW update utility for new code updating break Raid.
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program. Version 1.18.03 Build ID: IBM11803
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.18.03 - Update Utility release for IBM x86 servers.
Note: * - Fixed extremely low probable data compare error on I/O held in standby when followed by power cycle; extremely low probable data compare error due to nonvolatile cache(NVC) write data not getting written to disc. RETAIN TIP: H214784 - MIGR-5098277
Note: # - Fixed a block misalignment during a sequential read.
RETAIN TIP: H214635 MIGR-5098037
SAS 3.5"
- ST2000NM0034, ST4000NM0034, ST6000NM0034 to BC6B - similar to Note * above.
- ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5J - Enhance Dither Algorithm to prevent dwelling during Idle environments. - ST2000NM0043, ST4000NM0043 to EC5E - Enhance Dither Algorithm to prevent dwelling during Idle environments.
SAS 2.5"
- TXA2E21600GA6I to GB7P - add support in profile.
- HUC156030CSS20, HUC156060CSS20 to J2G6 - add support in profile.
SATA 3.5"
- ST2000NM0024, ST4000NM0024, ST5000NM0024, ST6000NM0024 to BB66 - similar to Note * above.
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5F - Enhance Dither Algorithm to prevent dwelling during Idle environments.
SATA 2.5"
- MTFDDAA120MBB, MTFDDAA240MBB, MTFDDAA480MBB, MTFDDAA800MBB to MB42 - add support in profile.
- SSDSC2BB080G4I, SSDSC2BB160G4I, SSDSC2BB300G4I, SSDSC2BB600G4I to D201NB39 - add support in profile.
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.17.01 - Update Utility release for IBM x86 servers.
Note: * - Fixed extremely low probable data compare error on I/O held in standby when followed by power cycle; extremely low probable data compare error due to nonvolatile cache(NVC) write data not getting written to disc. RETAIN TIP: H214784 - MIGR-5098277
Note: # - Fixed a block misalignment during a sequential read. RETAIN TIP: H214635 MIGR-5098037
This package acknowledges support of qualified devices and may include updates for drives with product ID strings of:
SAS 3.5"
- HUS724020ALS61, HUS724040ALS61 to N3L6 - internal updates.
- ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5H - See Note * above.
- ST2000NM0054, ST4000NM0054, ST6000NM0054 to EC66 - see Note * above.
- ST2000NM0043, ST4000NM0043 to EC5D - See Note * above.
- Other drive codes are present for support identification.
SAS 2.5"
- WD3001BKHG-23D, WD6001BKHG-23D, WD9001BKHG-23D to ZA34 - follow-on release. - WD3002BKTG-23E, WD6002BKTG-23E, WD9002BKTG-23E to ZC33 - follow-on release.
- HUC109030CSS60, HUC109060CSS60, HUC109090CSS60 to J2EH - follow-on release.
- TXA2D20200GA6I, STXA2D20400GA6I, TXA2D20800GA6I, TXA2E21600GA6I to GB7P - enhancements.
- ST300MM0006, ST600MM0006, ST900MM0006 to B56T - See Note * above.
- ST300MM0026, ST600MM0026, ST900MM0026 to E56E - See Note * above.
- ST2000NM0043, ST4000NM0043 to EC5D - See Note * above.
- ST1200MM0007 to B57E - See Note * above.
- ST1200MM0017 to E577 - See Note * above.
- HUSMM1620ASS20, HUSMM1640ASS20, HUSMM1680ASS20, HUSMM1616ASS20 to J4C8 - See Note # above - HUSMM1620ASS20E, HUSMM1640ASS20E, HUSMM1680ASS20E, HUSMM1616ASS20E to N4C8 - See Note # above
- Other drive codes are present for support identification.
SATA 3.5"
- MG04ACA200E, MG04ACA300E, MG04ACA400E, MG04ACA500E to SJ1D - performance inhancements.
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5C - See Note * above.
- ST2000NM0024, ST4000NM0024, ST5000NM0024, ST6000NM0024 to BB65 - See Note * above.
- WD2003FYYS-23W0B0 to WA36 - configuration additions.
- WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD39 - configuration additions.
- HUA723030ALA6 to MKAOA930 - enhancements. - HUA723020ALA6 to MK7OA930 - enhancements.
- Other drive codes are present for support identification.
SATA 2.5"
- MZ7GE240HMHP-000M3, MZ7GE480HMHP-000M3, MZ7GE960HMHP-000M3 to EXT0CA34 - ship level.
- Other drive codes are present for support identification.
SATA 1.8"
- Drive codes are present for support identification.
IBM Online SAS/SATA HDD/SSD Update Program. Version 1.16.05 Build ID: IBM11605
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.16.05 - Update Utility release for IBM x86 servers.
This package acknowledges support and may include updates for drives with product ID strings of:
SAS 3.5"
- ESXSST1000NM0001, ESXSST2000NM0001 to BC4B - ensures that after servicing an 03/11/00 error, an index for Parity Creations is calculated correctly after a power cycle, that would otherwise make the drive unresponsive.
- ESXSHUS724020ALS64, ESXSHUS724030ALS64, ESXSHUS724040ALS64 to J3L6 - Fixed unexpected 02/04/11 error; Fixed a drive logic self-initiated reset on read/write long commands; Fixed a problem with large write sequential transfers.
SAS 2.5"
- ESXSST9500620SS, ESXSST91000640SS to BD2K - ensures that after servicing an 03/11/00 error, an index for Parity Creations is calculated correctly after a power cycle, that would otherwise make the drive unresponsive.
SATA 2.5"
- SSDSC2BB012T4I, SSDSC2BB016T4I to G201NC32 - SCT WriteSame fix.
IBM Online SAS/SATA HDD/SSD Update Program. Version 1.16.04 Build ID: IBM11604
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.16.04 - Update Utility release for IBM System x servers.
This package acknowledges support and may include updates for drives with product ID strings of:
NOTE: Check notation under PCIe NVMe devices.
SATA 2.5"
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB42 - > A drop in host power supply may cause bad block growth > The bad block table may not properly increment > Background activity may continue after STANDBY, STANDBY IMMEDIATE, or SLEEP > ID173/202 may show incorrect value when the NAND erase count exceeds 3000 > Changed DRAM timing > Event log may be programmed when supply voltage from host is out of specification
- SSDSC2BB012I4I, SSDSC2BB016T4I to G201NC32 - SCT WriteSame fix that corrects a condition that may cause the drive to not respond.
PCIe NVMe 2.5"
- SSDPE2ME400G4I, SSDPE2ME800G4I, SSDPE2ME016G4I, SSDPE2ME020G4I to 8DV1ND34 - will require two update runs and system reboots for device fw update to complete--Please See the limitations in readme for details.
> Performance improvement on sub-4KB sequential write > Fix drive reports higher than actual data units read and write > Fix drive incorrectly counts unsafe power shutdown events on warm reboots
IBM Online SAS/SATA HDD/SSD Update Program. Version 1.16.03 Build ID: SAS11603
************************************************************************** IBM SAS/SATA HDD/SSD Update Program Version 1.16.03 - Update Utility release for IBM System x servers.
This package acknowledges support and may include updates for drives with product ID strings of:
NOTE: Check notation under PCIe NVMe devices.
SAS 3.5"
- ESXSST2000NM0034, ESXSST4000NM0034, ESXSST6000NM0034 to BC67 - GA code. - ESXSST2000NM0054, ESXSST4000NM0054, ESXSST6000NM0054 to EC66 - GA code.
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to XA39 - issues fixed: slow performance with PI enabled; drive hang on uncorrectable rd error in reallocation track; PERSISTANT RESERVATION command not working correctly; reliability improvements around off-track write protection.
SAS 2.5"
- ESXSTXA2D20200GA6, ESXSTXA2D20400GA6, ESXSTXA2D20800GA6, ESXSTXA2E21600GA6 to GB7P - fixes implemented to support PI issues.
- ESXSST300MP0005 to B675 - GA code. - ESXSST300MP0025 to E671 - GA code.
- ESXSST300MP0035, ESXSST600MP0035 to B683 - GA code. - ESXSST300MP0045, ESXSST300MP0045 to E685 - GA code.
- ESXSST300MX0012, ESXSST600MX0052 to BH53 - GA code.
- ESXSWD3001BKHG-23D, ESXSWD6001BKHG-23D, ESXSWD9001BKHG-23DS to ZA34 - issues fixed: slow performance with PI enabled; drive hang on uncorrectable rd error in reallocation track; PERSISTANT RESERVATION command not working correctly; drive was reporting 0B/11 instead of 03/11. - ESXSWD3002BKTG-23E, ESXSWD6002BKTG-23E, ESXSWD9002BKTG-23E to ZC33 - issues fixed: slow performance with PI enabled; drive hang on uncorrectable rd error in reallocation track; PERSISTANT RESERVATION command not working correctly; reliability improvements around off-track write protection.
SATA 3.5"
- MG04ACA200E, MG04ACA300E, MG04ACA400E, MG04ACA500E to SJ1C - GA code
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NS to BE2B - Update configuration change.
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB34 - > Some Out of Range LBAs accepted by NCQ commands where they should be aborted. > SataDownShift.srt failed, Smart attribute Raw lost with perform dirty pwr cycle . > Low Power Entry Bug Identified from Marvell Code Review > Track Timeout, Marvel 373 sequencer issue > Unreasonable ECC count in SMART ID 195
************************************************************************** IBM Online SAS/SATA HDD/SSD Update Program for Linux. Version 1.16.00 Build ID: SAS11600
******************************************* IBM SAS/SATA HDD/SSD Update Program Version 1.16.00 - First Update Utility release for IBM System x servers.
This package acknowledges support and may include updates for drives with product ID strings of:
NOTE: Check notation under PCIe NVMe devices.
SAS 3.5"
- ESXSST1000NM0023, ESXSST2000NM0023, ESXSST3000NM0023, ESXSST4000NM0023 to BC5E
- ESXSST2000NM0043, ESXSST3000NM0043, ESXSST4000NM0043, ESXSST1000NM0043 to EC5A
- ESXSST3300557SS, ESXSST3450757SS, ESXSST3600957SS to EA54
- ESXSST3300657SS, ESXSST3450857SS, ESXSST3600057SS to BA5A
- ESXSST33000650SS to BC3E
- ESXSST1000NM0001, ESXSST2000NM0001 to BC4A
- ESXSHUS724020ALS64, ESXSHUS724030ALS64, ESXSHUS724040ALS64 to J3L5
- ESXSHUS724020ALS61, ESXSHUS724040ALS61 to N3L5
- ESXSHUS723020ALS64, ESXSHUS723030ALS64 to J3K8
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to XA38
SAS 2.5"
- ESXSTXA2D20200GA6I, ESXSTXA2D20400GA6I, ESXSTXA2D20800GA6I, ESXSTXA2E21600GA6I to GB7H
- ESXSST300MM0006, ESXSST600MM0006, ESXSST900MM0006 to B56M; - ESXSST300MM0026, ESXSST600MM0026, ESXSST900MM0026 to E56D
- ESXST1200MM0007 to B57B - ESXST1200MM0017 to E576
- ESXSST9300605SS, ESXSST9600205SS, ESXSST9900805SS to B55E - ESXSST9300505SS, ESXSST9600105SS, ESXSST9900705SS to E558
- ESXSST9146853SS, ESXSST9300653SS to B63K
- ESXSST9146753SS, ESXSST9300553SS to E638 - ESXSST9500620SS, ESXSST91000640SS to BD2J
- ESXSHUC101212CSS60 to J2MA - ESXSHUC101212CSS61 to N2M9
- ESXSHUC156030CS420, ESXSHUC156060CS420 to J5G2 - ESXSHUC156030CSS20, ESXSHUC156060CSS20 to J2G4
- ESXSHUC156030CS420E, ESXSHUC156060CS420E to N5G2
- ESXSHUC156030CSS20E, ESXSHUC156060CSS20E to N2G4
- ESXSHUC101860CS420, ESXSHUC101890CS420, ESXSHUC101812CS420, ESXSHUC101818CS420 to J5H2 - ESXSHUC101860CS420E, ESXSHUC101890CS420E, ESXSHUC101812CS420E, ESXSHUC101818CS420E to N5H2
- ESXSHUC109030CSS60, ESXSHUC109060CSS60, ESXSHUC109090CSS60 to J2EG - ESXSHUC109030CSS61E, ESXSHUC109060CSS61E, ESXSHUC109090CSS61E to N2EG
- ESXSAL13SXB300N, ESXSAL13SXB600N to SC36
- ESXSMBF2300RC, ESXSMBF2600RC to SB2F
- ESXSMK1401GRRB, ESXSMK3001GRRB to SC2E - ESXSMK1401GRRR, ESXSMK3001GRRR to SF23 - ESXSMK3001GRDB, ESXSMK6001GRDB, ESXSMK9001GRDB to SB35
- ESXSWD3001BKHG-23D, ESXSWD6001BKHG-23D, ESXSWD9001BKHG-23D to ZA33 - ESXSWD3002BKTG-23E, ESXSWD6002BKTG-23E, ESXSWD9002BKTG-23E to ZC32
- EXSXHUSMM1620ASS20, EXSXHUSMM1640ASS20, EXSXHUSMM1680ASS20, EXSXHUSMM1616ASS20 to J4C6 - EXSXHUSMM1620ASS20E, EXSXHUSMM1640ASS20E, EXSXHUSMM1680ASS20E, EXSXHUSMM1616ASS20E to N4C6
SATA 3.5"
- WD1003FBYX-23Y7B0, WD2003FYYS-23W0B0 to WA35
- WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD37 - Resolves drive initiated reset (DBS (Debug Stop event)) encountered under a narrow timing window (~1ns) for specific command/access patterns, due to the drive’s handling of command automation where it was possible for an internal hardware resource conflict to occur between two tasks.
- ST33000650NS to BB3A
- ST1000NM0011, ST2000NM0011 to BB4A
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5A
- HUA723020ALA640 to MK7OA930 - HUA723030ALA640 to MKAOA930
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NSto BE2A
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB33
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to 5DV1NA37
- MZ7GE240HMHP-000M3, MZ7GE480HMHP-000M3, MZ7GE960HMHP-000M3 to EXST0CA34
PCIe NVMe 2.5"
- SSDPE2ME400G4I, SSDPE2ME800G4I, SSDPE2ME016G4I, SSDPE2ME020G4I to 8DV1ND32 - will require a system reboot for device fw update to complete.
********************************************************************* SAS/SATA HDD/SSD Update Program Version 1.15.00 - First Update Utility release for IBM System x servers.
This package acknowledges support and may include updates for drives with product ID strings of:
SAS 3.5"
- ESXSST1000NM0023, ESXSST2000NM0023, ESXSST3000NM0023, ESXSST4000NM0023 to BC5E
- ESXSST2000NM0043, ESXSST3000NM0043, ESXSST4000NM0043, ESXSST1000NM0043 to EC5A
- ESXSST3300557SS, ESXSST3450757SS, ESXSST3600957SS to EA54
- ESXSST3300657SS, ESXSST3450857SS, ESXSST3600057SS to BA5A
- ESXSST33000650SS to BC3E
- ESXSST1000NM0001, ESXSST2000NM0001 to BC4A
- ESXSHUS724020ALS64, ESXSHUS724030ALS64, ESXSHUS724040ALS64 to J3L5
- ESXSHUS724020ALS61, ESXSHUS724040ALS61 to N3L5
- ESXSHUS723020ALS64, ESXSHUS723030ALS64 to J3K8
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to
- ESXSWD1001FYYG-23S, ESXSWD2001FYYG-23S, ESXSWD3001FYYG-23S, ESXSWD4001FYYG-23S to XA38
SAS 2.5"
- ESXSTXA2D20200GA6I, ESXSTXA2D20400GA6I, ESXSTXA2D20800GA6I, ESXSTXA2E21600GA6I to GB7H
- ESXSST300MM0006, ESXSST600MM0006, ESXSST900MM0006 to B56M; - ESXSST300MM0026, ESXSST600MM0026, ESXSST900MM0026 to E56D
- ESXST1200MM0007 to B57B - ESXST1200MM0017 to E576
- ESXSST9300605SS, ESXSST9600205SS, ESXSST9900805SS to B55E - ESXSST9300505SS, ESXSST9600105SS, ESXSST9900705SS to E558
- ESXSST9146853SS, ESXSST9300653SS to B63K
- ESXSST9146753SS, ESXSST9300553SS to E638 - ESXSST9500620SS, ESXSST91000640SS to BD2J
- ESXSHUC101212CSS60 to J2MA - ESXSHUC101212CSS61 to N2M9
- ESXSHUC156030CS420, ESXSHUC156060CS420 to J5G2 - ESXSHUC156030CSS20, ESXSHUC156060CSS20 to J2G4
- ESXSHUC156030CS420E, ESXSHUC156060CS420E to N5G2
- ESXSHUC156030CSS20E, ESXSHUC156060CSS20E to N2G4
- ESXSHUC101860CS420, ESXSHUC101890CS420, ESXSHUC101812CS420, ESXSHUC101818CS420 to J5H2 - ESXSHUC101860CS420E, ESXSHUC101890CS420E, ESXSHUC101812CS420E, ESXSHUC101818CS420E to N5H2
- ESXSHUC109030CSS60, ESXSHUC109060CSS60, ESXSHUC109090CSS60 to J2EG - ESXSHUC109030CSS61E, ESXSHUC109060CSS61E, ESXSHUC109090CSS61E to N2EG
- ESXSAL13SXB300N, ESXSAL13SXB600N to SC36
- ESXSMBF2300RC, ESXSMBF2600RC to SB2F
- ESXSMK1401GRRB, ESXSMK3001GRRB to SC2E - ESXSMK1401GRRR, ESXSMK3001GRRR to SF23 - ESXSMK3001GRDB, ESXSMK6001GRDB, ESXSMK9001GRDB to SB35
- ESXSWD3001BKHG-23D, ESXSWD6001BKHG-23D, ESXSWD9001BKHG-23D to ZA33 - ESXSWD3002BKTG-23E, ESXSWD6002BKTG-23E, ESXSWD9002BKTG-23E to ZC32
- EXSXHUSMM1620ASS20, EXSXHUSMM1640ASS20, EXSXHUSMM1680ASS20, EXSXHUSMM1616ASS20 to J4C6 - EXSXHUSMM1620ASS20E, EXSXHUSMM1640ASS20E, EXSXHUSMM1680ASS20E, EXSXHUSMM1616ASS20E to N4C6
SATA 3.5"
- WD1003FBYX-23Y7B0, WD2003FYYS-23W0B0 to WA35
- WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD37
- ST9500620NS, ST91000640NS to BE2A
- ST33000650NS to BB3A
- ST1000NM0011, ST2000NM0011 to BB4A
- ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB5A
- HUA723020ALA640 to MK7OA930 - HUA723030ALA640 to MKAOA930
SATA 2.5"
- ST9500620NS, ST91000640NS
- MTFDDAK120MBB, MTFDDAK240MBB, MTFDDAK480MBB, MTFDDAK800MBB to MB33
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to 5DV1NA36
- MZ7GE240HMHP-000M3, MZ7GE480HMHP-000M3, MZ7GE960HMHP-000M3 to EXST0CA34
NOTE TO SERVICE - Reference RETAIN TIP H29851 ******************************************* SAS Hard Disk Drive Update Program Version 1.14.04 Critical Release Reference RETAIN TIP H29851
This package includes updates to drives with product ID strings of:
SAS 2.5"
Initial code Release - SMK3001GRDB, SMK6001GRDB, SMK9001GRDB to SB35
SATA 2.5"
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to NA36 - SSDSC2BB120G4I, SSDSC2BB240G4I, SSDSC2BB400G4I, SSDSC2BB800G4I to NB37 - fix to prevent possible drive lock up during format.
SATA 1.8"
Initial Code Release - SSDSC1NA200G3I, SSDSC1NA400G3I to NA36 - SSDSC1NB080G4I, SSDSC1NB240G4I, SSDSC1NB400G4I to NB37 - fix to prevent possible drive lock up during format.
=================================================================== IBM Online SAS/SATA Hard Disk Drive Update Program Version 1.14.03-2 Build ID: SAS11403-2
NOTE TO SERVICE - Reference RETAIN TIPS H211424 & H211667 ******************************************* IBM SAS Hard Disk Drive Update Program Version 1.14.03-2 Critical Release Reference RETAIN TIP H211424 & H211667
This package includes updates to drives with product ID strings of:
SAS 3.5"
Initial Code Releases - ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5B - ST2000NM0043, ST4000NM0043 to EC59 - WD1001FYYG-23S, WD2001FYYG-23S, WD3001FYYG-23S, WD4001FYYG-23S to XA35
Other - ST1000NM0001, ST2000NM0001 to BC4A - support persistent reservation - HUS723020ALS64, HUS723030ALS64 to J3K8 - servo adjustments
SAS 2.5"
Initial Code Releases - ST300MM0006, ST600MM0006, ST900MM0006 to B56H - ST300MM0026, ST600MM0026, ST900MM0026 to E568 - TXA2D20200GA6I, TXA2D20400GA6I, TXA2D20800GA6I, TXA2D21600GA6I to GB76 - see Retain Tip H211424. - HUC101212CSS60 to J2M7 - HUC101212CSS61 to N2M7 - T1200MM0007 to B576 - T1200MM0017 to E574 - ST600MX0001 to BH13 - WD3002BKTG-23E, WD6002BKTG-23E, WD9002BKTG-23E to ZC31 - ST9500431SS to ED12 - ST9146703SS to E536 - ST973352SS to E625 - ST9300553SS to E636 - HUC109030CSS61E, HUC109060CSS61E, HUC109090CSS61E to N2EF - MK3001GRDB, MK6001GRDB, MK9001GRDB to SB35 - drive Que depth fix; see Retain Tip H211667. - HUC109030CSS60, HUC109060CSS60, HUC109090CSS60 to J2EF - HUC109030CSS61E, HUC109060CSS61E, HUC109090CSS61E to N2EF
Other - WD3001BKHG-23D, WD6001BKHG-23D, WD9001BKHG-23D to ZA32 - performance, non-critical fixes and robustness changes.
- ST9600204SS to B54A with maintainance fixes and performance improvements.
- MBD2147RC, MBD2300RC to SB1B - drive Que depth fix; - MBE2073RC, MBE2147RC to SC18 - drive Que depth fix; - MBF2300RC, MBF2600RC to SB2F - drive Que depth fix; - MK1401GRRB, MK3001GRRB to SC2E - drive Que depth fix; see Retain Tip H211667.
- ST9500620SS, ST91000620SS to BD2F - support persistent reservation and maintainance fixes.
SATA 3.5"
Initial Code Release - WD801ABYS-23C0A0, WD1601ABYS-23C0A0 to 06.06H05 - WD5003ABYX-23 to WC38 - added mfg. parameters. - WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD36 - ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB58
Other
SATA 2.5"
Initial Code Release - SG9XCS2D50GEIBM to SE6H - WD3000BLHX-23V7BV to YA31 - SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to NA34 - SSDSC2BB120G4I, SSDSC2BB240G4I, SSDSC2BB400G4I, SSDSC2BB800G4I to NB34
Other - ST9250610NS, ST9500620NS, ST91000640NS to BE29 - maintainance updates. - MTFDDAK064MAR-1J1AA, MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA, MTFDDAK512MAR-1K1AA to MA57 - added mfg. parameters.
SATA 1.8"
Initial Code Release - SSDSC1NA200G3I, SSDSC1NA400G3I to NA34 - SSDSC1NB080G4I, SSDSC1NB240G4I, SSDSC1NB400G4I to NB34
Other - MTFDDAA064MAR-1J1AB, MTFDDAA128MAR-1J1AB, MTFDDAA256MAR-1K1AB, MTFDDAA512MAR-1K1AB to MA57 - added mfg. parameters.
=================================================================== Version 1.13.01 Build ID: SAS_113
NOTE TO SERVICE - Reference RETAIN H207993
******************************************* IBM SAS Hard Disk Drive Update Program Version 1.13.01 Critical Release Reference RETAIN H207993
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- HUS723020ALS64 to J3K7 Additions to VPD information used by manufacturing and fixes for overall robustness.
- HUS723030ALS64 to J3K7 Initial Code Release
- ST31000424SS, ST32000444SS to BC2D - ST1000NM0001, ST2000NM0001 to BC49 Fixes for overall robustness.
- ST33000650SS to BC3E Initial Code Release
SAS 2.5"
- MK1401GRRB, MK3001GRRB to SC29 Fixes for overall robustness.
- MBF2300RC, MBF2600RC to SB2C Initial Code Release.
- ST9300605SS, ST9600205SS, ST9900805SS to B55D ST9146853SS, ST9300653SS to B63B ST9500620SS, ST91000640SS to BD2E ST9300505SS, ST9600105SS, ST9900705SS to E557 ST9146753SS to E636 Additions to VPD information used by manufacturing and fixes for overall robustness.
SATA 3.5"
- ST500NM0011, ST2000NM0011, ST1000NM0011 to BB4A ST3500514NS, ST31000524NS, ST32000644NS to BB2C Reliability improvements, Additions to VPD information used by manufacturing
- ST33000650NS to BB3A Initial Code Release
- WD5003ABYX-23 to WC36, WD1003FBYX-23Y7B0 to WB35, WD2003FYYS-23W0B0 to WA35 Reliability improvements, Additions to VPD information used by manufacturing
- HUA723020ALA640 to MK7OA910 Additions to VPD information used by manufacturing.
- HUA723030ALA640 to MKAOA910 Initial Code Release
- HUA722050CLA330, HUA722010CLA330 to A3PH Initial Code Release
SATA 2.5"
- TE22D10100GE8IBM to SR3B Initial Code Release
- MTFDDAK064MAR-1J1AA, MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA, MTFDDAK512MAR-1K1AA to MA55 Initial Code Release
- ST9250610NS, ST9500620NS, ST91000640NS to BE28 Fixes for overall robustness.
SATA 1.8"
- MTFDDAA064MAR-1J1AB, MTFDDAA128MAR-1J1AB, MTFDDAA256MAR-1K1AB, MTFDDAA512MAR-1K1AB to MA55 Initial Code Release
- TX21B10100GE8IBM, TX21B10200GE8IBM, TX21B10400GE8IBM to SP3A Initial Code Release
Version 1.12.01 Critical Release Reference RETAIN #H207740
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA450900EST1, VPCA600900EST1 to A3C4, Corrects firmware bug that may cause data corruption. For further information, please refer to Retain Tip H207740.
- ST3300657SS, ST3450857SS, ST3600057SS to BA5A VPCA300900EST1, VPCA600900EST1 to A3C2 Additions to VPD information used by manufacturing
- ST3750630SS, ST31000640SS to BC1I ST31000424SS, ST32000444SS to BC2C Mode Page change to address performance issues under certain system configurations
- ST33000650SS to BC3D ST1000NM0001, ST2000NM0001 to BC48 Protection Information Fix - see Retain Tip H206140
- HUS723020ALS64, HUS723030ALS64 to J26C Initial Code Release
SAS 2.5"
- ST9300603SS, ST9146803SS to B53E ST9600204SS to B549 Additions to VPD information used by manufacturing
- ST9300605SS, ST9600205SS, ST9900805SS to B55C ST9146853SS, ST9300653SS to B63A ST9500620SS, ST91000640SS to BD2C ST9300505SS to E555 ST9146753SS to E635 Protection Information Fix - see Retain Tip H206140
- ST9600105SS, ST9900705SS to E555 Inital Code Release
- HUC106030CSS60, HUC106060CSS60 to D3A6 Performance improvements, critical fixes for Protection Information (PI) operation - see Retain Tip H206140
- MK1401GRRB, MK3001GRRB to SC27 Additions to VPD information used by manufacturing
- WD9001BKHG-23D, WD6001BKHG-23D, WD3001BKHG-23D to ZA31 Initial Code Release
SATA 3.5"
- WD2502ABYS-23B7A0 to 02.03B08 WD1602ABYS-23B7A0 to 02.03B07 Critical fix to address premature drive failures.
- ST3500514NS, ST31000524NS, ST32000644NS to BB2A ST33000650NS to BB38 ST1000NM0011, ST2000NM0011, ST500NM0011 to BB47 Fixes a potential, but rare data corruption issue which requires a background reallocation that exceeds the error recovery timer.
- HUA723020ALA640 to MK70A900 HUA723030ALA640 to MKA0A900 Initial Code Release
SATA 2.5"
- ST9160511NS, ST9500530NS to BE1A - ST9250610NS, ST9500620NS, ST91000640NS to BE25 Fixes a potential, but rare data corruption issue which requires a background reallocation that exceeds the error recovery timer.
SSD
- TX21B10200GE1IBM, TX21B10400GE1IBM, TX21B10100GE8IBM to PRO6SP36 TE22D10100GE8IBM to PRO6SR36 Initial Code Release
- MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA to MA52 Initial Code Release
- MTFDDAA512MAR-1K1AB, MTFDDAK064MAR-1J1AA, MTFDDAK512MAR-1K1AA, MTFDDAA064MAR-1K1AB, MTFDDAA128MAR-1K1AB, MTFDDAA256MAR-1K1AB to MA52 Fixes SMART attribute 190 (Current Temp) which caused warning messages with some versions of Linux
- STEC MACH8 IOPS to 2804 STEC M8PSB2 T4 to SM06 Additions to VPD information used by manufacturing Fixes potential drive failure if power loss occurs during firmware update.
- ST33000650SS to BC3A ST1000NM0001, ST2000NM0001 to BC44 Additions and corrections to VPD information used by manufacturing
SAS 2.5"
- ST9300605SS, ST9600205SS, ST9900805SS to B559 ST9146853SS, ST9300653SS to B637 ST9500620SS, ST91000640SS to BD29 ST9300505SS to E553 SST9146753SS to E633 HUC106030CSS60, HUC106060CSS60 to D390 Additions and corrections to VPD information used by manufacturing
- MK1401GRRB, MK3001GRRB to SC23 Fixes a pottential data corruption bug if there is an unexpected power loss.
SATA 3.5"
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15 ST3500514NS, ST31000524NS, ST32000644NS to BB29 ST33000650NS to BB36 ST1000NM0011, ST2000NM0011, ST500NM0011 to BB46
SATA SSD
- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB6C SG9XCS2D200GEIBM to SA03SE6C Fix for potential hang during an unexpected power cycle
MTFDDAK128MAR-1JAAB, MTFDDAK256MAR-1JAAB to MA44 Initial Release
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA600900EST1 to A3C0 Correction to VPD information used by manufacturing
- ST31000424SS, ST32000444SS to BC2B Fixes to improve robustness from certain read errors due to encroachment
- ST33000650SS to BC37 Fixes to improve overall robustness.
- ST1000NM0001, ST2000NM0001 to BC42 Inital Release
SAS 2.5" (SFF)
- ST9300605SS, ST9600205SS, ST9900805SS to B556 - ST9146853SS, ST9300653SS to B635 Fixes to improve overall robustness.
ST9300505SS to E552 ST9146753SS to E632 Initial Release
- ST9500620SS, ST91000640SS to BD26 Improve general robustness and added support for DPICZ
- HUC106030CSS60, HUC106060CSS60 to D340 Improve general robustness
- MBF2300RC, MBF2600RC to SB28 Improves performance in certain benchmarks
SATA 3.5"
- ST33000650NS to BB34 Fixes to improve overall robustness.
- ST1000NM0011, ST2000NM0011, ST500NM0011 to BB45 Initial Release
- ST3500514NS, ST31000524NS, ST32000644NS to BB29 Fixes for intermittent drive hangs
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15 Added enhancement for improved robustness
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NS to BE24 Initial Release
- ST9160511NS, ST9500530NS to BE19 Fixes for overall robustness.
SATA 2.5" SSD
- STEC MACH8 IOPS to 2765 STEC M8PSB2 T4 to SM05 Fixes potential drive lock up during cold or warm boots Fixes issues with RHEL 6.x installation
- SG9XCS2D200GEIBM to SA03SE6C Fixes default drive VPD information for manufacturing, the default LED behavior on certain systems and fixes issues with client install thru VMWare 5.x
SATA 1.8" SSD
- STEC M8PSB1 to 0409 STEC M8PSB1 T4 to SM16 Fixes potential drive lock up during cold or warm boots Fixes issues with RHEL 6.x installation
- SG9XCS1B50GMIBM to SA03SB6C SASG9XCS1F200GEIBM to SA03SB6C Fixes potential drive lock up during cold or warm boots and the default LED behavior on certain systems and fixes issues with client install thru VMWare 5.x
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- ST31000424SS, ST32000444SS to BC28 Added enhancement for improved RV robustness
- MBE2073RC, MBE2147RC to SC17 - MBA3073RC, MBA3147RC, MBA3300RC to SA0A Added VPD changes for manufacturing
SAS 2.5" (SFF)
- ST9300603SS, ST9146803SS to B53C ST9600204SS to B548 SST973452SS, ST9146852SS to B62C CBRCA146C3ETS0, CBRCA300C3ETS0 to C610 Added fixes for overall drive robustness
- MBD2147RC, MBD2300RC to SB1A Added VPD changes for manufacturing Addresses issues seen with DSA HDD Diagnostic test.
- MBF2300RC, MBF2600RC to SB25 Addresses issues seen with DSA HDD Diagnostic test.
- ST9500620SS, ST91000640SS to BD22 HUC106030CSS60, HUC106060CSS60 to D2F8 Inital Release
SATA 3.5"
- WD2502ABYS-23B7A0 , WD1602ABYS-23B7A0 to 02.03B07 Addresses firmware issues that may cause a drive to be marked defunct prematurely under certain application workloads.
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB14 ST3500514NS, ST31000524NS, ST32000644NS to BB28 Added enhancement for improved robustness
- WD5003ABYX-23 to WC31 Initial Release
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V10 (Critical) Addresses firmware issues that may cause a drive to be marked defunct prematurely under certain application workloads.
- ST9250610NS, ST9500620NS, ST91000640NS to BE21 Initial Release
SATA 2.5" SSD
- STEC MAC8 IOPS to 2732 STEC M8PSB2 T4 to SM04 Addresses an issue installing RHEL 6.0 onto this drive.
SATA 1.8" SSD
- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB63 Addresses rare issue where the drive may not being seen on power up.
- STEC M8PSB1 to 0408 STEC M8PSB1 T4 to SM15 Addresses an issue installing RHEL 6.0 onto this drive.
- ST373455SS, ST3146855SS, ST3300655SS to BA2D - ST373355SS, ST3146755SS, ST3300555SS to BA38 - ST3146356SS, ST3300656SS, ST3450856SS to BA4C - ST3300657SS, ST3450757SS, ST3600057SS to BA58 - ST3750630SS, ST31000640SS to BC1G - ST31000424SS, ST32000444SS to BC26 (All Above Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- MBA3073RC, MBA3147RC, MBA3300RC to SA08 This code corrects a firmware bug that may cause the drive to not come ready on a cold boot.
SAS 2.5" (SFF)
- ST973402SS, ST9146802SS to B52B - ST936751SS, ST973451SS to B617 - ST9146803SS, ST9300603SS toB53B - ST9600204SS to B546 - ST973452SS, ST9146852SS to B629 - ST9300503SS to E536 - ST9146752SS to E625 - ST9500430SS to BD14 (All Above Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
SATA 3.5"
- ST3500514NS, ST31000524NS, ST32000644NS to BB26
- WD2003FYYS-23W0B0 to WA32 - WDC WD1003FBYX-23Y7B0 to WB31 Initial release
SATA 2.5" SSD
- STEC MACH8 IOPS to 2582 (Critical) Corrects firmware bug that may cause data corruption. For further information, please refer to retain tip H197650.
SATA 1.8" SSD
- STEC M8PSB1 to 0405 (Critical) Corrects firmware bug that may cause data corruption. For further information, please refer to retain tip H197650.
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA450900EST, VPCA600900EST1 to A3B8 Initial Release
- VPBPA300C3EST1 to A529 Initial Release
- ST3300657SS, ST3450757SS, ST3600057SS to BA56 (Critical) Performance improvements under certain workloads. Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST31000424SS, ST32000444SS to BC21 Initial Release
SAS 2.5" (SFF)
- ST9300603SS, ST9146803SS to B53A (Critical) Performance improvements under certain workloads. Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST9600204SS to B544 (Critical) Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST973452SS, ST9146852SS to B626 Performance improvements under certain workloads.
- ST9500430SS to BD13 Performance improvements under certain workloads
- ST9300503SS to E534 and ST9146752SS to E623 Performance improvements under certain workloads.
- MBD2147RC, MBD2300RC to SB19 (Critical) MBE2073RC, MBE2147RC to SC16 (Critical) Corrects a firmware bug that erroneously reported medium errors which may cause the drive to report PFA alerts and in some cases be marked offline
SATA 3.5"
- WDC WD2502ABYS-23B7A0, WD2502ABYS-23B7A0, WD802ABYS-23B7A0, WD1602ABYS-23B7A0 to 02.03B05 (Critical) Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST3500514NS, ST31000524NS, ST32000544NS to BB26 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB13 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- HUA722020ALA330 to JKAOA3GA HUA722050CLA330 to JP2OA3GB HUA722010CLA330 to JP4OA3GB Initial Release
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V09 (Critical) This code corrects an additional issue where the drive may be marked defunct.
- ST9160511NS, ST9500530NS to BE18 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382. Also improves performance under certain workloads.
SATA 2.5" SSD
- STEC MACH8 IOPS to 2366 (critical) Corrects firmware bug that may cause degraded performance and in some cases the drive may not come ready after a warm or old boot.
SATA 1.8" SSD
- STEC M8PSB1 to 0404 Turns the default for write cache off Initial Release
IBM SAS Hard Disk Drive Update Program Version 1.06 (Critical)
Added support for the following controllers:
- IBM ServeRAID BR10il SAS controller v2 (49Y4731) - IBM ServeRAID M1015 SAS controller (46M0831) - IBM ServeRAID M5015 SAS controller (46M0829) - IBM ServeRAID M5014 SAS controller (46M0916)
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- ST373455SS, ST3146855SS, ST3300655SS to BA2A ST373355SS, ST3146755SS, ST3300555SS to BA36 (Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
- ST3750630SS, ST31000640SS to BC1E ST3146356SS, ST3300656SS, ST3450856SS to BA4A This code address an issue where the drive may report an erroneous hardware error to the controller.
- MBA3073RC, MBA3147RC, MBA3300RC to SA07 This code improves sequential write performance under certain workloads when write cache is turned on.
- ST3300657SS, ST3450757SS, ST3600057SS to BA52 NOTE: This is the first code release to be included in the hard drive update package.
SAS 2.5" (SFF)
- ST973402SS, ST9146802SS to B52A ST936751SS, ST973451SS to B616 (Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
- MBB2073RC, MBB2147RC to SB07 MBD2147RC, MBD2300RC to SB17 MBE2073RC, MBE2147RC to SC14 CBRCA146C3ETS0, CBRCA300C3ETS0 to C370 This code improves sequential write performance under certain workloads when write cache is turned on.
- ST9500430SS to BD11 This is the first code release to be included in the hard drive update package.
SATA 3.5"
- WD2003FYYS-23T8B0 to 01.00D04 This is the first code release to be included in the hard drive update package.
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V08 (Critical) This code corrects an issue where the drive may generate a false PFA alert. It also corrects an issue where the drive may be marked defunct
- ST9160511NS, ST9500530NS to BE16 This is the first code releases to be included in the hard drive update package.
=============================================================== IBM SAS Hard Disk Drive Update Program Version 1.05
SAS 2.5" (SFF)
ST9xxxx51SS to B616 ST9xxxx02SS to B52A - This code improves the robustness of write cache operations.
ST9xxxx52SS to B624 ST9xxxx03SS to B536 - This code improves the robustness of write cache operations and sequential write performance when write cache is enabled
MBD2xxxRC to SB14 - Initial release
SAS 3.5"
ST3xxxxx6SS to BA49 ST3750630SS to BC1D - This code improves the robustness of write cache operations.
SATA 3.5"
WDC WD2502ABYSxxxxx tp 02.03B04 - Fixes incorrect VPD data
SATA 2.5"
WD3000xxxxx to 04.04V05 - Adjusted PHY setting for better signal quality margin.
SATA 2.5" SSD
STEC MACH8 IOPS to 2269 GBRL0xxxxx to 4.17 GBRLBxxxxx to 4.26 - The new firmware will correct a rare data error condition in the drives where invalid data may be passed to the system without any error condition flagged.
Due to the severity of this potential issue, IBM strongly recommends applying this firmware as soon as possible.
For further information, please refer to retain tip H195663. =================================================================
IBM SAS Hard Disk Drive Update Program Version 1.04
SAS 2.5" (SFF)
CBRBAxxxxxx to C49B - Modified VPD for JSxx Blades
MBBxxxxxx to SB05 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller
MBC2073RC to SC04 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller
SAS 3.5"
MBAxxxxxx to SA06 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller
ST3xxxxx6SS to BA48 - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632
ST3750630SS to BC1A - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632
- Fixes a hang condition during failover operation on a Bladecenter-S chassis with an RSSM controller.
BBAxxxxxx to BH0K - Fixes an issue where a drive may prematurely report a PFA trip
GNAxxxxxx to BH0J - Fixes an issue where a drive may prematurely report a PFA trip
SATA 3.5"
ST31000340NS, ST370330NS, ST3250310NS, ST3500320NS to BB12 - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632
- This code addresses a rare potential for data loss. After a power cycle, the drive will no longer be available and becomes unresponsive. Data will become inaccessible due to the drive not responding. For further information, please refer to retain tip H194623.
WDC WD2502ABYSxxxxx tp 02.03B04 - Fixes incorrect VPD data
SATA 2.5"
WD3000xxxxx to 04.04V04 - Fixes a Critical issue - IBM recommends a backup of the data on the drive before attempting to update the firmware. This is a fix for an issue where data required for spinup of the drive may be overwritten rendering the drive inoperable on a subsequent warm or cold system reboot.
- Fixes a issue with an internal timer that may cause drive to go offline when used in a non-raid environment.
IBM SAS Hard Disk Drive Update Program Version 1.03
Added support for the following controllers:
IBM ServeRAID MR10il SAS Controller IBM ServeRAID MR10is SAS Controller IBM ServeRAID BR10i SAS Controller IBM ServeRAID BR10il SAS/SATA Controller IBM SAS/SATA RAID Kit IBM SAS Expansion Card (CFFv) for IBM BladeCenter IBM SAS Connectivity Card (CFFv) for IBM BladeCenter
New updates to drives with product ID strings of:
SAS 2.5" (SFF)
ST9146802SS, ST973402SS to B529 - Added support for JS2x Blades in a Bladecenter-S chassis - Picked up the latest network roll of firmware fixes to address some unexpected system hangs,
ST936751SS, ST973451SS to B615 - Added support for JS2x Blades in a Bladecenter-S chassis - Picked up the latest network roll of firmware fixes to address some unexpected system hangs,
CBRBAxxxxxx to C495 - Initial release
MBBxxxxxx to SB04 - Initial release
MBC2073RC to SC03 - Initial release
SAS 3.5"
VPBAxxxxxx to A496 - Added support for JS2x Blades in a Bladecenter-S chassis
ST3146855SS, ST3300655SS, ST373455SS to BA29 - Added support for JS2x Blades in a Bladecenter-S chassis - Picked up the latest network roll of firmware fixes to address some unexpected system hangs,
ST3450856SS to BA47 - IBM was notified by our vendor that there is a defect in a level of firmware used in the IBM 450GB 15K SAS 3.5" HS HDD (PN 41Y8454) in option 42D0519, which under certain conditions may lead to data being written or read back incorrectly on the drive. IBM has worked closely with the vendor to identify the problem and developed a firmware fix to resolve the problem. Customers should upgrade to firmware level BA47
MBAxxxxxx to SA05 - Initial release
ST3750630SS to BC17 - Initial release
SATA 3.5"
ST3250620NS, ST3500630NS, ST3750640NS to 3.AEV
ST3250621NS, ST3500631NS, ST3750641NS to 4AEV
ST31000340NS, ST3750330NS, ST3250310NS, ST3500320NS to BB10 - Initial release
HUA721050KLA330, HUA721075KLA330, HUA721010KLA330, to AB4A - Initial Release
SATA 2.5" SSD
GBRL001xxx, GBRL0031xxx to 4.14 - corrects intermittent hangs during operations =============================================================
IBM SAS Hard Disk Drive Update Program Version 1.02
Support of ServeRaid 8s Raid controller Support of ServeRaid 10i Raid controller Support of ServeRaid 10k Raid controller Support of ServeRaid 10m Raid controller Support of LSI 1078 SAS controller Support of SATA drives attached to SAS controllers
Support and updates to drives with product ID strings of:
VPAxxxxxx to A650 Change to improve performance in sequential write workloads Improvements to internal drive logging and media checking. Critical Fix: This code addresses a rare potential for data loss This code update should be applied to prevent the event from occurring.
ST340XXXAS and ST380XXXAS to 3.48 Fix to address Read Log Command abort error.
ST340XXXAS, ST380XXXAS and ST3160XXXAS to 3.05 Fix to address intermittent hard drive no-shows after system comes out of hibernation.
ST3500641NS to 3.AES Changes to the refresh rate of the DRAM used on the drive.
ST3500640NS to 3.AEJ Initial release.
HDTXX... & HDSXX... codes go to Masked ROM version. HDS725050KLA360 to AQ1A to also Fix an issue that occurs while running in NCQ mode with write cache disabled.
ST3xxxx4SS to BA26 Improves intialization times with some ServeRaid controllers Performance improvements under some sequential workloads.
ST3xxxx5SS to BA35 Improves intialization times with some ServeRaid controllers
ST9xxx51SS to B612 Intial release of firmware
ST9xxxx2SS to B526 Improves intialization times with some ServeRaid controllers
MAUxxxx and MAXxxxx Added support for new SAS features required by new SAS controllers.
IBM SAS Hard Disk Drive Update Program Version 1.01 Please refer to RETAIN tip H186019.
Support of ServeRaid 8e Raid controller Support of ServeRaid 8k Raid controller Support of ServeRaid 8l Raid controller Support of on-board LSI 1064 controller IBM MegaRaid 8480 Raid Controller
Firmware updates to drives with Product ID strings:
GNAxxxx and BBAxxxx to BH0G Picks up the latest network roll of firmware fixes to improve performance under some sequential workloads and improvements to signal quality parameters.
ST9xxxx to B51D amd ST3xxxx to BA18 Picks the latest network roll of firmware fixes to address unexpected system hangs and some performance improvements.
MAVxxxx to S116 and MAYxxxx to T107 Picks up the latest network roll of firmware fixes and to improve signal quality parameters.
MAXxxxx to T904 Initial release ============================================================
IBM SAS Hard Disk Drive Update Program Version 1.00 Initial Release
Support of Adaptec 48xxx based controllers Support of ServeRaid 8i Raid controller Support and updates to drives with product ID strings of: ST936701SS ST973401SS ST336754SS ST373454SS GNAxxxxx BBAXXXXX
ibm_fw_hddlegacy_sas-1_22_01_linux_32-64_chg
======================================================= Change History for Qlogic Converged Network Adapter FC/FCoE Driver ======================================================= Document Name: Change History Document Status: IBM General Avalibility Document Version: 8.07.00.42.c Latest Package Version: 8.07.00.42.c Latest Driver Version: 8.07.00.42.12.0-k Document Updated: 03/26/2017 Product: Qlogic FC/FCoE Linux Device Driver
RHEL7, RHEL6, SLES11, SLES12, UEK, UEK2, XS65, XS6: * qla2xxx: Add support to disable laser for ISP27XX. * qla2xxx: Add RDP extensions. * qla2xxx: Set relogin flag when we fail to queue login requests. * qla2xxx: Fix default value descriptions for module parameters. * qla2xxx: Enable T10-DIF for ISP27XX. * qla2xxx: Use valid BBCR offset and datatype. * Revert "qla2xxx: Set echo test mailbox command option bit15 correctly."
Version 8.07.00.27 Fixes and Ehancements:
Software/Driver
* qla2xxx: Avoid asynchronous abort requests.
* qla2xxx: Avoid crossing initiator/target modes during AEN handling.
* qla2xxx: Fix invalid offset reference of inquiry response data.
Version 8.06.00.10 Fixes and Ehancements:
Software/Driver
* Remove entry in outstanding_cmds array if we fail to abort a request.
* Clear RISC INT reg only for an event and not always while polling.
* Fix undefined behavior in call to snprintf().
* Added T10 DiF/DiX support for ISP83xx.
* ISP83xx CNA support * IDC support for three protocols. * Loopback support. * Beacon support.
* Added support for bidirectional commands
* Added support for MCTP dump
* ISP83xx(16G FC) support for Xenserver 6.0 and Oracle UEK.
* SRB Consolidation.
* RSCN handling changes.
* Increase in support of maximum fibre devices.
* Enhancements to support ISP83xx (Limited support). * Driver features supported * 10GB link support only * Port device discovery * LUN discovery * I/O * Perturbations * SG resets of host and SCSI devices.
* Driver features not supported * Beacon support * Loopback * T10 DIX/DIF * SFP read/write * QCC GUI Support * QCC CLI Support * NPIV * Multi-Queue * Boot from SAN * FC-Tape * SLES10.3 driver: * Fix not to MPI reset on ISP83xx is not included.
* Implemeted beacon on/off for ISP82xx.
* Add support for ISP82xx to capture dump (minidump) on failure.
* Provide method for updating I2C attached VPD.
* Resync with latest ISP24xx/25xx firmware (5.08.00).
Industry Standards Compliance ----------------------------- * N/A
3. Bug Fixes
The following fix has been made to the Fibre Channel and FCoE Adapter Inbox Driver Update for Linux Kernel 2.6.x and 3.x:
* 8.04.00.12.xx.y-k * Update the copyright information. * Display the lock owner on lock acquire failure. * Move loopback mode reset after chip reset check. * Extra loopback error handling for ISP83xx. * Do link initialization on get loop id failure. * Do MPI reset only for 81xx.
V2632 (RHEL 6.x, SLES 11.x, Citrix 6.0, UEK): * Revert "qla2xxx: Optimize existing port name server query matching." * Revert "qla2xxx: Avoid losing any fc ports when loop id's are exhausted." * Don't free pool that wasn't allocated. * Unload hangs after issuing BSG commands to vport.
Citrix 6.0: * Create initrd as a part of installation and removal of the driver rpm. * RPM install should install driver under extra instead of driver directory.
RHEL 5.x, SLES 10.x: * MBA_IDC_NOTIFY case should fallthru. * Add fw_dump_size sysfs attribute file. * Add test for validity of virtual host in netlink interface.
SLES 10.x: * Add 8031/2031 cases to request firmware.
* 8.04.00.11.xx.y-k * Move marking fcport online ahead of setting iiDMA speed. * Add 16Gb/s case to get port speed capability. * Get VPD information from common location for CNA. * Dont clear drv active on iospace config failure. * Display that driver is operating in legacy interrupt mode. * Add "16" speed to link speeds array in qla2x00_iidma_fcport() function * Correct race in loop_state assignment during reset handling. * Reject loopback request if one is already in progress. * Update the FTP site references in the driver sources.
V2632 (RHEL 6.x, SLES 11.x Citrix 6.0 and UEK): * Obtain loopback iteration count from bsg request. * Parameterize the link speed string conversion function. * Update ql2xextended_error_logging parameter description with new options. * Fix typo in qla2xxx driver. * Free rsp_data even on error in qla2x00_process_loopback(). * Avoid null pointer dereference in shutdown routine.
RHEL 5.x: * Remove fabric_logout() calls from qla2x00_dev_loss_tmo_callbk() function.
SLES10.x: * Clear local references of rport on device loss timeout notification from FC transport.
* 8.04.00.10.xx.y-k * Honor status value of 2 for report-id acquisition. * Ignore driver ack bit if corresponding presence bit is not set. * Add Gen3 PCIe speed 8GT/s to the log message. * Acquire risc semaphore before resetting ISP.
V2632 (RHEL 6.x, SLES 11.x Citrix 6.0 and UEK): * Ramp down queue depth for attached SCSI devices when driver resources are low. * Determine the number of outstanding commands based on available resources. * Fix for kernel crash when external loopback diagnostic is run through BSG interface. * Fix coccinelle warnings in qla2x00_relogin. * Test and clear FCPORT_UPDATE_NEEDED atomically. * Use correct Request-Q-Out register during bidirectional request processing * Fix typo in qla83xx_fw_dump function. * Move noisy Start scsi failed messages to verbose logging level. * Fix for warnings reported by sparse.
RHEL 5.x: * Inclusion of 4G/8G firmware version 5.08.00. * Log message when qla2xenablemsix module parameter is set to 2( MSI mode) and adpater does not support MSI mode. * Revert "qla2xxx: Use GFF_ID to check FCP-SCSI FC4 type before logging into Nx_Ports" * Revert "qla2xxx: No fcport FC-4 type assignment in GA_NXT response."
Citrix 6.x: * RPM build should hide the directory naming convention from user.
* 8.04.00.09.xx.y-k * No fcport FC-4 type assignment in GA_NXT response. * Fix checkpatch error in qla2xxx_mctp_dump. * Change in setting UNLOADING flag and FC vports logout sequence while unloading qla2xxx driver. * Clear unsupported 'states' during Get-FW-State queries.
V2632 (RHEL 6.x, SLES 11.x Citrix 6.0 and UEK): * Pass correct parameters while creating an initrd. * Remove spurious taking of ha->vport_slock spinlock.
UEK: * Add macro for kernel extended version.
RHEL 5.x: * Use GFF_ID to check FCP-SCSI FC4 type before logging into Nx_Ports. * Pass correct parameters while creating an initrd.
8.04.00.08 Initial release of Qlogic 10Gb FC Driver for RHEL5
qlgc_dd_fc_qla2xxx-8_07_00_42_c_sles12_32-64_chg
uEFI Flash Update Version 1.40 (BuildID A8E122B) Change History
Version 1.40 - BuildID: A8E122B ------------------------------------------------- Problem(s) Fixed: - Fixed an issue where system memory peformance is degraded while detecting correctable errors in a Memmory DIMM. - Fixed an potential OS hang when handling certian memory events.
Enhancements: Limitations: Dependencies:
Version 1.30 - BuildID: A8E120C ------------------------------------------------- Problem(s) Fixed: - Fixes an issue where OS may crash depending on level of the Intel processors in the system. - System Management Mode (SMM) BIOS Vulnerability - privilege escalation issue.
Enhancements: Limitations: Dependencies:
Version 1.21 - BuildID: A8E118D ------------------------------------------------- Problem(s) Fixed: - Next Server Restart, NextBootEnabled functions not resulting in PXE Boot in Legacy Mode.
Enhancements: Limitations: Dependencies:
Version 1.20 - BuildID: A8E118C ------------------------------------------------- Problem(s) Fixed: - Fixed OpenSSL vulnerabilities as reported in CVE Advisories: CVE-2015-1793, CVE-2015-1789, CVE-2015-1790, CVE-2015-1792 - Fixed issue when PXE booting on the next boot Limitations: Dependencies:
Version 1.10 - BuildID: A8E116C ------------------------------------------------- Problem(s) Fixed: - Updated UEFI's OpenSSL code to address these security vulnerabilities: CVE-2015-0209, CVE-2015-0286, CVE-2015-0287, CVE-2015-0288, CVE-2015-0289 - Fixed issue of system not rebooting after making a change to a setting in Setup. - Fixed issue of system configuration is not correct when disabling Emulex ports.
Enhancements: Limitations: Dependencies:
Version 1.00 - BuildID: A8E114I ------------------------------------------------- Problem(s) Fixed: - Fixed issue of system hanging during boot process with BroadComm adapter present - Fixed issue of Agentless feature not providing necessary information. Enhancements: Limitations: Dependencies:
Version 1.00 - BuildID: A8E114H ------------------------------------------------- Problem(s) Fixed: - Updated UEFI's OpenSSL code to address these security vulnerabilities: CVE-2014-3571, CVE-2014-3569, CVE-2014-3572, CVE-2014-8275, CVE-2014-3570. - Correct configuration selection for serial COM ports settings under F1/Setup. - Resolve security issue when flashing UEFI code. - Fixed boot sequence when booting with secure boot enable, - Fixed the secondary pciDevices array table to contain the correct values for devices on the secondary pci bus. - Fixed OS crashing when parameter "intel_iommu=on" passes to the linux kernel. Enhancements: -Enchance UEFI Recovery code to automatically recover in the event that an user enables Secure Boot without MS 3rd party certificate. Limitations: Dependencies:
Version 1.00 - BuildID: A8E112B ------------------------------------------------- Problem(s) Fixed: - SKLM (Security Key Lifecycle Manager) support Enhancements: Limitations: Dependencies:
Version 1.00 - BuildID: A8E112A ------------------------------------------------- Problem(s) Fixed: - Various fixes preventing IMM and UEFI communication breakdowns that could lead to IMM crashing - Fixed an issue in which QPI fail down would not be reported - Fixed an issue in which GPT corruption would cause a system hang Enhancements: - User now has more time at UEFI splash screen to enter F1 setup or pDSA diagnostics - System Event Log will now notify user when booting from backup bank Limitations: Dependencies:
Version 1.00 - BuildID: A8E110A ------------------------------------------------- Problem(s) Fixed: Enhancements: - Support for FlashDIMMs Limitations: Dependencies: - Please use with IMM level 58W or later
Version 1.00 - BuildID: A8E108M ------------------------------------------------- Problem(s) Fixed: - Fixed an issue in which the boot order was unable to be set via ASU - Fixed an issue in which a system could end up in an infinite reboot loop - Fixed an issue in which a system could hang during boot following a double bit memory error Enhancements: Limitations: Dependencies: - Please use with IMM level 58I or later
Version 1.00 - BuildID: A8E108L ------------------------------------------------- Problem(s) Fixed: - Fixed an issue in which an address parity error could cause the system to appear hung - Numerous cosmetic and functional setup menu fixes - Fixed an issue preventing console redirection settings from being dynamic - Numerous error reporting fixes including DIMM isolation for memory errors - Fixed an issue in which duplicate device IDs were sent to the IMM, causing an IMM crash - Fixed multiple cases in which uefi would hang during boot Enhancements: - Updated to Intel MRC 1.4 - Updated onboard USB3.0 driver firmware Limitations: Dependencies: - Please use with IMM level 58I or later
Version 1.00 - BuildID: A8E104U ------------------------------------------------- Problem(s) Fixed: - Fixed issue in which single-socket systems could hang during UEFI boot. - Fixed issue in which system would not boot to generic hard drive boot order entry. - Fixed issue in which editing boot order using ASU would cause valid boot entries to disappear. Enhancements: Limitations: Dependencies:
Version 1.00 - BuildID: A8E104T ------------------------------------------------- Problem(s) Fixed: - ASU can not configure bootorder through IMM CIM interface. - After a create iSCSI attempt in F1 setup menu, ASU will try to read iSCSI settings from UEFI XML file. In this case, ASU will not find property for iSCSI in XML file. Enhancements: Limitations: Dependencies:
Firmware Version: 11.2.1193.38 Supported On: System x Rack and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support - Windows 2016 Support - VMware ESXi 6.5 Support
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
- When modifying configuration values for an iSCSI target, attempting to save the target with any invalid values may result in all values for that target being cleared. If this occurs, re-add the target using only valid configuration values. Please consult the Emulex Boot Manual for a description of valid configuration values.
Problems Fixed: - PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140) - "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086) - FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561) - UE seen while booting the system after a CoreDump - When NIC traffic has run on all the 8 vNICs of an ASIC, the vnics of first port are not honoring the assigned BW - SRIOV performance & Fairness for 16VMs is low on Linux and VMware - ML2 VFA5 device name is show "N/A" under IMM web and CLI of server management>Adapters - BW changes not getting updated with vNIC1 mode - Enable 100M/10M speed in set speed for SGMII interface - UCM/vNIC2, Ports/PCI functions supporting FCoE need to be differentiated to make it easier for the user - UCM/vNIC2 ability to program VirtWWN/WWPN independent of BFS Enable - iSCSI boot not working on higher order PCI functions (PF8 11)on 4 port controllers on ARI enabled systems - Can't install Windows2012 onto the iSCSI LUN whose LUN ID is not 0 - Fixed several issues related to IBM Agentless inventory management - Under heavy bi-di traffic with XE102/XE104 network disconnects can occur during failover/switch side link bounce
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.261.41 Supported On: IBM System x
Problems Fixed: - Hit BSOD during VMQ overnight traffic test with cpu affinity change - IBM VFA5 Adapter causing software panic on IBM G8246 Switch in UFP mode - LPVIDs are not getting saved in vNIC2 mode if we change mode from vNIC1 mode to vNIC2 - In MC VINC1, VNIC2, UFP modes, user should see only 4 functions per port for 2 port card
Incremental Interoperability: - Emulex VFA5 2x10 GbE SFP+ Adapter and FCoE/iSCSI SW for IBM System x - Emulex VFA5 2x10 GbE SFP+ PCIe Adapter for IBM System x - Emulex VFA5 2x10 GbE SFP+ Integrated Adapter for IBM System x
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
TMM Firmware Update for ServeRAID M5100 Series SAS/SATA Controllers
Adapters Supported: ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481) ServeRAID M5110e SAS/SATA Controller for IBM System x ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 1.01.03 - ------------------- TMMB: 70-25842-12 - Fixed issue where update may fail in 64 bit architecture.
Version 1.01.02 - ------------------- TMMB: 70-25842-12 - Fixed issue where update may fail to install when multiple ServerRAID adapters are installed
Version 1.01 - Initial release ------------------- TMMB: 70-25842-12 - Fixed issue where CVPM could report "Relearn timeout" during a relearn cycle (Retain Tip H183319) ibm_fw_sraidmr_5100-tmm-1_01_03_linux_32-64_chg
BIOS and Firmware Update for ServeRAID M5200 Series SAS/SATA Controllers
Adapters Supported: ServeRAID M5225-2GB SAS/SATA Controller ServeRAID M5210e SAS/SATA Controller for IBM System x ServeRAID M5210 SAS/SATA Controller
NOTE TO SERVICE - Reference RETAIN #N/A
Version 24.16.0-0104 - High Impact/High Probability of Occurrence ------------------- HII: E3.21.14.03 UEFI Driver: 0x06150501 BIOS: 6.32.02.1 MR FW: 4.660.00-8218 iMR FW: 4.660.01-8219
Fixes: - Fixed an issue where value defined for the DDR turning parameter DP_IO_VREF_1_2 was wrong for M5210. (SCGCQ01350295) - Fixed an issue where device PD for PM1633 Samsung SSD were not to accessible. (SCGCQ01268412) - Fixed an issue where the amber LED did not turn on when a configured disk was removed. (SCGCQ01343017)
Version 24.16.0-0101 - High Impact/High Probability of Occurrence ------------------- FW Package: 24.16.0-0101 HII: E3.21.14.03 UEFI Driver: 0x06150501 BIOS: 6.32.02.1 MR FW: 4.660.00-8214 iMR FW: 4.660.01-8215
Fixes: - Fixed an issue where some log context in UART was missing in TTY dump. (SCGCQ01230749) - Fixed an issuer kill adapter command was executed in line 1272 in file ../../raid/1078dma.c after pulling enclosure cable with IOs running on 240VD, JBOD SCGCQ00857533 - Fixed an issue where cache data could be lost when term log is set to "on." (SCGCQ01267851 Port of - SCGCQ01261426) - Fixed an issue where CRC mismatch and invalid log event found while querying for Controller properties and learn cycle in parallel. (SCGCQ01219985 Port of Defect - SCGCQ00919945) - Fixed an issue where rebuild error on PD with iMR 9341-8i SAS3008. (SCGCQ01220128 Port of - SCGCQ00915417) - Fixed an issue where drives were not marked as Foreign upon OCR when controller already has max configured PD's (SCGCQ01219897 Port of Defect - SCGCQ01163849) - Fixed an issue where drives with configuration were getting converted to JBOD if system already has maximum configurable drives. (SCGCQ01149764 Port of Defect SCGCQ01136693) - Fixed an issue where StorCLI failed to create single PD R0 from unconfigured good drive which has replaced a UBAD foreign drive. (SCGCQ01290418 Port of Defect SCGCQ01282181) - Fixed an issue where RAID personality, MR_DCMD_CFG_AUTOCFG DCMD is disabled in non-240 VD environment. (SCGCQ01267801 Port of Defect SCGCQ01213915) - Fixed an issue where StorCLI was not showing virtual drives after personality switch from SDS to RAID. (SCGCQ01238639 Port of Defect - SCGCQ01081305) - Fixed an issue where the controller became unresponsive after hitting OCM error. (SCGCQ01219901 Port of Defect - SCGCQ00924986) - Fixed an issue where the firmware halts upon changing controller personality to JBOD mode with MCTP enabled. (SCGCQ01260889 Port of Defect SCGCQ01252243) - Fixed an issue where firmware logs printed in UART were missing in tty dump. (SCGCQ01230749) - Fixed an issue where OS hung and iMR FW reset when delete and create VD commands using previous powersave physical drive spindowned. (SCGCQ01287286) - Fixed an issue where StorCLI was not showing virtual drives after personality switch from SDS to RAID. (SCGCQ01093890 PORT OF Defect - SCGCQ01081305) - Fixed PCI device page enclosure level/connector name to match SAS device page. (SCGCQ01071374) - Fixed an issue where mem 45569e20, cache line ffffffff' observed while running BGI on RAID 5 Volume with media errors. (SCGCQ01266169, SCGCQ01256120) - Fixed an issue where local storage admin config FSM failure on setting TR on 64 VDs, when there were a large number of events transferred over OOB, one event could be missing in some cases. (SCGCQ01243832, SCGCQ01243833, SCGCQ01243834, SCGCQ01243836 PORT OF Defect SCGCQ01128180) - Fixed an issue where some logs printed in UART were missing in TTY dump. (SCGCQ01242651, SCGCQ01242650, SCGCQ01242649 PORT OF Defect SCGCQ01230749) - Fixed an issue where firmware breaks MonTask: line 245 in file ../../raid/1078int.c with IOs on max VD configured and BGOps. (SCGCQ00895481, SCGCQ00895482, SCGCQ00895474 Defect SCGCQ00890133) - Fixed an issue where as part of R1 undergoing RLM to a R0 volume, the medium errors that were injected, were discovered but not reported as corrected. (SCGCQ00893669 PORT OF Defect -SCGCQ00846621) - Fixed an issue where iEEESGL flag was not getting set for IO request in SES DCDB handler. (SCGCQ01186523, SCGCQ01238262, SCGCQ01242590, SCGCQ01242592, SCGCQ01242597 PORT OF Defect - SCGCQ01157072)
Enhancements: - Added defines for SAS 4 and PCIe 4 speeds. (SCGCQ00948955) - Modified PCIe Link config pages to include a link field. (SCGCQ00954619) - MR API bit to indicate if the profile is NVMe Only profile. (SCGCQ01213092) - Fixed an issue where the foreign configuration that has been imported went off-line within few seconds, as all the drives are getting transitioned to Unconfigured-Good with PD_InsertionPostProcess() getting kicked-in. (SCGCQ01198744 Port of Defect SCGCQ00800589) - Added two new MFI_STAT values to better describe RAID 10 volume creation errors: MFI_STAT_INVALID_DRIVE_COUNT and MFI_STAT_UNEVEN_SPAN_NOT_SUPPORTED. (SCGCQ01222698) - Isolated faulty cable issue from bad drive issue. (SCGCQ01203751) - Removed all defines and structure fields related to SOP support. (SCGCQ00925839) - Removed all defines and structure fields related to AHCI support. (SCGCQ00948258) - Added EclosureLevel and ConnectorName fields to PCIe Device Page 0 with the same meaning as SAS Device Page 0. (SCGCQ00949638) - Added IOCException bit 10 to indicate that backend PCIe device support has been disabled due to an initialization failure and added InitStatus field to PCIe IO Unit Page 1 t provide more detail.(SCGCQ01009104) - Added flag to force completion queue entry return for NVMe Encapsulated request. (SCGCQ01013930) - Added Negotiated Link Rate and Negotiated Port Width to PCIe Device page 0. (SCGCQ01017027) - Added bit to LinkFlag field of PCIe IO Unit Page 1 PhyData to specify SRIS mode. (SCGCQ01018687) - Updated header file to include SATADeviceWait time to IO Unit page 11. (SCGCQ01092340) - Added new definitions for the ImageType field of FwDownload and FwUpload messages. Also, added new flash region definitions for the Flash Layout Extended Image Data. (SCGCQ01136127) - Added reason codes MPI26_EVENT_ACTIVE_CABLE_PRESENT and MPI26_EVENT_ACTIVE_CABLE_DEGRADED to Active Cable Exception Event Data. (SCGCQ01146583) - Defined interface to support firmware assisted VD/JBOD properties: max IO size, device queue depth. (SCGCQ01188711) - Fixed an issue where L2/L3 Cache error was detected on the RAID controller during boot (24 hours after shutdown hang. (SCGCQ01219839 Enhancement Request SCGCQ01018958)
Version 24.16.0-0092 - High Impact/High Probability of Occurrence ------------------- FW PACKAGE: 24.16.0-0092
MR FW: 4.660.00-8156
iMR FW: 4.660.01-8157
BIOS: 6.32.02.1
UEFI: 0x06150501
HII: 03.21.14.01
Fixes:
- Fixed an issue where MR_RAID_CTX_G35 reserved field has one bit too many, resulting in 17 bits in a U16 - (SCGCQ00886417)
- Fixed an issue where controller may hang when an OCR is triggered on a RAID5 LD with no supercap - (SCGCQ00926628)
- Fixed an issue where PDs are getting swapped and rebuild starts on incorrect PD after an enclosure power cycle - (SCGCQ00927155)
- Worked around an issue where a false ReplyParityError may occur - (SCGCQ00927504)
- Fixed an issue where numSGEExt field was removed from MPI25_SCSI_VENDOR_REGION, affecting support for 1MB IO - (SCGCQ00927738)
- Fixed an issue where CacheVault size reports as 0KB for some controllers - (SCGCQ00929077)
- Fixed an issue where controller firmware may halt with error "MonTask: line 1281 in file ../../raid/1078dma.c" - (SCGCQ00931397)
- Fixed an issue where ONFI hardware was disarmed on OCR - (SCGCQ00933096)
- Fixed an issue where MSM does not show "hide" option after "unhide" on RAID0 - (SCGCQ00933123) - Fixed an issue where rebuild doesn't complete with cmd_block_flush on RAID6 with SAS SSD - (SCGCQ00933841) - Fixed an issue where storcli is unable to create logical drives via auto-configuration, such as with command "storcli /cx set autopdcache=r0" - (SCGCQ00935727)
- Fixed an issue where a new field in RAID_MAP_EXT causes backward compatibility issues - (SCGCQ00940224)
- Fixed an issue where online firmware update may fail in Windows due to language attribute - (SCGCQ00941886)
- Fixed an issue where performance was lower than expected due to DataCacheInvalidateSnoop was not being used for sense buffer- (SCGCQ00944526)
- Fixed an issue where makefile is missing changes required for enabling PLDEBUG - (SCGCQ00945858)
- Fixed an issue where performance was lower than expected due to stale calls to processdevicewaitQ - (SCGCQ00947221)
- Fixed an issue where code events had repetitive IDs - (SCGCQ00948535)
- Fixed an issue where a value assigned to a variable is never used - (SCGCQ00948781)
- Fixed an issue where error "MonTask: line 245 ..1078int.c" may occur on reboot with foreign import - (SCGCQ00948931)
- Fixed an issue where two enclosure IDs are displayed in MSM Physical tab when connected via multipath to some enclosures - (SCGCQ00950425)
- Fixed an issue where firmware fails to copyback from hotspares - (SCGCQ00952836)
- Fixed an issue where inquiry string is not updated during drive firmware upgrade through offline mode update - (SCGCQ00953396)
- Fixed an issue where code analysis tool reported issues - (SCGCQ00954107)
- Fixed an issue where firmware may hang on enclosure power cycle - (SCGCQ00976597)
- Fixed an issue where error "MonTask: line 1281 in file ../../raid/1078dma.c" may occur on enclosure power cycle - (SCGCQ00976780)
- Fixed an issue where CacheCade firmware may not get enough time to flush windows when no free window is available - (SCGCQ00976904)
- Fixed an issue where ring buffer print was occurring even when PLDEBUG is not enabled - (SCGCQ00979831)
- Fixed an issue where controller firmware may halt at "MonTask:" when running IO to CacheCade Virtual Drives - (SCGCQ00980216)
- Fixed an issue where controller firmware may halt at "MonTask:" during enclosure power cycle - (SCGCQ00981645)
- Fixed an issue where DATATLB error may occur on hotplug of some enclosures - (SCGCQ00983232)
- Fixed an issue where controller firmware may halt when running SAS adapter diagnostic command from storcli - (SCGCQ00987879)
- Fixed an issue with some unused values in code - (SCGCQ00987940)
- Fixed some issues discovered in code review - (SCGCQ00987966)
- Fixed an issue where error "MonTask: line 909 in file ../../raid/raidscsi.c" may occur during heavy IO and power cycles - (SCGCQ00988674)
- Fixed an issue where data length may not be set appropriately based on CBD size - (SCGCQ00988813)
- Fixed an issue where storclio may fail to read some VPD information from SBR - (SCGCQ01065177, Port of SCGCQ00990939)
- Fixed an issue where OCR is not enabled by default in release candidate builds - (SCGCQ00991489)
- Fixed an issue where a performance issue may occur - 9% drops for 6Gig 512BSATASSDs with 24PD R5 in RW 32KB IOSz for 256QD - (SCGCQ00991492)
- Fixed an issue where kill adapter may occur when restoring multipath with SATA drives - (SCGCQ00992114)
- Fixed an issue where an uninitialized byte transfer variable may cause unaligned DMA lengths - (SCGCQ00994097)
- Fixed an issue where controller firmware may fault when importing a configuration with only Global Hotspare PDs on an iMR controller - (SCGCQ00994846)
- Fixed an issue where controller firmware may hang on abort of Background Initialization of a VD expansion - (SCGCQ00996532)
- Fixed an issue where pinned cache data structure members may need to be reinitialized between firmwares with different cache header versions - (SCGCQ00996607)
- Fixed an issue where enclosure discovery may fail when enclosure with spun-down drives is disconnected and reconnected - (SCGCQ00996692)
- Fixed an issue where error "IO error 9 in CheckFwIoDescList" may occur on cable pull/push - (SCGCQ00997291)
- Fixed an issue where CPU affinity define values may not be updated properly to align with CPU affinity structure changes - (SCGCQ01000077)
- Fixed an issue where DCMD processing may return before setting the JBOD as a boot device in NVRAM - (SCGCQ01000230)
- Fixed an issue where OCR may not be blocked after firmware downgrade - (SCGCQ01000359)
- Fixed an issue where SAS SSD RAID5 performance may be lower than expected - (SCGCQ01001861)
- Fixed an issue where CtrlInfo.adapterOperations3.supportProfileChange is missing in API- (SCGCQ01001936, SCGCQ01014835)
- Fixed an issue where number of LDs may not be checked before calling RM_SataBBMUpdateDivertNodesFromSBBMTable - (SCGCQ01002055)
- Fixed an issue where CacheCade Virtual Drive deletion path refers to the wrong Virtual Drive - (SCGCQ01002268)
- Fixed an issue where controller firmware may hang after connecting some enclosures with SATA drives - (SCGCQ01002798)
- Fixed an issue where error "MonTask: line 1281 in file ../../raid/1078dma.c" may occur when cables are removed/reinserted in a multipath environment with IO - (SCGCQ01002921)
- Fixed an issue where some changes were not ported - (SCGCQ01003552)
- Fixed an issue where controller may experience assertion failure when drives are being removed/reinserted with background IO - (SCGCQ01004144)
- Fixed an issue where DRAM signature may receive a stale copy on ONFI restore - (SCGCQ01004279)
- Fixed an issue where firmware switches descriptors and prepares for an offload even when SuperCap is absent - (SCGCQ01004385)
- Fixed an issue where performance may be lower than expected for Sequential Reads in RAID mode - (SCGCQ01012499)
- Fixed an issue where error "MonTask@line 179 in file ../../dm/src/chipmgr.c" may occur on repeated system reboots - (SCGCQ01015019)
- Fixed an issue where CacheCade parameters are populated in controller info even when 240VD feature is enabled - (SCGCQ01015026)
- Fixed an issue where SAS Port PAge 0 and SAS IO UNIT Page 1 did not function correctly resulting in MonTask error - (SCGCQ01015470)
- Fixed an issue where controller firmware may throw invalid arguments when setting debug variable for some commands - (SCGCQ01015761)
- Fixed an issue where controller firmware may exhibit MonTask error when setting up debug variables with levels from storcli - (SCGCQ01016534)
- Fixed an issue where controller firmware perform cache offload and restore operation even on a clean shutdown - (SCGCQ01018477)
- Fixed an issue where SDS personality was not supporting 1MB IO - (SCGCQ01020626)
- Fixed an issue where SDS personality did not have SAS drive queue depth of 128- (SCGCQ01020631)
- Fixed an issue where divert locks were not being used for Write-Back volumes on Sequential Read - (SCGCQ01020634)
- Fixed an issue where error "Core 0 in 245 in file ../../raid/1078int.c" may occur on cable remove/reinsert on JBODs with IO - (SCGCQ01020979)
- Fixed an issue where firmware may incorrectly disable the cache offload engine after an OCR when pinned cache is present and a clean shutdown occurs - (SCGCQ01021488)
- Fixed an issue where a DATATLB error may occur after flashing controller firmware and rebooting - (SCGCQ01023585)
- Fixed an issue where controller firmware may halt when controller firmware update occurs immediately after a drive microcode update - (SCGCQ01024661)
- Fixed an issue where error "Line 245 in ../../raid/1078int.c" may occur when rebooting server after inserting Virtual Drives when pinned cache is present - (SCGCQ01028404)
- Fixed an issue where write policy may not be retained after unblocking the SDVs and making the CacheCade Virtual Drive / SVD Optimal - (SCGCQ01028464)
- Fixed an issue where a MonTask error may occur when an SVD is associated with CacheCade and one of the SVD member drives is removed - (SCGCQ01030089)
- Fixed an issue where unsupported message types in MCTP path were not handled correctly - (SCGCQ01030166)
- Fixed an issue where an L2 Cache Error may occur when performing cable remove/reinsert on an enclosure - (SCGCQ01030408)
- Fixed an issue where TweakIO was not supported on iMR - (SCGCQ01032429)
- Fixed an issue where a cache restore operation may take more than 90 seconds when power cycles occur with pinned cache present - (SCGCQ01033348)
- Fixed an issue where error "line 1279 in file ../../raid/1078dma.c" with PL fault - (SCGCQ01033740)
- Fixed an issue where a Pinned Cache critical message may occur when booting from S3 sleep mode - (SCGCQ01033930)
- Fixed an issue where error "line 4839 in file ../../raid/cache.c" may occur with cache offload - (SCGCQ01034706)
- Fixed an issue where more than one special task could run on a CacheCade Virtual Drive - (SCGCQ01034955)
- Fixed an issue where recheck for presence of pinned cache may not occur after command block grant - (SCGCQ01034977)
- Fixed a timing issue by removing previous change SCGCQ01023287 - (SCGCQ01035343)
- Fixed an issue where Virtual Drive creation may fail in RAID mode on personality change - (SCGCQ01036091)
- Fixed an issue where controller firmware may fault with error "line 1279 in file 1078dma.c" - (SCGCQ01036154)
- Fixed an issue where a kill adapter may be issued when a TUR is sent to a device after IO timeouts - (SCGCQ01037095)
- Fixed an issue where controller firmware may fault when multipath is broken during IO - (SCGCQ01037747)
- Fixed an issue where EPDs may not be created after system reboot - (SCGCQ01038702)
- Fixed an issue where IO to JBOD may fail on some drives when a path is broken in a multipath scenario - (SCGCQ01038719)
- Fixed an issue where controller firmware may hang during an OCR when a reconstruction from RAID0 to RAID1 is in progress - (SCGCQ01039732)
- Fixed an issue where a read from an uninitialized pointer may occur - (SCGCQ01040543)
- Fixed some issues discovered as part of code review - (SCGCQ01040575)
- Fixed an issue where controller firmware may fault with error "MonTask: line 605 in file ../../raid/routines.c" when controller firmware update and drive firmware updates are performed simultaneously - (SCGCQ01040587)
- Fixed an issue where error "Assertion failure in ../../raid/cmd.c line 3089" may occur if host task management completes before pending commands are aborted or completed - (SCGCQ01040595)
- Fixed an issue where pinned cache may result in an assertion failure - (SCGCQ01041463)
- Fixed an issue where some error cases may not be handled properly - (SCGCQ01041729)
- Fixed an issue where abort task management function failes to abort firmware commands split into multiple internal commands - (SCGCQ01042128)
- Fixed an issue where a kill adapter may occur when disableErrorRecovery=1 and a DCMD is sent - (SCGCQ01042237)
- Fixed a compilation issue - (SCGCQ01042829)
- Fixed an issue where HII menu may not allow mode change - (SCGCQ01046130)
- Fixed issues discovered as part of code review - (SCGCQ01047319)
- Fixed an issue where error "MonTask: line 1280 in file ../../raid/1078dma.c" may occur when toggling SSD caching on/off during IO - (SCGCQ01048675)
- Fixed an issue where random performance may drop from 1.1M to 0.8M with SAS SSD - (SCGCQ01049230)
- Fixed an issue where supportBit functionality was not present for MR_CFG_USER_CONFIGURABLE - (SCGCQ01049236)
- Fixed an issue where cache bypass may not work with 4k drives and a random workload - (SCGCQ01049253)
- Fixed an issue where PLDEBUG was not disabled - (SCGCQ01049262)
- Fixed an issue where code may try to access 255th Logical Drive when only 240 are supported - (SCGCQ01049335)
- Fixed an issue where makeSystem bit in MR_PD_ALLOWED_OPS was not disabled - (SCGCQ01050314)
- Fixed an issue where alternate path cleanup on device removal may not occur correctly - (SCGCQ01052105)
- Fixed an issue where JBOD behavior may automatically change to EPD - (SCGCQ01053601)
- Fixed an issue where EPD may be deleted after a controller OCR - (SCGCQ01054436)
- Fixed an issue where CacheCade Virtual Drive performance was lower than expected - (SCGCQ01055907)
- Fixed an issue where MonTask error may occur on firmware upgrade - (SCGCQ01056349)
- Fixed an issue where error "DATA TLB ERROR(SRR0/1,ESR) exception: sf=c0137f50" may occur under IO to VDs and EPDs in EPD mode - (SCGCQ01057471)
- Fixed an issue where error handling may not occur for direct attached devices during targetID allocation - (SCGCQ01058026)
- Fixed an issue where SAS Address for paths may not be shown in firmware events when true multipath is enabled - (SCGCQ01058118)
- Fixed an issue where firmware flash with OCR may result in "Host memory not available" - (SCGCQ01059104)
- Fixed an issue where OCR was allowed in Safe Mode - (SCGCQ01059795)
- Fixed an issue where MonTask error may occur when IO is underway during SVD CacheCade association process - (SCGCQ01060661)
- Fixed an issue where MonTask DATATLB error may occur on IO timeout with immediate IO - (SCGCQ01061150)
- Fixed an issue where Virtual Drives may be displayed as 0.000TB after doing a factory reset - (SCGCQ01061594)
- Fixed an issue where rebuild may not recover properly on medium errors - (SCGCQ01063920)
- Fixed an issue where an EPD may become Foreign on EPD removal/reinsertion - (SCGCQ01064307)
- Fixed an issue where an incorrect message may be displayed in EPD mode when no Virtual Drives are present - (SCGCQ01064584)
- Fixed an issue where firmware may report failure when initiating an Instant Secure Erase against Foreign drives that are Locked - (SCGCQ01064725)
- Fixed an issue where enclosure topology may change after deleting EPD/JBOD - (SCGCQ01066150)
- Fixed an issue where drive slot information may not be shown properly, or always shows as 0-3:1:0 - (SCGCQ01066199)
- Fixed an issue where firmware may allow a reconstruction from RAID0 to RAID6 on iMR - (SCGCQ01066211)
- Fixed an issue where enclosure topology information may not be cleared from NVRAM - (SCGCQ01069328)
- Fixed an issue where firmware may throw an event with "Pass-through EPD" instead of "JBOD" - (SCGCQ01070146)
- Fixed an issue where error "DATA TLB ERROR(SRR0/1,ESR) exception: sf=c0137f50" may occur - (SCGCQ01070174)
- Fixed an issue where controller firmware may fail to discover a directly-attached SSD - (SCGCQ01073684)
- Fixed an issue where DDF may be read when the drive is locked by a third-party application - (SCGCQ01074264)
- Fixed an issue where IO stalls may be seen when Foreign Drives are imported while Pinned Cache is present - (SCGCQ01074390)
- Fixed an issue where controller firmware may fault with no cache metadata while running heavy IO - (SCGCQ01075043)
- Fixed an issue where debug routines were not as robust as possible - (SCGCQ01075835)
- Fixed an issue where a DATATLB error may occur on import of a Foreign Configuration - (SCGCQ01077584)
- Fixed an issue where JBOD may show up as a RAID0 in 240VD configuration - (SCGCQ01077659)
- Fixed compiling issues for iMR - (SCGCQ01077981)
- Fixed an issue where controller firmware may issue kill adapter when power cycling a secondary enclosure repeatedly - (SCGCQ01078220)
- Fixed an issue where error "FW Crash at line 2001 in file /bbu/onfi.c" may occur when running IO on Virtual Drives when a CacheCade Virtual Drive is present - (SCGCQ01080073)
- Fixed an issue where controller cannot set personality behavior after flashing firmware - (SCGCQ01080529)
- Fixed an issue where storcli not showing Virtual Drive after controller personality switch - (SCGCQ01081305)
- Fixed an issue where controller was not properly determining if a drive needs to be locked - (SCGCQ01083145)
- Fixed an issue where activity LED is always on even when no drives are present - (SCGCQ01083581)
- Fixed an issue where L2 Cache Error occurs when IO is run with cable remove/reinsert - (SCGCQ01087818)
- Fixed an issue where error "MonTask: line 3169 in file mptrec.c" may occur on cable remove/reinsert- (SCGCQ01089223)
- Fixed an issue where Phase 12 physical layer was not - Integrated - (SCGCQ01089372)
- Fixed an issue where EPDs auto configuration fails during OCR on 240VD setup when Pinned Cache is present - (SCGCQ01096547)
- Fixed an issue where a Physical Layer fault may occur when running IO on SVD when a CacheCade Virtual Drive is present a target resets are issued to Secure JBOD - (SCGCQ01117179)
- Fixed an issue where controller firmware did not have enough descriptors for 2-die chips - (SCGCQ01118693)
- Fixed an issue where an ECC error spike may be observed during a Cache Restore operation when read eye training has failed - (SCGCQ01124194)
- Fixed an issue where compilation broke due to increase in iopath size by 1120 bytes - (SCGCQ01126393)
- Fixed an issue where a DATATLB error may be observed when IO, target resets, OCR and a rebuild occur concurrently - (SCGCQ01130939)
- Fixed an issue where controller firmware event logs show EPD creation when booted in JBOD mode - (SCGCQ01130979)
- Fixed an issue where a kill adapter may occur when moving a PI-enabled RAID5 Virtual Drive to degraded state - (SCGCQ01131151)
- Fixed an issue where retry mechanism for Cache Offload may run when ECC errors is less than 40 - (SCGCQ01131808)
- Fixed an issue where Write Back volumes may not be imported when changing controller personality - (SCGCQ01135382)
- Fixed an issue where controller firmware may disable Fast Path for SED/FDE JBOD - (SCGCQ01135893)
- Fixed an issue where SES topology information may not be updated as expected - (SCGCQ01137834)
- Fixed an issue where UEFI driver may not load - (SCGCQ01138961)
- Fixed an issue where MR_DCMD_CFG_AUTOCFG DCMD is not allowed when ignore64ldRestriction is not set - (SCGCQ01139912)
- Fixed an issue where some messages in VDM queue may not be initialized with proper values - (SCGCQ01149312)
- Fixed an issue where a MonTask error may occur when Cache Offload does not complete successfully - (SCGCQ01149971)
- Fixed an issue where debug code added for testing was not removed - (SCGCQ01152456)
- Fixed a performance issue where normal IOs were being impacted by inline DMA for double-buffered IO - (SCGCQ01154297)
- Fixed an issue where controller firmware may use a bad block for Cache Offload operation - (SCGCQ01159064)
- Fixed an issue where coalescing was enabled for Write-Through EPDs in JBOD personality - (SCGCQ01161309)
- Fixed an issue where performance may drop 15% SR IO Sizes-4K QD(256),12G SAS HDD,x16 - (SCGCQ01166024)
- Fixed an issue where performance may drop 12% to 22% SW IO Sizes-16K QD(2) ,12GSAS HDD,x8,x16x,24,x40PD - (SCGCQ01166028)
- Fixed an issue where a Fatal Firmware error may occur during power cycle - (SCGCQ01167011)
- Fixed an issue where performance may drop 20% SR, 8K-IO Size,QD(256) RAID-10 6G SATA-HDD x16DC - (SCGCQ01171907)
- Fixed an issue where very high write latency may occur - (SCGCQ01176422)
- Fixed an issue where activity LED may be lit and never turn off - (SCGCQ01191412)
- Fixed an issue where performance may drop 6% to 15% Perf drop in all IO size with Higher QD in 12G SAS HDD [x16EC,x24EC,x40EC] - (SCGCQ01193231)
- Fixed an issue where error "MonTask: line 4789 in file ../../raid/cache.c" may occur when importing a RAID0 CacheCade Virtual Drive - (SCGCQ00942270)
- Fixed some code review defects - (SCGCQ00980759)
- Fixed an issue where writes may fail on JBODs after an OCR - (SCGCQ00981721)
- Fixed an issue where host DDF memory is not reserved after OCR followed by firmware flash - (SCGCQ00992541)
- Fixed an issue where a kill adapter may occur on heavy IO with background operations on CacheCade Virtual Drives and SVD - (SCGCQ00995919)
- Fixed an issue where controller firmware may asser when JBOD is removed during an OCR - (SCGCQ00996138)
- Fixed an issue where a suspended rebuild does not start on a RAID1 CacheCade physical drive even after SSCD flush has completed - (SCGCQ00999971)
- Fixed an issue where error "Montask in line 164 in file ../../raid/2108vDma.c" may occur when scanning for Virtual Drives on directly-attached PI drives - (SCGCQ01000488)
- Fixed an issue where storcli command "storcli /cx show preservedcache" will report success on an iMR controller - (SCGCQ01002022)
- Fixed an issue where kill adapter may occur when running 64K IOs on Virtual Drives and JBODs with a mix of 6Gbps and 12Gbps drives - (SCGCQ01023587)
- Fixed an issue where a drive microcode update start event is not logged when offline method used - (SCGCQ01024062)
- Fixed an issue where insertion/removal of a secondary SEP or expander device would affect firmware internally maintained enumerated topology order - (SCGCQ01024970)
- Fixed an issue where controller firmware may hang on power cycle of an enclosure - (SCGCQ01043365, Port of SCGCQ01025024)
- Fixed an issue where all EPD errors may not return MFI_STAT_SCSI_DONE_WITH_ERROR - (SCGCQ01025697)
- Fixed an issue where EPDs may be created in DDF_ForeignScan() - (SCGCQ01028289)
- Fixed a code merge issue - (SCGCQ01029522)
- Fixed an issue where a DATATLB error "restore_cache_line_buffer +1b0" may occur on enclosure removal while updating drive firmware - (SCGCQ01029529)
- Fixed an issue where Unavailable flag may not be cleared for VDs even after spin-up recovery - (SCGCQ01030591)
- Fixed an issue where storcli drive inquiry command may fail when true multipath is enabled - (SCGCQ01033041)
- Fixed an issue where a DATATLB "DM_PL_ProcessCompletion+334" error may occur while running IO - (SCGCQ01033082)
- Fixed an issue where controller firmware did not allocate targetID based on the port and slot the JBOD is direct attached to - (SCGCQ01033957)
- Fixed some code review issues - (SCGCQ01036929)
- Fixed an issue where backend Physical Layer frames for Core0 were not 4k - (SCGCQ01037133)
- Fixed an issue where kill adapter may occur when power cycling enclosures - (SCGCQ01037718)
- Fixed an issue where enclosure enumeration order should remain consistent across OCRs and reboots - (SCGCQ01038595)
- Fixed an issue where incorrect values may occur in CacheCade Virtual Drive counters - (SCGCQ01039080)
- Fixed an issue where unsupported message type handling does not occur according to MCTP spec - (SCGCQ01039363)
- Fixed an issue where controller firmware allows switch from EPD to EPD-passthrough even with more than 128 devices - (SCGCQ01039421)
- Fixed an issue where a diagnostics test failure moves a Secure JBOD drive to Foreign Unconfigured Good - (SCGCQ01039512)
- Fixed an issue where controller firmware may crash during hibernation - (SCGCQ01042005)
- Fixed an issue where ldlimit may not be able to reset to default when Virtual Drives exist with targetID greater than 64 - (SCGCQ01042131)
- Fixed an issue where storcli may show an incorrect number of Physical Drives - (SCGCQ01042249)
- Fixed an issue where controller may show port number as "null" or the same even with different types of port connectivity - (SCGCQ01045937)
- Fixed an issue where an out of bound read and uninitialized scalar variable may occur - (SCGCQ01046119)
- Fixed an issue where controller cannot create the 240th Virtual Drive even though 240 are supported - (SCGCQ01046644)
- Fixed some code review issues - (SCGCQ01047222)
- Fixed an issue where "OOB_slaveOnly" variable may not be set to 0 for PCIe path - (SCGCQ01049035)
- Fixed an issue where debug prints were not removed in Host Task Management and EPD creation path - (SCGCQ01049304)
- Fixed some code review issues - (SCGCQ01050889)
- Fixed an issue where flags indicating SSC flush status may not be cleared even after completion of the SSC flush - (SCGCQ01053360)
- Fixed an issue where iMR controller restart may fail after firmware flash even though OCR is enabled - (SCGCQ01053769)
- Fixed some code review issues - (SCGCQ01054547)
- Fixed an issue where error "Exception in core 0" may occur when running target resets with IO - (SCGCQ01058187)
- Fixed an issue where controller firmware hangs after destaging preserved cache - (SCGCQ01059184)
- Fixed an issue where a kill adapter may occur when aborting a Full Initialization on 240 Virtual Drives - (SCGCQ01059439)
- Fixed an issue where a target reset may be issued on an incorrect device handle in true multipath Write-Back configuration - (SCGCQ01059769)
- Fixed an issue where error "MonTask: line 2379 in file ../../raid/2108vI2o.c" may occur - (SCGCQ01060599)
- Fixed an issue where error "FW crash at line 1155 in file ../../dm/src/dm.c" may occur - (SCGCQ01061211)
- Fixed an issue where error "Controller crash observed at line 1280 in file ../../raid/1078dma.c" when rebuilding a RAID1 - (SCGCQ01062346)
- Fixed an issue where SSC flush flags may be cleared in a non-command-block context - (SCGCQ01062386)
- Fixed an issue where storcli may display "Max SGE Count 60" even after largeIOsupport is enabled - (SCGCQ01064082)
- Fixed an issue where a DATATLB error "firmware break at Line 245 in ../../raid/1078int.c" may occur - (SCGCQ01064652)
- Fixed an issue where firmware logs may show an incorrect print for Background Initialization start on a RAID0 Virtual Drive after completing a Reconfiguration - (SCGCQ01065567)
- Fixed an issue where a kill adapter may occur when hotplugging 240 EPDs with IO in progress - (SCGCQ01066104)
- Fixed an issue where L2 Cache Error may be seen during ref tag error recovery on a PI Virtual Drive - (SCGCQ01066219)
- Fixed a performance issue where up to ~18% Perf Drop, SW for 4K/8k/16K @ 4&16QD, RW for 8K @ 4 QD, 12G SAS SSD,24PD,R5 - (SCGCQ01067709)
- Fixed an issue where controller may fail a drive for a SMART error even when MRIE mode is 2 or 3 - (SCGCQ01070758)
- Fixed an issue where not enough information was included in dump memory to debug memory alloc/free related issues - (SCGCQ01073663)
- Fixed an issue where controller firmware may halt on Pinned Cache generaion with multiple RAID0 Virtual Drives - (SCGCQ01075170)
- Fixed an issue where failed FastPath / immediate IO may report as success leading to SCSI-3 PRR failure - (SCGCQ01076183)
- Fixed an issue where a DATATLB error may occur when running IO on a max-PD Virtual Drive with Daisy-chained enclosures - (SCGCQ01076235)
- Fixed an issue where command queue depth only scaling to 64 for SAS HDDs - (SCGCQ01076289)
- Fixed an issue where multiInitSupport was not in the EepromMfcDisplay debug function - (SCGCQ01079664)
- Fixed an issue where controller firmware crash may occur when running IO in JBOD mode and multipath is enabled - (SCGCQ01080258)
- Fixed an issue causing iMR compilation problems - (SCGCQ01081326) - Fixed an issue where error "Montask line 121 in file ../../raid/taskman.c" with "No more tasks available!" - (SCGCQ01082101) - Fixed an issue where security key may be deleted when switching controller personality - (SCGCQ01085646)
- Fixed an issue where cache thresholds may not be adjusted appropriately on Pinned Cache generation - (SCGCQ01099559)
- Fixed an issue where error "Input parameters are invalid" may occur when creating a Virtual Drive in Advanced configuration - (SCGCQ01125119)
- Fixed an issue where double buffering code was not under an #ifdef for easy switch - (SCGCQ01131004)
- Fixed a performance issue where 5.5% drop in R10,R0 with 16K IO size SR-4QD with 40PD-12G-4K-SAS-HDD-SS-256K-WB-mode-Win2012-R2 - (SCGCQ01134731)
- Fixed a performance issue where 15% to 20% drops SW IO Sizes-256K QD(1,2),12G SAS HDD,x16,x24,x40- (SCGCQ01166023)
- Fixed a performance issue that may occur with Virtual Drives with 4Kn members - (SCGCQ01180459)
- Fixed a performance issue where RAID10 reads intermittently provide very poor performance - (SCGCQ00930527)
- Fixed an issue where controllers with 2GB of DRAM may fail to discover drives - (SCGCQ00987952)
- Fixed an issue where MSM provides "Make EPD" option for Unconfigured Good drives - (SCGCQ00995279)
- Fixed an issue where a kill adapter may occur under heavy IO in a multipath environment - (SCGCQ01016542)
- Fixed an issue where error "Assertion failure at line 807 in /raid/cache.c" may occur when running CacheCade Virtual Drive association/deassociation and SVD background operations are in progress - (SCGCQ01018367)
- Fixed an issue where DMA context switching settings are non-optimal for less than 24 disk expander configurations - (SCGCQ01020635)
- Fixed an issue where error "Firmware crash@line 108 in file ../../raid/taskman.c" may occur when performing creation/deletion of EPDs - (SCGCQ01023898)
- Fixed an issue where Unconfigured drives may be marked as Foreign even when no DDF is present - (SCGCQ01023963)
- Fixed an issue where error "Assertion failure in ../../dm/src/dm.c at line 1054" may occur on enclosure power cycle - (SCGCQ01025328)
- Fixed an issue where true multipath was not enabled - (SCGCQ01028614)
- Fixed an issue where enclosure devices at sasLevels greater than 1 were determined as direct attached devices - (SCGCQ01029470)
- Fixed an issue where exposeMultipath EPD param during behaviour mode change was not handled properly - (SCGCQ01029550)
- Fixed an issue where controller firmware fails to import Foreign configuration with Pinned Cache - (SCGCQ01029579)
- Fixed an issue where error "MonTask: line 2357 in file ../../raid/2108vI2o.c" may occur when running IO on 64 Virtual Drives and an Online Controller Reset is performed - (SCGCQ01030234)
- Fixed an issue where Operating System fails to boot due to continuous Logical Drive write map sync prints - (SCGCQ01030470)
- Fixed an issue where DDF PdDataInfo structure may be overwritten while a DDF update is in progress - (SCGCQ01030749)
- Fixed an issue where AutoConfig options set 0 after flashing firmware - (SCGCQ01033250)
- Fixed an issue where system may hang on boot when a reconstruction is in progress - (SCGCQ01034677)
- Fixed an issue where more than one reconstruction at a time may be allowed - (SCGCQ01036076)
- Fixed an issue where JBOD or EPD-passthrough may not be able to be created from Unconfigured drives when behavior mode is JBOD - (SCGCQ01039737)
- Fixed an issue where applications may fail CacheCade Virtual Drive creation when controller booted in 240VD mode is switched to 64VD mode - (SCGCQ01040017)
- Fixed an issue where Virtual Drive policies may not revert back on downgrade failure due to error "MFI_STAT_FLASH_NOT_ALLOWED" - (SCGCQ01041187)
- Fixed an issue where error "Montask line 1279 in file ../../raid/1078dma.c" may occur on performing target resets while running IO to Virtual Drives and JBODs - (SCGCQ01041735)
- Fixed an issue where Clear Foreign Configuration and Clear Configuration may report success even on failure - (SCGCQ01042004)
- Fixed some compilation issues - (SCGCQ01042472)
- Fixed an issue where defaults may be set on reboot after changing MFC settings - (SCGCQ01045951)
- Fixed an issue where boot drive setting may change to the first Virtual Drive by default on every reboot - (SCGCQ01045976)
- Fixed some code review issues - (SCGCQ01046172)
- Fixed an issue where controller firmware may fault during a firmware upgrade - (SCGCQ01051069)
- Fixed an issue where controller may incorrectly process the device wait queue during host task management - (SCGCQ01053010)
- Fixed an issue where Mode E offline flashing may display failure even after the image transfer is successful - (SCGCQ01054885)
- Fixed an issue where a kill adapter may occur when running Background Operations with OCR while CacheCade Virtual Drive association/dissociation in progress - (SCGCQ01058771)
- Fixed an issue where controller firmware may fault when downgrading - (SCGCQ01058792)
- Fixed an issue where an L2 Cache Error may be reported during OFC on iMR controllers - (SCGCQ01059873)
- Fixed an issue where error "Assertion failure in ssd_cache_fw.c" may occur during CacheCade Virtual Drive association/dissociation and Background Operation start/top and secondary enclosure cable insert/remove - (SCGCQ01059919)
- Fixed an issue where DATATLB error "Fatal firmware error: Line 245 in ../../raid/1078int.c" may occur - (SCGCQ01061565)
- Fixed an issue where error "MonTask at line 245 in file /raid/1078int.c" may occur when importing a Foreign SED/FDE configuration - (SCGCQ01065547)
- Fixed an issue where commands may not fail bakc to host if Command Block is not granted for more than 20 seconds - (SCGCQ01066198)
- Fixed an issue where "C0:MFI_STAT_NOT_FOUND" may be shown in firmware log when running IO against EPD/JBOD and system reboot/shutdown occurs - (SCGCQ01068464)
- Worked around an issue where spurious interrupts may cause a Physical Layer fault D230 - (SCGCQ01068609)
- Fixed an issue where a DATATLB error may occur when CacheCade support is not enabled on the system - (SCGCQ01069431)
- Fixed an issue where controller personality mode remains the same even when it has been changed to single-drive RAID0 - (SCGCQ01074396)
- Fixed an issue where stale enclosure entries may remain in topology array even after removing an enclosure - (SCGCQ01076184)
- Fixed an issue where only 30 Physical Drives may be able to be converted to Unconfigured Good on iMR controllers - (SCGCQ01077558)
- Fixed an issue where controller RAID layer may not handle RDM_STATUS_FAILED error - (SCGCQ01082528)
- Fixed an issue where cache may not be initialized after the deletion of the last targetID - (SCGCQ01156911)
- Fixed an issue where controller firmware may fault under heavy IO and target resets in progress with more than 32 EPDs - (SCGCQ01010222)
- Fixed an issue where controller firmware may fault when marking a Physical Drive of a CacheCade Virtual Drive as missing followed by a Replace Missing operation - (SCGCQ01021539)
- Fixed an issue where persistent reservation may not occur for true multipath configurations - (SCGCQ01022350)
- Fixed an issue where an improper offload of MEM_ - Fixed region in DDR may occur on reboot of host with Pinned Cache - (SCGCQ01029481)
- Fixed an issue where cache windows may not be properly allotted after making a RAID0 CacheCade Virtual Drive offline and then online - (SCGCQ01030735)
- Fixed an issue where controller firmware may hang on target reset to multiple drives - (SCGCQ01030891)
- Fixed an issue where the Virtual Drive ID may not be properly allocated when creating 240 Virtual Drives - (SCGCQ01035495)
- Fixed an issue where pldebug was not enabled - (SCGCQ01037904)
- Fixed an issue where if and else case were both returning FALSE - (SCGCQ01040437)
- Fixed an issue where controller firmware may crash when running IO to a dual-core capable Virtual Drive with Pinned Cache present - (SCGCQ01041766)
- Fixed an issue where an Assertion failure error may occur when Task Management is issued to EPDs with background IO - (SCGCQ01047185)
- Fixed some code review issues - (SCGCQ01047193)
- Fixed an issue where load balance may not occur on boot due to outstanding IO in disk - (SCGCQ01050467)
- Fixed an issue where only 26 drives can be converted as Unconfigured Good - (SCGCQ01059916)
- Fixed an issue where JBODs may go to Failed state when running Full Initialization with multipath cable push/pull - (SCGCQ01060295)
- Fixed an issue where incorrect Physical Drive details may be shown in an EPD deletion event - (SCGCQ01061128)
- Fixed an issue where a "VD missing" message may be displayed at POST after deleting an EPD and rebooting the system - (SCGCQ01061827)
- Fixed a compilation issue - (SCGCQ01063479)
- Fixed an issue where an error "kill adapter at line 1280" may occur under IO and multipath cable push/pull under RHEL7 - (SCGCQ01065343)
- Fixed an issue where controlelr name may not be displayed in any applications - (SCGCQ01069489)
- Fixed an issue where a DATATLB error may occur on iMR controllers when attempting to enable TTY to see discovery logs - (SCGCQ01078092)
- Fixed an issue where some controllers may fault with Uncorrectable ECC error detected - (SCGCQ01080061)
- Fixed an issue where an incorrect offset to devstateTAble pointers may occur - (SCGCQ01081352)
- Fixed an issue where an EPD may move to Shield state on SCSI/Immediate IO respose of BUSY - (SCGCQ01095557)
- Fixed an issue where an error "FW crash at line 8003 in file ../../raid/pd.c" may occur when performing target resets and Background IO - (SCGCQ01100216)
- Fixed an issue where AutoConfig DCMD may not report the correct stsatus for non-240VD mode - (SCGCQ01156132)
- Fixed an issue where text4 section may not load during firmware initialization - (SCGCQ01027455)
- Fixed some code review defects - (SCGCQ01031313)
- Fixed an issue where DATATLB error may occur when updating controller firmware when offline Disk Groups are present, followed by a server reboot - (SCGCQ01034958)
- Fixed an issue where error "Assertion failure at line 2359 in file ../../raid/2108vI2o.c" may occur when switching personalities - (SCGCQ01035492)
- Fixed an issue where error "Exception in Core 0" may occur during reconstruction of SVD when a CacheCade is present - (SCGCQ01037857)
- Fixed an issue where controller firmware may hang when creating a RAID1 and RAID0 Virtual Drive - (SCGCQ01042209)
- Fixed an issue where EPDs may be converted to Unconfigured Good when performing enclosure power cycles - (SCGCQ01046038)
- Fixed an issue where buffer overruns may occur - (SCGCQ01047035)
- Fixed an issue where values provided for MRIE mode may not be validated properly - (SCGCQ01048239)
- Fixed an issue where IO failures during path removal in true multipatch may not be handled correctly - (SCGCQ01054654)
- Fixed an issue where Auto Import of Foreign Configurations may fail for RAID1 Virtual Drive when Pinned Cache is present - (SCGCQ01060671)
- Fixed an issue where storcli may allow to set link speed to 1.5Gbps even though that is not supported - (SCGCQ01061902)
- Fixed an issue where a personality switch from EPD to single-drive RAID0 may fail even when there is no configuration - (SCGCQ01065596)
- Fixed a typo - (SCGCQ01070821)
- Fixed an issue where controller may hang when flashing a 4MB image - (SCGCQ01157158)
- Fixed an issue where controller firmware returns success to applications even though a Secure JBOD conversion as failed - (SCGCQ01038757)
- Fixed an issue where a timer list issue may occur when creating/deleting EPDs on a large config - (SCGCQ01043654)
- Fixed an issue where error "Failed to get VD VF mapping list" may occur on query "show VF map" - (SCGCQ01064037)
- Fixed an issue where MonTask error "No More Task available!!" may occur when a task management is issued from the Operating System - (SCGCQ01085194)
- Fixed an issue where L2/L3 Cache Error may be detected on controller during boot after shutdown - (SCGCQ01018958)
- Fixed an issue where device discovery may infinite loop when firmware gets a timeout for READ CAPACITY command - (SCGCQ01015624)
- Fixed an issue where a BSOD may occur on firmware upgrade from non-240VD firmware to 240VD-firmware when OS is behind the controller - (SCGCQ00829978, SCGCQ00829979, SCGCQ00829980, Port of SCGCQ00825725)
- Fixed an issue where firmware may return incorrect values for Logical Drive Physical Sector Size when Force Emulation is set on a 4Kn drive - (SCGCQ00918755, Port of SCGCQ00905002)
- Fixed an issue where an exception may occur on import of a Foreign Configuration whe number of Virtual Drives is greater than the supported 31 - (SCGCQ00935533, Port of SCGCQ00927528)
- Fixed an issue where storcli show all command triggers a datastore disconnect in VMWare ESXi - (SCGCQ00935551, Port of SCGCQ00928506)
- Fixed an issue where MonTask error may occur on boot after creating 240 Virtual Drives and rebooting the system - (SCGCQ00945341, Port of SCGCQ00905416)
- Fixed an issue where a kernel panic and/or MonTask error may occur due to host command count being incorrectly updated - (SCGCQ00976812, Port of SCGCQ00948256)
- Fixed an issue where dirty cache was not being ignored when firmware is updated with cache version change - (SCGCQ00988757, Port of SCGCQ00944012)
- Fixed an issue where security-related commands run even if a lock key is not assigned to controller - (SCGCQ00988906, Port of SCGCQ00940921)
- Fixed an issue where controller firmware may crash when running IO if the FastPath engine tries to add the timer for a new IO - (SCGCQ00988908, SCGCQ01017522, Port of SCGCQ00917821)
Worked around an issue where a firmware fault may occur due to a false ReplyParityError - (SCGCQ00988988, SCGCQ00988989, Port of SCGCQ00927504)
- Fixed an issue where locate LED may remain on for a reinserted drive - (SCGCQ01014122, Port of SCGCQ00998112)
- Fixed an issue where a DATATLB error may occur when hotplugging some enclosures - (SCGCQ01015796, Port of SCGCQ00983232)
- Fixed an issue where firmware may hang when trying to complete a FW_RAID_MAP command - (SCGCQ01022257, Port of SCGCQ01015745)
- Fixed an issue where Abort Task may fail to abort outstanding FastPath command - (SCGCQ01023239, Port of SCGCQ01020088)
- Fixed an issue where controller may be unable to import Foreign, locked Secured Drives - (SCGCQ01023287, Port of SCGCQ00994721)
- Fixed an issue where IOs may be terminated on EPDs when doing target resets while disks go Offline - (SCGCQ01028573, Port of SCGCQ00953540)
- Fixed an issue where initial boot prints may be missing during firmware initialization and restore operations - (SCGCQ01041470, Port of SCGCQ01012327)
- Fixed an issue where ECC bit count may not be programmed to 24 correctly - (SCGCQ01069986, Port of SCGCQ01051207)
- Fixed an issue where CTRL-R may not automatically refresh the screen after some operations - (SCGCQ01070182, Port of SCGCQ01068368)
- Fixed an issue where Spare Pool start address may be set incorrectly after some cache offload and restore operations - (SCGCQ01070258, Port of SCGCQ01069753)
- Fixed an issue where performance degradation may occur due to MultiCpuAtomicDec()/MultiCpuAtomicInc() functions modifying scsi_pending_cmds - (SCGCQ01073190, Port of SCGCQ01044217)
- Fixed an issue where Data Protection bit may not be cleared during Secure Erase and reboots - (SCGCQ01078532, SCGCQ01078533, SCGCQ01078536, SCGCQ01069761, Port of SCGCQ01065119)
- Fixed an issue where a read retry is needed when ECC errors in excess of 24bits per 1100 bytes occur - (SCGCQ01081899, SCGCQ01081900, SCGCQ01089927, Port of SCGCQ01078237)
- Fixed an issue where LUID may be changed during import of Foreign configuration from non-240VD firmware to 240VD firmware - (SCGCQ01084595, SCGCQ01087947, SCGCQ01163258, SCGCQ01163768, Port of SCGCQ00907658)
- Fixed an issue where error "15=Fatal firmware error: Line 1972 in ../../raid/flex.c" or "MonTask: line 1972 in file ../../raid/flex.c" may occur on boot when running a rebuild and a reconstruction - (SCGCQ00996655, SCGCQ01088182, SCGCQ00907979, Port of SCGCQ00902755)
- Fixed an issue where IO failures may be observed on 4Kn Virtual Drives with PI enabled - (SCGCQ01117016, SCGCQ01118907, SCGCQ01129839, SCGCQ01130945, SCGCQ01130999, SCGCQ01131000, SCGCQ01131001, SCGCQ01131002, SCGCQ01131003, Port of SCGCQ01081912)
Disable support for PI and do not allow PI to be re-enabled - (SCGCQ01128064, Port of SCGCQ01105478)
- Fixed an issue where import of a max Foreign Configuration may fail - (SCGCQ01129847, Port of SCGCQ00679180)
- Fixed an issue where error "bladeErrorIsrTask ChanNum 0 intStatus" may occur when enabling security on controller - (SCGCQ01130922, SCGCQ01130938, Port of SCGCQ01077578)
- Fixed an issue where presence of pinned cache may not result in a move of all unpinned windows of a degraded CacheCade Virtual Drive to read-only - (SCGCQ01136063, Port of SCGCQ01118285)
- Fixed an issue where controller firmware may fault when running command "storcli /c0 set termlog=on" - (SCGCQ01139844, Port of SCGCQ01129530)
- Fixed an issue where CTRL-H was allowing user to enable PI when PI is disabled - (SCGCQ01141456, Port of SCGCQ01139294)
- Fixed an issue where EPDs may not be created after system reboot when Physical Drive erase is in progress on one or more drives - (SCGCQ01146473, Port of SCGCQ01144014) - Fixed an issue where a kill adapter may occur during a simultaneous rebuild, reconstruction and drive pull - (SCGCQ01149315, Port of SCGCQ01143971)
- Fixed an issue where configured drives may be converted to JBOD if system already has maximum number of configurable drives - (SCGCQ01149763, Port of SCGCQ01136693)
- Fixed an issue where controller may report 1MB as IO size regardless of the IO type or mode - (SCGCQ01180170, SCGCQ01180171, Port of SCGCQ01137690)
- Fixed an issue where iEEESGL flag may not be set for IO requests in SES DCDB handler - (SCGCQ01186523, SCGCQ01205429, Port of SCGCQ01157072)
- Fixed an issue where Logical Drive to Physical Drive LDA conversion happens using PRL11 for LBAs that have not yet been migrated - (SCGCQ01201996, Port of SCGCQ01186096)
- Fixed an issue where flash block read timeouts may be observe when flash file system read failures and read eye training failures occur simultaneously - (SCGCQ01229234, Port of SCGCQ01208490)
- Fixed an issue where MR_DCMD_CFG_AUTOCFG DCMD may be disabled in non-240 VD environment - (SCGCQ01232073, Port of SCGCQ01213915)
- Fixed an issue where controller firmware may assert when booting with 4K drives - (SCGCQ00935534, Port of SCGCQ00927547)
- Fixed an issue where Auto RAID0 may fail with 8 enclosures connected - (SCGCQ00938868, Port of SCGCQ00934300) - Fixed an issue where code was not detecting crossage of 1 MB page boundary through proper Assert - (SCGCQ00947988, Port of SCGCQ00931010)
- Fixed an issue where rebuild fails to start on CacheCade virtual drives after successful import - (SCGCQ00954124, Port of SCGCQ00950030)
- Fixed an issue where am rebuild error "Error f0" may occur on iMR controllers - (SCGCQ00979952, Port of SCGCQ00915417)
- Fixed an issue where Locate LED may remain on for reinserted drive - (SCGCQ00999675, Port of SCGCQ00997675)
- Fixed an issue where a MonTask or DATATLB error may occur when there is Pinned Cache involving degraded, sliced Virtual Drives - (SCGCQ01023909, SCGCQ01023910, Port of SCGCQ00997180)
- Fixed an issue where LED may not turn off when a drive is removed - (SCGCQ01026815, Port of SCGCQ01003387)
- Fixed an issue where SEP devices at sasLevels greater than 1 may be determined as Direct Attached Devices - (SCGCQ01027840, Port of SCGCQ01004946)
- Fixed an issue where a MonTask error may occur when IO, target resets and cable insert/remove are occurring simultaneously - (SCGCQ01028575, Port of SCGCQ00979797)
- Fixed an issue where correct slot number may not be collected for SES enclosures - (SCGCQ00925533, SCGCQ01180864, Port of SCGCQ00903181)
- Fixed an issue where drive may not be marked as Foreign on OCR when controller already has max configured drives - (SCGCQ01202208, Port of SCGCQ01163849)
- Fixed an issue where controller configuration may be lost when connecting a stale configuration - (SCGCQ01205397, Port of SCGCQ01170701)
- Fixed an issue where error "MonTask: line 3386 in file ../../dm/src/devmgr.c" may occur when running IO to JBOD SAS SSD and cables removed/reinserted - (SCGCQ01232131, Port of SCGCQ01213918)
- Fixed an issue where error "adapter at base port not responding" may appear on boot when firmware issues mode sense command to faulty drives - (SCGCQ01001353, Port of SCGCQ00999966)
- Fixed an issue where error "Firmware crash @line 245 in file ../../raid/1078int.c" may occur on enclosure power cycles - (SCGCQ01022262, Port of SCGCQ01015293)
- Fixed an issue where message "I2C 4 PID 10 SCL STUCK Low! while I2C Rx receiving data intStatus 00008000" may still be printed in firmware log - (SCGCQ01026304, Port of SCGCQ01007592)
- Fixed an issue where firmware returns an error when flashing individual components through storcli such as NVDATA, BTBL etc - (SCGCQ01030747, Port of SCGCQ01015302)
- Fixed an issue where totalLines required to carry IO/Flush operation may not be restricted to primary core - (SCGCQ01033265, Port of SCGCQ01019324)
Enhancements:
- Added Physical Layer library version 12.0.5.0 - (SCGCQ01231972)
- Reverted DDR tuning changes for some controllers - (SCGCQ01224232)
- Added handling for 128 drives per enclosure - (SCGCQ00920037) - Integrated Physical Layer 12.00.05.00 - (SCGCQ01162534)
- Added feature for firmware to complete SYNC_CACHE command for VDs even if mode page bit is disabled - (SCGCQ01125303)
- Added feature to support exporting RAID geometry - (SCGCQ00936726)
- Added "supported bits" mbox value to MR_DCMD_CFG_AUTOCFG - (SCGCQ01025967, Port of SCGCQ01020092)
- Unblocked MCTP over PCIe levels - (SCGCQ01145325, Port of SCGCQ01134167)
- Added MR_DCMD_CFG_AUTOCFG for iMR for GET operation - (SCGCQ01232103, Port of SCGCQ01228949)
- Added capability to expose each SAS expander-attached SEP as a separate Enclosure PD - (SCGCQ01150206, Port of SCGCQ01093800) Converted some unrecoverable errors to recoverable errors - (SCGCQ00943806, Port of SCGCQ00890049)
- Added feature to handle the presence and absences of randomizer - (SCGCQ01156575, Port of SCGCQ01133554)
- Added support for SCSI SANITIZE/Crypto commands on JBOD drives - (SCGCQ01144707, Port of SCGCQ01129378)
- Removed reset of Idle Timers - (SCGCQ01223113, Port of SCGCQ01145782)
- Added ability to allow security commands to drives which are not managed by SafeStore - (SCGCQ01026630, Port of SCGCQ01007634)
- Added changes for Profile management API support - (SCGCQ00883008, SCGCQ00883045)
Version 24.12.0-0039 - High Impact/High Probability of Occurrence ------------------- FW Package: 24.12.0-0039 HII: E3.19.07.06 UEFI Driver: 0x06130201 BIOS: 6.30.03.2 MR FW: 4.620.00-8080 iMR FW: 4.620.01-8081
Fixes: - Disabled further usage of PI due to a potential data issue (SCGCQ01128078) - Fixed an issue where In CTRL-R the controller is giving the option to enable the drive protection under controller operations (F2) with firmware which does not support the data protection. (SCGCQ01139294, SCGCQ01074426, SCGCQ01131138) - Fixed an issue where a configured drive is inserted, rebuild started on wrong virtual drive after the enclosure power cycle. (SCGCQ00988970 Port of SCGCQ00927155) - Fixed an issue where the screen is not refreshing after operations in CTLR-R. (SCGCQ01088160) - Fixed an issue where controller broke into montask upon reboot after running a rebuild and reconstruction. (SCGCQ01088178 Port of SCGCQ00902755) - Fixed an issue where /O failures observed on 4k virtual drive with data Protection Enabled, when virtual drive goes offline due to source drive error when Rebuild is progressing on a degraded virtual drive (SCGCQ01130941 Port of SCGCQ01081912) - Fixed an issue for iMR where the supported configurable physical drive count is already filled and more configured drives are added and get converted to JBOD and their configuration was cleared. (SCGCQ01149762) - Fixed an issue where data compare error found during recovery of CacheCade pinned windows across OCR/Reboot or discard of CacheCade pinned windows while CacheCade degrade flush in progress. (SCGCQ01136062) - Fixed an issue where iEEESGL flag was not getting set for IO request in SES DCDB handler. (SCGCQ01186523 Port of SCGCQ01157072) - Fixed an issue where L2/L3 Cache error was detected on the RAID controller during boot. (SCGCQ01155454 Port of SCGCQ01018958)
Enhancement(s): - Revert the DDR tuning changes for specific PCI IDs. (SCGCQ01224232) - SCSI SANITIZE/Crypto on JBOD Drives under MR. (SCGCQ01155380 Port of SCGCQ01129378)
Version 24.12.0-0033 - High Impact/High Probability of Occurrence -------------------
Fixes: - Fixed an issue where changing RAID FoD key (Add/Remove) through customer application will make the original VD change to foreign. (SCGCQ01111615) - Fixed an issue where security is disabled on a ServRAID M5210 controller after a FOD key is added or removed until next reboot. (SCGCQ01132432)
Enhancement: - Added the capability for users to save the FoD key to TMM through the MSM pop-up advanced software options. (SCGCQ01085797)
Version 24.12.0-0024 - High Impact/High Probability of Occurrence --------------------
Fixes: - Fixed the potential of a data miscompare that was observed only at a vendor test facility under very heavy I/O and abnormal practices (SCGCQ00990093, Port of SCGCQ00976904) - Fixed an issue where performing back-to-back target resets on the same JBOD may results in an Controller Reset (SCGCQ00857181) - Fixed an issue where firmware may allow a Reconstruction to be performed when Pinned Cache is present (SCGCQ00857692) - Fixed an issue where "MonTask" error may occur when importing a Foreign Configuration (SCGCQ00860066) - Fixed an issue where controller does not Stop on Error and boots into Operating System when Pinned Cache is present(SCGCQ00860503) - Fixed an issue where firmware allows CacheCade Virtual Drive deletion when Pinned Cache is present (SCGCQ00871973) - Fixed an issue where a firmware downgrade FW downgrade may fail when IO and Background Operations are being performed (SCGCQ00873239) - Fixed an issue where error "Core 0 exception in line 245 in ../../raid/1078int.c" may occur when Target Reset sent to Physical Disks in parallele with Background Operations (SCGCQ00878554) - Fixed an issue where error "Assertion failure in ../../dm/src/dmDrvPrep.c at line 836" may occur (SCGCQ00879198) - Fixed an issue where firmware may hang on Task Abort (SCGCQ00881901) - Fixed an issue where iPtr and rPtr values may be greater than the size of the buffer (SCGCQ00886685) - Fixed an issue where more IOs were allowed than the available buffer could support (SCGCQ00894472) - Fixed an issue where the Operating System may become unresponsive after creating multiple sliced Virtual Disks (SCGCQ00894608) - Fixed an issue where adapter may reset under certain conditions (SCGCQ00895554) - Fixed an issue where error "line 1271 in file ../../raid/1078dma.c" may occur when running FastPath with CacheCade (SCGCQ00898799) - Fixed an issue where forceCacheFlush was occurring in an iMR context where it doesn't apply (SCGCQ00899762) - Fixed an issue where importing 240 Virtual Drives may cause a firmware fault (SCGCQ00900601) - Fixed an issue where error "line 229 in file ../../raid/mtask.c" may occur when Hibernating Windows 10 (SCGCQ00905864) - Fixed an issue where importing a Foreign Configuration may fail (SCGCQ00908325) - Fixed an issue where FastPath IO may not time out properly (SCGCQ00910124) - Fixed an issue where StorCLI may report an incorrect ScapBatVersionNO when using command "/c0/cv show all" (SCGCQ00914343) - Fixed an issue where some default values may not be picked up for unchanged controller properties sharing the same byte (SCGCQ00914740) - Fixed an issue where chain mid allocation for JBOD may fail (SCGCQ00915081) - Fixed an issue where configuration creation may fail after creation of a CacheCade Virtual Drive followed by JBOD creation (SCGCQ00917307) - Fixed an issue where a cable pull during a Target Reset on JBOD may result in a data TLB error (SCGCQ00923289) - Fixed an issue where controller may become unresponsive after hitting an OCM error(SCGCQ00924986) - Fixed an issue where the Physical Device map was being updated unnecessarily (SCGCQ00927173) - Fixed an issue where some drives could not be discovered successfully (SCGCQ00927792) - Fixed an issue where attempting to stop a Drive Erase operation from application may cause firmware to hang (SCGCQ00928150) - Fixed an issue where controller disappears when performing a cable pull (SCGCQ00928333) - Fixed an issue where CacheCade Virtual Drive creation may fail with false error (SCGCQ00930044) - Fixed an issue where controller may hang when importing a drive into a RAID0 CacheCade Virtual Drive (SCGCQ00934196) - Fixed an issue where firmware would not allow an Online Firmware Update (SCGCQ00936693) - Fixed an issue where error "line 219 in file ../../raid/mficmd.c" may occur when powering system on from S3 sleep (SCGCQ00937487) - Fixed an issue where error "MonTask: line 1281 in file /raid/1078dma.c" may occur when running enclosure cable pulls with CacheCade Virtual Drive (SCGCQ00941531) - Fixed an issue where firmware recovers invalid cache after firmware update (SCGCQ00944012) - Fixed an issue where LdInitPdDone did not include flush command block (SCGCQ00945033) - Fixed an issue where driver may panic and controller may reset on medium errors with Pinned Cache (SCGCQ00948257) - Fixed an issue where Virtual Drives don't revert back to Write-Back once the controller Pinned Cache is destaged (SCGCQ00948466) - Fixed an issue where firmware may fault when running full initialization on Virtual Drives with LDBBM entries created during Consistency Check (SCGCQ00952627) - Fixed an issue where a SES Discovery Error may occur on repeated retries for some expanders (SCGCQ00976741) - Fixed an issue where the drive bay LED may not turn off when the drive is removed (SCGCQ01003387) - Fixed an issue where error "MonTask: line 4946 in file ../../raid/ld.c" may occur when multipath cable pull occurs Patrol Read (SCGCQ00857528) - Fixed an issue where Locate LED turns off when cable failover performed (SCGCQ00869681) - Fixed an issue where "Watchdog Timer Exception" error followed by firmware fault after initiating Physical Drive erase operation (SCGCQ00872140) - Fixed an issue where a firmware fault occurs when issuing Task Management commands on 240 JBODs while running IO (SCGCQ00872889) - Fixed an issue where Virtual Drive deletion could cause IO freeze time to increase (SCGCQ00873201) - Fixed an issue where a data TLB error would occur after issuing task abort (SCGCQ00873991) - Fixed an issue where "MonTask" error may occur due to a Full-Disk Encryption / Self-Encrypting Disk that fails to spinup (SCGCQ00874332) - Fixed an issue where error "adapter at baseport not responding" may occur (SCGCQ00880919) - Fixed an issue where cache is not flushed immediately upon firmware recieving the cache-flush out-of-band command (SCGCQ00882125) - Fixed an issue where IO may slow while deleting Virtual Drives (SCGCQ00891924) - Fixed an issue where IO halts on JBODs with "read/write error" when the target drives are reset in Linux (SCGCQ00893588) - Fixed an issue where "MonTask: line 1413 in file ../../raid/config.c" may occur when creating a CacheCade Virtual Drive (SCGCQ00894610) - Fixed an issue where firmware does not log controller property change event for enabling/disabling 240VD feature (SCGCQ00895577) - Fixed an issue where event length may come up as 0 (SCGCQ00897406) - Fixed an issue where firmware was not seding the proper status for aborted commands (SCGCQ00900250) - Fixed an issue where controller firmware may fault during Hibernation or when the driver loads twice (SCGCQ00902938) - Fixed an issue where firmware may fault after creating 240 Virtual Drives and rebooting the server (SCGCQ00905416) - Fixed an issue where progress for CacheCade disassociation activity is not displayed for all source Virtual Drives (SCGCQ00906846) - Fixed an issue where error "Assert at line 1181 mpthostcmd.c" may occur when FastPath has been disabled or for a timeout IO (SCGCQ00910006) - Fixed an issue where error "LMID HS-FIFO Error 0x8" may occur when removing a redundant path to a JBOD with IO (SCGCQ00914274) - Fixed an issue where applications may show incorrect value for Max Parallel Commands field of Controller Information in iMR(SCGCQ00914751) - Fixed an issue where firmware was failing ABORT TASK and ABORT TASK SET commands on SATA JBOD (SCGCQ00915088) - Fixed an issue where exception may occur on Online Controller Reset (SCGCQ00917523) - Fixed an issue where "MonTask" error may occur in a drive removal or multipath removal scenario (SCGCQ00919229) - Fixed an issue where the wrong MFI_STAT is returned from PdDcmdSysPdMapAbort (SCGCQ00930593) - Fixed an issue where an Online Firmware Update may fail when downgrading from firmware that supports 240 Virtual Drives to firmware that does not (SCGCQ00930917) - Fixed an issue where "DM_EnableFastPathOnDevice :: FP enabled on devhandle" may be printed in logs even though FastPath is enabled (SCGCQ00936617) - Fixed an issue where "C0:Index 0098 allocated from pool 3" prints continuously in log with 12Gbps Enclosures and SATA drives (SCGCQ00937572) - Fixed an issue where firmware prematurely rejects ONFI flash module (SCGCQ00937617) - Fixed an issue where SafeID may change on repeated queries using StorCLI (SCGCQ00941577) - Fixed an issue where firmware may fault when importing Virtual Drives with Pinned Cache (SCGCQ00949440) - Fixed an issue where Write-Back Virtual Drives are converted to Write-Through on system reboot or Online Controller Reset(SCGCQ00859720) - Fixed an issue where a Data TLB error may occur when firmware is upgraded or downgraded (SCGCQ00867065) - Fixed an issue where a Data TLB error may occur when aborting a host command (SCGCQ00874357) - Fixed an issue where firmware may fault when running IO with Task Resets on JBODs (SCGCQ00877673) - Fixed an issue where error "MonTask: line 245 in file ../../raid/1078int.c" may occur while running IO with 64 Virtual Drives and removing drives belonging to CacheCade (SCGCQ00878587) - Fixed an issue where cache flush was occurring during Virtual Drive deletion (SCGCQ00878923) - Fixed an issue where IO dip is seen when deleting Virtual Drives (SCGCQ00879193) - Fixed an issue where a Data TLB error may occur when sending Target Reset on JBOD via out-of-band commands (SCGCQ00881919) - Fixed an issue where perTunerMode is not set correctly after a controller reset (SCGCQ00882897) - Fixed an issue where error "MonTask: line 2735 in file ../../ssd/ssd_cache_fw.c" may occur when error are injected repeatedly (SCGCQ00887019) - Fixed an issue where a rebuild cannot be started for a degraded CacheCade Virtual Drive after heavy IO (SCGCQ00887428) - Fixed an issue where error "MonTask: line 245 in file ../../raid/1078int.c" may occur with IOs on maximum Virtual Drives configured and Background Opertations are occurring (SCGCQ00890133) - Fixed an issue where Patrol Read doesn't resume after Consistency Check completes after a system reboot (SCGCQ00894344) - Fixed an issue where StorCLI throws an error when performing "/c0/vx show all" after a Full Initialization on RAID1 Virtual Drive with SSDs (SCGCQ00904899) - Fixed an issue where a firmware fault occurs when a copyback operation fails to start (SCGCQ00904905) - Fixed an issue where LUID is changed when importing a non-240VD configuration to a 240VD firmware (SCGCQ00907658) - Fixed an issue where a "MonTask" error may occur when under heavy JBOD IO and the JBOD IOs begin failing (SCGCQ00915078) - Fixed an issue where error "line 1279 in file ../../raid/1078dma.c" may occur on iMR firmware during boot (SCGCQ00915092) - Fixed an issue where controller reset occurs under stress with 240 Virtual Drives configured (SCGCQ00915398) - Fixed an issue where Online Firmware Update would fail due to driver reload issues (SCGCQ00915454) - Fixed an issue where a Data TLB error may occur during reconstrution operation when Target Resets are issued to JBODs (SCGCQ00921993) - Fixed an issue where "Core 0 exception" is seen when trying to import Foreign Configurations with Pinned Cache (SCGCQ00863880) - Fixed an issue where CTRL-R interface does not show correct port information when hotplugging enclosure paths (SCGCQ00866487) - Fixed an issue where firmware may fault when an enclosure with an especially slow drive is present (SCGCQ00867120) - Fixed an issue where error "MonTask: line 1280 in file ../../raid/1078dma.c" may occur on out-of-band command timeout (SCGCQ00872875) - Fixed an issue where error "Assertion failure in ../../raid/cache.c at line 774" may occur after pulling out an enclosure cable (SCGCQ00878097) - Fixed an issue where write performance drops in RAID5, Write-Through, No Read-Ahead, Stripe Size 64, 1MB IO at queue depth 128/256 (SCGCQ00878414) - Fixed an issue where an imported 4K-drive RAID0 becomes Unconfigured Good on reboot (SCGCQ00895689) - Fixed an issue where Online Firmware Update fails with "not supported" message (SCGCQ00915073) - Fixed an issue where Logical Drive IO for FastPath-capable RAID0/RAID1 were not handled properly in the presence of a RAID5/RAID6 Write-Through volume running sequential write streams (SCGCQ00915409) - Fixed an issue where a CRC mistmatch and Invalid Log Event are surfaced when checking Controller Properties in parallel with a Learn Cycle (SCGCQ00919945) - Fixed an issue where performance drops are seen on writes to RAID1 FastPath volumes (SCGCQ00931895) - Fixed an issue where event messages reporting CacheCade Virtual Disk target ID and remaining CacheCade size are incorrect (SCGCQ00864019) - Fixed an issue where firmware faults when using an Online Controller Reset from StorCLI after having issued "supportResetNow" (SCGCQ00878150) - Fixed an issue where an "Exception in Core -0" error may occur on iMR firmware under VMWare (SCGCQ00904103) - Fixed an issue where "MsgAlloc: No free messages, poolIndex=4" may appear in logs while running IO on JBODs (SCGCQ00908982) - Fixed an issue where the TTY log dump is not persistent across multiple boots (SCGCQ00877100) - Fixed an issue where drives that return errors for all protocol commands may be retried indefinitely (SCGCQ00805369) - Fixed an issue where setting the Learn Cycle property of iBBU09 gives an i2C error (SCGCQ00837206) - Fixed an issue where driver may hang with LSI2008-based adapters (SCGCQ00843390) - Fixed an issue where device wait queue is not cleared when drive is no longer online (SCGCQ00878401) - Fixed an issue where Windows may BSOD on firmware upgrade when running driver 6.707.08.00 (SCGCQ00886272) - Fixed an issue where disableImmediateIO NVDATA value is not honored by firmware (SCGCQ00886666) - Fixed an issue where Foreign Configuration could be cleared even when Pinned Cache is present (SCGCQ00889209) - Fixed an issue where a Virtual Drive under Reconstruction may go Degraded if the drive being reconstructed is removed before the operation completes (SCGCQ00891282) - Fixed an issue where a "MonTask" error may occur after initiating a RAID Level Migration (SCGCQ00891288) - Fixed an issue where system hang may occur after aborting running Consistency Checks repeatedly (SCGCQ00895265) - Fixed an issue where a "MonTask" error may occur after creating 240 Virtual Drives and rebooting the server (SCGCQ00908121) - Fixed an issue where LUID is changed when importing a non-240VD configuration to 240VD-enabled controller (SCGCQ00908153) - Fixed an issue where a Virtual Drive may disappear on reboot if created with drives from a previously-deleted Virtual Drive (SCGCQ00914823) - Fixed an issue where device wait queue is not cleared if a drive is no longer online (SCGCQ00923279) - Fixed an issue where message "Found invalid event at fc4966ec" is printed in firmware log every 5 seconds (SCGCQ00931370, SCGCQ00979910) - Fixed an issue where firmware is unable to detect all Virtual Drive's "Degraded" status for partial Virtual Drives created on the same Physical Drives (SCGCQ00942380) - Fixed an issue where driver may panic and firmware may hang when medium errors are present (SCGCQ00954118) - Fixed an issue where firmware does not discard dirty cache after firmware update (SCGCQ00992657) - Fixed an issue where some Recoverable Errors were marked as Unrecoverable (SCGCQ01015699) - Fixed an issue where HII and Ctrl-R show an incorrect message when trying to import a 65th Virtual Drive (SCGCQ00803718) - Fixed an issue where Functional Level Reset (FLR) was not supported (SCGCQ00843936) - Fixed an issue where Write-through and Write-back cache policies can be changed via Windows Logical Disk Properties. (SCGCQ00883311) - Fixed an issue where many "LdDcmd ***** return pinned list 0" messages may be printed in firmware log (SCGCQ00895459) - Fixed an issue where an alert is repeated twice for Cancel Consistency Check on Virtual Drives (SCGCQ00900027) - Fixed an issue where error "Controller encountered fatal error and was reset" may occur under heavy IO and background operations (SCGCQ00905603) - Fixed an issue where CacheCade-related 240 Virtual Drive checks were not checking controller properties (SCGCQ00905809) - Fixed an issue where out-of-band applications may not display Show Configuration Summary when 240 Virtual Drives are created (SCGCQ00908237) - Fixed an issue where a RAID0 using 4k drives may not be visible after reboot (SCGCQ00999181) - Fixed an issue where firmware may not poll all temperature sensor channels every 5 seconds (SCGCQ00844152) - Fixed an issue where Hard Drive RAID0 and RAID10 performance at 1M stripe size is suboptimal between queue depths of 16 to 256 (SCGCQ00876154) - Fixed an issue where StorCLI will report Success when flashing an MR-only package on an iMR-only controller (SCGCQ00882149) - Fixed an issue where 'Fw initializing devices' may hang with specific failed drives (SCGCQ00884719) - Fixed an issue where controller may report cache size as "0" when no logical drives are present (SCGCQ00891273) - Fixed an issue where a Physical Disk may not go to Online state even after creating a Virtual Drive on it (SCGCQ00910741) - Fixed an issue where error "SAS core detected EEDP error in application tag" may occur (SCGCQ00936647) - Fixed an issue where "storcli /c0 show all" shows many Bad Block messages in the log (SCGCQ00892136) - Fixed an issue where firmware may log Controller Properties Changed events twice (SCGCQ00908238) - Fixed an issue where a Virtual Drive under Reconstruction may be set Degraded if the drive under reconstruction is removed (SCGCQ00922677) - Fixed an issue where firmware may enter fault state after system power cycle with an SSD drive (SCGCQ00835227) - Fixed an issue where firmware may fault and RSOD may occur when a Virtual Drive is deleted when a Reconstruction is in progress on a PI-enabled VD combined with a slow initialization on another Virtual Drive (SCGCQ00872263) - Fixed an issue where firmware doesn't report no SMART error when a Predictive-Failure Analysis (PFA) drive is present (SCGCQ00841772) - Fixed an issue where firmware may not detect inserted drives (SCGCQ00876142)
Enhancements: - Added support for restarting Patrol Reads after they are interrupted by a Consistency Check (SCGCQ00883176) - Added ability to enable and disable 1M IO support via controller property (SCGCQ00893029) - Added support for Task Management for JBOD/sysPDs (SCGCQ00855457) - Reduced Command Block latency during Background Operations (SCGCQ00865372) - Added ability to not moe Write-back Virtual Drives to Write-through when Pinned Cache is less than 50% of available buffers (SCGCQ00852502) - Updated iMR queue depth to 928 (SCGCQ00888862, SCGCQ00930846, SCGCQ00896497) - Disabled SATA HOQ support for iMR controllers (SCGCQ00942547) - Added Task Management support for JBOD/sysPD (SCGCQ00861819, SCGCQ00855457) - Re-enabled 1M IO support (SCGCQ00874200) - Added support for Event Reporting for SuperCap Health after Learn Cycles (SCGCQ00894455)
Version 24.9.0-0026 - High Impact/High Probability of Occurrence -------------------
Fixes: - Fixed an issue in iMR mode where "Controller encountered fatal error and was reset" errors can occur under heavy IOs and background operations (SCGCQ00894643) (RETAIN Tip H001154) - Fixed an issue where driver health protocol may report unhealthy if more than 64 VDs are configured (SCGCQ00830918) - Fixed an issue where VDs beyond 64 may not be reported in legacy OpROM pOST display list (SCGCQ00826174) - Fixed an issue where "StorCLI /cX add VDs detailed" menu provides incorrect syntax for R1E (SCGCQ00501437) - Fixed an issue where CLI "show all" command fails with error "Error! App exec failed in FW PCLIError! Internal" (SCGCQ00518543) - Fixed an issue where the dedicated hot spare option in HII may be grayed out for RAID1 under the profile based configuration menu (SCGCQ00873973) - Fixed an issue where HII drive management and enclosure management may report only port 4-7 connected when ports 0-3 and 4-7 are connected to the same expander (SCGCQ00870398) - Fixed an issue where HII may hang or multiple enclosure entries will be seen in enclosure eanagement form after repeated navigation (SCGCQ00878350) - Fixed an issue where a 15-character VD name is truncated to 14 characters (SCGCQ00854606) - Fixed an issue where profile-based VD creation menu doesn't explain each profile's drive selection criteria (SCGCQ00884229) - Fixed an issue where some overlap may be seen during legacy OpROM pOST when more than one controller is present and there are boot messages for the second controller (SCGCQ00866982) - Fixed an issue where MSM may display "The requested command has invalid arguments" when 'Schedule Consistency Check' is selected (SCGCQ00832908) - Fixed an issue where a controller may not be accessible through RAIDLink until the OS is up and running (SCGCQ00847001) - Fixed an issue where drive firmware on certain SED/FDE SATA SSDs could not be updated (SCGCQ00856977) - Fixed an issue where an error "MonTask: line 1272 in file ../../raid/1078dma.c" may occur while running IO in a virtual machine (SCGCQ00822403) - Fixed an issue where a JBOD PD may not be able to be converted to Unconfigured Good in Solaris (SCGCQ00834552) - Fixed an issue where an "Instruction TLB" error may occur when a StorCLI /cX set autopdcache=r0 or similar command is executed (SCGCQ00835586) - Fixed an issue where firmware may hang in multipath scenario when cable pull/push test is performed at the same time as an array property change is issued (SCGCQ00836496) - Fixed an issue where a secure erase on a SATA SSD in HII may fail or lead to a hang in HII (SCGCQ00841317) - Fixed an issue where the controller may reset in some situations with media errors and VD undergoing manual rebuild after drives are taken offline, under stress (SCGCQ00825126) - Fixed an issue where the 3x08 chip Errata ID - 2012-RC714 may lead to PCIE 3.0 hot reset non-compliance (SCGCQ00829129) - Fixed an issue where rebuild performance on RAID1 is always slower than other RAID configurations (SCGCQ00841359) - Fixed an issue where patrol read properties window won't show up in MSM (SCGCQ00797676) - Fixed an issue where an L2 unrecoverable cache error may be seen during patrol read properties modification when VDs are made offline (SCGCQ00847162) - Fixed an issue where a VD erase may not resume after reboot when a CacheCade VD is present (SCGCQ00851810) - Fixed an issue where controller boots to OS even when pinned cache is present and boot error handling is set to stop on error (SCGCQ00860503) - Fixed an issue where firmware cannot detect some newly-inserted drives (SCGCQ00860270) - Fixed an issue where "MonTask: line 1518 in file ../../raid/2108vI2o.c" may occur in conjunction with a VMWare Guest abrupt shutdown (SCGCQ00852670) - Fixed an issue where connector name field is displayed as port 4-7 when actually both ports 0-3 and 4-7 are connected (SCGCQ00868215) - Fixed an issue where "line 243 in file ../../raid/1078int.c" error may occur during rebuild (SCGCQ00856256) - Fixed an issue where no error message shown when there is a failure to disable SSD caching of an offline VD (SCGCQ00905310) - Fixed an issue where "1 JBOD(s) found on the host adapter" may appear in legacy OpROM post even though no JBODs are present (SCGCQ00882729) - Fixed an issue where firmware may halt with "line 245 in file ../../raid/1078int.c" in log under stress with maximum VDs and background operations (SCGCQ00890133) - Fixed an issue where the HII may report a different Battery/SuperCap status than MSM/StorCLI would (SCGCQ00879726) - Fixed an issue where the firmware may hang due to an "Illegal Instruction Exception" error (SCGCQ00850441) - Fixed an issue with less-than-expected performance of Write-Verify SCSI commands in RAID0 (SCGCQ00866261)
Enhancements: - Added more descriptive port information to include link width in PHYs (SCGCQ00854621)
Version 24.7.0-0056 - Moderate Impact/Low Probability of Occurrence ------------------- Fixes: - Fixed issue where UNMAP or TRIM commands might fail on SSD in JBOD Mode (SCGCQ00853147) (RETAIN Tip H214381) - Fixed an issue where an iMR RAID configuration may fail to import to 12gbps MR (SCGCQ00833765)
Version 24.7.0-0052 - High Impact/High Probability of Occurrence ------------------- Fixes: - Incorporated MegaRAID FW stack 6.6 - Fixed an issue where a drive reporting itself as 0MB shows up as Unconfigured Good (SCGCQ00784319) - Fixed an issue where the firmware might hang during error handling of sense code 0b/47/xx (SCGCQ00701744) - Fixed an issue where some SSDs may cause the system to hang at POST (SCGCQ00595506) - Fixed an issue where an iMR RAID config may fail to import to 12gbps MR (SCGCQ00833765) - Fixed an issue where R0, R5 and R6 read bandwidth dropped abruptly at 256K block size with 24drive SATA SSD config (SCGCQ00609808) - Fixed an issue where RAID10 performance is under-performing (SCGCQ00794773) - Fixed an issue where in some cases the LSI chip would convert an incoming chip reset to a system reset (SCGCQ00664261) - Fixed an issue where many pRdm/pRequest/pReply messages would appear in LSI firmware log (SCGCQ00752195) - Fixed an issue where when a consistency check is aborted, the adapter may reset (SCGCQ00819811) - Fixed an issue where Patrol read does not start and gives incorrect warning message (SCGCQ00728404) - Fixed an issue where the controller may reset unexpectedly during error handling (SCGCQ00825126) - Fixed an issue where StorCLI may report Enclosure Not Found (SCGCQ00843146) - Fixed an issue where x880 nodes may report excessive 'SCL STUCK Low! While I2C Rx Receiving Data' in LSI firmware log (SCGCQ00728935) (Retain TIP H213891) - Fixed an issue where the command timeout for FED (SED) drives is too short, resulting in 05/2C codes (SCGCQ00797355) - Fixed an issue where bandwidth falls as queue depth increases on R5/R6 24/40 drive SAS HDD configs at 256k block size (SCGCQ00701768) - Fixed an issue where some drives may get bad PI CRC even though data is correct resulting in drive failure (SCGCQ00819314) - Fixed an issue where the firmware may exposed more than 240VDs to host even if host driver doesn't support that many (SCGCQ00829214) - Fixed an issue where MSM may display an error message if 'Schedule Consistency Check' is selected (SCGCQ00832908) - Blocked CacheCade deletion when multiple CacheCade volumes are associated with Virtual Drives, preventing data issues (SCGCQ00838953) (Retain TIP H214323) - Fixed an issue where the MegaRAID POST may display "The native configuration is not supported by current firmware" (SCGCQ00812842) - Fixed an issue where the EFI Driver Health Protocol will show Fail when more than 64VDs are configured (SCGCQ00830918) - Fixed an issue where OS may BSOD when upgrading firmware on a controller the OS has booted from if Online Controller Reset is performed (SCGCQ00825725) - Fixed an issue where controller wouldn't go to halt state after multibit ECC errors detected (SCGCQ00783186) - Fixed an issue where Opal-compliant FDE (SED) drives were being marked as FDE/SED when they shouldn't be (SCGCQ00788250) - Fixed an issue where correctable ECC error interrupts were being masked (SCGCQ00814997) - Fixed an issue where reconstructed VDs were not being reflected in MSM until system reboot (SCGCQ00839018) - Fixed an issue where controller commands may fail when an LD is deleted during reconstruction (SCGCQ00821693) - Fixed an issue where firmware would go to MonTask when making VDs offline while a Rebuild is occurring under IO (SCGCQ00825775) - Fixed an issue where commands to FDE (SED) drives may not respond within 500ms (SCGCQ00844445) - Fixed an issue where the firmware may allow the OS to change VD cache settings (SCGCQ00844447) - Fixed an issue where HDD/SSD microcode updates may report fail even though they succeeded (SCGCQ00553252) - Fixed an issue where slot numbers may be wrong systems with 32 drive slots (SCGCQ00529592)
Enhancements: - Improved Jetstress / Exchange latencies (SCGCQ00717161) - Added support for Learn Cycle debug commands in firmware (SCGCQ00814991) - Added ability to clear the MaintainPdFailHistory (SCGCQ00474559) - Improved drive rebuild performance (SCGCQ00427581) - Improved Cache Offload error handling on read from the flash interface (SCGCQ00524419) - Improved average latency and max latency in Windows operating systems (SCGCQ00671670) - Implemented power throttling (SCGCQ00457280) - Improved load balancing on >2 drive R1 VD of SSDs (SCGCQ00593588) - Added ability for firmware to report the temperature for all SAS/SATA HDD/SSD (SCGCQ00490822) - Added support for communicating with multiple controllers over I2C (SCGCQ00485924) - Added a retry of IO commands as LDIO if raid map sync is failed with MFI_STAT_CONFIG_SEQ_MISMATCH (SCGCQ00651680) - Added support for Self-Encrypting Drives in JBOD mode (SCGCQ00399739) - Improved accuracy of ROC temperature display (SCGCQ00575037) - Increased range of priorities for background tasks, CC/PR/Rebuild/Migrate/BGI (SCGCQ00313882) - Added support for 512e drives (SCGCQ00619363) - Prevented a situation where there may be excessive overtemp warnings in the firmware log (SCGCQ00820067) - Improved DDR3 signalling margin during heavy I/O workloads (SCGCQ00824711)
Version 24.2.1-0052 - Non-Critical ------------------- Enhancement(s): - Added a special handling for interactive password. - Implemented mechanism to allow system BIOS to put entries for iMR memory allocation into proper table. Fixes: - - Fixed an issue where boot message ‘cached data was lost,’ even when there was no battery present. - Fixed an issue where the ‘cli set securitykey=Lsi@12345’ command fails with error code 1001 and error message invalid key.resent. - Fixed an issue where foreign configurations fails to import maximum number of configurations. - Fixed simpleswap port mapping. - Fixed an issue where ‘Cli show all’ command fails with error message ‘Error! App exec failed in FW PCLIError! Internal.’ - Fixed an issue where Coherency bit was not enabled in SRAM TLBs.
Version 24.2.1-0045 - Non-Critical ------------------- Fixes: - Fixed an issue where cache offload failured with pinned cache on R5 VD. - Fixed an issue where using upper case characters in command 'cli set securitykey' fails with error code '1001' and error message 'invalid key.' - Fixed an issue where system would not boot into legacy mode. - Fixed an issue where default setting of VD doesn't reflect MFC's setting. - Fixed an where ServeRAID M5210 showed the wrong slot numbers in both MR and iMR, in both HII and MSM.
Version 24.2.1-0027 - Non-Critical ------------------- Enhancment(s): - Added support for ServeRAID M5200 Series 4GB Flash/RAID 5 Upgrade for IBM System x (47C8668) - Added event in firmware to indicate that an INIT operation was halted due to reboot or other failure Fixes: - Increase backplane support to 32 slots. - Enable 512E support. - Fixed an issue where system is not allocating memory correctly when MR and iMR are in the same configuration - Fixed an issue where the user is Unable to create a RAID10 through Ctrl R using 4k drives. - Fixed an issue where on a local key management (LKM) enabled controller, the user is asked to enter the security key to unlock and import a foreign drive, which is locked and has external key management (EKM) enabled. - Fixed an issue where switching between external key management (EKM) and Local Key Management (LKM) without rebooting results in the current secret key string becoming invalid/null. - Fixed an issue where cache memory size is listed as zero in controller Information. - Fixed an issue where re-keying a controller with External key management (EKM) enabled and rebooting the system results in a corrupted key ID and an error message "Unable to communicate with EKMS ..." is displayed. - Fixed an issue where performing an online firmware update or online controller reset (OCR) on a controller with External key management (EKM) enabled, results in all secured drives marked as foreign. - Fixed an issue where CacheCade volumes, which are not supported, could be created using 4K SSD's. - Fixed an issue where removing the last physical drive of arrays could result in a firmware fault. - Fixed an issue where MegaRAID Storage Manager does not show an option to create virtual drives when the first drive in the array is missing in a partial virtual drive where all drives are configured. - Fixed an issue where switching the security mode from external key management (EKM) to local key management (LKM) on iMR controller will result in a corrupted controller key. - Fixed an issue where performing a re-key operation in external key management (EKM) mode without doing a reboot, and then switching to local key management Mode(LKM) results in the Firmware logs showing that a drive security key was created but HII says the key is incorrect.
Version 24.0.2-0013 ------------------- -Initial release ibm_fw_sraidmr_5200-24_16_0-0104_linux_32-64_chg
Broadcom NetXtreme I Firmware Update Utility for IBM servers and options using the Broadcom NetXtreme I family of ethernet ASICs.
Package Version: 17.4.4.5a, April 04, 2017 Previous Version: 17.4.4.2a, March 08, 2016
This update package supports the following Broadcom devices: =============================================================================== - BCM5720 NetXtreme I Dual Port GbE Adapter / Part No: 90Y9370 - BCM5719 NetXtreme I Quad Port GBE Adapter / Part No: 90Y9352 - BCM5718 Flex System EN2024 4-port 1Gb Ethernet Adapter / Part No: 49Y7900 - BCM5719 NetXtreme I LOM / x3250 M5 - BCM5718 NetXtreme I LOM / BladeCenter HS23E, Flex x220 Compute Node - BCM5717 NetXtreme I LOM / x3100 M5
This package updates the Broadcom Firmware Code to the levels shown under the "Current" column for the devices listed below :
Notes: 1. An asterisk (*) following a version number represents a certified driver. 2. Arrows (<<) between versions indicate the component has been updated from the previous released software kit. 3. If code is not listed for a particular device, it is not implemented on that device. 4. Three asterisks (***) in the 'Current' column indicates this firmware is actually contained in the respective System UEFI update package, which is separate from this package. Please check that package for version details.
- Fixed issue with tx/rx flow control in shared nic mode where connection to IMM is lost for a period of time after the server is powered off. - Fixed issue with mac address filtering in shared nic mode where connection to IMM is lost after a system reboot.
UEFI and Boot Code: - Added individual port enable/disable functionality in F1 Setup and ASU for the NetXtreme I Quad Port GBE Adapter
Licensed Materials - Property of IBM. (C)IBM and other(s) 2017. IBM is a trademark of IBM in the United States, other countries, or both.
(C) Copyright IBM 2017. LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is delivered pursuant a General Services Administration "GSA" contract, use, reproduction, or disclosure is subject to restrictions set forth in Contract No. GS-35F-05925.
brcm_fw_nic_17_4_4_5a_linux_32-64_chg
=============================================================================== Emulex NIC Device Driver for Linux ===============================================================================
Device Driver Version: 11.2.1193.31 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support
Device Driver Version: 10.2.363.0 Supported On: System x and BladeCenter
Problems Fixed: - Multiple performance improvements in virtualized environments (SR-IOV,UMC) - Resetting Transparent Vlan to Default Vlan is not working - Cleanup ethtool set settings code - ARI on IBM x3650M4: All functions are not displayed in Linux
Device Driver Version: 10.2.261.0 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Provide link state control for VFs - ethtool shows port as fibre though copper cable is connected. - Multi channel config should be determined via port resource descriptor - Showing WoL supported in ethtool for BE3 where it is not supported - be2net driver crash when umc enabled - ip link show command shows vlan for vfs although vlan creation is failed on the vfs - Emulex be2net driver does not support IOMMU pass through mode
Device Driver Version: 10.0.800.0 Supported On: IBM System x
Problems Fixed: - Low bi-di throughput seen on 1g ports of HS-23 LOM - Multiple performance improvements - Bonding driver takes approx 20 seconds to be ready
Incremental Interoperability: - RHEL 5.10 - RHEL 6.5 - XE-102 and XE-104 ASIC (OCx14xxx) - Support for set and get channels ethtool operation
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.4 and above 64-bit with KVM * SLES11 SP3 and above 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
Device Driver Version: 4.6.267.4 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 KVM configurations - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 SR-IOV configurations - SR-IOV configuration section of the Linux NIC Driver Documentation has been modified to improve clarity
Incremental Interoperability: - S3 Resume on IBM Flex - SLES 11.3 on IBM System x and BladeCenter
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.3 and 6.4 64-bit with KVM * SLES11 SP2 and SP3 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
- Use of SR-IOV with the XEN hypervisor is not supported at this time.
- Use of SR-IOV with the KVM hypervisor requires the use of macvlan network interfaces.
Device Driver Version: 4.6.148.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - Ethernet performance issues in a variety of workloads - VFs are not displayed after driver re-load when is VFs attached to VM - vLAN tagging in Switch Agnostic vNIC mode
Incremental Interoperability: - RHEL 5.9 - RHEL 6.4 - Network performance varies with workload. An ethernet driver tuning script and instructions is now included with the be2net driver. - Switch Independent Mode within hypervisor OS's
Known Issues: - Multi-channel is not supported in RHEL5.x XEN. This is a kernel limitation - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 KVM configurations - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 SR-IOV configurations - SR-IOV is not supported with RHEL5.x XEN
Device Driver Version: 4.4.180.0 Supported On: IBM Flex
Device Driver Version: 4.2.389.0 Supported On IBM System x and BladeCenter
Problems Fixed: - Unloading the driver hangs the system after running IPv6 traffic - Link status messages cleaned up when in Switch Agnostic mode - Miscellaneous network performance issues to improve throughput - Miscellaneous problems related to SRIOV to improve usability - Ethtool wol command displays wol enabled even when disabled - Ethtool speed reported as 10000Mb/s for disabled devices in Switch Agnostic mode
Incremental Interoperability: - RHEL6.3 GA Kernel - Increase default B/W for SRIOV vf's to 10Gb from 100Mb
Device Driver Version: 4.1.413.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - WOL changes for Linux NIC driver as mentioned in Bug# 24543 - SR IOV UE when attempt to do multiple (3 times) driver load/unload - Speed is 10000Mb/s for Disabled devices in UMC Mode - Incorrect Duplex value is shown for unconnected port of NC552m in Rhel6.1 32bit - SLES 11 SP2 GMC: Enable support for Lnx NIC Driver - SRIOV: When VGT is configured for a VF, ip link show doesn't display it for the VF configured. - RHEL 5.8 GA: Enable support for Lnx NIC Driver - ip link command with vlan = 4095 has toggling effect - ip link command with vlan =0 should remove guest VGT privilege
Device Driver Version: 4.1.334.39 Supported On: IBM System x and BladeCenter
Problems Fixed: - SR-IOV: Can't load be2net driver in a VM after the VM has been rebooted - SR-IOV: Unload PF driver with VF driver loaded causes system instability - SR-IOV: VF MAC always gets Emulex OUI - SR-IOV: Partition the limited per port VLAN entries across VFs and PFs - Non Member VLAN packets not received in interface promiscuous mode in BE3 - Avoid CQ full condition in HW - be2net: use RX_FILTER cmd to program multicast addresses - account for skb allocation failures in ethtool stats - Support 60 second delay to Linux NIC driver to allow FAT dump completion on recovery from EEH - Link status is up [ethtool and OCM] when the bandwidth is assign 0 for UMC configuration - Remove msix module parameter - Use V1 version of COMMON_NTWK_LINK_STATUS_QUERY for Lancer. - Emulex: Ethtool failing to update FW - Emulex: Panic in be2net driver in SLES11-SP2-B7 on adapter - TCP ACKs from different connections are getting received in single queue - Multicast filtering feature not working on PPC - Exit of mcast promiscous mode not working - VLAN promiscous mode cannot be set on Lancer - Can't communicate after changing MAC address via VLAN interface - Improper memory accounting in received packets - WOL changes for Linux NIC driver as mentioned in bug - Transparent VLAN tagging feature not working in SR-IOV
BIOS/FW/UEFI Update for IBM N2200 Series SAS/SATA HBA Controllers
Controller Supported: IBM N2215 SAS/SATA HBA for IBM System x (47C8676) IBM N2225 SAS/SATA HBA for IBM System x (00AE912) IBM N2226 SAS/SATA HBA for IBM System x (00AE916)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 1.13 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.31.02.00 13.00.02.00 15.00.02.00
Firmware Fixes: - Fixed issue where Power On Reset Observed While Executing LOG SENSE Command to SATA Drive. (SCGCQ01081163) - Fixed issue where PL Fault 4203 observed while executing REPORT ZONES SCSI Command to SATA Drives. (SCGCQ01094926) - Fixed issue where unsupported Log Sense commands fail with 'INVALID COMMAND OPERATION CODE' instead of 'INVALID FIELD IN CDB' - SATA only (SCGCQ01079905) - Fixed issue where SANITIZE Command is Not Failed With Expected Sense Data for Service Action EXIT FAILURE MODE - SATA only (SCGCQ01115136) - Fixed issue where Unable to un-register a device because of outstanding Task Set Full MID (SCGCQ01112415, Port of SCGCQ01076294) - Fixed issue where Fast back-to-back or parallel PCIe configuration requests after certain addresses can generate bad Config Read data resulting in 0x2622 fault (SCGCQ01062410, Port of SCGCQ01047773) - Fixed issue where I/O could timeout if task management fails (SCGCQ01131412, Port of SCGCQ01113324) - Fixed issue where Fault 0x265D encountered on inserting a faulty drive in place of RAID 1 member (SCGCQ01149263, Port of SCGCQ01096884) - Fixed issue where PL fault 5854 seen when system boots with all SATA drives in setup in spun down mode (SCGCQ01204852, Port of SCGCQ01155407) - Fixed issue where OS failed to boot after hot-plug on the RAID 1 member. (SCGCQ01163158, Port of SCGCQ01084723) - Fixed issue where Storlib/storlibtest stuck on a bad drive while retrieving phyinfo (SCGCQ01180929, Port of SCGCQ01171835) - Fixed issue where outstanding SATA passthorugh IO can cause target reset from timer callback check if sata Initialization not done yet (SCGCQ01205281, Port of SCGCQ01172334) - Fixed issue where 'iop show cfg all' command is not listing all Expander's config pages (SCGCQ01118587, Port of SCGCQ01110070) - Fixed issue where CPU hangs due to out of bound access of Timer wheel RAM while manually adding FPE timer. (SCGCQ01090984, Port of SCGCQ01089094) - Fixed issue where drive timeout occurs with large number of drives attached (SCGCQ01145424, Port of SCGCQ01118894) - Fixed issue where while running stress, controller crashes with 0x584A fault (SCGCQ01064158, Port of SCGCQ01041762)
Enhancements: - Modified the code to check the LBA OUT OF RANGE condition greater than the last LBA. (SCGCQ01113946) - Assign the enclosure level index for direct attached enclosures ie., the controller itself. (SCGCQ01057508)
BIOS: Fixes: - Fixed issue where PCI Info field missing in legacy BIOS config utility(SCGCQ01092124) - Fixed issue where command timeout not handled properly (SCGCQ01099923) - Fixed issue where BIOS config utility is hung while deleting a missing volume. (SCGCQ01113664) - Fixed issue where BIOS config utility fails to read configuration pages when large topology is connected. (SCGCQ01190203) - Fixed issue where Connecting a Faulty drive to the controller results in BIOS config utility crash (SCGCQ01191180) - Fixed issue where Legacy BIOS stuck in infinite loop when a faulty drive is connected with the controller. (SCGCQ01091176) - Fixed issue where Start Stop Unit (SSU) command loads cartridge of a sequential media while booting. (SCGCQ01093694) - Fixed issue where Legacy BIOS stuck in infinite loop when a faulty drive is connected with the controller. (SCGCQ01095670, Port of SCGCQ01091176)
Enhancements: - Device Properties screen to display Connector Name, enclosure Level and Slot values of a device. (SCGCQ01072668)
UEFI: Fixes: - Fixed issue where in HII, device properties may have duplicate device identifiers. (SCGCQ01112383)
Version 1.12 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.29.02.00 12.00.02.00 14.00.00.00
Firmware Fixes: - Fixed an issue where Raid creation is failed when tried to create a RAID using SATA drives. (SCGCQ00998155) - Fixed an issue where any pure SEP devices (i.e. not marked as an SSP Target) are not exposed to the management controller through the MCTP Inventory command. (SCGCQ00943216) - Fixed an issue where Fault 0xD102 occurred while executing Write Buffer SCSI Command to SATA Drives (SCGCQ00953463) - Fixed an issue where a debug print was trying to access the address of variable type and causing core exception in IOPs that use PLI_CTRL_REQ_SET_SINGLE_DUAL_CONTEXT_TXDMA. (SCGCQ01004146 port of SCGCQ01004143) - Fixed an issue where 265D fault observed when "IOP show cfg all" executed from UART with BIOS flashed (SCGCQ01025868) - Fixed an issue where spun down SATA drive showed up as non NCQ drive after initialization. (SCGCQ00999741, SCGCQ01005428 Port of SCGCQ00999741) - Fixed an issue where I/O timeout could occur when running auto read/write I/Os and non-auto read/write I/Os through FPE, especially when the I/Os were single threaded. (SCGCQ01023261 Port of SCGCQ01022368) - Fixed an issue where RAID creation failed with SATA drives. (SCGCQ01024544) - Fixed an issue where attaching a SATA drive that sends an invalid/unsupported initial FIS signature directly to a controller phy resulted in that phy getting reset by the firmware until the drive was removed.SCGCQ00872060 - Fixed an issue where some “packet exception busy retry” responses have a bad CRC value in the CRC field. This only impacts MCTP over I2C when in slave response mode, SCSI IOs out to drives, and drives that were removed. (SCGCQ01019763 Port of SCGCQ01019438) - Fixed an issue where latency observed during controller diag reset operations or during controller boot when two enclosures with mix of SAS/SATA drives are connected. (SCGCQ01001465) - Fixed an issue where the inquiry command sent via MCTP from the BMC to the controller, in which the controller did not respond with inquiry data after communicating to an I2C attached SCSI enclosure processor based back-plane. SCGCQ00896512 - Fixed an issue where MCTP: I2C slave with high MPI request rate from host and BMC can cause a host request timeout, and , the BMC may experience I2C bus problems until the controller is either reset or times out on the I2C operation. (SCGCQ01087653) - Fixed an issue where controller was unnecessarily faulting for correctable L2 parity errors. (SCGCQ00976726, SCGCQ00941520 PORT OF SCGCQ00934325) - Fixed an issue where an extra garbage byte was present at the end of a second I2C packet in a message. This primarily impacts the standard I2C mode, in which the controller is allowed to act as both an I2C master and slave and controls the size of the packet. (SCGCQ00925199, SCGCQ00955069 PORT OF SCGCQ00916929) - Fixed an issue where firmware panic (code: 0000265D) and ROM BIOS hung could occur for SAS3FW IR raid10 after removing a drive and powering on the HBA controller. (SCGCQ01062417, SCGCQ01061628 Port of SCGCQ01024976) - Fixed an issue where fault 0xD073 could occur during heavy IO when a timed out IO completed while firmware is handling the timeout. (SCGCQ01064661 Port of SCGCQ01052686) - Fixed an issue where firmware does not use the IOCInit Timestamp field to fill in the SAS IO Unit Page 16 and SAS Phy Counter Event. (SCGCQ00884836, SCGCQ00955132 Port of SCGCQ00872141) - Fixed an issue where the standard Port Status Yellow LED GPIO fails to properly turn on and off with link changes. (SCGCQ00917803, SCGCQ00991716 Port of SCGCQ00907921) - Fixed an issue where PL timer function timestamp print fills ring buffer. (SCGCQ00991772) - Fixed an issue where build failure occurred if MCTP is enabled and Config trap hardware workaround was disabled (SCGCQ01082977 Port of SCGCQ01075828) - Fixed an issue where the IOP generated a false reply parity error, which resulted in a 0x1500 fault. (SCGCQ00929813, SCGCQ00955133 Port of SCGCQ00927500) - Fixed an issue where a SATA error is received while trying to obtain the message ID (MID) in the Rx Context Manager. When this occurs, the MID cannot be validated resulting in a variable being assigned a NULL value, which the firmware then attempted to access and resulted in a 265D fault. (SCGCQ00930637 Port of SCGCQ00928401) - Fixed an issue where some of the drives under external enclosure are marked as direct attached. (, SCGCQ00933717, SCGCQ00991711 Port of SCGCQ00926285) - Fixed an issue where target mode controller sometimes would mistakenly return Open Reject (Protocol not supported) for open requests, when the link to connected IT controller is broken repeatedly. (SCGCQ01009227) - Fixed an issue where initiator/target moved can generate two target add events (SCGCQ00941678, SCGCQ00941521 Port of SCGCQ00934337) - Fixed an issue where 265D fault observed when "iop show cfg all" executed from UART with BIOS flashed. (SCGCQ01030564) - Fixed an issue where fast back-to-back or parallel PCIe configuration requests after certain addresses can generate bad Config Read data (SCGCQ01062342, SCGCQ01062409 Port of SCGCQ01047773) - Fixed an issue where initiator/target moved can result in Initiator missing event but no corresponding Target missing event. (SCGCQ00941666 port of SCGCQ00915308, SCGCQ00955068)
Enhancements: - Added a NVDATA option to enable or disable the bandwidth based PL algorithm to set hardware with single or dual context. (SCGCQ00948044, SCGCQ00948045 Port of SCGCQ00942005) - Modified SCSI IO Reply to include Observed Application Tag, Observed Reference Tag and Observed Guard. (SCGCQ01002367 SCGCQ00988360) - Discovery due to non responding SATA drive is now timed to last for the amount of seconds configured in NVDATA (SCGCQ00996678) - Modified "SAS IO Unit Page 4" to add a new field "SATAHintingTimeout" (SCGCQ00996127) - Modified SCSI IO Reply to include Observed Application Tag, Observed Reference Tag and Observed Guard. (SCGCQ00988360) - Added support for PCIe devices to Target Reset Method (SCGCQ00686666) - Added IOCCapabilities bit to indicate PCIe SRIOV support and added three new fields in IOCFacts reply message to include SGE modifier fields. (SCGCQ00852827) - Added ConfigurationFlags field to IOC Init message along with definition of bit to enable/disable NVMe SGL format. Added control operations to enable and disable SGL format for a specific NVMe device. Added bit in PCI device page two to indicate current configuration. (SCGCQ00872169) - Additional added PCIe Enumeration Event EnumerationStatus bit to indicate when there are more devices than resources. (SCGCQ00884740) - Added support for non-contiguous slot numbers defined in manufacturing page 7. (SCGCQ01000709) - Return EEDP/DIF error data of the first error frame detected by the hardware during READ in the MPI Reply error message frame (SCGCQ01000193) - Differentiate between L2 correctable and uncorrectable faults. (SCGCQ00966698, SCGCQ00929811 PORT OF Defect - SCGCQ00929810) - Enhanced PLI_CTRL_REQ_GET_SATA_HINT_INFO to also provide information of an active SATA Hinting discovery at a given time. (SCGCQ01058123)
BIOS Fixes: - Fixed an issue where BIOS config utility showed Package version field is displayed and PCI Info field is missing. (SCGCQ01092124) - Fixed an issue where junk characters were displayed when one of the enclosures was powered off while the config utility cursor is in Manage Volume screen. (SCGCQ01034754 Port of SCGCQ01020187) - Fixed an issue where initialization failure of one faulty controller reports IOC Facts failed for successful initialization of good adapter. (SCGCQ01034746 Port of SCGCQ01029556) - Fixed an issue where SAS3008 IT/IR adapter installed and a single SAS drive, the INT 13 Function 48H doesn't show physical geometry of the drive, hang with invalid buffer size, and has buffer overrun. (SCGCQ00996538 port of SCGCQ00988924) - Fixed an issue where legacy BIOS encountered an infinite loop when a faulty drive was connected with the controller. (SCGCQ01091176) - Fixed an issue where SplitRom utility for legacy BIOS prints the wrong value for sizeof Frame Buffer (SCGCQ00933107) - Fixed an issue where incorrect values for cylinders, heads, and sectors were reported on 4K drives. (SCGCQ00987624 Port of SCGCQ00980976) - Fixed an issue where controller IR firmware is displayed as IT firmware when SAS Address is not programmed. (SCGCQ01034758 Port of SCGCQ01033766)
Enhancements: - Modified SCSI IO Reply to include Observed Application Tag, Observed Reference Tag and Observed Guard. (SCGCQ01002367 SCGCQ00988360) - Added a new field "SATAHintingTimeout" to SAS IO Unit page four (SCGCQ00996127) - Added support for PCIe devices to Target Reset Method (SCGCQ00686666) - Added IOCCapabilities bit to indicate PCIe SRIOV support and added three new fields in IOCFacts reply message to include SGE modifier fields. (SCGCQ00852827) - Added ConfigurationFlags field to IOC Init message along with definition of bit to enable/disable NVMe SGL format. Added control operations to enable and disable SGL format for a specific NVMe device. Added bit in PCI device page two to indicate current configuration. (SCGCQ00872169) - Additional added PCIe Enumeration Event EnumerationStatus bit to indicate when there are more devices than resources. (SCGCQ00884740) - BIOS config utility topology has been changed to be in consistent with other utilities such as MR config utility. (SCGCQ00850331)
UEFI Driver Fixes: - Fixed an issue where associated physical disk form is not updating with the proper PD missing data. (SCGCQ01010356) - Fixed an issue where HII Form is displaying question ID mismatch with option value popup while physical disk properties screen is entered. (SCGCQ01008746)
Enhancements: - Modified SCSI IO Reply to include Observed Application Tag, Observed Reference Tag and Observed Guard. (SCGCQ01002367 SCGCQ00988360) - Added a new field "SATAHintingTimeout" to SAS IO Unit page four (SCGCQ00996127) - Added support for PCIe devices to Target Reset Method (SCGCQ00686666) - Added IOCCapabilities bit to indicate PCIe SRIOV support and added three new fields in IOCFacts reply message to include SGE modifier fields. (SCGCQ00852827) - Added ConfigurationFlags field to IOC Init message along with definition of bit to enable/disable NVMe SGL format. Added control operations to enable and disable SGL format for a specific NVMe device. Added bit in PCI device page two to indicate current configuration. (SCGCQ00872169) - Additional added PCIe Enumeration Event EnumerationStatus bit to indicate when there are more devices than resources. (SCGCQ00884740) - View physical Disk Properties HII form is modified to be in consistent with other utilities such as BIOS CU. (SCGCQ00850330) - Added support on ARM-64 (SCGCQ00976647) - Serial number of drive is retrieved from Inquiry command VPD page 80 and displayed as Unit Serial Number (VPD) is device properties screen. (SCGCQ00987903)
Version 1.11.02 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.27.03.00 11.00.06.00 13.00.00.00
Firmware 11.00.06.00: Fixes:
- Fixed an issue where in the IOP a false reply parity error is being generated, which results in a 0x1500 fault. (SCGCQ00929813, Port of SCGCQ00927500) - Fixed an issue where some packet exception busy retry responses have a bad CRC value in the CRC field for MCTP over I2C when in slave response mode for SCSI IOs out to drives, and drives that were removed. (SCGCQ01019438) - Fixed an issue where MCTP I2C slave with high MPI request rate from host and BMC can cause a host request timeout. (SCGCQ01087653) - Fixed an issue where distinguishing between L2 correctable and uncorrectable faults was difficult, due to a shared fault code of (0x26B4). (SCGCQ00929811, PORT OF SCGCQ00929810) - Fixed an issue where I/O timeout could occur when running read/write I/Os (auto) and non-read/write I/Os through FPE, especially when the non-read/write I/Os are single threaded (SCGCQ01023261, Port of SCGCQ01022368) - Fixed an issue where FW panic (code: 0000265D) and ROM BIOS hung for SAS3FW IR RAID10, while updating state of a volume after power cycle on controller, an operation attempt on non-existing private member variable causes data TLB error. (SCGCQ01061628, Port of SCGCQ01024976) - Fixed an issue where that FW does not use the IOCInit timestamp field to fill in the SAS IO unit page 16 and SAS Phy counter event (SCGCQ00884836, Port of SCGCQ00872141) - Fixed an issue where the standard Port Status Yellow LED GPIO fails to properly turn on and off with link changes. (SCGCQ00917803, Port of SCGCQ00907921) - Fixed an issue where a build failure occurs if MCTP is enabled and config trap hardware workaround is disabled. (SCGCQ01082977, Port of SCGCQ01075828) - Fixed an issue where the controller is unnecessarily faulting for correctable L2 parity errors. (SCGCQ00976726, Port of SCGCQ00934325) - Added a NVDATA option to enable or disable the bandwidth based PL algorithm enhancement, which sets hardware with Single or Dual Context. (SCGCQ00948044, Port of SCGCQ00942005) - Fixed an issue where spun down SATA drives show up as non NCQ drives after initialization. (SCGCQ01005428, Port of SCGCQ00999741) - Fixed an issue where 265D fault observed when "iop show cfg all" executed from UART with BIOS flashed. (SCGCQ01030564, Port of SCGCQ01025868) - Fixed an issue where very fast back-to-back or parallel reads of the PCIe Configuration Space after or during the firmware handled addresses can cause the data firmware is writing to be picked up by the next configuration read, when firmware has to write to its Configuration Space. (SCGCQ01062409, Port of SCGCQ01047773) - Fixed an issue where there is an extra garbage byte at the end of a second I2C packet in a message. This primarily impacts the standard I2C mode. (SCGCQ00925199, Port of SCGCQ00916929) - Fixed an issue where a target moved can result in Initiator missing event but no corresponding target missing event. (SCGCQ00941666, Port of SCGCQ00915308) - Fixed an issue where an initiator/target moved can generate two target add events. (SCGCQ00941678, Port of SCGCQ00934337) - Fixed issue where SES diagnostic command may fail with backplane expander. (SCGCQ00991690, Port of SCGCQ00976691) - Fixed issue where attached edge device frame buffering (EDFB) enabled expander may drop attached drives. (SCGCQ00999909, Port of SCGCQ00897639) - Fixed issue where drives in external enclosure would be listed as direct attached. (SCGCQ00933717, Port of SCGCQ00926285)
BIOS 8.27.03.00 Fixes - Fixed an issue where IOC facts failed error is displayed in CU when one of two controllers is faulty. (SCGCQ01029556) - Fixed an issue where INT 13 Function 48H doesn't show physical geometry of the drive, hang with invalid buffer size, and has buffer overrun. (SCGCQ00988924) - Fixed an issue where the wrong values of cylinders, heads, and sectors reported on a 4K drive. (SCGCQ00980976) - Fixed an issue where junk characters are seen when one of the enclosures is powered off while the cursor is in Manage Volume screen. (SCGCQ01034754) - Fixed an issue where controller IR firmware is displayed as IT firmware when SAS address is not programmed. (SCGCQ01034758, Port of SCGCQ01033766)
Version 1.11.01 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.27.00.00 11.125.00.00 13.00.00.00
Firmware Fixes: - Fixed issue where invalid or unsupported signature FIS was not validated for expander attached SATA drives (SCGCQ00852290) - Fixed issue where BUSY TIMEOUT PERIOD Field was incorrectly populated in UCM Control Mode Page for SATA Drive (SCGCQ00871463) - Fixed issue where during SATA FORMAT Operation, REQUEST SENSE command is not failed with expected response where DESC bit is set (SCGCQ00872727) - Fixed slot assignment to direct attach SEP Device Handle that previously resulted in slot number out of bounds condition (SCGCQ00894230) - Fixed issue where locate was not working for a particular slot in the external enclosure due to firmware not picking up the correct phy index (SCGCQ00932707) - Fixed issue where 19th entry of Self-Test Results Log Page was not showing during SAT translation. (SCGCQ00847941) - Fixed issue where SATA hinting feature causes IO timeouts with slow spin up drives under Linux (SCGCQ00867345) - Fixed issue where SCSI ATA passthrough code did not check for correct CDB length (SCGCQ00915201) - Fixed issue where SES command locate fails for first time after discovery when slot number information source bit is set (SCGCQ00923283) - Fixed fault 0x4300 during discovery error recovery testing (SCGCQ00860398) - Fixed issue where SES locate was not working for external enclosure (SCGCQ00915737) - Fixed fault d060 observed when running IOs with link_reset Task management command in a loop (SCGCQ00865100, Port of SCGCQ00840603) - Fixed issue where after cable pull, SAS device page 0 entry device present for missing expander after discovery complete (SCGCQ00910603, Port of SCGCQ00904470) - Fixed PL Fault 0x6002 When Sending SCSI Security Protocol Out Commands to SATA SSDs (SCGCQ00910188, Port of SCGCQ00888033) - Fixed PL Fault 0x5833 When Performing Controller Reboots (SCGCQ00895602, Port of SCGCQ00888103) - Fixed issue where IOs completed with good status when EEDP Check enabled and EEDP error injected with 4096 block size(SCGCQ00856981, Port of SCGCQ00855669) - Fixed issue where system hangs after adapter reset with heavy IO load (SCGCQ00877119, Port of SCGCQ00646625) - Fixed issue where when using a large number of SATA drives, out of resource condition may cause IOs to be pended indefinately (SCGCQ00887685, Port of SCGCQ00885544) - Fixed issue where SATA SSDs in locked state not showing up after manually loading driver. (SCGCQ00859102, Port of SCGCQ00843668) - Fixed issue where SSD Marked Failed After Encountering 03/1100 Sense (Medium Error) (SCGCQ00945560, Port of SCGCQ00933048) - Fixed long I/O latency with large burst of non-auto I/Os generated while other read/write I/Os are running (SCGCQ00884667, Port of SCGCQ00884179) - Fixed issue where fast back-to-back or parallel PCIe configuration requests after certain addresses can generate bad Config Read data (SCGCQ01070088, Port of SCGCQ01047773) - Fixed PL Fault 0x5814 while handling Task Management during IO Timeout (SCGCQ00860153, Port of SCGCQ00842366)
UEFI Fixes: - Fixed issue where UEFI/HII offered RAID10 & RAID1E creation even when these RAID levels are disabled (SCGCQ00855519) - Fixed issue where following a system BIOS update, system hangs in HII 'Change Controller Properties'. (SCGCQ00907731) - Fixed issue where the SEP devices are not exposed in Extended SCSI Passthru protocol (SCGCQ00907013, Port of SCGCQ00905547)
UEFI Enhancements: - Use PCI IO Protocol Write function as alternate to Serial IO write function to route debug messages to serial port of host system. (SCGCQ00898744) - Add Logical Block Size of disk to device properties screen in HII. (SCGCQ00886820) - Eliminate Maximum transfer size limitation of BlockI/O calls in SAS3 IT UEFI (SCGCQ00850298) - Modify Port and Phy Configuration in UEFI HII to accomodate multiple SAS cores and disabled core. (SCGCQ00834025, Port of SCGCQ00802753) - Added relevant help message for Phy settings. (SCGCQ00869976)
BIOS Fixes: - Fixed long response delays with config utility navigation response. (SCGCQ00884882) - Fixed issue where BIOS CU displays "page read error" messages when connected to large topology. (SCGCQ00886786) - Fixed help text of format tab for 4K SAS drives. (SCGCQ00860653, Port of SCGCQ00834444)
BIOS Enhancements: - Add Logical Block Size of disk to device properties screen. (SCGCQ00898447, Port of SCGCQ00887338) - Change Auto-Refresh Interval for BIOS Configuration Utility (CU) Topology Screen (SCGCQ00898423, Port of SCGCQ00887368)
Version 1.09.04 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.21.06.00 09.00.02.00 10.00.00.00
Fixes: - Fixed issue where HDD removal not properly reported as Target Device missing when attached to adapter through an expander. (SCGCQ00777858) - Fixed issue where Fault State (0x265d) is observed in driver logs while connecting an enclosure with fully populated SATA drives (SCGCQ00856085) - Fixed issue where 0x7C54 fault seen during I/T switching (SCGCQ00847013) - Fixed issue where certain drive pull scenarios result in longer time to discovery running (~3+ seconds) (SCGCQ00843759) - Improved PCIe Config operation handling to avoid 0x0D03 faults (SCGCQ00836878) - Fixed issue where controller could fault with 0x4A00 during link break (SCGCQ00793956) - Fixed the occurrence of fault 0x1708, when a free MID is attempted to be failed to the host. (SCGCQ00826420) - Fixed occurrence of fault 0x5814/0x5813 while handling Task Management during IO Timeout (SCGCQ00865024) - Fixed issue where SATA drive with slow spin up can cause IO timeout in Linux. (SCGCQ00869554) - Fixed system hang after adapter reset with heavy IO load (SCGCQ00877099) - Fixed issue with slow BIOS interface response with certain hardware e nvironments (SCGCQ00888867) - Fixed UEFI issue where in an environment with multi-lun devices where lun size varies, backup GPT corruption can occur (SCGCQ00907441)
Enhancements: - In BIOS added a new field to Device Properties called "Logical Sector Size". The possible values are 512B, 4K and Unknown. (SCGCQ00887338) - Improved the response time in UEFI HII utility for SAS3 IT/IR Controllers (SCGCQ00821793)
Version 1.07 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.15.01.00 07.00.01.00 08.00.00.00 Firmware:
Fixes: - Fixed issue where 0xD025 fault appeared while running non-FastPath I/O to SATA disk with outstanding FastPath I/Os to SAS disk (SCGCQ00604668) - Fixed fault 0xD071 while running stress and glitching all 4 phys as part of a cable break test. (SCGCQ00590502) - Fixed MPI Power Management Global Request Change to Reduced or Standby state results in "Operation State Not Supported" or "IOC Busy" (SCGCQ00584284) - Fixed issue where when transitioning MPI Power Management speed from lower to higher rate the command falsely reported as successful (SCGCQ00584288) - Fixed issue with mixture of FastPath IO's and standard firmware path IO's timing out on SATA disks (SCGCQ00576190) - Fixed SATA only issue where Multiple 'Write Verify' SCSI commands with zero data length leads to f/w fault (0x4203 or 0x4C31). (SCGCQ00549293) - Fixed fault 0x6230 while disabling expander phys and running stress in multi-path failover environment (SCGCQ00692652) (SCGCQ00699059) - Fixed various conditions causing 0x6230 fault when cable breaking (SCGCQ00669775) (SCGCQ00699057) (SCGCQ00643835) - Fixed issue where rapid successive controller resets would cause HBA to stop responding on the PCIe bus (SCGCQ00556766) - Fixed issue where when phy power management is enabled, TARGET RESET function fails yet command is reported a success. (SCGCQ00570820) - Fixed issue where PCIe Link Down can cause transmit margin field to not reset resulting in PCIe validation tests failing (SCGCQ00663185) - Fixed issue where SCSI command is not failed with expected response when SATA drive undergoing a format operation and reserved fields are set as Non-Zero value (SCGCQ00679566) - Fixed issue where read log ext command wasn't issued by PL FW to recover from error during the failure of write verify command (SCGCQ00675166) - Fixed IOC fault state 0x1609 caused by Message Unit Reset (SCGCQ00582515) - Fixed issue where SAS Phy page 1 and 2 error counters wrap around when maximum values are reached. (SCGCQ00651231) - Fixed fault 0x265D when running large block IO with higher Qdepth (SCGCQ00600832) - Fixed issue in Transport Layer Retries Code causing 0x265D and 0x0501 faults (SCGCQ00609576) - Fixed issue where Bad TLB entry causes 0x26B5 fault in IT/IR firmware (SCGCQ00629210) - Fixed 0x6828 fault when using large CDB (SCGCQ00614498) - Fixed fault 0x1901 seen when running Unmap IO’s during task aborts for a SATA drive (SCGCQ00711858) - Fixed issue where system gets hung & reboot while running IO's along with diag reset on the Controller which has Active and Inactive volumes. (SCGCQ00714125) - Fixed issue where cards would fault with 58B4 on power up due to incorrect SERDES setting (SCGCQ00728903) - Fixed WRITE SAME(10) and WRITE SAME(16) SCSI commands fail on last LBA of SATA Drive, incorrectly reporting logical block out of range. (SCGCQ00703433) - Fixed fault 0x4203 when WRITE AND VERIFY (16) command us executed to SATA Drive for LBA Out of Range (SCGCQ00705320) - Fixed issue where ATA Translation of sector count in sense data is inconsistent for READ DMA pass-through cmd (SCGCQ00712688) - Fixed issue where CLI command to dump L1 data cache causes 0x265D fault (SCGCQ00715317) - Fixed SATA Init problem causing 0x6230 controller fault (SCGCQ00683795) - Fixed fault 0x265D hit when booting controller with attached enclosure (SCGCQ00709712) - Fixed issue where Negotiated Physical Link Rate in SAS IO Unit Page 0 may not be correct after pulling a cable (SCGCQ00696408) - Fixed issue in NVDATA where SGPIO PHYs reversed (SCGCQ00750746) - Fixed I2C slave status interrupt not always cleared with I2C Write operation (SCGCQ00731646)
Enhancements: - Improved implementation of SCSI transport layer (SATL) handling while the SATA drive is in security 'frozen' state (SCGCQ00549302) - SCSI Transport Layer: Indicate support for the ATA Device Server Password security protocol (SCGCQ00625580) - IO Processor Target Mode performance improvements (SCGCQ00685827)
UEFI:
Fixes: - Fixed issue where the navigation of HII screens was very slow when no drives are connected to an expander (SCGCQ00569123) - Reduce the boot time for UEFI driver for large configurations (SCGCQ00498101) (RETAIN Tip H212119) - Fixed issue where HII configuration utility did not print the complete SAS address (SCGCQ00709781) - Fixed issue where View Physical Disk Properties screen on HII was not showing correct disk details (connector:encl:slot) when more than 8 disks are directly attached. (SCGCQ00691104)
Enhancements: - Obtain the Physical Slot number from the PCI Bridge first and use fall back to SMBIOS table if unable retrieve slot number from PCI Bridge. (SCGCQ00498095) - Retry Test Unit Ready command if drive foes not respond on first try. (SCGCQ00518198) - Adding a small delay (2 seconds) to get proper operation status after starting an operation (like consistency check) in HII (SCGCQ00621480) - Enhanced HII configuration utility to display tape drive information (SCGCQ00700835)
BIOS:
Fixes: - Fixed issue where the system boot hangs when Legacy BIOS is disabled (using HII) on certain UEFI systems. (SCGCQ00637088) - Fixed issue where the Legacy BIOS failed to detect certain large capacity SAS drives (SCGCQ00696486)
Enhancements: - Support configurable timeout for Start Stop Unit Command. (SCGCQ00694336)
Ehhanncements: - Add support for N2225 and N2226 SAS/SATA HBA Controllers Fixes: - Fixed an issue where SAS SSDs may not show up in the uEFI configuration Utility (HII)
=============================================================================== Emulex iSCSI Device Driver for Linux ===============================================================================
Device Driver Version: 11.2.1193.12 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support
Device Driver Version: 10.2.365.0 Supported On: System x and BladeCenter
Problems Fixed: - be2iscsi rpm is failing with dependencies error - Unable to iSCSI SAN install RHEL/SLES/WIN2012R2 with UFP - Server is getting rebooted when we run IPv4+IPv6 bi-di NIC traffic simultaneously on UMC enabled interfaces
Device Driver Version: 10.2.261.1 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Write error while running traffic - System crashed after running converged IO with driver load unload in a - Possible backlog of eq might happen if _process_cq keep processing for a long time: causes fw UE - Driver memory leak resulting in "DMA: Out of SW-IOMMU space" errors in dmesg file output
Device Driver Version: 10.0.803.21 Supported On: IBM System x
Problems Fixed: - Unable to OEMSEAddTarget or OEMSEDiscoverTaget successfully and get entries in mili2d.log - Emulex drivers are not working on RHEL5 and RHEL6 errata kernel updates - IO Read/Write almost halts with 'DMA: Out of SW IOMMU space' messages while running iSCSI Multipath I/O
Device Driver Version: 4.4.175.0 Supported On: IBM Flex
Problems Fixed: - Cleaned up a cosmetic problem with warning messages during driver compile from source - System crashes when we run simultaneous IO to 6 vNIC�s with iSCSI IO - Linux kdump kernel crashes during shutdown after capturing dump, if be1iscsi driver running
Device Driver Version: 4.1.402.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - LUN is not getting detected for OEM CNA in SLES 11 SP2 64 bit OS - ioctl semaphore deadlock when running load/unload loop with target - SLES 11 SP2 GMC: Enable support for Lnx iSCSI Driver - RHEL 5.8 GA: Enable support for Lnx iSCSI Driver
Device Driver Version 4.1.334.39 Supported On: IBM System x and BladeCenter
Problems Fixed: - Emulex: Warning messages seen while building Emulex drivers on RHEL platform - Unable to load be1iscsi driver during iSCSI boot OS install - Modprobe be1iscsi hangs when system with max targets login - be1iscsi unload hangs the system - fw rebooted on 1st mbox cmd after driver load > unload > load - Failed to initialize iscsi driver - need to define DMA_32BIT_MASK / DMA_64BIT_MASK in Linux kernel 3.x.x
Firmware Version: 2.03x14 Boot Code Version: 11.20a6 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support - Windows 2016 Support - VMware ESXi 6.5 Support
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.02x11 Boot Code Version: 5.30a6 Supported On: System x Flex
Problems Fixed: - None
Incremental Interoperability: - Grantley based ITE
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.02x11 Boot Code Version: 5.30a3 Supported On: System x and BladeCenter
Problems Fixed: - Roll boot code version number to avoid conflict with IBM UXSPi updates
Incremental Interoperability: - Inventory support for the System x xHMC (Chassis Hardware Management Console) for IBM Rack FC HBAs - Grantley Rack Servers
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.02x11 Boot Code Version: 5.13x4 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Server intermittently fails to boot during rolling SANboot (any OS) - Fixed a boot hang associated with server BIOS change
Incremental Interoperability: - Inventory support for the Flex xHMC (Chassis Hardware Management Console)
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.01a11 Boot Code Version: 5.12a13 Supported On: IBM System x and BladeCenter
Problems Fixed: - Emulex FC Adapter does not auto-enable SAN boot mode when boot target configuration is made via IFM (BOFM) - Emulex FC configuration utility is in the wrong F1 setup screen - IBM CIOv adapter connected to Brocade 8 Gig FC BladeCenter switch intermittently Links up at less than 8 Gig
Firmware Version 2.01a3 Boot Code Version: 5.12a5 Supported On: IBM System x and BladeCenter
Incremental Interoperability: - Enhanced timeout notifications for processing abort failures.
Problems Fixed: - All multi-abort I/Os are returned on the same ring from which the ABORT_MXRI command was received. - Changed the TRCV response in the abort state to CMD RJT to enable the TRSP to be processed. - Corrected an issue with blocked TSEND operations. - Corrected a buffer leak issue with RRQ exchanges. - Corrected an issue where the TRCV IOCB was de-queued improperly causing a XFR_RDY flood. - Corrected an issue where the OXID field was not loaded in the XRI_ABORTED IOCB. - Corrected an issue in recognizing whether an EEPROM is present.
Firmware Version: 11.2.209.19 Supported On: System x Rack and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support - Windows 2016 Support - VMware ESXi 6.5 Support
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 10.3.145.0 Supported On: System x Flex
Problems Fixed: - None
Incremental Interoperability: - Grantley based ITE
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 10.2.377.18 Supported On: System x
Problems Fixed: - Link does not recover during IO + Port Cycling with FW 1.1.43.3 - BIOS versions return multiple values - LPe16k point to point (direct attached) connection not bootable in legacy BIOS - LPe16k point to point (direct attached) connection performance issues in legacy BIOS
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 10.2.261.36 Supported On: IBM System x and Flex
Problems Fixed: - Server will halt on black screen during rolling reboot of Windows 2012 x64 uEFI SANboot - Server intermittently fails to boot during rolling SANboot (any OS) - Fixed a boot hang associated with server BIOS change - Reported firwmare version in CMM is intermittently incorrect - Unable to set pause Flow control when connected to DCBX switch with PFC off - during cable pull testing a 40 second delay in link up experienced with Brocade switch ports - I/O completion and abort completion WQE are generated out of order - Unexpected WCQE in RQ CQ seen in RXRI mode while performing cable pulls
Incremental Interoperability: - Inventory support for the Flex xHMC (Chassis Hardware Management Console) - Crosslink & Express Lane on LPe16k based solutions
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 1.1.43.21 Supported On: IBM System x
Incremental Interoperability: - None
Problems Fixed: - Server will halt on black screen during UEFI rolling reboot reboot cycle test with 16Gb HBA under Windows 2012 x64 - Allows installing and booting from an MSA2040 array configured in PT-PT direct mode at 16G speed. We're now able to enable Autoscan and install/boot from multiple OSes - Added support to bypass configuring pnp Boot Table in a multipath situation. Fixes Microsoft Windows Server 2008 bug. - Fixed the "Read Rev Failure" issue during POST to accept "0" address value as a valid. - Fixed the wrong VPD HBA model number display on the banner and properties, and change the proper VPD data field size. - Fixed the timeout issue on Flogi when try to select a HBA device without connecting to a target or FC switch. - System will halt during reboot cycle test under Windows 2012 x64 UEFI - Fixing PCI Function Number decoding issue in BOFM code - Boot fails during SLES11 SP3 rolling reboot - Enable BFS and update the NVRAM if BOFM target is available - Add Diagnostic support for UEFI 16Gb FC - Reconnect menu item causes a System BIOS exit request only on AMI core system BIOS - Adding port's protocol name and WWPN in browser help menu
Firmware Version: 1.1.43.12 Supported On: IBM System x and Flex
Incremental Interoperability: - IBM Flex System FC5052 2-port 16Gb FC Adapter - IBM Flex System FC5054 4-port 16Gb FC Adapter - FC support for support for ASU/Config Patterns for Flex and ASU for IBM System x & BladeCenter - Direct PT - PT connections - Extended SCSI Pass Thru Protocol - IBM Tape unit interoperability - see SSIC for more information - SLES 11.3 on IBM System x
Problems Fixed: - Windows 2012 OS will not resume from Sleep mode - Boot Device entries can be lost after exiting from BIOS setup
Firmware Version: 1.1.21.9 Supported On: IBM System x
Incremental Interoperability: - IBM Server machine types. Refer to IBM ServerProven for specifics
Problems Fixed: - Fixed FCP_CONF handling bug - No SRR sent after drop write data frame, I/O fails - Adapter does not invoke recovery after dropped read data frame - I/O throughput performance improvements - Link failover when connected to FC Tape - Cosmetic: Cleaned up miscellaneous error handling messages in debug log files - If a new device comes online and attempts to acquire an AL_PA after the link has already come up, the FC link appears to hang until the cable is pulled - Cleaned up link negotiation at 4GB/8GB/16GB speeds with specific switches
Multi-boot Image for 8Gb FC HBAs Release Notes version MB_4.10.05
This software license applies only to QLogic customers. QLogic Corporation. All rights reserved.
Table of Contents
1. Version 2. 8Gb BIOS 3. 8Gb EFI 4. 8Gb FCode 5. Trademarks 6. Notices 7. Contacting Support
1. Version
These release notes describe the changes, fixes, known issues, and release details that apply to the multi-boot package for 8Gb HBAs. This package is a compressed file that contains:
Kit Version 4.10.05
Q25A5410.BIN contains: ---------------- * BIOS version 3.31 * UEFI version 6.14 signed * Firmware version 8.03.00 FlasUtil version 1.89 VPD version 10.01a Efiutil version 3.17
BIOS:
Version 3.31 * Removed Beta Banner Version 3.31 Beta 2 * Added back Spin-up delay.(FOR DEBUG USE ONLY) (ER136488) * Fixed issue with OCSD (ER136720)
Version 3.31 Beta 1 * Fixed bug in setting pointer for NVRAM access. This * bug was created in version 3.30.
Version 3.30 * Removed Beta Banner Version 3.30 Beta 1 * Added code to check for CTRl-Q disabled(ER135448). * Added code to allow 4G data rate for 26xx(ER135693). * Added check for which copy of FW to use(Baker only). * Fixed issue with supporting 64bit Bar(ER136098).
Version 3.29 * Fixed issue causing MD2 CLP to fail (ER135507). Version 3.29 Beta 2 * Added code to fix CLP issue with 13G Dell system Version 3.29 Beta 1 * Fixed bug in displaying Execution Throttle in CTRL-Q utility correctly for 4/8G HBA. Version 3.28 * Removed Beta Banner Version 3.28 Beta 2 * Added coded to load/start FW for OCBB/OCSD only when BIOS is disabled Version 3.28 Beta 1 * Added support of Baker HBA
UEFI Driver:
6.14
* Fixed formatting problems in the HII WWN Database menu. The formatting problems only exist on older System X servers. (ER140666) * Microsoft signed driver.
========================================================================== Change History ==========================================================================
Kit Version 4.10.02
Q25A2410.BIN contains: ---------------- * BIOS version 3.27 * UEFI version 6.13 signed * Firmware version 8.03.00 FlasUtil version 1.89 VPD version 10.01a Efiutil version 3.17
UEFI Driver:
6.13
* Updated HII to support System X and AMI based servers. (ER137721) * Changed HII WWN Database behavior. The WWPN/LUN list is now created when the driver starts. This allows driver to run on AMI based servers. (ER137721) * Updated a few HII strings. (ER137721) * Fixed bug in UCM support. Callback flag now used to determine browser mode or UCM mode. (ER137721) * UCM WWN field is now a string. UCM did not properly support UINT64. (ER137721) * Microsoft signed driver.
Kit Version 3.11.06
Q25A6311.BIN contains: ---------------- * BIOS version 3.27 * UEFI version 6.12 signed * Firmware version 7.04.00 FlasUtil version 1.89 VPD version 10.01a Efiutil version 3.17
* Added code to not configure any targets when FA Boot LUN enabled but FA BOOT LUN not found. ER133769. * Added code to allow FA Boot LUN when FA WWPN enabled * Added options in CTRL-Q utility to enable FA WWPN and FA BOOT LUN. * Fix minor cosmetic error in display of Fcode/EFI versions for show port CLP.(ER133294) * Added support FA BOOT LUN * Added 8G support for show port clp * Changed VLAN ID max value from 4095 to 4094. * Removed spinup option from CTRL-Q. * Changed CTRL-Q to allow max value for Login Retry, * Port Down Retry, Link Down Count of 65535.ER(116099) * Removed Helga support * Added support for show port clp. * Remove EV boot order option from OEM BIOS. * Added CTRl_Q option to set VLAN_ID for FCoE HBA's(ER110593). * Changed Banner to display 'FCoE' for Schultz (ER110784). * Added additional time to login target when called * after EFI driver unloads. (ER110755,ER110855) * Added code to handle boot LUN Greater Than 255 (ER109195). * Added code to display message when 64 bit address is detected. * Removed port number from HII formset title. This fixes a UCM parsing issue. (ER134560).
Kit Version 3.11.01
Q25A1311.BIN contains: ---------------- * BIOS version 3.24 * UEFI version 6.10 * Firmware version 7.04.00 FlasUtil version 1.89 VPD version 10.01a Efiutil version 3.17
* Changed Banner to display 'FCoE' for Schultz (ER110784). * Added additional time to login target when called after EFI driver unloads. (ER110755,ER110855) * Added code to handle boot LUN Greater Than 255 (ER109195). * Added code to display message when 64 bit address is detected. * Added support for Execution Throttle for P3P (ER106372) * Added code to not display connection options for Hilda Trinity adapter. * Checked for invalid LUN in CTRL-Q scan devices.
========================================================================== Change History ==========================================================================
Kit Version 3.10.09
Q25A9310.BIN contains: ---------------- * BIOS version 3.24 * UEFI version 6.09 * Firmware version 7.02.00 FlasUtil version 1.89 VPD version 10.01 Efiutil version 3.17
1. Change History 2. Known Issues 3. Notices 4. Contacting Support
1. Change History
These release notes describe the changes, fixes, known issues, and release details that apply to the FC-FCoE BIOS version 3.24.
This section contains:
* 1.1 Version * 1.2 Changes * 1.3 Bug Fixes
1.1
Version 3.24 * Removed Beta Banner
Version 3.24 Beta 1 Changed Banner to display 'FCoE' for Schultz (ER110784). Added additional time to login target when called after EFI driver unloads. (ER110755,ER110855)
Version 3.23 * Removed Beta Banner
Version 3.23 Beta 2 Added code to handle boot LUN Greater Than 255 (ER109195).
Version 3.23 Beta 1 * Added support for Helga.
Version 3.22 * Added code to display message when 64 bit address is detected.
Version 3.21 * Removed Beta Banner
Version 3.21 Beta 1 * Added support for Execution Throttle for P3P (ER106372) * Added code to not display connection options for Hilda Trinity adapter. * Checked for invalid LUN in CTRL-Q scan devices.
Version 3.20 * Fixed bug in CTRL_Q utility that could cause some cosmetic display issues. * Added Hilda CLP _hss support. * Configured ISP24xx if on slot 0. * Added "QLogic" to PnP productid (ER104424) * Checked for 4G flag in NVRAM for Hilda FC.(ER104714)
Version 3.19 * Removed Beta Banner
Version 3.19 Beta 1 * Fixed bug with CTRL-Q Loopback Utility (ER100729).
Version 3.18 * Removed Beta Banner
Version 3.18 * Added code to check/program Feature Config checksum. * Fixed bug that could cause buffer overrun in CTRL-Q with Report Lun command (ER100294). * Added check for PCI address change when updating option card data structure.
Version 3.18 Beta 1 * Changed code to use 32 bit pointer to allocate/deallocate EBDA memory. * Added code to check/program Feature Config checksum.
Version 3.17 * Removed Beta Banner
Version 3.17 Beta 1 * Fixed cosmetic issue in displaying data rate in CTRL-Q
Version 3.16 * Changed text for 8300 series adapter External loopback (ER98690). * Fixed display issue with CTRL-Q Diskutility(ER98727) * Fixed Lun select issue with CTRL-Q (ER98675).
Version 3.15 * Removed Beta Banner
Version 3.14 Beta 3 * Fixed bug in displaying selectable boot lun (ER98226) * Removed 4G data rate option for OEM adapter (ER98228) * Limited leading '0's in CTRL-Q menu (ER98389). * Set 'Aggressive Cooling' flag for OCSD. * Enabled Personality Change option.
Version 3.14 Beta 2 * Fixed issue with not restoring defaults on port 1 (ER 97619) * Fixed issue with serdes data saved incorrectly. (ER 97654) * Added code to limit Report Lun List size to 256 luns Version 3.14 Beta 1 * Added check for 0 lun count when selecting device (ER 97385) Version 3.14 * Removed 'Beta' from banner Version 3.13 Beta 17 * Disabled Personality Change option in CTRL-Q. * Fixed bug with WWNN handling for MCTP.(ER 96920) Version 3.13 Beta 16 * Added check for Set MD2 set to 0 (restore defaults) (ER96912) * Added code to reset Port Config after Internal loopback test for 8300 series adapter(FCoE). Version 3.13 Beta 15 * Added support for 16 bit lun (ER96090). Version 3.13 Beta 14 * Added support for Set MD2 CLP string. Version 3.13 Beta 13 * Added code to issue Load Flash FW (3) MB command for 8300 series adapter as part ISP start sequence. (ER 94035). Version 3.13 Beta 12 * Fixed code to prevent async event from causing BIOS to hang when scanning for devices (ER94371). * Added check for Internal Loopback mode when connected to F-Port (ER71773). * Added check for 8300 series adapter FW Auto Load when re-initing ISP. * Version 3.13 Beta 11 * Fixed code to disable ALT+1 Hotkey (ER92844) . * Fixed CTRL-Q code mailbox timeout (ER92957). Version 3.12 Beta 10 * Added warning message in Personality change screen Version 3.12 Beta 9 * Updated BIOS to version 3.12 of non-8300 series adapter BIOS Version 3.12 Beta 8 * Updated 8300 series adapter BIOS code with version 3.11 fixes
Version 3.11 * Removed check for Virtual Address flag on Cold Boot.
Version 3.10 * Changed code to check for signature aaaaaaaah before* updating virtual mac address.
Version 3.09 * Changed code to ignore soft boot signature aaaaaaaah*
Version 3.08 * Added code to save device number in OCSD.
Version 3.07 * Added code to read cold boot register signature to determine when BIOS should update/restore virtual Mac address.
Version 3.06 * Fixed bug where retry count was not always being updated.
Version 3.05 * Added code to support ECHO loopback command.
Version 3.04 * Removed Beta from banner.
Version 3.04 Beta 4 * Fixed bug in clp_hss processing. * Updated some ETOC header data fields.
Version 3.04 Beta 3: * Changed code passing Sensor Data pointer
Version 3.04 Beta 2 * Added support for passing ETOC pointer. * Added support for posting port status for EFI use.
Version 3.04 Beta 1 * Added support for sensor data reporting.
Version 3.03 * Added support NCSI Flex Address.
Version 3.02 * Fixed bug in setting mailbox timeout for TUR.
Version 3.01 * Removed CTRL-Q Loopback test for P3P.
Version 3.00 * Removed Beta banner
Version Beta 14 * Added code to get serial number from VPD data for ISP2532. * Fixed bug in display loopback error status.
Version Beta 13 * Fixed bug in verifying FW for non-P3P HBA's. * Removed QLogic vendor id from BIOS banner. * Added retry for LLIOCB when status subcode is 4.
Version Beta 12 * Fixed bug in not setting up retry count for P3P.
Version Beta 11 * Added support for -LR option * Changed error message when no ISP Functions found.
Version Beta 10 * Added code to check for Wocket card.
Version Beta 9 * Fixed bug with not clearing P3 Async Event.
Version Beta 8 * Added additional check for P3 INIT Complete.
Version Beta 7 * Increased p3_busy_wait delay
1.2 Changes
The following changes have been made to the BIOS for FC-FCoE Adapters between versions 3.02 and 3.24.
* Changed Banner to display 'FCoE' for Schultz (ER110790). * Added additional time to login target when called * after EFI driver unloads. (ER110755.ER110855) * Added support for Helga. * Added code to display message when 64 bit address is detected. * Added support for Execution Throttle for P3P (ER106372) * Added code to not display connection options for Hilda Trinity adapter. * Checked for invalid LUN in CTRL-Q scan devices. * Fixed bug in CTRL_Q utility that could cause some cosmetic display issues. * Added Hilda CLP _hss support. * Configured ISP24xx if on slot 0. * Added "QLogic" to PnP productid (ER104424) * Checked for 4G flag in NVRAM for Hilda FC.(ER104714) * Fixed bug with CTRL-Q Loopback Utility (ER100729). * Added code to check/program Feature Config checksum. * Fixed bug that could cause buffer overrun in CTRL-Q with Report Lun command (ER100294). * Added check for PCI address change when updating option card data structure. * Changed code to use 32 bit pointer to allocate/deallocate EBDA memory. * Added code to check/program Feature Config checksum. * Fixed cosmetic issue in displaying data rate in CTRL-Q * Changed text for Hilda External loopback (ER98690). * Fixed display issue with CTRL-Q Diskutility(ER98727) * Fixed Lun select issue with CTRL-Q (ER98675). * Fixed bug in displaying selectable boot lun (ER98226) * Removed 4G data rate option for OEM adapter (ER98228) * Limited leading '0's in CTRL-Q menu (ER98389). * Set 'Aggressive Cooling' flag for OCSD. * Enabled Personality Change option. * Fixed issue with not restoring defaults on port 1 (ER 97619) * Fixed issue with serdes data saved incorrectly. (ER 97654) * Added code to limit Report Lun List size to 256 luns * Added check for 0 lun count when selecting device (ER 97385) * Disabled Personality Change option in CTRL-Q. * Fixed bug with WWNN handling for MCTP.(ER 96920) * Added check for Set MD2 set to 0 (restore defaults) (ER96912) * Added code to reset Port Config after Internal loopback test for Hilda(FCoE). * Added support for 16 bit lun (er96090). * Add support for Set MD2 CLP string. * Added code to issue Load Flash FW (3) MB command for Hilda as part ISP start sequence. (ER 94035). * Fixed code to prevent async event from causing BIOS to hang when scanning for devices (er94371). * Fixed code to disable ALT+1 Hotkey (er92844) . * Fixed CTRL-Q code mailbox timeout (er92957). * Added warning message in Personality change screen. * Updated BIOS to version 3.12 of non-hilda BIOS * Removed check for Virtual Address on Cold Boot. * Changed code to check for signature aaaaaaaah before updating virtual mac address. * Changed code to ignore soft boot signature aaaaaaaah * Added code to save device number in OCSD. * Added code to read cold boot register signature to determine when BIOS should update/restore virtual Mac address. * Fixed bug where retry count was not always being updated. * Added code to support ECHO loopback command. * Added support NCSI Flex Address.
1.3 Bug Fixes
The following fixes have been made to the BIOS for FC-FCoE Adapters between versions 3.00 Beta 7 and 3.24.
* Changed Banner to display 'FCoE' for Schultz (ER110790). * Added additional time to login target when called * after EFI driver unloads. (ER110755.ER110855) * Added code to handle boot LUN Greater Than 255 (ER109195). * Checked for invalid LUN in CTRL-Q scan devices. * Fixed bug in CTRL_Q utility that could cause some cosmetic display issues. * Added Hilda CLP _hss support. * Configured ISP24xx if on slot 0. * Added "QLogic" to PnP productid (ER104424) * Checked for 4G flag in NVRAM for Hilda FC.(ER104714) * Fixed bug with CTRL-Q Loopback Utility (ER100729). * Added code to check/program Feature Config checksum. * Fixed bug that could cause buffer overrun in CTRL-Q with Report Lun command (ER100294). * Added check for PCI address change when updating option card data structure. * Changed code to use 32 bit pointer to allocate/deallocate EBDA memory. * Added code to check/program Feature Config checksum. * Fixed cosmetic issue in displaying data rate in CTRL-Q * Changed text for Hilda External loopback (ER98690). * Fixed display issue with CTRL-Q Diskutility(ER98727) * Fixed Lun select issue with CTRL-Q (ER98675). * Fixed bug in displaying selectable boot lun (ER98226) * Removed 4G data rate option for OEM adapter (ER98228) * Limitleading '0's in CTRL-Q menu (ER98389). * Set 'Aggressive Cooling' flag for OCSD. * Fixed issue with not restoring defaults on port 1 (ER 97619) * Fixed issue with serdes data saved incorrectly. (ER 97654) * Added code to limit Report Lun List size to 256 luns * Added check for 0 lun count when selecting device (ER 97385) * Disabled Personality Change option in CTRL-Q. * Fixed bug with WWNN handling for MCTP.(ER 96920) * Added check for Set MD2 set to 0 (restore defaults) (ER96912) * Added support for 16 bit lun (er96090). * Add support for Set MD2 CLP string. * Added code to issue Load Flash FW (3) MB command for Hilda as part ISP start sequence. (ER 94035). * Fixed code to prevent async event from causing BIOS to hang when scanning for devices (er94371). * Fixed code to disable ALT+1 Hotkey (er92844) . * Fixed CTRL-Q code mailbox timeout (er92957). * Added warning message in Personality change screen. * Updated BIOS to version 3.12 of non-hilda BIOS * Removed check for Virtual Address on Cold Boot. * Changed code to check for signature aaaaaaaah before updating virtual mac address. * Changed code to ignore soft boot signature aaaaaaaah * Added code to save device number in OCSD. * Added code to read cold boot register signature to determine when BIOS should update/restore virtual Mac address. * Fixed bug where retry count was not always being updated. * Added code to support ECHO loopback command. * Fixed bug in clp_hss processing. * Updated some ETOC header data fields. * Changed code passing Sensor data pointer * Added support for passing ETOC pointer. * Added support for posting port status for EFI use. * Added support for sensor data reporting. * Added support NCSI Flex Address. * Fixed bug in setting mailbox timeout for TUR. * Increased p3_busy_wait delay * Added additional check for P3 INIT Complete. * Fixed bug with not clearing P3 Async Event. * Added code to check for Wocket card. * Added support for -LR option * Changed error message when no ISP Functions found. * Fixed bug in not setting up retry count for P3P. * Fixed bug in verifying FW for non-P3P HBA's. * Removed QLogic vendor id from BIOS banner. * Added retry for LLIOCB when status subcode is 4. * Added code to get serial number from VDP data for ISP2532. * Fixed bug in display loopback error status. * Fixed bug in setting mailbox timeout for TUR.
2. Known Issues
None
3. Notices
Information furnished in this document is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are only for illustrative purposes. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.
4. Contacting Support
For further assistance, contact QLogic Technical Support at: http://support.qlogic.com
Trademarks
Accelera, Accelerating Cluster Performance, InfiniCon Systems, InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo, ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
(c) Copyright 2014. All rights reserved worldwide. QLogic and the QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
1. Change History 2. Known Issues 3. Notices 4. Contacting Support
1. Changes History
UEFI Driver:
6.11
* AIM Fcode info. is now hidden if the option ROM does not contain Fcode. (ER133730) * Fixed errors in AIM UUID and AIM Serial Number info. (ER133802)
6.10
* Added default UUID support. (ER133286) * Added N/A for undefined vpd fields. (ER133286) * Added v1.28 AIM spec. changes. (ER133286) * Changed a few field sizes to match the AIM spec. (ER133286)
6.09
* Added AIM support for 8G standup cards. (ER132095) * Changes in place to reduce image size. Image binary is now X64. (ER132119)
6.08
* Added fix to hide or list HII elements selectively. (ER116233)
6.07
* Updated to get PN & Card SKU dynamically from I2C VPD for AIM. (ER116141) * Corrected help text string. (ER115814)
6.06
* Updated MTU size and AIM version references as per revised requirement. (ER113361)
6.05
* Updated AIM config strings as per revised requirements. (ER113361)
6.04
* Update AIM support as per revised requirements. (ER113361) * Added fix for boot settings persistency issue in BOFM supported legacy BIOS. (ER112641)
6.03
* Added support for IBM AIM. (ER113428)
6.02
* Added fix to persist user changes made on static forms. (ER112639) * Added feature to dynamically list targets in HII. (ER105725) * EDKII Successor of older tiano/EDKI driver ver 2.51. (07/17/13)
Efiutil:
3.17
* Add fix for 25xx ver_info command. (ER104543)
3.16
* Removed hardcoded subsystem id check. (ER0103883) * Replaced with MBI image traverse for ssid match. (ER0103883)
3.15
* Fixed ambiguity in firmware version display. (ER0103456)
2. Known Issues
* Dynamic target listing in HII requires UEFI 2.3 or later system compliance. * Efiutil does not support the 2.0 Shell. Please load the 1.0 Shell before running Efiutil.
3. Notices
Information furnished in this document is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are only for illustrative purposes. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.
4. Contacting Support
For further assistance, contact QLogic Technical Support at: http://support.qlogic.com
Trademarks
Accelera, Accelerating Cluster Performance, InfiniCon Systems, InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo, ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
(c) Copyright 2017. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
qlgc_fw_fc_8g-mb4_10_05_c_linux_32-64_chg
BIOS/FW/UEFI Update for IBM N2125 SAS/SATA Controller
Controller Supported: IBM N2125 SAS/SATA Controller (46C9011)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 1.20.01 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 07.39.00.00 20.00.02.00 07.27.04.00
Enhancements: - Added System X agentless support - Indicate support for the ATA Device Server Password security protocol - Allow UEFI and BIOS to be Enabled/Disabled individually - Added ConnectorName and EnclosureLevel fields to SAS Device Page 0 to help identify physical location of a target device - Set SATA HOLD threshold to be configurable in NVDATA - If HW can gets into a stuck state, clear that state upon break received.
Fixes: - Set SAS drives to track bad blocks using a bad block table rather than using a SCSI Write Long. - Fixed DMAGroup performance issue. - Fixed issue with Phase 18 IR FW boot a RAID volume (such as raid 10), 2308 bootup hangs at OROM "Initializing.." and fault 8803 seen. - Fixed report Luns command to a SATA drive fails with CheckCondition/Invalid Field in CDB when Allocation length set to Zero. - Fixed issue where Raid Accelerator IOs can hang if the stream of IOs suddenly stops. - Fixed issue where an invalid frame sent during a PIO-mode SATA passthrough command results in resetting the drive. - Fixed issue where lots of NCQ I/O error messages were reported. - Fixed issue where certain PCIe timeouts occur in the presence of link unavailable, and a hang condition or data corruption can occur. - Fixed issue where system hangs after adapter reset with heavy IO load. - Fixed issue where access to Last Logical Block Address (LBA) of SATA Drive is Prevented and LBA out Of range by one block is missed. - Made change to deal with link getting stuck and causing missing drives. - Fixed IR issue where page header information is not filled in when RAID PHYS DISK PAGE 0 is returned for a non-RAID Disk drive. - Fixed issue where controller hits 0x265d fault while creating volume when there is an inactive volume. - DID_SOFT_ERRORs are seen when hot plug is performed on the RAID1 volume along with IOs. - Fixed issue where system gets hung and reboots while running IO's along with diag reset on the Controller which has active and inactive volumes. - Fixed latency spikes seen during performance testing on OEM system - MPI 2.5: distribute target command buffers received across multiple reply queues. - Fixed issue where command sas2flash -dflash results in a non-functional system. - Fixed issue where internal device reset storm after controller reset using long CDB. - Fixed 0x6003 Fault Due to Task Management of Lost IO - Fixed 0x58A1 fault occurs on partner controller while issuing MUR to a target mode controller with outstanding IOs. - Fixed issue where IO error and stop when hot plug a HDD from RAID1 - Fixed issue where fault 8901 is seen once the volume is roamed.
Enhancement - Reduce the boot time for UEFI driver for large configurations Fixes: - Fixed an issue that caused the Integrated Management Module (iMM) in System x servers to report Warning: Sensor GPT Status has transitioned from normal to non-critical state. - Fixed an issue where 4k sector size drives with 512e reporting enabled show wrong physical size when running a read capacity 16 command. - Fixed an issue where speed negotiation for 3Gig SATA drives is not handled properly. - Added Support for Report Luns Command - Fixed an issue where OS hang during install of Linux system to a SSD - Fixed an issue where SAS device page 0 may still be present for Initiator devices that have been removed from the topology. - Fixed an issue where RHEL 6.3 hangs during boot with IBM 600GB High IOPS MLC Modular Adapter - Fixed an issue where a non-PI volume made up of all PI capable drives, may come up as PI enabled after a controller reset. - Fixed an issue where a fault 0X8808 occurs when a reset is issued to the controller that has max number of active/inactive volumes - Fixed an issue where "Device Present" Flag of SAS device page0 is not set for initiator controller in then target controller when two controllers are connected to each other in initiator/target mode. - Fixed an issue where extended tags and PCIe upconfigure capability are disabled in SAS2208 and SAS2308. - Fixed an issue where force full discovery does not trigger rediscovery of an expander after the initial expander discovery fails. - Fixed an issue where single RAID0 volume activation was succeeding, even though controller does not support single drive RAID0. - Fixed an issue where RAID1 volume of Non-PI drives moves to optimal state when a PI drive is hotplugged and 'Enable PI mixing' not enabled. - Fixed an issue where Locate LED's stop automatically after 3-4 minutes before user issues command to turn off the Locate LED's. - Fixed an issue where fault 0x8618 is seen when a new volume is created in the presence of another volume which is undergoing resync along with IO. - Fixed an issue background initialization does not start on RAID0 volume with PI drives, after removing and reinserting a volume member.
BIOS - Fixed an issue where core BIOS displays warning message when it fails to add all of the drives connected to int13 chain, then waits for user to press any key to continue further, rather than continuing after 3 seconds. - Fixed an issue where incorrect adapter is being tagged as the first adapter found. - Fixed an issue where the save or discard changes prompt appears after a failed attempt to set volume as the boot device in BIOS CU. - Fixed an issue where BIOS CU provides incorrect device pointer when checking for raid disk to allow/disallow setting boot device. - Fixed an issue where device properties screen is invoked from a direct attach device using Alt+D in SAS topology screen, device traversing [Alt+N & Alt+P] is restricted within the direct attach device and expander attach devices are not traversed. - Fixed an issue where the drive status field does not show 'Max dsks' when trying to select 11th drive for RAID10 volume. - Fixed an issue maximum Int13 devices settings does not get honored, when the value is set as 0 in BIOS CU - Fixed an issue where drive size of 1.088GiB was showing as 1.880GiB. - Fixed an issue current boot device set to device at slot 4" message Not displaying for Adaptors with boot order other than 0. - Fixed an issue where the BIOS CU navigates to create new volume screen instead of back to raid properties screen. - Fixed an issue where BIOS banner showed 'FF' for slot information. - Fixed an issue where the drive's SMART status is always shown as no irrespective of drive's SMART status, under Pred Fail column of the manage hot spare screen and create new volume screen. - Fixed an issue where SAS2 BIOS: volume size shows inconsistent value in the create new volume' screen after selecting the last volume member. - Fixed an issue where a disabled adapter causes the second adapter status to show as unavailable even though the second adapter is enabled. Uefi Enhancement 1/2 - Added capability to create an IR RAID volume in non-PI mode, even when all member drives are PI Capable. - Added PI info and ability to control creation of PI Volume in UCM of BSD HII. - Added new form manage PHY settings to support enabling or disabling of a controller PH Fixes: - Fixed an issue view foreign volume option is disabled with a foreign volume in the configuration.
- Fixed issue where acceptable indistro device drivers may not pass minium driver check. ibm_fw_mpt2sas_n2125-1_20_01_linux_32-64_chg
============================ R E L E A S E N O T E S ============================
Broadcom Linux bnx2 and 10GigE Virtual Bus Drivers(VBD)
Version 2.2.5r 04/20/2016 Copyright (c) 2016 Lenovo Corporation All rights reserved
NOTE: These driver release information is the original from the vendor. They include multiple driver change histories for multiple Linux Operating Systems. Some drivers may or may not pertain to all Linux Operating Systems but are part of this file for references.
Fixes: ------ 1. Problem: BZ1300681 [RH] - Parity recovery under traffic is very long.
Change: Don't wait for Tx completions on recovery.
Introduced: Day 1.
Relevance: All.
bnx2fc ====== Version 2.10.3 (March 23, 2016): ================================
Fixes & Features ================
1. Problem: Cont00085342 - host reboots while running interop Cause: Try to return a request back to the SCSI layer that was already offlined. Change: Check
1. Change: Add the interfaces to get FC-NPIV table
Impact: N/A
bnx2 2.2.5m (January 20, 2015) ================================ Enhancements ----- 1. Change: Merge re-branding changes to the main branch.
Impact: N/A
Fixes -----
1. Problem: Out of memory issue when the adapter is reset. This was reported by a customer.
Cause: kmalloc() failure in bnx2_gunzip_init() during memory fragmentation conditions (~40K contiguous physical memory is not available).
Change: Use vmalloc() instead of kmalloc() for uncompressing the firmware buffer.
2. Problem: UDP packets cannot pass to the upper application, packets are filtered out by our driver or firmware.
Cause: SORT mode was enabled in the code to fix a WOL issue on adapter series 5706/5708.
Change: We have found that disabling SORT mode in chip_init routine fixes the issue reported. We have verified WOL is functioning on 5709/5716 adapters after disabling SORT mode in chip_init.
cnic 2.5.20e (January 20, 2015) ============================ Enhancements ------------ 1. Change: Merge re-branding changes to the main branch.
1. Problem: Fix compilation warnings in newer kernels due to changes introduced in RHEL6.6 support.
Cause: Warnings due to incompatible pointer type initialization because netdev_features_t is 64-bits in newer kernels whereas in RHEL6.6 kernel it is defined to 32-bit.
Change: Change Makefile to look for netdev_features.h to define netdev_features_t as appropriate. Also added check to prevent calling set_netdev_ops_ext() API since kernel expects not to mix ndo_fix_features/ndo_set_features with ethtool_ops.
Cause: Rearrangement of new hw_features flag with the introduction of new structure net_device_ops_ext and APIs and multiple redefinitions.
Change: Added checks to avoid multiple redefinitions of APIs. The features and hw_features are assigned and get_netdev_hw_features() and set_netdev_hw_features() for RHEL6.6 specific checks.
2. Problem: Fix netdev features for newer kernels.
Cause: hw_features in netdev for newer kernels was not getting set.
Change: hw_features field in nedev needs to be set for user selectable features. Added NETIF_F_RXCSUM flag in hw_features and features field of netdev to change rx checksum using ethtool.
Impact: Added support for RHEL6.6 and newer kernel.
bnx2 2.2.5jr (August 21, 2014) =========================== Enhancements ----- 1. Change: As part of re-branding Linux bnx2 driver, removed NetXtreme II/NX2/Nx2 keywords
Impact: N/A
cnic 2.5.20dr (August 21, 2014) ============================ Enhancements ------------ 1. Change: As part of re-branding Linux cnic driver, removed NetXtreme II/NX2/Nx2 keywords
Impact: N/A
bnx2 2.2.5ir (July 30, 2014) =========================== Enhancements ----- 1. Change: Added re-branding changes for Linux bnx2 driver
Impact: N/A
cnic 2.5.20cr (July 30, 2014) ============================ Enhancements ------------ 1. Change: Added re-branding changes for Linux cnic driver
bnx2 2.2.5i (July 22, 2014) =========================== Enhancements ------------ 1. Change: (CQ74921)Revert changes for Broadcom re-branding for Linux bnx2 & cnic OOB drivers
Impact: N/A
cnic 2.5.20b (July 22, 2014) ============================ Enhancements ------------ 1. Change: (CQ74921)Revert changes for Broadcom re-branding for Linux bnx2 & cnic OOB drivers
Impact: N/A
2. Change: Added upstream patch to sync up with upstream driver cnic,bnx2i,bnx2fc: Fix inconsistent use of page size
The bnx2/bnx2x rings are made up of linked pages. However there is an upper limit on the page size as some the page size settings are 16-bit in the hardware/firmware interface. In the current code, Some parts use BNX2_PAGE_SIZE which has a 16K upper limit and some parts use PAGE_SIZE. On archs with >= 64K PAGE_SIZE, it generates some compile warnings. Define a new CNIC_PAGE_SZIE which has an upper limit of 16K and use it consistently in all relevant parts.
Impact: FCoE, iSCSI
Fixes -----
1. Problem: (CQ74840) Compilation Error in cnic driver for RHEL 6.3 and SLES 11.1
Cause: Undefined rcu_access_pointer in RHEL 6.3 and SLES 11.1
Change: cnic need to use rcu_access_pointer to obtain the object reference but this routine is not defined in older RHEL and SLES distros. Added call to rcu_access_pointer using macro for RHEL 6.3 and SLES 11.1
Impact: iSCSI and FCoE
2. Problem: Compilation failure in cnic driver for RHEL 6.5
Cause: Undefined enum _DEFINE_SKB_SET_HASH and skb_set_hash() in RHEL 6.5.
CNIC driver includes bnx2x.h header file. There were some changes made in bnx2x driver using enum _DEFINE_SKB_SET_HASH and skb_set_hash() API. As a result of this change the cnic build failed due to those missing definitions.
Change: Added enum _DEFINE_SKB_SET_HASH and skb_set_hash() in bnx2_compat.h under a new define D_DEFINE_SKB_SET_HASH. In the Makefile, add a rule to check if skb_set_hash() is defined in skbuff.h. If not, then D_DEFINE_SKB_SET_HASH is added to the EXTRA_CFLAGS which would pickup the definitions from bnx2_compat.h.
Impact: bnx2, iSCSI and FCoE
3. Problem: (CQ74942)Kernel panic on CNIC driver load on sles12
Cause: Bug in kernel version code check
Change: Use proper version check macro
Impact: bnx2, iSCSI and FCoE on sles12
bnx2 2.2.5h (June 24, 2014) =========================== Enhancements ----- 1. Change: (CQ74364)Re-branding for Linux bnx2 driver
Impact: N/A
cnic 2.5.19e (June 24, 2014) ============================ Enhancements ------------ 1. Change: (CQ74364)Re-branding for Linux cnic driver
Impact: N/A
package 2.710.52 (June 18, 2014) ============================ Fixes ----- 1. Problem: cnic module does not compile on Xen/REHL5 kernels
Cause: rcu_access_pointer macro is not part of Xen/RHEL5 kernels.
Change: (CQ74100) Define the macro rcu_access_pointer in the driver code if required.
Impact: Xen/REHL5 kernels
2. Problem: (CQ74192) bnx2.c:4387: warning: assignment discards qualifiers from pointer target type
cnic 2.5.19d (June 11, 2014) ============================ Enhancements ------------ 1. Change: (CQ74187) Use proper netdev API for abstracting netdev upon receiving any netdev event
Impact: N/A
Fixes -----
1. Problem: (CQ73766, RHEL BZ1079384) bnx2fc: kernel BUG: sleeping function called from invalid context
Cause: cnic_rcv_netevent() calls ulp_ops->indicate_netevent() under a rcu_read_lock(), that makes the context atomic and bnx2fc_indicate_netevent() takes a mutex. Hence the sleeping-in-atomic causing call trace.
Change: Because the called function, such as bnx2fc_indicate_netevent(), can sleep, we cannot take rcu_lock(). To prevent the rcu protected ulp_ops from going away, we use the cnic_lock mutex and set the ULP_F_CALL_PENDING flag. The code already waits for ULP_F_CALL_PENDING flag to clear in cnic_unregister_device().
Impact: FCoE
2. Problem: (CQ73766, RHEL BZ1094613) ifdown/ifup repeatedly on a fcoe interface causes call trace in cnic_alloc_uio_rings
Cause: We are allocating memory with GFP_KERNEL under spinlock.
Change: Don't take cnic_dev_lock in cnic_alloc_uio_rings(). Since this is the only call manipulating the cnic_udev_list and it is always under rtnl_lock, cnic_dev_lock can be safely removed.
Change: The iSCSI netlink message needs to be sent before the ulp_ops is cleared as it is sent through a function pointer in the ulp_ops. This bug causes iscsid to not get the message when the bnx2i driver is unloaded.
Impact: iSCSI
4. Problem: (CQ74100/BZ1087813) suspicious RCU usage in cnic driver
Cause: Calling rcu_dereference without rcu_read_lock.
Change: cnic need to access the object protected using rcu lock. If rcu_dereference is called without proper read_rcu_lock, RCU debug print stack with suspicious lock issue. If there is a need to access the object without read lock rcu_access_pointer need to be used instead.
Impact: iSCSI and FCoE
cnic 2.5.19c (May 14, 2014) ============================ Enhancements ------------ 1. Change: Added support for UFP FCOE
Impact: FCoE in UFP mode only.
Fixes ----- 1. Problem: (CQ73854)No LUNs discovered in UFP mode, (CQ73853)Kernel stack trace at scsi_eh_2 in UFP mode, (CQ73820)bnx2x driver asserted with driver v7.10.35
Cause: FCP command is going out with VLAN ID 0 (Null VLAN ID). The VLAN tag was missing from the FCP packet as VLAN flag was set to zero in offload_connection and enable_connection ramrods.
Change: vlan_flag in the fcoe_kwqe_conn_offload3 should be set to 1 before sending offload_connection and enable_connection ramrods. Removed code block clearing vlan_flag in fcoe_kwqe_conn_offload3 before calling offload_connection in UFP mode.
Impact: FCoE in UFP mode only.
cnic 2.5.19b (Mar 05, 2014) ============================ Enhancements ------------ 1. Change: Add support for FCoE in UFP mode according to the UFP HSI. The support is transparent to bnx2fc.
Impact: FCoE in UFP mode only.
package 2.710.10 (Feb 25, 2013) =============================== Fixes ----- 1. Problem: Package does not compile on newer kernels
Cause: kernel compatibility issue.
Change: Added new CFLAGS from bnx2x Makefile for bnx2x_compat.h.
Impact: Newer distributions such as RHEL7.
bnx2 2.2.5f (Feb 20, 2014) =========================== Fixes ----- 1. Problem: (CQ72407) "shutdown -h now" causes NMI on 5709 in some scenarios.
Cause: If the function has not been brought up (ifup), system shutdown will cause a WAIT3 and D3 sequence without prior chip reset. This may cause the firmware to power down the PHY which will cause the function to become unresponsive to MMIO reads. The CPU will timeout and NMI as a result.
Change: Added some logic to tell firmware to skip the PHY power down.
Impact: 5709 only. Only ifdown and system shutdown sequences are affected. No run-time impact.
bnx2 2.2.5e (Feb 05, 2014) =========================== Enhancements ------------ 1. Change: Indication if the driver is beta or release in a printk upon firmware dump.
Impact: ESX only.
cnic 2.5.18d (Feb 05, 2014) ============================ Fixes ----- 1. Problem: (CQ72694) Crash in bnx2x_cnic_notify() when getting iSCSI statistics.
Cause: Calling bnx2i_get_stats() after bnx2i has unregistered the device.
Change: cnic should use the per device RCU protected cp->ulp_ops[] when making the upcall to get statistics. It was incorrectly using the global cnic_ulp_tbl which is always valid even if individual devices have been unregistered.
Impact: iSCSI and FCoE
bnx2 2.2.5d (Jan 14, 2014) =========================== Fixes ----- 1. Problem: (CQ71941) Kernel panic when loading bnx2 driver on RHEL6.5 with inbox cnic driver loaded.
Cause: Incompatibility with inbox cnic driver.
Change: Added padding in bnx2 structure so that the inbox cnic driver will always detect NULL in the cnic_probe field.
Impact: RHEL6.5 and newer kernels (SLES11SP3 is not affected)
bnx2 2.2.5c (Jan 06, 2014) =========================== Enhancements ------------ 1. Change: Added ability to read PCI config registers and indirect memory via the ESX private IOCTL.
Impact: bnx2 ESX only.
2. Change: Add reporting of MDI/MDIX status to ethtool.
Impact: Copper devices only.
bnx2 2.2.5b (Nov 18, 2013) =========================== Fixes ----- 1. Problem: (CQ71793) 5709 sometimes does not link up in 100Mbps forced speed.
Cause: PHY advertisement register needs to be set to 0 when speed is forced. The default advertisement register value is 10 Mbps and it will not link up when the speed is 100 Mbps.
Change: Set advertisement register to 0 when speed is forced.
Impact: 5709C forced speed.
bnx2 2.2.4g (Nov 07, 2013) =========================== Fixes ----- 1. Problem: PHY loopback test fails when set to 100Mbps on 5708 Copper.
Cause: Regression caused by enabling auto-MDIX (PHY reg 0x18 shadow 7 bit 9).
Change: Disable it on 5708.
Impact: 5708 only.
bnx2 2.2.4f (Oct 29, 2013) =========================== Fixes ----- 1. Problem: Netqueue didn't get stop and re-initialized properly during reset task, change coalece setting, and self test operations.
Cause: Normal Netqueue stop and re-initialized operations weren't executed while the device went through a full reset.
change: Added proper Netqueue stop/start operations in the above code paths.
Impact: ESX only.
cnic 2.5.18c (Oct 29, 2013) ============================ Enhancements ------------ 1. Change: Add signature to the iSCSI TX doorbell to prevent iscsiuio from getting the wrong value when using older kernel drivers.
Impact: bnx2x iSCSI only.
bnx2 2.2.4e (Oct 23, 2013) ============================ Enhancements ------------ 1. Change: (CQ69514) Enable auto-MDIX when autoneg is disabled by setting copper PHY register 0x18 shadow 7 bit 9.
Impact: All bnx2 copper devices.
2. Change: Display driver version in vmkernel.log during ESX fw dump.
Impact: ESX only.
package 2.78.33 (Sept 23, 2013) =============================== Fixes ----- 1. Problem: Package does not compile on Xen Server 6.2
Cause: kernel compatibility issue.
Change: Added new CFLAGS from bnx2x Makefile for bnx2x_compat.h.
Impact: All distributions. These fixes are only compatible with bnx2x 1.78.56 and newer.
bnx2 2.2.4d (Sept 12, 2013) ============================ Fixes ----- 1. Problem: cnic irq failed to run after esxcli network nic down/up event.
Cause: esxcli network nic down/up event causes bnx2 driver go through bnx2_close and bnx2_open. The sequence of events will re-allocate status block memory and the new status block memory address is not communicated to cnic after bnx2_open.
Impact: bnx2 ESX only.
cnic 2.5.18b (Sept 12, 2013) ============================ Fixes ----- 1. Problem: iSCSI does not work with bnx2x 1.78.52.
Cause: bnx2x doorbell change not compatible with existing iscsiuio.
Change: Pass modified iSCSI CID to iscsiuio for backwards compatibility.
Impact: bnx2x iSCSI.
2. Problem: Panic in cnic after ifdown/ifup bnx2x iSCSI device.
Cause: Accessing uninitialized FCoE EQ. Bug introduced in 2.5.17c which started using bnx2x NO_FCOE macro. cnic did not consistently use NO_FCOE, causing FCoE EQ to be accessed by mistake.
Change: Use NO_FCOE macro consistently in cnic code.
Impact: FCoE.
bnx2 2.2.4c (Aug 30, 2013) ============================ Enhancements ------------ 1. Change: Fix compile errors see on ESX * struct chip_core_dmp definition conflicts with bnx2x, scoped this struct to have a bnx2 prefix * Compiled FW dump for ESX5.5
Impact: bnx2 ESX only.
cnic 2.5.17c (Aug 30, 2013) ============================ Fixes ----- 1. Problem: cnic crash when shutting down 57811 device.
Cause: 57811 Chip ID not reconized by cnic.
Change: Re-structured code to use common bnx2x macros for Chip ID, port ID, pfid.
Impact: iSCSI and FCoE on all bnx2x devices.
bnx2 2.2.4b (Aug 12, 2013) ============================ Fixes ----- 1. Problem: CQ70286 IOVP: PSOD while executing NIC up/down command using esxcli.
Cause: New bnx2_free_irq() also disable MSIX/MSI on the device during bnx2_close. When bnx2_open is called, driver attempt to get INTA interrupt instead of MSIX/MSI interrupt.
Change: Don't disable MSIX/MSI on the device upon close.
Impact: ESX only.
2. Problem: WoL does not work during suspend if device is not up.
Cause: WoL setup skipped in bnx2_suspend() if device is not up.
Change: Always setup WoL in bnx2_suspend().
Impact: bnx2 suspend.
Enhancements ------------ 1. Change: Update 5709 firmware to 6.2.1.c to include mechanism to flush the iscsi OOO ring to silence some error messages about stale hardware index.
Impact: iSCSI on these bnx2x devices where the iSCSI license can only be fully determined after firmware is loaded.
2. Change: Changes to match the new 5709 6.2.1.c firmware to flush the iSCSI OOO ring.
Impact: 5709 iSCSI.
bnx2 2.2.3t (July 23, 2013) ============================ Fixes ----- 1. Problem: CQ70262 IVOP: PSOD HeavyIOChangeMTU test on 5709 card.
Cause: During ring size change, bnx2_free_irq() was called without checking reset_irq flag.
Change: Don't call bnx2_free_irq() if reset_irq flag is false.
Impact: ESX only.
2. Problem: (CQ69619) ethtool NVRAM operations fail when device is down.
Cause: Driver checks and prevents NVRAM operations when device is down.
Change: Remove the check. The driver now stays in D0 power state when the device is down and NVRAM operations are possible.
Impact: ethtool -e|-E
cnic 2.5.16j (July 23, 2013) ============================= Fixes ----- 1. Problem: (RHEL BZ 759217) System hangs when attempting iSCSI connections on 57711E.
Cause: iSCSI license changes from supported to unsupported between bnx2x probe and bnx2x open. bnx2i is unaware that the device does not support iSCSI and attempts to do offload which never completes. The recent change to eliminate symbol_get() to obtain bnx2x_cnic_probe() exposed the problem.
Change: Check iSCSI license again during ->drv_register_cnic(). If there is no iSCSI license, skip ->ulp_start().
Impact: iSCSI on these bnx2x devices where the iSCSI license can only be fully determined after firmware is loaded.
bnx2 2.2.3s (June 27, 2013) ============================ Fixes ----- 1. Problem: PCI shutdown function does not work on ESX.
Cause: system_state and SYSTEM_POWER_OFF not defined.
Change: Added compatibility code.
Impact: ESX only.
bnx2 2.2.3r (June 27, 2013) ============================ Enhancements ------------ 1. Change: (CQ68271, 68277) In order to support ethtool NVRAM operations when the device is down, the following changes were made:
- converted to use new WoL and PM kernel APIs - removed power state changes during open and close - added pci shutdown function to setup WoL during shutdown - converted to new style suspend/resume driver APIs
Impact: Everything related to WoL, shutdown, suspend, resume. Because of the significant changes, the system should be rebooted after running "make install" for the new driver. Without reboot, the new driver may not work as it is not aware that the older driver has put the device into D3hot state.
bnx2 2.2.3q (May 24, 2013) ============================ Enhancements ------------ 1. Change: Simplified compatibility code for driver section macros, __devinit, __devexit, etc.
Impact: None.
bnx2 2.2.3p (May 23, 2013) ============================ Fixes ----- 1. Problem: Bootcode firmware may not detect new message from driver. (VMWare reported issue)
Cause: The initial sequence number may not be unique enough.
Change: Read from the firmware mailbox and add one to it as the initial sequence number.
Impact: All devices.
Enhancements ------------ 1. Change: Made changes to compile on the latest 3.x kernels.
Impact: All.
cnic 2.5.16i (May 23, 2013) ============================= Fixes ----- 1. Problem: (CQ69177) MTU change causes PSOD at bnx2x_drv_ctl
Cause: The OOO handler was falsely triggered to handle OOO tx completions even when bnx2x has failed to allocate resources for the OOO ring. This has caused bnx2x to hit a NULL ptr dereference.
Change: Fixed the cnic OOO handler.
Impact: bnx2x iSCSI only.
cnic 2.5.16h (April 30, 2013) ============================= Enhancements ------------ 1. Change: Added max_fcoe_exchanges parameter so that bnx2fc can support multiple FCoE ports on a device.
Impact: FcoE only.
bnx2 2.2.3o (April 30, 2013) ============================ Fixes ----- 1. Problem: (BDKL225) __napi_schedule assertion when bnx2 switch from MSI to INTx.
Cause: NAPI was not disabled before IRQ is freed when switching from msi mode to INTA mode which prevents VMkernel from updating the stale napi->intr_cookie value.
Change: Disabled NAPI before free IRQ and then re-enable NAPI after chip is re-initialized. In addition, enabling of NAPI should always be done after chip_init().
Impact: All.
bnx2 2.2.3n (Mar 11, 2013) ========================== cnic 2.5.16g (Mar 11, 2013) ========================== Fixes ----- 1. Problem: cnic driver does not compile on XEN server.
Cause: Shared bnx2x_compat.h relies on some CFLAGs to compile properly on XEN server.
Cause: Firmware bug and cnic error handling bug for TCP_CLOSE ramrod.
Change: Added check for iscsi completion error when receiving the TCP_CLOSE ramrod completion.
Impact: bnx2x iSCSI only.
bnx2 2.2.3m (Jan 28, 2013) ========================== cnic 2.5.16e (Jan 28, 2013) =========================== Fixes ----- 1. Problem: (CQ67528) cnic/bnx2 crash when both drivers are loaded on some kernels.
Cause: Shared struct bnx2 compiled differently on bnx2 and cnic, causing cnic to reference the wrong field.
Change: Added bnx2_compat0.h to define the common CFLAGs that affect structure sizes for both drivers to include.
Impact: All (if cnic is loaded)
bnx2 2.2.3k (Jan 25, 2013) ========================== Fixes ----- 1. Problem: CNIC driver didn't get started after bnx2_open().
Cause: CNIC driver is stopped when bnx2_close() is invoked. However, there is no equivalent turn on mechanism when bnx2_open() is called. The issue prevent bnx2i to offload iscsi connections during session recovery.
Change: Added equivalent cnic start procedure in bnx2_open().
Impact: ESX only.
cnic 2.5.16d (Jan 25, 2013) =========================== Fixes ----- 1. Problem: (CQ67375) Unable to turn iSCSI TCP delayed ACK on after it's been turned off.
Cause: tcp_flags in cnic's socket structure not cleared between destroy and create calls.
Change: Clear tcp_flags during socket create call.
Impact: iSCSI only.
2. Problem: (CQ67306) iSCSI TCP delayed ACK not working.
Cause: Firmware HSI change.
Change: Adapted to new firmware HSI which is now defining delayed ACK globally for the HBA.
Impact: iSCSI only.
cnic 2.5.16c (Jan 15, 2013) =========================== Fixes ----- 1. Problem: cnic does not compile on SLES11SP2.
Cause: bnx2x_compat.h conflicts with SLES11SP2 header files.
Change: Modilfed Makefile to detect SLES distribution so that the proper CFLAG can be defined for bnx2x_compat.h
Impact: SLES distributions only.
cnic 2.5.16b (Dec 12, 2012) =========================== bnx2 2.2.3j (Dec 12, 2012) ========================== Enhancements ------------ 1. Change: (CQ60429, 66302) Simplify cnic probing by not using symbol_get(). symbol_get() is unreliable as it fails while the network driver is still initializing.
Impact: iSCSI and FCoE (driver loading and unloading).
Cause: Race condition during simultaneous remote reset and local TCP close/reset. This may be a partial fix and additional fixes in other areas/drivers may be necessary to completely address all symptoms.
Change: If remote reset is detected to be in progress during local close/reset, it will wait for outstanding RAMRODs to complete. Without the wait, bnx2i will proceed to destroy the connection while the SRCH_DELETE/TERM_OFFLOAD RAMRODs are still pending.
Impact: bnx2x iSCSI only.
bnx2 2.2.3i (Nov 05, 2012) ========================== Enhancements ------------ 1. Change: (CQ65960) Make minor compatibility changes to support RHEL6.4
Impact: None.
2. Change: Added support for latest 3.x kernels.
Impact: All supported kernels.
cnic 2.5.14c (Nov 05, 2012) ========================== Fixes ----- 1. Problem: (CQ65178) Panic when loading and unloading cnic with bnx2i and bnx2fc.
Cause: The iSCSI EQ does not get reset during cnic init. When we get the first cnic IRQ, the iSCSI EQ index may be non-zero in the status block, causing the cnic driver to dereference NULL pointer.
Change: Added code to clear the iSCSI EQ index in the STORM memory.
Impact: 10G iSCSI.
bnx2 2.2.3h (Oct 16, 2012) ========================== Fixes ----- 1. Problem: Netdump crash when runing with ESX6.0 OS.
Cause: bnx2 poll controller routine is not compatible with ESX6.0.
Change: For ESX6.0, bnx2 will use ESX poll controller for netdump.
Cause: There is race condition where netdev_watchdog() could erroneouly flag tx timeout in a small window when bnx2_netif_stop() disabled tx queue state while carrier is still on.
Change: Carrier must be turned off before netif_tx_disable() is called.
cnic 2.5.12e (Aug 22, 2012) ========================== Fixes ----- 1. Problem: (CQ 65270): bnx2x IRQ assert on 57712 and newer devices that support iSCSI only.
Cause: Not arming IRQ properly when detecting that the device does not support FCoE. Regression from cnic 2.5.12c enhancement #3.
Change: Added function pointer to arm IRQ correctly based on chip type.
Impact: iSCSI and FCoE on all 10G devices.
cnic 2.5.12d (Aug 21, 2012) ========================== Fixes ----- 1. Problem: (CQ 65249): cnic panic on functions that support FCoE only.
Cause: Code accessing iSCSI resources that aren't initialized or allocated on functions that don't support iSCSI.
Change: Check for valid UIO resource before trying to free it. Always initialize iSCSI OOO resources.
Impact: 10G iSCSI and FCoE.
bnx2 2.2.3d (Aug 15, 2012) ========================== Fixes ----- 1. Problem: (CQ 65163): unhandled NETQUEUE messages 16 and 17 seen in vmkernel logs
Cause: Not properly handling unsupported NetQueue ops
Change: Properly handle the NetQueue ops 16 and 17 without printing the warning message
Impact: ESX only
Enhancements ------------ 1. Change: Try to recover from PCI block reset during TX timeout. Red Hat users have reported PCI block resets that could not be recovered during tx timeout.
Impact: None.
2. Change: Added mk_kernel_patch.sh to patch bnx2 driver into kernel tree.
Impact: None.
cnic 2.5.12c (Aug 15, 2012) ========================== Enhancements ------------ 1. Change: Added firmware dump support for ESX6.0.
Impact: ESX6.0.
2. Change: Reduced maximum iSCSI abort delay to 5 seconds
Impact: iSCSI
3. Change: Allocate FCoE or iSCSI resources on a cnic only if the device supports the protocol. This will reduce memory consumption on multi-function devices.
Impact: iSCSI and FCoE
bnx2 2.2.3c (July 09, 2012) ========================== Fixes ----- 1. Problem: Unmapping the wrong DMA address in bnx2_free_tx_skbs() in rare cases.
Cause: Not skipping the last entry in the tx BD ring.
Change: Use the proper macro to get the next BD entry.
Impact: On systems with IOMMUs enabled, the bug can be triggered when doing resets (ifdown, MTU change) during heavy TX traffic.
cnic 2.5.12b (July 03, 2012) ============================= Enhancements ------------ 1. Change: Updated to bnx2x firmware 7.4.8 HSI for TX BDs.
Cause: Bug in cnic when max OOO resource is reached
Change: Initailized packet descriptor to fix the bug.
Impact: iSCSI only.
bnx2 2.2.3b (June 29, 2012) ========================== Fixes ----- 1. Problem: Compile error in RHEL6.x kernel and similar kernels.
Cause: skb_frag_size() compatibility code not detected properly.
Change: Fixed Makefile to detect it from skbuff.h
Impact: None.
bnx2 2.2.2b (June 24, 2012) ========================== Fixes ----- 1. Problem: (CQ63682)PSOD in ESX upon device open.
Cause: NAPI was not disabled properly upon device close. Thus, ASSERT occurs upon reopening device.
Change: Add NAPI disable upon close and add netif_tx_disable for both linux and ESX build.
Impact: bnx2.
2. Problem: Enableing RSS interferes with RX NETQ feature when compiled for ESX build.
Cause: RSS is enabled by default in bnx2. The RSS feature will lead to firmware bypass NETQ code path.
Change: Disable RSS by default when compiled for ESX.
Impact: ESX.
Enhancements ------------ 1. Change: Partial sync-up with upstream driver. Please see Changelog.
Impact: All
cnic 2.5.11c (June 12, 2012) ============================= Fixes ----- 1. Problem: (CQ62298 Partial fix) When running in INTA mode, MTU change does not work. iSCSI/FCoE does not resume after MTU change.
Cause: During mtu change, bnx2x does not know that cnic is no longer handling IRQs.
Change: Added a new flag to let bnx2x know that cnic is no longer handling IRQ during reset.
Impact: bnx2x iSCSI and FCoE.
2. Problem: (CQ62937) bnx2x asserts during iSCSI test with corrupted TCP NOP-IN.
Cause: Corrupted NOP-IN falls outside of TCP window, causing FW to go into OOO mode. TCP close with outstanding OOO causes problem and the close does not complete.
Change: FW change to return an error in this case and cnic driver change to handle this error by proceeding to clean up the connection.
Impact: bnx2x iSCSI.
cnic 2.5.11b (April 30, 2012) ============================= Fixes ----- 1. Problem: (CQ62298 Partial fix) Fix for CQ62026 in cnic 2.5.9d introduced a regression of clearing the CNIC_UP flag before all CIDs have been deleted. The regression is causing warning messges that some CIDs have not been deleted. After fixing this, we're still encountering further bnx2x error messages in the INTA code path.
Change: Wait for all CIDs to be deleted before clearing CNIC_UP flag.
Impact: iSCSI and FCoE on all bnx2x devices.
bnx2 2.2.1l (April 18, 2012) ============================ Fixes ----- 1. Problem: PSOD on ESX because of inconsistant NetQueue state when the NetQueues are allocated/freed out of order
Cause: The forced freeing of the NetQueue before the NetQueue allocation can cause the incorrect NetQueue to be freed and marked incorrectly.
Change: Remove the freeing of the NetQueue in the allocation path and allow the load balancer to control the error path when NetQueue's could not be allocated/freed.
Impact: ESX only.
cnic 2.5.10c (April 18, 2012) ============================= Enhancements ------------ 1. Change: Added iface_num parameter to cm_create() and iscsi_nl_send_msg()to support bnx2i 2.7.2.2b.
Impact: iSCSI only.
bnx2 2.2.1k (April 04, 2012) ============================ Enhancements ------------ 1. Change: Reduced code size of FTQ dump during tx_timeout.
Impact: None.
cnic 2.5.10b (April 04, 2012) ============================= Enhancements ------------ 1. Change: Added PCI pass through support for bnx2x E2/E3 devices.
Cause: cp->ctx_tbl is NULL during cnic_ctl() call with COMPLETION_CMD.
Change: cnic is registered with the L2 drivers before we allocate the cp->ctx_tbl so it is possible to get called while cp->ctx_tbl is NULL. Added check for CNIC_UP flag before proceeding to dereference cp->ctx_tbl. This together with the RCU code will completely fix the problem.
Cause: Middle-box test corrupts packets and causes iSCSI fw to generate 0x4 (NIC_ERR) completion code. This conflicts with new logic that uses NIC_ERR to convey parity error.
Change: Redefined parity error completion code to be 0x81 for L4, iSCSI, and FCoE.
Impact: FCoE and iSCSI.
bnx2 2.2.1g (Feb 28, 2012) ========================== Fixes ----- 1. Problem: Calling of bnx2_vlan_rx_kill_vid() is not rtnl_lock protected. Change: hold rtnl_lock when execute this routine under ESX4.0 and ESX4.1. Impact: ESX4.0/4.1 only.
bnx2 2.2.1f (Feb 8, 2012) ========================== Fixes ----- 1. Problem: (CQ61327) Unable to pass traffic on RHEL5.x
Cause: bp->num_rx_rings not initialized due to backport errors. This was introduced in 2.2.1e when adding ethtool -l|L support.
Change: Initialized bp->num_rx_rings to 1 on these older kernels.
Impact: RHEL5 and SLES10 only.
cnic 2.5.8f (Feb 06, 2012) ========================== Enhancements ------------ 1. Change: Added VLAN update from iscsiuio. This allows VLAN to be specified in iface.
Impact: iSCSI only.
cnic 2.5.8e (Jan 24, 2012) ========================== Enhancements ------------ 1. Change: Enhanced FCoE parity recovery by sending immediate FW_DESTROY completion with error during parity error recovery.
Impact: FCoE only.
bnx2 2.2.1e (Jan 24, 2012) ========================== Enhancements ------------ 1. Change: Added support for ethtool -[l|L]. Please refer to README.TXT for details.
Impact: 5709 with support for MSIX only.
cnic 2.5.8d (Jan 19, 2012) ========================== Enhancements ------------ 1. Change: Enhanced FCoE driver registration to provide FCoE capabilities to bnx2x driver.
Impact: Systems with Management support of these features. These changes were made to match bnx2x 1.72.07.
2. Change: (CQ60867) Backed out earlier changes related to this CQ. genksyms checksums are based on structure names and type names, so the scheme of using an identical structure with a different name will not work.
Impact: None.
cnic 2.5.8c (Jan 10, 2012) ========================== 1. Problem: (CQ60744) Lose connection to FCoE targets after parity error recovery.
Cause: (Partial) DISABLE_CONN SPQ message does not complete, causing delaying waiting for bnx2fc to timeout.
Change: Added immediate KCQ error completion for FCOE_DISABLE_CONN. when SPQ fails.
Cause: If a TCP connection fails due to parity error, termination sequence does not follow the expedited error recovery path. This causes unnecessary delay during parity error recovery.
Change: Set the HW_ERR bit when TCP connection fails due to SPQ error. Termination will then follow the expedited error recovery path.
Impact: iSCSI on bnx2x.
3. Problem: (CQ60867) Module versioning warning when installing cnic driver on SLES11SP2 without matching bnx2i/bnx2fc.
Cause: cnic_register_driver() stub in cnic.c does not have cnic_ulp_ops structure that matches inbox bnx2i/bnx2fc.
Change: Added dummy cnic_ulp_ops that match RHEL6.2 and SLES11SP2 structures.
Impact: None.
bnx2 2.2.1d (Jan 10, 2012) ========================== Fixes ----- 1. Problem: PSOD seen in TX handling in either bnx2_tx_int() or bnx2_start_xmit() routines
Cause: Memory re-ordering is occuring so that the TX BD is not updated before the ringing of the TX doorbell.
Change: On ESX the wmb() macro is defined to only as a compiler barrier. Redfine the wmb() macro to properly synchronize memory using the sfence instruction.
Impact: ESX only.
cnic 2.5.8b (Jan 05, 2012) ========================== Enhancements ------------ 1. Change: Added CNIC_CTL_FCOE_ENHANCED_STATS_CMD and CNIC_CTL_FCOE_CAPABILITIES_GET_CMD as stubs.
Cause: SPQ errors during parity error recovery was not propagated to L4 and ULP, causing unnecessary long timeouts.
Change: Added immediate KCQ error completion for L4 and iSCSI kwqes if SPQ fails.
Impact: iSCSI on bnx2x.
bnx2 2.2.1c (Dec 21, 2011) ========================== Fixes ----- 1. Problem: (CQ60281) BNX2 hang on ESX 4.1 when changing tx ring size with Ethtool.
Cause: BNX2 set_ringparam() ethtool ops callback attempts to hold rtnl_lock while vmlinux has already held this lock when when invoking this callback. This leads to deadlock situation and driver will hang forever.
Change: Make sure all ethtool ops callbacks don't hold rtnl_lock.
Impact: ESX only.
2. Problem: (BDKL87) PSOD in bnx2 start_xmit() path when stressing with change ring size script on ESX 4.1u2.
Cause: When using ESX4.0/4.1u0-u2, the vmkernel doesn't not check tx queue state properly in certain race condition. This can lead to bnx2 start_xmit() to deference NULL tx buffer.
Change: check tx queue state before proceed with stat_xmit().
Impact: ESX4.0/4.1u0-u2.
cnic 2.5.7h (Dec 08, 2011) ========================== Enhancements ------------ 1. Change: Added iSCSI and FCoE driver status and counters support.
Impact: Systems with Management support of these features.
2. Change: Added upstream patches to sync up with upsteam driver: net: treewide use of RCU_INIT_POINTER net: remove ipv6_addr_copy()
Impact: None.
bnx2 2.2.1b (Dec 08, 2011) ========================== Enhancements ------------ 1. Change: Added several upstream patches to sync up with upsteam driver: net: treewide use of RCU_INIT_POINTER bnx2: fix skb truesize underestimation net: Remove unnecessary driver assignments of ethtool_ringparam fields to zero
Impact: None.
bnx2 2.1.12b (Oct 14, 2011) =========================== Fixes ----- 1. Problem: (CQ59255) iSCSI warning messages appear and performance drops when connected to a lefthand target.
Cause: Packets with invalid TTT generate warnings and exception handling.
Change: Updated to 6.2.3 firmware for 5706 and 6.2.1.b for 5709
Impact: iSCSI
cnic 2.5.7g (Sep 23, 2011) ========================== Enhancements ------------ 1. Change: Added cnic_register_driver()/cnic_unregister_driver stubs so that depmod will not return errors if native bnx2i/bnx2fc drivers have not been updated.
Impact: None.
bnx2 2.1.11e (Sept 19, 2011) =========================== Enhancements ------------ 1. Change: Set the feature, NETIF_F_NO_SCHED, for ESX 5.0 and greater releases only
Impact: ESX only
Fixes ----- 1. Problem: Compile errors on some older kernels.
Cause: Compatibility API pci_is_pcie() requires bool type which may not be defined on older kernels.
Change: Moved bool type compatibility definition above pci_is_pcie().
Impact: None.
bnx2 2.1.11d (Aug 30, 2011) =========================== Enhancements ------------ 1. Change: Integrate Code Review Comments from VMware * Add feature flag to reflect if a device is compliant with network scheduling. * Conditionally move bnx2 drivers to high memory * Remove unused field/code
Impact: ESX only
2. Change: Remove unnecessary read of PCI_CAP_ID_EXP from upstream.
Impact: minor (5709 only).
cnic 2.5.7f (Sep 13, 2011) ========================= Fixes ----- 1. Problem: Duplicate cp local variable in cnic_shutdown_rings().
Cause: Coding error.
Change: Removed duplicate variable.
Impact: None.
cnic 2.5.7e (Aug 8, 2011) ========================= Fixes ----- 1. Problem: (CQ57498) System hangs during bnx2x parity error recovery.
Cause: cnic waits for RAMRODs to complete without timeout. During parity error recovery, all DMAs will stop.
Change: Added timeouts to all RAMRODs.
Impact: iSCSI and FCoE on bnx2x
cnic 2.5.7d (July 28, 2011) =========================== Enhancements ------------ 1. Change: Increased the max number of FCoE sessions to 1024.
Impact: FCoE.
bnx2 v2.1.11c (July 26, 2011) ============================ Enhancements ------------ 1. Change: Upstream sync to use ethtool_cmd_speed API.
Impact: None.
2. Change: Added memory barrier to sync transmit descriptor before updating TX mailbox. We believe that this may fix some very rare panics reported by VMWare.
Impact: bnx2 packet transmit.
cnic 2.5.7c (July 26, 2011) =========================== Fixes ----- 1. Problem: FCOE_DESTROY_FUNC ramrod not completing, causing timeout and OOO cleanup timeout during MTU change.
Cause: FCOE_DESTROY_FUNC was sent before all FCoE CIDs have been deleted.
Change: Wait for all (2 seconds delayed) FCoE CFC_DELETE ramrods to be completed before sending FCOE_DESTROY_FUNC.
Impact: FCoE only.
cnic 2.5.7b (July 19, 2011) =========================== Enhancements ------------ 1. Change: Re-instated vlan_id in ->indicate_netevent(). It is needed by bnx2fc to handle NETDEV_UNREGISTER on VLAN devices.
Impact: bnx2fc.
2. Change: Allocate FCoE CID space only on E2+ devices.
Impact: None.
bnx2 v2.1.11b (July 19, 2011) ============================ Enhancements ------------ 1. Change: Added tx_timeout error handling and made it common with VMWare code.
Impact: bnx2 NETDEV WATCHDOG error handling
2. Change: Fix compile errors on the latest net-next upstream kernel.
bnx2 v2.1.10d (July 12, 2011) cnic 2.5.6c (July 12, 2011) ========================================================= Fixes ----- 1. Problem: Not compiling on 3.0.0 kernel.
Cause: Makefile not recognizing the 3.0.x kernel
Change: Modified Makefile and sync'ed with upstream drivers.
Impact: None.
bnx2 v2.1.10c (July 1, 2011) ============================ Fixes ----- 1. Problem: Not compiling on older kernels (such as RHEL5.4) and newer kernels (such as 2.6.36)
Cause: Problems with compatibility code.
Change: Fixed compatibility code.
Impact: None.
bnx2 v2.1.10b (June 30, 2011) ============================ Enhancements ------------ 1. Change: Added more complete MCP dump during error conditions.
Impact: None.
2. Change: Modified driver messages slightly to match upstream format (by using netdev_printk, netdev_err, etc).
Impact: None.
Fixes ----- 1. Problem: Not reading iSCSI license on 570x devices reliably.
Cause: We were reading from the CP scratch pad before the CP firmware is loaded.
Change: Read from MCP shmem location instead.
Impact: 1G iSCSI on bnx2 devices.
cnic 2.5.6b (June 30, 2011) ============================ 1. Problem: (CQ56522, CQ56259) Unable to connect to iSCSI target, bnx2x firmware assert during iSCSI connection
Cause: iSCSI L2 ring CID has been changed in bnx2x 1.70.14. uIP is using a hardcoded value of 0x11.
Change: cnic now passes the CID to uIP.
Impact: iSCSI on bnx2x devices.
2. Problem: (CQ56230) Cannot compile on some 32-bit systems.
Cause: Passing 64-bit NULL pointer as 32-bit 0 dma_addr_t value.
Change: Use 0 instead of NULL for dma_addr_t values.
Impact: None.
cnic 2.5.5b (June 22, 2011) ============================ Enhancements ------------ 1. Change: Added WWN info to cnic_eth_dev. This is a temporary solution until ndo_fcoe_get_wwn() is implemented.
Impact: None.
bnx2 v2.1.9b (June 22, 2011) ============================ Enhancements ------------ 1. Change: Added del_timer_sync() in bnx2_remove_one() from upstream commit 8333a46ad3877485e4d67ef499c6dda36bfd1f9a. See ChangeLog for details.
Impact: None.
bnx2 v2.1.8c (June 16, 2011) ============================ Enhancements ------------ 1. Change: In ESX, bnx2 will setup int mode during .probe time. However, the dev->name will be finalized only when pci_announce_device is done. So, we assign irq->name in bnx2_request_irq instead of in bnx2_setup_int_mode.
Impact: ESX only.
cnic 2.5.4b (June 1, 2011) ============================ Fixes ----- 1. Problem: (CQ55915) iSCSI does not connect on 57800 in 4-port mode.
Cause: cl_qzone_id was wrong on the 3rd and 4th port. uIP also has some problems determining 4-port mode.
Change: Fixed the QZONE_ID macro.
Impact: bnx2x iSCSI.
bnx2 2.1.8b (June 1, 2011) ============================ Fixes ----- 1. Problem: (CQ55422) NCSI firmware version displayed backwards on PPC.
Cause: Endian bug when reading the data from shared memory.
Change: Fixed byte swapping issue.
Impact: None.
2. Problem: bnx2 does not compile on some PPC distros.
Cause: pci_enable_pcie_error_reporting() not properly defined in some distros.
Cause: Added #ifdef to prevent compiling pci_enable_pcie_error_reporting() on PPC since it uses EEH instead of AER.
cnic 2.4.5b (May 16, 2011) ========================== Enhancements ------------ 1. Change: Check CFC delete error code during completion. If it is set, do not reuse the CID. This change is only compatible with bnx2x 1.64.30 or newer.
Cause: TCP reset request may not complete if there is a race with firmware receiving a remote RST.
Change: Added code to handle TCP reset racing with remote RST and TCP close racing with remote FIN.
Impact: iSCSI
cnic 2.4.3b (April 28, 2011) ============================ Fixes ----- 1. Problem: cnic may lose interrupts after processing 64 kcq entries.
Cause: The driver handles a maximum of 64 entries before calling the ulp drivers. If the chip has more entries, the driver does not handle the rest but acknowledges the latest status block index.
Change: Changed the logic to keep looping until all kcq entries are handled.
Impact: iSCSI and FCoE on all devices.
cnic 2.4.2b (April 21, 2011) ============================ Fixes ----- 1. Problem: (CQ54715, CQ54717) XSEMI parity error detected during iSCSI login on 57712 in NPAR mode.
Cause: Statistic counter ID greater than MAX_STAT_COUNTER_ID_E2 in client init data for iSCSI L2 ring.
Change: Check client ID against MAX_STAT_COUNTER_ID_EXX before enabling statistics.
cnic 2.4.1c (April 11, 2011) ============================ Fixes ----- 1. Problem: (CQ49586) iSCSI reboot test fails after a few iterations.
Cause: TCP port 60000 is used every time during boot. During reset, the TCP connection is never terminated so using the same port to connect to the target during reboot will not work.
Change: Added randomization of the first TCP port to use.
Impact: iSCSI.
bnx2 v2.1.6b (April 6, 2011) ============================ Enhancements ------------ 1. Change: Get iSCSI license information to prevent cnic from registering if there is no license. This will make it consistent with 10G behavior.
Impact: iSCSI only.
cnic 2.4.1b (April 6, 2011) =========================== Fixes ----- 1. Problem: (CQ53236) FCoE HBA not functional after reloading bnx2x.
Cause: In some distros, NETDEV_UP can happen immediately after NETDEV_REGISTER while bnx2x module is still in init state. At this time, cnic will not be able to symbol_get() from bnx2x, preventing the cnic from registering.
Change: Check all events, and we should be able to catch NETDEV_CHANGE abd register cnic.
cnic 2.4.0b (Mar 29, 2011) ========================== Enhancements ------------ 1. Change: Updated cnic to with with bnx2x 1.70.x and added support for 578xx devices.
Cause: Race condition between cnic driver and hardware DMA'ing a new status block with new iSCSI events. The bug was introduced when adding FCoE support.
Change: 1. Add proper memory barrier after reading status block. 2. After servicing FCoE EQ, we must loop back and check the iSCSI EQ again because we may have a newer status block index that is read after servicing the iSCSI EQ.
Impact: 57712 iSCSI and FCoE.
bnx2 v2.1.5c (Feb 15, 2011) cnic 2.3.5c (Feb 15, 2011) ====================================================== Enhancements ------------ 1. Change: Updated 5709 firmware to 6.2.1a, with netq fixes and iSCSI performance regression fixes.
Impact: 5709.
bnx2 v2.1.5b (Feb 08, 2011) cnic 2.3.5b (Feb 08, 2011) ====================================================== Fixes ----- 1. Problem: iSCSI does not connect in DCB environment.
Cause: iSCSI packets are tagged with the wrong ethertype.
Change: Added initialization of xstorm's reserved_vlan_type field.
Cause: BNX2_NETQ_HW_OPENED bit was not properly set.
Change: When the NetQueue device is openned properly set the BNX2_NETQ_HW_OPENED bit in the netq_flags field.
Impact: ESX NetQueue
2. Problem: NetQueue could possibly get out of sync with the uppper layers
Cause: The queue cleanup code between the driver and upper layer is not synchronized
Change: Introduce the NetQueue lock to synchronize the cleaning of the queues between the vmkernel and the bnx2 driver.
Impact: ESX NetQueue
3. Problem: iSCSI may not work if multi-function is disabled in NPAR NICs.
Cause: Bug in logic in detecting NPAR mode.
Change: Offload bit should not be checked if iSCSI MAC address is invalid.
Impact: iSCSI on 57712 NPAR NIC.
bnx2 v2.0.22c (Jan 6, 2011) cnic 2.2.12c (Jan 6, 2011) ========================================================= Enhancements ------------ 1. Change: Updated to 6.2.1a firmware for 5709. It has fixes for CQ51953 (ESX netqueue issue) and CQ51894 (iSCSI performance).
Impact: 5709 iSCSI and L2.
bnx2 v2.0.22b (Jan 4, 2011) cnic 2.2.12b (Jan 4, 2011) ========================================================= Enhancements ------------ 1. Change: Send netlink IF_DOWN message during cnic_unregister_device(). This fixes the problem of bnx2i referencing freed hba when we used to send the netlink message during cnic_unregister_driver().
Impact: iSCSI.
2. Change: Upstream fix for memory leak in cnic_alloc_uio_rings() when we cannot allocate all the memory.
Impact: None.
3. Change: Upstream fix to remove flush_scheduled_work() since it is obsolete.
Impact: None.
4. Change: Do not allow iSCSI on bnx2x devices in MF mode. The hardware does not yet support it.
Impact: iSCSI.
Fixes ----- 1. Problem: SPQ RAMROD type field does not consistently contain the function ID.
Change: Fixed in cnic_submit_kwqe_16() for HSI 6.0 and above.
Impact: iSCSI in NPAR mode.
bnx2 v2.0.21b (Dec 21, 2010) cnic 2.2.11b (Dec 21, 2010) ========================================================= Enhancements ------------ 1. Change: Call cm_connect_complete() when an invalid path_response netlink message is received. This will speed up iscsid in disconnecting the connection. This helps to resolve CQ49665.
Cause: Referencing the cp->kcq1 pointer before checking that the device is up.
Change: Fixed logic so that the cp->kcq1 pointer will only be refernced after checking the device is up.
Impact: iSCSI.
Enhancements ------------ 1. Change: Added retry logic in iscsi_nl_send_msg() to retry netlink messages to userspace.
Impact: iSCSI.
bnx2 v2.0.20f (Dec 09, 2010) cnic 2.2.10f (Dec 09, 2010) ========================================================= Fixes ----- 1. Problem: (CQ51544) Unable to connect to iSCSI targets on 57712 NPAR LOMs with NPAR disabled.
Cause: ff:ff:ff:ff:ff:ff iSCSI MAC address was used in this case.
Change: Add code to detect invalid MAC address and use port MAC address instead. That's the only to determine NPAR is disabled.
Impact: 57712 iSCSI.
2. Problem: MTU change in INTA mode crashes occasionally.
Cause: Status block may be accessed if INTA is shared with another device during reset. There is a short period that the status block is freed.
Change: Free IRQ before freeing status block.
Impact: bnx2 MTU change/ring size change.
3. Problem: Heap corruption reported by VMWare.
Cause: list_del() is called after kfree() in OOO code.
Fix: call list_del() before kfree().
Impact: iSCSI OOO.
bnx2 v2.0.20e (Dec 06, 2010) cnic 2.2.10e (Dec 06, 2010) ========================================================= Enhancements ------------ 1. Change: Adjusted hc timeout for EQ to use the T6.0 value of 4. This will match T5.x HC timeout values.
Impact: 10G iSCSI only.
2. Change: Minor changes to match upstream code.
Impact: None.
bnx2 v2.0.20d (Nov 16, 2010) cnic 2.2.10d (Nov 16, 2010) ========================================================= Fixes ----- 1. Problem: VMware NetQueue not working properly on 5709.
Cause: HSI mismatch.
Change: Updated HSI to match T6.0 bnx2 firmware.
Impact: NetQueue on 5709.
Enhancements ------------ 1. Change: Adjusted kernel compatibility code to compile on RHEL5.6.
Impact: bnx2 and cnic.
bnx2 v2.0.20c (Oct 28, 2010) cnic 2.2.10c (Oct 28, 2010) ========================================================= Fixes ----- 1. Problem: NMI occurs during repeated load/unload of bnx2 driver on 5709.
Cause: The 5709 chip's DMA block wasn't stopped properly before reset.
Change: Fixed by clearing DMA_ENABLE in NEW_CORE_CTL register and polling for pending bus transactions to stop.
Impact: 5709.
Enhancements ------------ 1. Change: Update 5706/5708/5709 firmware to 6.2.1.
Impact: All 1G devices.
2. Change: Fixed one circular lock dependency issue with bnx2i when making up call to send iSCSI NL message.
Enhancements ------------ 1. Change: (CQ49858) Support KVM pass-through mode by eliminating config cycles to non-standard PCI registers (PCICFG_MISC_CONFIG, PCICFG_REG_WINDOW*).
Impact: All chips.
bnx2 v2.0.18c (Sep 13, 2010) cnic 2.2.6c (Sep 13, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49832) bnx2 flow control not working
Cause: Mistakenly disabled in firmware in 2.0.17j to fix CQ46393.
Change: Re-enabled RV2P flow control with additional fixes to for a number of odd flow control issues. New firmware versions are 6.0.15 for 5706/5708 and 6.0.17 for 5709.
Impact: 5706/5708/5709.
Enhancements ------------ 1. Change: Added zeroing of the iSCSI L2 ring's RX BD page to help signal ring shutdown to uIP.
Cause: A mismatch was found in the txbd where the hw prod idx did not match the sw prod idx (via the vlan_id field). The problem will show when uIP restarts without cnic reload. Since uIP restarted, it has lost all previous history about the uio ring.
Change: Added cnic_shutdown_rings to the uio_close path so whenever uio_open is called from uIP, the rings will start off fresh.
Impact: 570X/5771X iSCSI.
2. Problem: (CQ49211) Connection via bnx2i path fails in SuSE 11 SP1
Cause: For 5708/09, the previous firmware set did not take the l2 frame header length into account in the placement filter.
Change: Updated to 5706/08 fw 6.0.14 and 5709 fw 6.0.16 which addresses this issue.
Impact: 570X iSCSI.
bnx2 v2.0.17k (Aug 18, 2010) cnic 2.2.5k (Aug 18, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI sessions do not recover when running under heavy stress conditions with the socket layer.
Cause: The NetLink buffer would get congested, so that the response to the PATH_UPDATE back to uIP would not be delivered.
Change: Use CNIC to throttle the number of outstanding PATH_REQ's to uIP, easing the congestion on the Netlink buffer.
Cause: RV2P firmware was set to drop input packets at a rate which is slower than input line rate when the host stops posting buffers. This has caused the rxp ftq to backup which eventually led to the rxp ftq hw to assert PAUSE and flood the network.
Change: RV2P firmware was modified to disable any waiting before dropping the input packet when the host doesn't post buffers.
Cause: cnic_wq destroyed while cnic_delete_task() is still queued in the workqueue.
Change: Call destroy_workqueue() after cnic_release() which waits for the cnic_delete_task() to finish.
Impact: 10G iSCSI.
bnx2 v2.0.17f (July 30, 2010) cnic 2.2.5f (July 30, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI license not read correctly on 57712 in NIC partitioning mode.
Cause: Missing NIC partitioning license logic.
Change: Added NIC partitioning license logic.
Impact: 10G iSCSI.
Enhancements ------------ 1. Change: Updated 5709 firmware to 6.0.13. The new 5709 firmware has additional rx and tx performance improvements.
Impact: 5709.
bnx2 v2.0.17e (July 29, 2010) cnic 2.2.5e (July 29, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49117, CQ49111) Soft locup when unloading bnx2x with cnic and bnx2fc/bnx2i loaded.
Cause: cnic_cm_stop_bnx2x_hw() thread under rtnl_lock() and pci_bus_sem has to wait for cnic_delete_task() to finish the 2-second wait and CFC DELETE of every FCoE or iSCSI connection. There may be work structs scheduled on the common workqueue ahead of cnic_delete_task() that require the same semaphores, leading to the soft lockup.
Change: Use a dedicated workqueue for cnic_delete_task().
Impact: 10G iSCSI and FCoE.
2. Problem: (CQ49113) Compilation error with bnx2x 1.60.30. (CQ48828) lediag fails with cnic loaded.
Cause: license_key structure changed to use all 32-bit fields. This change is to fix CQ48828 (lediag fails with cnic loaded). 16-bit access causes lediag failure.
Change: Made corresponding change to read 32-bit values for the iSCSI license.
Impact: 10G iSCSI.
3. Problem: (CQ49097) cnic panics when loading on 5708.
Cause: The driver uses NULL OOO ring pointers to initialize OOO for 5708.
Change: Skip OOO completely on 5708.
Impact: bnx2 iSCSI.
bnx2 v2.0.17d (July 28, 2010) cnic 2.2.5d (July 28, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49071) Soft lockup during system shutdown after logging in to 10G iSCSI sessions.
Cause: This was introduced in 2.2.5c when fixing CQ49003. flush_scheduled_work() can deadlock because we're holding rtnl_lock and linkwatch_event may be on the workqueue.
Change: Fixed by using flags to wait for the cnic_delete_task() to finish.
Impact: 10G iSCSI.
2. Problem: cnic driver does not load on 5708 devices.
Cause: Bug in driver that skips devices without OOO support.
Change: OOO setup has been changed so that cnic initialization will continue even if OOO fails for whatever reason on all chips.
Impact: iSCSI.
Enhancements ------------ 1. Change: Updated 5708 firmware to 6.0.11 and 5709 firmware to 6.0.12. The new 5709 firmware fixes small packet rx performance issue. Some adiitional fixes for iSCSI and OOO.
Impact: All bnx2 chips.
bnx2 v2.0.17c (July 23, 2010) cnic 2.2.5c (July 23, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49003) Panic in cnic_free_bnx2x_conn_resc() during ifdown with many 10G iSCSI active sessions.
Cause: cancel_work_sync() is not available in RHEL5.x kernels to wait for cnic_delete_task() to finish before freeing the device's data structures (in particular the csk table).
Change: Use flush_scheduled_work() to wait instead.
Cause: UIO device deleted before userspace has closed the device, causing various failures including kernel panic.
Change: Separated UIO structure from cnic_dev structure so that we can wait until UIO is closed before unregister and deleting UIO.
Impact: iSCSI. This change should have possitive impact on ifup/ifdown, MTU change/selftest/hotplug/etc with active iSCSI sessions.
Enhancements ------------ 1. Change: Allocate the actual number of MSI-X vectors instead of always 9. Also, keep trying if the number of vectors is less than the desired number.
Impact: 5709 networking and iSCSI.
bnx2 v2.0.16c (July 12, 2010) cnic 2.2.4c (July 12, 2010) ========================================================= Enhancements ------------ 1. Change: Added VLAN_TAG_PRESENT to distinguish between physical and VLAN netevents in cnic.
Impact: FCoE.
bnx2 v2.0.16b (July 8, 2010) cnic 2.2.4b (July 8, 2010) ========================================================= Fixes ----- 1. Problem: (CQ48753) cnic will not compile with bnx2x 1.60.27.
Cause: IGU symbols not defined without ELINK_DEBUG defined.
Change: Added ELINK_DEBUG.
Impact: None.
2. Problem: (CQ48717) Kernel panic in bnx2x during ifdown with active iSCSI sessions.
Cause: uio_close() is called after the device is already down. bnx2x will crash when we try to shutdown the iSCSI ring.
Change: Shutdown the iSCSI ring even if uio_close() is not called in the shutdown path.
Impact: 10G iSCSI.
Enhancements ------------ 1. Change: Always run in MSI-X mode on 5709.
Impact: 5709.
2. Change: Added wait of 2 seconds when sending PATH_REQ if UIO has not been opened yet. This improves the liklihood of login success during the first login if using older iscsid.
Cause: pci_save_state()/pci_restore_state incompatibility in older kernel. DECLARE_PCI_UNMAP_ADDR() caused dma mapping field to be undefined on kernels not using IOMMU.
Change: Do not use pci_save_state()/pci_restore_state() on older kernels. Use dma_addr_t to declare mapping fields.
Impact: None.
bnx2 v2.0.15j (June 30, 2010) cnic 2.2.3j (June 30, 2010) ========================================================= Fixes ----- 1. Problem: bnx2x firmware asserts if cnic is loaded on 57711E (MF) functions 2 and higher and the device is brought up.
Cause: Statistics for iSCSI ring not implemented, casuing firmware to assert when the iSCSI ring is initialized.
Change: Do not enable statistics if the clien ID is bigger than MAX_STAT_COUNTER_ID.
Impact: bnx2x iSCSI on 57711E.
2. Problem: cnic terminations for iSCSI and FCoE connections may panic or hang during repeated ifdown/ifup.
Cause: Data structures may be freed while cnic is still waiting for the 2 second CFC_DELETE wait time.
Change: Use cancel_work_sync() to wait for the completion of the cnic_delete_task(). Check that the CTX_FL_DELETE_WAIT flag has been set before waiting.
Impact: bnx2x iSCSI and FCoE.
3. Problem: (CQ48642) Compile errors on older kernels.
Cause: VMWARE_ESX_DDK_VERSION not defined in Linux.
Cause: Race condition between bnx2i initiated TCP close and an asynchronous RESET_COMP from firmware.
Change: Re-structured cnic code that handles close, abort, and various completion events to ensure all scenarios are accounted for with no race conditions.
Impact: All iSCSI connection termination scenarios.
Enhancements ------------ 1. Change: Added host iSCSI IP address to the cnic_dev structure so that bnx2i can report it to sysfs. This is needed for iSCSI boot during pivot_root.
Cause: PCI MSIX attributes not defined in kernel .h files.
Change: Added compatibility code.
Impact: None.
bnx2 v2.0.15d (June 2, 2010) cnic 2.2.3d (June 2, 2010) ========================================================= Fixes ----- 1. Problem: (CQ47942) rmmod hangs if the device has been opened and closed more than once.
Cause: netif_napi_add() called once during every ->open(). netif_napi_del() is only called once during rmmod.
Change: Call netif_napi_del() in ->close().
Impact: None.
bnx2 v2.0.15c (May 21, 2010) cnic 2.2.3c (April 21, 2010) ========================================================= Fixes ----- 1. Problem: service iscsid restart on 5709 does not work.
Cause: Not restarting KWQ correctly due to stale context.
Change: Fixed by correctly zeroing KWQ/KCQ/RX context memory.
Impact: bnx2 iSCSI.
2. Problem: iSCSI license not read correctly on 57711E in single function mode.
bnx2 v2.0.15b (May 12, 2010) cnic 2.2.3b (April 12, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI does not work on 57712.
Cause: License checking always disabled on 57712.
Change: Added proper checking for 57712 iSCSI license.
Impact: None.
2. Problem: (CQ47360) Compile errors on older kernels not supporting UIO and latest iSCSI.
Cause: New cnic driver will only compile on kernels newer than 2.6.31 and some selected distros that have the backport.
Change: Makefile changes to compile cnic only on supported kernels.
Impact: None.
Enhancements ------------ 1. Change: Changed bnx2_cnic_probe() to bnx2_cnic_probe2() so that out-of-tree driver componenets will not inter- operate with upstream components. This avoids compatibility problems that often lead to kernel crashes.
Impact: Out-of-tree cnic will not operate with upstream L2 drivers and vice versa.
2. Change: Revert the PRS_REG_NIC_MODE change done in 2.0.11h. Newer bnx2x driver (1.60.18+) do not require this setting.
2. Change: Added VLAN ID to netdev event callback.
Impact: bnx2i.
bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1c (April 30, 2010) ============================================================ Enhancements ------------ Add debug code to dump all KWQE's (RAMROD) posted to 5771x chipset. This feature can be enabled/disabled using module parameter, by default this feature is disabled. Also a exported function is introduced to dump 3 pages worth of KCQE's
bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1b (April 22, 2010) ============================================================ Enhancements ------------ 1. Change: cnic has been updated to be similar to the upstream versions using UIO with added T6.0 iSCSI support for 10G and other bug fixes.
Impact: iSCSI now requires UIO, new bnx2i, and bnx2x 1.60.16+.
bnx2 v2.0.11j (April 22, 2010) cnic 1.10.2j (April 22, 2010) ============================================================ Fixes ----- 1. Problem: (CQ47298) Does not compile with bnx2x 1.60.16.
Cause: cnic_if.h has changed.
Change: Updated code to be compatible with new cnic_if.h.
Impact: None.
bnx2 v2.0.11i (April 15, 2010) cnic 1.10.2i (April 15, 2010) ============================================================ Fixes ----- 1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours of traffic.
Cause: Chip timing out on write cycle to the MSI-X mask bit, causing the unmask operation to be dropped.
Change: Increase GRC timeout in register 0x8cc. (Same fix from 2.0.8e).
Impact: bnx2x MSI-X mode.
2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and VLANs are used with cnic loaded.
Cause: bond_del_vlans_from_slave() holds bond->lock when calling ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to stop the rx handling while changing the vlgrp. The call also calls bnx2_cnic_stop() which has many sleeping functions.
Change: Do not stop cnic when VLANs are changed. Since there is no reset during VLAN change, there is no need to stop cnic. (Same fix from 2.0.8e).
Impact: VLAN and iSCSI.
3. Problem: (CQ46940) Poor small packet performance on 5709.
Cause: FTQ discards caused by bottlenecks in firmware.
Change: Upgraded to 5.0.0.j15 MIPS firmware for 5709. (Same fix from 2.0.8c)
Impact: 5709.
Enhancements ------------ 1. Change: Improved rx performance by prefetching next entry's descriptor header and SKB.
Impact: All chips.
2. Change: Updated cnic interface to support out-of-order processing. This is needed for bnx2x 1.60.15 but the feature is not available in cnic yet.
bnx2 v2.0.11b (Jan 28, 2010) cnic 1.10.2b (Jan 27, 2010) ======================================================== Enhancements ------------ 1. Change: Saved bnx2 statistics block before MTU change, ring change, etc.
Impact: bnx2 statistics.
bnx2 v2.0.10b (Jan 12, 2010) cnic 1.10.1b (Jan 12, 2010) ======================================================== Enhancements ------------ 1. Change: Improved cnic's MTU change/reset logic to fix multiple problems in VMWare.
Impact: iSCSI.
2. Change: Converted to bnx2x T6.0 HSI.
Impact: bnx2x iSCSI.
bnx2 v2.0.8e (April 13, 2010) cnic 1.9.13b (Dec 16, 2009) ========================================================= Fixes ----- 1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours of traffic.
Cause: Chip timing out on write cycle to the MSI-X mask bit, causing the unmask operation to be dropped.
Change: Increase GRC timeout in register 0x8cc.
Impact: bnx2x MSI-X mode.
2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and VLANs are used with cnic loaded.
Cause: bond_del_vlans_from_slave() holds bond->lock when calling ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to stop the rx handling while changing the vlgrp. The call also calls bnx2_cnic_stop() which has many sleeping functions.
Change: Do not stop cnic when VLANs are changed. Since there is no reset during VLAN change, there is no need to stop cnic.
Impact: VLAN and iSCSI.
bnx2 v2.0.8d (April 02, 2010) cnic 1.9.13b (Dec 16, 2009) ========================================================= Enhancements ------------ 1. Change: Improved rx performance by prefetching next entry's descriptor header and SKB.
Cause: Stale status block with old KCQ index after restarting hardware.
Change: Added some additional cleanup and initialization steps including zeroing the status block.
Impact: None.
Enhancements ------------ 1. Change: Updated RV2P P1 for 5709 to 5.0.0.j10 to address a flow control issue that can lead to context corruption. Flow control watermarks have also been optimized.
Impact: 5709 flow control.
bnx2 v2.0.6b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44801) Unable to compile bnx2 on most 2.6 kernels.
Cause: print_mac() kernel compatibility not defined correctly.
Fix: Simple compatibility fix.
Impact: None.
bnx2 v2.0.5b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009) ======================================================= Enhancements ------------ 1. Change: Sync'ed up with latest upstream bnx2 driver. Please see ChangeLog for details.
Impact: Yes, Linux and VMWare.
bnx2 v1.9.42b (Dec 1, 2009) ======================================================= Fixes ----- 1. Problem: Compile error against the VMware ESX 4.0 DDK
Cause: vmk_IscsiNetHandle is not defined with the VMware ESX 4.0 DDK
Change: Added compile flag
Impact: None.
Enhancements ------------
1. Change: Add BMAPILNX ioctl to allow for FW upgrade
2. Problem: (CQ42096) iSCSI sessions do not recover after running selftest/ifdown/etc with max sessions connected.
Cause: cnic_lock mutex has circular dependency, causing deadlock when iscsid tries to cleanup connections.
Change: Merged in upstream cnic patches to avoid circular dependency.
Impact: None.
Enhancements ------------ Change: (CQ43088) Changed the firmware version string format.
Impact: None.
bnx2 v1.9.40b (Nov 18, 2009) cnic 1.9.10b (Nov 12, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44528) Kernel runs out of memory after load/unload bnx2.
Cause: RX SKB buffers were not freed.
Change: Fixed the regression introduced by VMWare development.
Impact: None.
2. Problem: (CQ44399) iLAB 5.10 connection establishment test failure.
Cause: Firmware SYN-ACK handling issue.
Change: Updated firmware to 5.0.0.j6 in bnx2_fw.h and 5.0.0.j9 in bnx2_fw2.h.
Impact: iSCSI.
Enhancements ------------ Change: (CQ43088) Added VPD-R V0 firmware version string to ethtool -i.
Impact: None.
bnx2 v1.9.39b (Nov 6, 2009) cnic 1.9.10b (Nov 12, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44470) Kernel panics when bnx2/bnx2x is unloaded with active iSCSI sessions.
Cause: NETDEV_UNREGISTER will cause bcm570x_* transport to be destroyed while sessions may still be active.
Change: Use module referencing to prevent bnx2/bnx2x from unloading. This is a simple interim solution to revert back to the old behavior. In T6.0, we will migrate to the upstream driver architecture and network drivers will be able to be unloaded again.
Impact: None.
Enhancements ------------ Change: Added a short register dump during NETDEV_WATCHDOG.
bnx2 v1.9.35b (Oct 22, 2009) ======================================================= Fixes ----- 1. Problem: If only 1 queue is used on VMware ESX, iSCSI offload would fail.
Cause: The inboxed VMware driver would only use 1 MSI-X vector. Because of this the driver would not setup MSI-X
Change: Always setup MSI-X reguardless of the number of MSI-X vectors used.
Impact: 5709 iSCSI on VMware
bnx2 v1.9.34b (Oct 20, 2009) ======================================================= Fixes ----- 1. Change: Updated xinan firmware to 5.0.0.j8 Nop timeout tuning (VMware PR467194) Added a new data fw heartbeat to work with the new bootcode and also handle older bootcode.
1. Change: Make NetQueue module parameters more explict.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.32b (Oct 8, 2009) cnic v1.9.7c (Oct 8, 2009) ======================================================= Fixes ----- 1. Problem: CNIC unable to handle an unsolicited RESET COMPLETE which would result in a hung session.
Cause: The CNIC driver couldn't handle unexpected SYN.
Change: The CNIC driver will now handle an unsolicited RESET COMPLETE and cleanup properly.
Impact: cnic
Enhancements ------------
1. Change: Allow the default NetQueue options to be controlled through the macro, BNX2_ENABLE_NETQUEUE.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.31b (Oct 6, 2009) ======================================================= Fixes ----- 1. Problem: PSOD would occur when alloc()'ing NetQueue's
Cause: With the removal of the global 'disable_netq' parameters, the NetQueue CID's weren't being mapped in some cases
Change: Always map the NetQueue CID's
Impact: bnx2 VMware ESX NetQueue
bnx2 v1.9.30b (Oct 5, 2009) ======================================================= Fixes ----- 1. Problem: PSOD would occur because of TX timeouts
Cause: The VMware netdev watchdog timer was ran before the reset task got a chance to run on a loaded system.
Change: Elongated the TX timeout value for VMware ESX only to allow for the reset task to run.
Impact: bnx2 VMware ESX
Enhancements ------------
1. Change: Updated vmkernel module parameter, 'force_netq', to allow NetQueue setting to be adjusted per function rather then globally for all functions.
Impact: bnx2 VMware ESX
bnx2 v1.9.29b (Oct 1, 2009) ======================================================= Fixes ----- 1. Change: Updated xinan firmware to 5.0.0.j7 and teton firmware to 5.0.0.j4 which will fix L2 hang due to iSCSI PDU's padding byte extended to another TCP segment
Impact: 5706/5708/5709.
bnx2 v1.9.28b (Sep 25, 2009) ======================================================= Fixes ----- 1. Change: Updated firmware to 5.0.0.j6 which will add the corresponding flow control trip point.
Impact: 5709.
bnx2 v1.9.27b (Sep 24, 2009) cnic v1.9.7b (Sep 24, 2009) ======================================================= Fixes ----- 1. Problem: For the cnic users would see in the kernel logs:
Cause: The function was not taking into account the wrapping of the software and hardware producer indexes.
Change: Recaculate the difference between the index with wrapping taken into account.
Impact: cnic
Enhancements ------------
1. Change: Updated firmware to 5.0.0.j5 which increased the rxpq depth from 32 to 256 to enhance the performance on systems without flow control.
Impact: 5709.
bnx2 v1.9.26c (Sep 17, 2009) ======================================================= Enhancements ------------ 1. Change: Cleanup the VMware NetQueue code. Eliminate unneeded RX flush routine, fix the number of queues to be the same on 1500 and 9000 MTU sized packets.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.26b (Sep 14, 2009) ======================================================= Fixes ----- 1. Problem: VMware PSOD on MTU change
Cause: MSI-X window was remapped to the beginning of the PCI config space. The driver would disable the bar space because the MSI-X window was remapped incorrectly. This would eventually cause a PSOD.
Change: Before the chip reset, the driver would disable MSI-X, after the chip reset, MSI-X is re-enabled.
Cause: If the driver is unable to allocate memory for the buffers, the device is not properly shutdown.
Change: Added logic to shutdown device if unable to allocate buffers and complete the setup of the device.
Impact: bnx2, changing MTU and ring sizes.
Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j3 for better small packet rx performance. Firmware also fixes header digest error during I/O.
Enhancements ------------ 1. Change: If a TX timeout occurs, there could be the possiblity that the chip is hung. By printing chip state into the kernel ring buffer, it will be easier to determine this.
Impact: bnx2 iSCSI.
2. Change: The bnx2 firmware should always be matched with the proper bnx2 driver. The bnx2 firmware version string are now printed. It will be easier to identify the running firmware.
Impact: bnx2
3. Change: When a TX timeout occurs and the chip is reset, the ability to debug the chip further is lost. This is because the chip state information is lost during the reset. The users have a choice to prevent the chip reset.
Impact: bnx2
4. Change: Add a check to see if there was a KCQ overflow was in the bnx2x firmware. Now this check has been moved to the CNIC so that the driver could control the cleanup/recovery.
Impact: bnx2 iSCSI.
bnx2 v1.9.21b (July 16, 2009) ========================================================== Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j2 to fix remote reset problem
Impact: bnx2 iSCSI.
bnx2 v1.9.20b (July 09, 2009), cnic v1.9.3 (July 09, 2009) ========================================================== Fixes ----- 1. Problem: (CQ42534) cnic.c does not compile on older kernels.
Cause: Some iscsi_proto constants not defined in
Change: Added the constant definitions if not already defined.
Impact: None.
Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j to fix TMF releated iSCSI issues.
Cause: cnic driver sets the MSS without knowing the actual MSS option and timestamp option during TCP connection.
Change: Changed driver to set MSS to 0xffff so that firmware can calculate MSS on its own.
Impact: bnx2x iSCSI.
2. Problem: 1G iSCSI fails when initiator and target MTUs don't match and timestamp is enabled.
Cause: Firmware was not adjusting for the 12-byte timestamp option if MSS was reduced by MSS option.
Change Updated firmware to 5.0.0.i
Impact: bnx2 iSCSI.
3. Problem: (CQ42353) Unable to disable TCP timestamp on 10G iSCSI.
Cause: Timestamp was hardcoded to be enabled for 10G.
Change: Update global timestamp option during each TCP connection.
Impact: bnx2x iSCSI.
4. Problem: (CQ42329) bnx2x MC assert during IPv6 login/logout.
Cause: EQ filled with more than 128 L4 kcqes without MSI-X interrupt for 2 seconds. The driver can only buffer 128 L4 kcqes.
Change: Increased L4 kcqe buffer to 256 entries as a temporary solution. Need to understand the delayed interrupt issue.
Impact: None.
bnx2 v1.9.18b (June 25, 2009), cnic v1.9.1 (June 24, 2009) ========================================================== Enhancements ------------ 1. Change: Added FTQDiscard counter to the list of counters being reported. During small packet test, there may be FTQ overflow and this counter is very useful.
Impact: None.
2. Change: Updated firmware to 5.0.0.h to improve small packet L2 performance and to enhance iSCSI TMF handling.
Impact: 5706/5708/5709.
bnx2 v1.9.17b (June 24, 2009), cnic v1.9.1 (June 24, 2009) ========================================== Fixes ----- 1. Problem: Leaking NetQueues if the firmware did not respond in time
Cause: System might be clogged and there is not enough time to process the KCQ
Change: Updated driver/firmware to allow the calling of the free RX queue request before a RX alloc request is issued
Impact: 5709
2. Problem: An offloaded iSCSI connection would get stuck
Cause: Issing an offload request might fail, and this was not handled properly.
Change: Updated driver/firmware to return the proper return code and handle offload connection failures.
Impact: 5706/5708/5709
3. Problem: tasklet_init() is being called on a task that is scheduled
Cause: When the CNIC calls register_device(), that task might already be schedled.
Change: tasklet_disable() is insufficient because the tasklet remains scheduled and stays on the tasklet list, instead tasklet_kill() is now used.
Impact: 5706/5708/5709
bnx2 v1.9.16b (June 10, 2009), cnic v1.9.0 (June 10, 2009) ========================================================== Enhancements ------------ 1. Change: (CQ38228) Use symbol_get() for ipv6 symbols so that the cnic driver will load without necessarily loading ipv6 modules.
Impact: iSCSI over IPv6.
2. Change: Updated 5706/08/09 MIPS firmware to 5.0.0.g.
Impact: 5706/08/09.
3. Change: Backported some dma_mapping_error() checking.
2. Change: In the cnic driver, save the last allocated TCP port during unregistration so that previously used TCP ports will not be immediately re-used.
bnx2 v1.9.13b (May 18, 2009) ========================================== Fixes ----- 1. Problem: Potentially exceeding the NetQueue limit recommendations by VMware which could stress system resources
Cause: When system resources are strained.
Change: There are now limits on the number of NetQueues which the driver will request: When the MTU is 1500 the max number of queues per port is 8 When the MTU is 9000 the max number of queues per port is 4
Impact: NetQueue enabled version of VMware ESX
2. Problem: Getting conflicting NetQueue and iSCSI completions
Cause: When MSI-X is not used on a 5709, NetQueue is still enabled
Change: NetQueue is not disabled is MSI-X is not used.
Impact: NetQueue enabled version of VMware ESX
bnx2 v1.9.12b (May 13, 2009) ========================================== Fixes ----- 1. Problem: Potentially returning a negative number of NetQueues
Cause: When calculating the number of rings, we use the calculation from the number of msi-x vectors returned, The number of NetQueues returned could potentially be negitive if only 1 vector was returned. This is because the driver was subtracting 2 instead of subtracting 1 (for the default queue) from the total number of rings.
Change: Return the proper number of queues not including the default queue.
Impact: NetQueue enabled version of VMware ESX
bnx2 v1.9.11b (May 12, 2009), cnic v1.8.5 (May 13, 2009) ======================================================== Fixes ----- 1. Problem: TCP Delay ACK not working on bnx2x iSCSI
Cause: Disabled in cnic driver.
Change: Fixed csk->tcp_flags definitions and enabled the proper storm bit for delay ACK.
bnx2 v1.9.10b, cnic v1.8.4 (May 11, 2009) ========================================== Fixes ----- 1. Problem: NetQ and iSCSI do not work in Vmware environment.
Cause: 1. cnic driver is overwriting CP and COM mailbox bit values newly defined to support multiple kcqs.
2. Firmware is completing some iSCSI kcqes on the NetQ's kcq.
Change: Fixed cnic driver to only set and clear bit 0 of the CP and COM mailbox.
Firmware has been updated to 5.0.0d. This firmware also supports TCP timestamp option for iSCSI connections.
Impact: 5706/5708/5709 iSCSI, NetQ.
bnx2 v1.9.9b (May 1, 2009) ========================================== Fixes ----- 1. Problem: There is link, but can't pass traffic on ESXi
Cause: Bits in the RX context are being trampled during the renegotiation of the link.
Change: RX context offset 0x6 should only be initialized once during init and not be updated during run-time. Offset 4 contains the BIDX that's mapped to the mailbox.
Impact: VMware with NetQueue
bnx2 v1.9.8b, cnic v1.8.2 (April 27, 2009) ========================================== Enhancements ------------ 1. Change: Updated cnic driver to support 1.50.x HSI as well as the older 1.48.107 HSI. A compile flag will be used to select one or the other.
Impact: iSCSI on bnx2x.
2. Change: Spec file and Makefile changes detect the proper module install directory.
Impact: installation.
bnx2 v1.9.7b, cnic v1.8.1 (April 22, 2009) ========================================== Fixes ----- 1. Problem: Compile error with redfinition of struct kwqe.
Cause: Both the CNIC and bnx2 defined this structure.
Change: Because the bnx2 definition is L2 specific, it was renamed to struct l2_kwqe.
Impact: None.
2. Problem: Add context memory DMA alignment for 57710.
Cause: For the 57710 context memory needs to be 16k aligned. Without this alignment you will see errors when trying to establish more then 5 iSCSI connections on VMware ESX 4.0 U1.
Change: Properly aligned the context memory by allocating a bigger chunk of memory and then finding the proper alignment. This reduces the number of possible connections in half but now we can properly establish more then 5 connections on VMware.
Impact: iSCSI.
bnx2 v1.9.6b (April 17, 2009) ============================= Enhancements ------------ 1. Change: Added NetQueue support for VMware.
Impact: 5709.
bnx2 v1.9.5b (April 17, 2009) ============================= Enhancements ------------ 1. Change: Updated to 5.0.0.a firmware with NetQ support and iSCSI max connection license information. RV2P firmware unchanged: 4.6.16 for 5706, 4.6.15 for 5709.
Impact: All chips.
2. Change: Set USE_INT_PARAM on 5709. This will switch the chip in use "interrupt mode" coalescing after MSI/MSI-X.
Impact: 5709.
3. Change: Included 5706 when doing statistics block DMA workaround.
Impact: 5706.
bnx2 v1.8.8b (March 12, 2009) ============================= Enhancements ------------ 1. Change: Updated to latest 4.6.17 CP firmware for 5709.
Impact: iSCSI licensing on 5709.
bnx2 v1.8.7b, cnic v1.7.8 (March 10, 2009) ========================================== Enhancements ------------ 1. Change: Reverted 5706/5708 firmware to 4.6.16. Low latency interrupt mode does not work on 5706/5708.
Impact: None.
2. Change: VMWare changes to expose max. number of iSCSI connections in the cnic_device structure.
Cause: msi related symbols undefined because CONFIG_PCI_MSI is not enabled on Xen kernels.
Change: Added CONFIG_PCI_MSI around the msi related code.
Impact: None.
2. Problem: (CQ39818) iSCSI targets do not reconnect after running self test.
Cause: Interrupt is disabled by bnx2 before notifying CNIC to clean up and stop. As a result, bnx2i will not receive interrupts when closing the connections if sharing INTA/MSI with network.
Change: Disable interrupt after notifying CNIC to stop.
Impact: iSCSI.
bnx2 v1.8.6b, cnic v1.7.7 (March 2, 2009) ========================================= Enhancements ------------ 1. Change: Updated to new 5706 firmware (4.6.17) and 5709 firmware (4.6.16). New interrupt coalescing mode for improved latency and iSCSI cache line fix on 5709.
Cause: Bug in bnx2_free_rx_mem(). The jumbo page ring memory was freed incorrectly using the wrong local variable as array index.
Change: Fixed bug by using the correct variable as array index.
Impact: Jumbo frames.
2. Problem: (CQ38965) iSCSI connection timeout on bnx2x.
Cause: During CFC Delete RAMROD completion handling, the wrong (older) iSCSI connection ID can sometimes be retrieved using the harware CID. The CID in the mapping table was not cleared after the CID was freed.
Fix: Adding clearing of the CID in the data structure after a CID is freed.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: (CQ38744) Reduced R2TQ memory usage to match new firmware interface (firmware 4.8.9). This reduces the amount of kernel memory substantially for each iSCSI connection on bnx2x.
bnx2 v1.8.2b, cnic v1.7.2 (Nov 25, 2008) ======================================== Fixes ----- 1. Problem: bnx2x iSCSI does not work on functions 2 or above.
Cause: This was caused by multiple problems: a) Status block ID specified by bnx2x was wrong. b) MSI-X vector assigned to CNIC was wrong. c) New method to ack. status block using HC register was not implemented. d) Status block ID in CSTORM status block is always 0, and as a result, the status block ID used to ack. the status block was wrong.
All these problems only affect functions 2 and above.
Change: All problems fixed in bnx2x and cnic.
Impact: bnx2x iSCSI.
bnx2 v1.8.2b, cnic v1.7.1 (Nov 15, 2008) ======================================== Enhancements ------------ 1. Change: Added CNIC support for Multi function bnx2x iSCSI.
Impact: bnx2x iSCSI.
bnx2 v1.8.2b, cnic v1.6.2 (Nov 12, 2008) ======================================== Enhancements ------------ 1. Change: Updated to latest 4.6.13 5709 firmware to fix context corruption with flow control enabled.
Impact: 5709.
2. Change: Added support for 5716S PCI ID.
Impact: None.
Fixes ----- 1. Problem: (CQ35904) Netdump does not work.
Cause: Problem introduced by MSI-X multiqueue. IRQ handlers were changed to take bnx2_napi parameter instead of netdev parameter.
Change: Fixed by passing proper parameter to IRQ handler from netpoll. All IRQ handlers are called when using multiple MSI-X vectors.
Impact: 5709 netpoll.
bnx2 v1.8.1f, cnic v1.6.1 (Nov 5, 2008) ======================================== Fixes ----- 1. Problem: All TSO packets corrupted on 5706/5708.
Cause: Firmware bug zeroing the wrong field in IP header.
Change: Updated to latest 4.6.11 5706/5708 firmware and 4.6.12 5709 Firmware.
Impact: 5706/5708/5709.
2. Problem: bnx2x chip asserts when trying to make iSCSI connection to an unknown IP address.
Cause: When connection fails, the driver sends a command to an unitialized CID.
Change: Added logic to only send deletion commands to initialized CIDs.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: Added support for one single VLAN to a bnx2x iSCSI interface.
Impact: bnx2x iSCSI.
bnx2 v1.8.1e, cnic v1.6.0 (Oct 27, 2008) ======================================== 1. Change: Updated to latest 5709 firmware to fix iSCSI data integrity problem.
Impact: 5709.
bnx2 v1.8.1d, cnic v1.6.0 (Oct 23, 2008) ======================================== Enhancements ------------ 1. Change: Updated to latest bnx2 firmware to fix iSCSI data integrity problem.
Impact: 5706/5708/5709.
2. Change: Updated to the latest bnx2x HSI files.
Impact: bnx2x iSCSI.
bnx2 v1.8.1c, cnic v1.5.9 (Oct 13, 2008) ======================================== Fixes ----- 1. Problem: (CQ37905) Unable to compile on SLES10 SP2.
Cause: DIV_ROUND_UP macro not defined in this kernel.
Change: Added it for compatibility.
Impact: None.
Enhancements ------------ 1. Change: Updated to latest 5709 firmware that fixes an NCSI problem.
Impact: 5709.
2. Change: Handle TCP reset in the middle of TCP close more appropriately.
Impact: iSCSI.
3. Change: Handle iSCSI license checking in the same way as 5708/5709.
Impact: iSCSI on bnx2x.
bnx2 v1.8.1b, cnic v1.5.8 (Oct 13, 2008) ======================================== Fixes ----- 1. Problem: bnx2x iSCSI CIDs may be allocated outside the range of allocated host memory.
Cause: CID range bigger than the amount of allocated host context memory.
Change: Changed to match the CID range with memory range.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: Sync'ed with the latest upstream driver bnx2 1.8.1.
Impact: None.
2. Change: Implemented iSCSI connection license enforcement for bnx2x devices.
Impact: bnx2x iSCSI.
bnx2 v1.8.0j, cnic v1.5.7 (Oct 6, 2008) ======================================== Fixes ----- 1. Problem: (CQ37610) Chip hangs when changing MTU with active iSCSI connections.
Cause: Both cnic and bnx2 drivers setting up the chip at the same time.
Change: Added check so that the register_cnic function will fail if the bnx2 driver is in reset.
Impact: iSCSI.
2. Problem: (CQ37762) Able to unload bnx2/bnx2x drivers while there are active iSCSI connections.
Cause: CNIC driver does not have a reference count on the BNX2/BNX2X drivers.
Change: This became a problem after the register_cnic function was no longer exported. To solve the problem, the CNIC driver will now get an explicit reference during register_cnic.
Impact: iSCSI.
3. Problem: (CQ37429) MMIO access while the chip is in D3hot state.
Cause: The driver does not check if_running state consistently during ethtool operations.
Change: Added proper checks to all ethtool and multicast change functions.
Impact: ethtool operations and multicast operations.
Enhancements ------------ 1. Change: Simplified ipv4 TSO logic in the driver. This was made possible with newer 5708 firmware.
Impact: 5708 TSO and other traffic.
2. Change: ethtool -p now blinks forever. This is the standard behavior in most other net drivers.
Impact: ethtool -p.
bnx2 v1.8.0i, cnic v1.5.5 (Sep 30, 2008) ======================================== Fixes ----- 1. Problem: (CQ36787) iSCSI login/logout commands fail on 5709 after a while.
Cause: Not handling the KWQ completion properly on 5709 in INTA/MSI mode.
Change: Changed to handle KWQ completions by checking the cmd_consumer_index instead of the rx_quick_index15.
Impact: 5709 ISCSI in INTA/MSI mode.
2. Problem: (CQ37497) CNIC driver does not compile on powerpc.
Cause: csum_ipv6_magic() not defined.
Change: Added #include
Impact: None.
v1.8.0g (Sep 24, 2008) ======================== Fixes ----- 1. Problem: (CQ37511) System locks up when loading cnic driver on 2.6.16 kernel.
Cause: symbol_put_addr() in 2.6.16 tries to acquire the same lock twice.
Change: Workaround by using __symbol_put() which does not have the same problem.
Impact: None.
v1.8.0f (Sep 23, 2008) ======================== Fixes ----- 1. Problem: (CQ37405) Kernel panic when performing ifup/ifdown with iSCSI connections on bnx2x devices.
Cause: Sending searcher delete to bnx2x devices when connection was not established (due to Spanning Tree or other reasons).
Change: Check PG offload state before sending searcher delete.
Impact: iSCSI on bnx2x.
v1.8.0e (Sep 22, 2008) ======================== Enhancement ----------- 1. Change: Updated to latest driver firmware 4.6.6 for 5709.
Impact: 5709.
2. Change: Updated cnic so that it will not crash even if using older bnx2/bnx2x drivers without CNIC support. The net driver can also be loaded after cnic and it will still work without crashing.
Impact: iSCSI.
3. Change: (CQ 37381) Updated driver to check Vaux PRESET before allowing WoL. This is needed to support 5709 quad-port boards.
v1.8.0c (Aug 25, 2008) ======================== Fixes ----- 1. Problem: Does not compile on older kernels.
Cause: "__maybe_unused" undefined on older kernels. "num_online_cpus()" undefined on 2.4 kernels.
Change: Added compatibility code to workaround.
Impact: None.
v1.8.0b (Aug 25, 2008) ======================== Enhancement ----------- 1. Change: Updated to latest driver firmware 4.6.2 for 5709.
Impact: 5709.
v1.7.9c (Aug 5, 2008) ======================== Fixes ----- 1. Problem: bnx2 does not compile on older kernels.
Cause: is missing on 2.6.19 and older kernels.
Change: Added compatibility code to check for kernel version before including the file.
Impact: none.
v1.7.9b (Aug 5, 2008) ======================== Enhancements ------------ 1. Change: Added multi-tx ring for 5709. This fetaure is available on 2.6.27 kernel when using MSI-X.
Impact: 5709
2. Change: Added support for 57710 iSCSI in the CNIC driver.
v1.7.7b (July 9, 2008) ======================== Enhancements ------------ 1. Change: Added probe function so that the CNIC driver can get the pci_device pointer earlier before registration.
Impact: iSCSI.
2. Change: Added support for 5716.
Impact: None.
v1.7.6c (June 6, 2008) ======================== Enhancements ------------ 1. Change: Added multi-ring RX support on 5709 using MSI-X. This feature is only available on 2.6.24 and newer kernels running on SMP machines.
Impact: 5709.
2. Change: Added secondary unicast address support. We now support up to 5 unicast addresses. This feature is only available on 2.6.23 and newer kernels.
Impact: All chips.
v1.7.6b.1 (Aug 14, 2008) ======================== Fixes ----- 1. Problem: (CQ36808) VLAN tagged packets received by host stack without the VLAN tag.
Cause: If no VLANs are set up using vconfig, and if the driver configures the chip to strip the VLAN tag, the problem can happen. With IPMI or UMP enabled, the driver is likely to configure the chip to strip the VLAN tag.
Change: Modified the driver to re-insert the VLAN tag when necessary. I.e. when IPMI/UMP is enabled and vconfig has not setup any VLANs.
Impact: All chips receiving VLAN traffic.
v1.7.6b (May 29, 2008) ======================== Fixes ----- 1. Problem: IPv4 TSO generates bad packet when the TSO packet size is 1-MSS.
Cause: Probably firmware does not expect this boundary condition.
Change: Detect this 1-MSS condition in driver and skip the TSO logic. 1-MSS TSO packet will be treated like a regular TX checksum offload packet.
Impact: TSO on all chips.
2. Problem: Cannot disable VLAN stripping even when management firmware is disabled.
Cause: The new logic to check firmware VLAN stripping capability was buggy.
Change: Fixed the code so that VLAN stripping can always be disabled if management firmware is disabled.
Impact: VLAN/management firmware.
v1.7.5d (May 13, 2008) ======================== Enhancements ------------ 1. Change: Incorporated latest firmware 4.4.18. Bug fix is in RV2P.
Impact: All chips.
v1.7.5c (May 7, 2008) ======================== Enhancements ------------ 1. Change: Incorporated latest firmware 4.4.17. Bug fix is in RV2P.
Impact: All chips.
v1.7.5b (May 5, 2008) ======================== Fixes ----- 1. Problem: (CQ35080) Hard lock when running ethtool -s on the device that is in the down state.
Cause: I/O to the device to set link speed in D3-hot state can cause lockup because the chip does not respond to I/O.
Change: ethtool -s will just store the new settings without configuring the new speed. When the device is later brought up, the new speed will be set as part of chip init.
Impact: All chips.
2. Problem: (CQ35075 CQ35042) Various compile errors on SuSE SLES 9 and SLES 10 distro kernels.
Cause: ip_hdr() and __le32/__le32 backported to the distro kernels.
Change: Adjusted compatibility defines.
Impact: None.
Enhancements ------------ 1. Change: Incorporated latest 5709 firmware 4.4.16. Timer context scanning is reduced with this firmware to 500us. With this, the temporary enhancement in 1.7.4c #2 has been removed.
Impact: 5709 iSCSI.
v1.7.4e (April 26, 2008) ======================== Fixes ----- 1. Problem: (CQ34841) 5709 does not link up on some remote PHY systems.
Cause: No initial link interrupt.
Change: Added code to poll for link when remote PHY is present.
Impact: Remote PHY systems.
2. Problem: (CQ34767) Kernel panic on 5709 when using jumbo frames with NCSI traffic.
Cause: RV2P bug causing RX packets to overwrite kernel memory.
Change: Updated to latest RV2P code for 5709 and 5708.
Impact: 5706/5708/5709.
v1.7.4d (April 17, 2008) ======================== Fixes ----- 1. Problem: IPv6 iSCSI does not work.
Cause: Added code in the last version 1.7.3c to check for CONFIG_IPV6 before enabling the IPv6 CNIC support. This failed to check for CONFIG_IPV6_MODULE if IPv6 is configured as module in the kernel configuration.
Change: Changed the checking to CONFIG_IPV6 or CONFIG_IPV6_MODULE.
Impact: None.
v1.7.4c (April 16, 2008) ======================== Fixes ----- 1. Problem: (CQ34814, CQ33984) Driver does not compile on 2.4 kernels.
Cause: __le32 and __be32 not defined in 2.4 kernels.
Change: Defined these as u32 on 2.4 kernels.
Impact: 2.4 kernels.
Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.12 firmware to fix various iSCSI problems.
Impact: 5709.
2. Change: Slowed down the timer block reload time. It was noticed that after the CNIC driver was unloaded, the timer context memory was reloaded in a tight loop by the chip. This issue needs to be properly addressed in the firmware at a future date.
Impact: iSCSI.
v1.7.4b (April 11, 2008) ======================= Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.11 firmware to fix various iSCSI problems.
Impact: 5709.
v1.7.3k (April 9, 2008) ======================= Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.10 firmware to fix various iSCSI problems. CID ranges are now read directly from shared memory.
v1.7.3g (March 10, 2008) ======================= Enhancements ------------ 1. Change: Updated to latest 5709 firmware version 4.4.7.
Impact: 5709.
v1.7.3f (March 10, 2008) ======================= Fixes ----- 1. Problem: CNIC takes a long time to resolve ARP, causing iSCSI to fail.
Cause: NETEVENT_NEIGH_UPDATE event notifier sometimes takes a long time to be called.
Change: This is under investigation. For now, the workaround is to use the existing neighbour entry if it is in NUD_VALID state. Previously, we would only use it if it was in NUD_CONNECTED state.
Impact: iSCSI neighbour resolution.
2. Problem: iSCSI sometimes fails to initialize.
Cause: The KWQ is in full condition and prevents any KWQE to be sent to the firmware. This is caused by the KWQ consumer index in the status block not initializing to 0.
Change: Added workaround to skip the KWQ full condition check when sending the first KWQE. This should be properly fixed in firmware.
Impact: None.
v1.7.3d (February 15, 2008) ============================ Fixes ----- 1. Problem: System hangs with iSCSI traffic.
Cause: Infinite loop in NAPI poll.
Change: Fixed the problem of not comparing the CNIC tag properly when determining whether there is more work in NAPI poll.
Impact: None.
2. Problem: iSCSI does not work on 5709
Cause: Not initializing 5709 properly for iSCSI. The chip_id field was not propagated to the CNIC driver.
Change: Fixed the chip_id field.
Impact: None.
v1.7.3c (February 09, 2008) ============================ Enhancements ------------ 1. Change: Updated 5708 and 5709 firmware to version 4.4.2.
Impact: All devices.
2. Change: Updated RV2P firmware to the latest. This may fix the jumbo frame issue.
Impact: All devices, especially jumbo frames on 5709 Bx.
3. Change: Modified CNIC interface in preparation for 57710 devices.
Impact: iSCSI.
v1.7.2f (February 04, 2008) ============================ Fixes ----- 1. Problem: Temporary workaround for one prototype 5709S mezz. card not working.
Cause: The driver was looking at the wrong shared memory location to identify the card.
Change: Fixed the code to check the correct BNX2_SHARED_HW_CFG_CONFIG location.
2. Change: Added temporary workaround for one prototype 5709S mezz. card. The workaround will be removed once newer cards are available.
Impact: 5709S.
v1.7.1e (January 14, 2008) ============================ Enhancements ------------ 1. Change: Updated 5709 firmware to 4.1.1 for IPv6 iSCSI support.
Impact: 5709.
2. Change: Updated 5708 RXP firmware to 4.1.1.
Impact: 5706/5708.
3. Change: Updated RV2P firmware for 5709.
Impact: 5709.
4. Change: Added IPv6 support to CNIC driver.
Impact: New BNX2I driver must be used with this new CNIC driver.
v1.7.1d.3 (February 7, 2008) ============================ Fixes ----- 1. Problem: 5706S continues to not link down occasionally on some blade systems.
Cause: In some cases, even turning off the tx current does not cause the link to go down.
Change: Link transition can be triggered based on the SYNC_FAILED bit in the AN_DEBUG register when all else fails.
Impact: 5706S.
v1.7.1d.1 (February 1, 2008) ============================ Fixes ----- 1. Problem: 5706S still not linking down occasionally on some blade systems when the switch blade is disconnected.
Cause: Occasionally, all the bits that we check will falsely indicate link up and trigger the parallel detect logic on this blade platform. Once in parallel detect mode with autoneg disabled, the driver will never detect link down.
Change: Disabled parallel detect on this platform by checking PCI sub IDs to identify the device.
Impact: Parallel detect not supported on this vendor device.
v1.7.1d (January 25, 2008) ============================ Fixes ----- 1. Problem: 5706S still not linking down on some blade systems when the switch blade is disconnected.
Cause: This is the same problem that was fixed in 1.7.0b. After switch module is removed, the SYNC_FAILED bit sometimes toggles low, and this causes the parallel detect logic in the driver to trigger and disable autoneg. Disabling autoneg causes false link to come up immediately.
Change: It seems that the RUDI_INVALID bit can be used to prevent the above from happening. Modified parallel detect code to additionally check the RUDI_INVALID bit and trigger only when the bit is cleared.
Impact: Parallel detect logic in 5706S.
v1.7.1c (December 27, 2007) ============================ Fixes ----- 1. Problem: Driver crashes when adding VLAN and bonding.
Cause: Bonding calls driver's VLAN function in interrupt context with lock held. We recently added a VLAN feature in 1.6.8b which requires chip reset when VLANs are added or removed. The reset will call vmalloc/vfree which must not be called in interrupt context.
Change: Reverted the VLAN feature for now. Will workaround it in the future.
Impact: 5709 only. This new VLAN feature is no longer available.
v1.7.1b (December 24, 2007) ============================ Fixes ----- 1. Problem: Driver crashes when using jumbo frames on 5709 A1.
Cause: RV2P firmware problem.
Change: Disabled jumbo page ring on 5709 Ax chips.
Impact: Jumbo receive page rings not supported on 5709 Ax.
2. Problem: CNIC driver prints "Failed waiting for ref count to go to zero" when unloading the driver. This is a minor cosmetic issue.
Cause: Minor bug in driver comparing ref_count to 1 instead of zero during exit.
Change: Fixed the code to check for ref_count == 0.
Impact: None.
v1.7.0b (December 12, 2007) ============================ Fixes ----- 1. Problem: (CQ33032) CPU utilization increases dramatically when TSO is enabled.
Cause: Driver is spending a lot of unnecessary time in TX handling code when TSO is enabled. This regression was introduced when the TX handling code was changed to match the RX handling code. The RX handling code was changed to fix a packet rot problem. When TSO is enabled, the tx index can stop at non-packet boundaries and the code will keep waiting until it gets to the next packet boundary.
Change: Fixed it to handle this condition properly.
Impact: None.
2. Problem: 5706S does not link down in some blade systems.
Cause: Hardware problem.
Change: Added workaround logic to check periodically and force a link down when the PHY reports SYNC status failed. This only works when autoneg is enabled.
Impact: 5706S.
v1.6.8e (December 10, 2007) ============================ Fixes ----- 1. Problem: When using jumbo MTU with large RX ring sizes, system will crash or the driver won't load.
Cause: Bug in driver where the page descriptor array was declared too small.
Change: Fixed the array size.
Impact: None.
2. Problem: CNIC driver won't compile on kernels without CONFIG_PCI_MSI.
Cause: Some code needs to be conditionally compiled only when CONFIG_PCI_MSI is set.
Change: Added #ifdef CONFIG_PCI_MSI where necessary.
Impact: None.
3. Change: Disabled iSCSI on 5709 until next release.
Impact: None.
v1.6.8d (December 07, 2007) ============================ Change: Reverted the 5706S workaround made in 1.6.8c because it was unreliable.
Cause: RV2P firmware incorrectly placed jumbo data into SKB.
Change: New RV2P firmware.
Impact: Jumbo frames on all hardware.
2. Problem: (CQ32817) ethtool loopback test fails. 3. Problem: (CQ32842) Chariot test fails.
Cause: RX buffer size too small to contain MTU-sized frame. This was introduced by the new Jumbo RX logic.
Change: Fixed RX buffer size logic.
Impact: Traffic on all hardware.
4. Problem: (CQ32862) Fails to compile on RH9u9.
Cause: Kernel API skb_fill_page_desc() backported to RH kernel causing duplicate definition.
Change: Adjusted compatibility code.
Impact: None.
5. Problem: (CQ32866) ISCSI driver fails to compile with 1.6.8b.
Cause: print_mac() multiply defined when bnx2.h is included in the bnx2i driver.
Change: Changed print_mac() to static inline.
Impact: None.
6. Problem: 5706S does not link down in some blade systems.
Cause: Hardware problem.
Change: Added workaround logic to check periodically.
Impact: 5706S.
Enhancements ------------ 1. Change: Added flow control logic on 5709.
Impact: 5709.
2. Change: Updated all firmware to 4.0.5.
Impact: All hardware.
v1.6.8b (November 28, 2007) ============================ Enhancements ------------ 1. Change: Added MSIX support for 5709 B0.
Impact: 5709 B0.
2. Change: Added multi-page buffer support for Receive Jumbo frames.
Impact: All chips. This feature is experimental at this point.
3. Change: Allow VLAN tags in receive packets when management firmware is enabled.
Impact: 5709 only. This feature is experimental and requires new boot code and UMP/IPMI code.
4. Change: Updated firmware to 4.0.3.
Impact: All chips.
v1.6.7b (October 16, 2007) ============================ Fixes ----- 1. Problem: (CQ31861) Remote copper PHY does not link up if WoL is enabled.
Cause: bnx2_set_power_state() assumes that only copper devices support WoL and proceeds to configure the copper PHY to 10/100 Mbps. This assumption is no longer valid after Serdes WoL support was added in 1.6.3c.
Change: Fixed the code to take check for Serdes and copper when setting up the PHY for WoL.
v1.6.5b (September 25, 2007) ============================ Fixes ----- 1. Problem: (CQ30086) 5709 A1 does not link up when connected to some Broadcom devices.
Cause: Early DAC wakeup workaround needed for 5709 A1.
Change: Added workaround.
Impact: None.
Enhancements ------------ 1. Change: Added CNIC support for iSCSI.
Cause: Link test and loopback test were not modified to support remote PHY.
Change: Added remote PHY support to link test and changed the code to skip PHY loopback on remote PHY since it's not supported.
Impact: None.
2. Problem: (CQ30625) ethtool speed settings are lost after ifdown.
Cause: The remote PHY settings stored in firmware is not the same as the driver's last setting.
Change: Modified the code to keep the driver's setting unless there's is change in the remote PHY media.
Impact: ethtool -s on remote PHY systems.
Enhancements ------------ 1. Change: Change ethtool's wol setting to NVRAM's default and add support for Serdes WoL if NVRAM supports it.
Impact: ethtool wol's default setting.
v1.6.3b (July 13, 2007) ======================= 1. Problem: Problems reading and writing flash on 5709.
Cause: Hardware changes in 5709.
Change: Rearranged current flash code to properly support 5709.
Impact: Changes will impact flash operations on 5706/5708/5709 devices.
2. Problem: (CQ30516) Management firmware version string disappears on 2nd modprobe of the driver.
Cause: The 2nd modprobe will program the device back to D0 from D3hot. This causes a reset and it will take some time before the management firmware information will be available.
Change: Added a proper wait loop to wait for the firmware information to be deposited in shared memory.
Impact: None.
v1.6.2f (July 3, 2007) ======================= 1. Problem: The fix for CQ29488 in the previous version is problematic and needs to be reverted.
Cause: Adding the netif_carrier_off() call before register_netdev() in bnx2_init_one() can cause problems if register_netdev() fails. netif_carrier_off() can queue a link watch event that can run later. If register_netdev() fails, the netdev structure will be freed and the link watch event may panic when it is scheduled to run.
Change: Moving the netif_carrier_off() to after register_netdev() also will not work as it can cause race conditions with the interrupt handler. So the best thing to do is to revert the earlier fix and not address the CQ29488 issue.
Impact: CQ29488 is not fixed.
v1.6.2e (July 3, 2007) ======================= Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY (continued).
Cause: ifup script may be using mii-tool to obtain link status, and interfering with remote PHY firmware.
Change: Block mii-tool ioctl access when remote PHY firmware is present.
Impact: None.
2. Problem: (CQ29488) Driver reports link up in ethtool before the interface is brought up.
Cause: The netdevice structure's initial link setting is up and that gets reported directly by ethtool.
Change: Added netif_carrier_off() call in bnx2_init_one().
Impact: None.
v1.6.2d (June 22, 2007) ======================= Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY.
Cause: The fix in 1.6.2b still has a problem. The copper or Serdes default link setting does not follow the correct port when the port is changed during chip reset.
Change: Fix the code to always refresh the port and link setting during chip reset.
Impact: None.
2. Problem: (CQ30181) Cannot compile on 2.4 kernels.
Cause: USEC_TO_SEC constant is not defined on older kernels.
Change: Added conditional #define for this constant on older kernels.
Impact: None.
Enhancements: ------------- 1. Change: Update 5709 firmware to 3.7.1.
Impact: 5709 devices.
v1.6.2b (June 21, 2007) ======================= Enhancements: ------------- 1. Change: Added management firmware version to ethtool -i.
Impact: None.
Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY.
Cause: The driver is using the wrong port when setting up the remote PHY link.
Change: Fixed bug to always use the correct requested port or default port when setting remote PHY link.
Impact: None.
2. Problem: (CQ30028) Advertised Autoneg not set in ethtool.
Cause: Remote PHY code is not setting the flag which is for information only.
Change: Added code the set the flag for consistency.
Impact: None.
v1.6.1c (May 22, 2007) ===================== Enhancements: ------------- 1. Change: (CQ28907) Added support for setting copper and fibre speeds.
v1.5.10c (May 4 , 2007) ======================= Fixes: ------ 1. Problem: Extremely low TSO performance when destination has a smaller MSS than the source.
Cause: Packets smaller than MTU are not processed as TSO packets.
Change: Removed the SKB length check when doing TSO.
Impact: None.
v1.5.10b (May 1, 2007) ========================= Enhancements: ------------- 1. Change: Removed Remote PHY until next release.
Impact: No Remote PHY support.
2. Change: Added check for 2.5G capability before enabling 2.5G on 5709S.
Impact: None.
Fixes: ------ 1. Problem: (CQ28438) NETDEV WATCHDOG after OS boot.
Cause: The mailbox queue is halted after the OS reads config. register 0x94.
Change: Set MQ_CONFIG_HALT_DIS in register MQ_CONFIG on 5709 A0 and A1.
Impact: None.
v1.5.9b (April 20, 2007) ======================= Enhancements: ------------- 1. Change: Enhanced remote PHY support for 5708S.
Impact: None.
Fixes: ------ 1. Problem: (CQ29056) Driver does not compile on SLES 10 SP1 kernel.
v1.5.1b (November 15, 2006) =========================== Enhancement: ------------ 1. Change: Added support for 5709.
Impact: None.
v1.4.52c (March 07, 2007) ========================= Enhancement: ------------ 1. Change: Increase maximum receive ring size to 4080. The default is kept the same at 255.
Impact: None.
v1.4.51b (December 21, 2006) ============================ Fixes: ------ 1. Problem: (CQ27802) Cannot enable flow control in some cases.
Cause: In some cases when flow control is forced to on, the driver detects no changes in advertisement, and as a result, will not re-autoneg. Without the link change, flow control settings will not change.
Change: Added some code to setup flow control when no other PHY settings are made. This will ensure that flow control changes will take effect immediately.
Impact: None.
v1.4.50b (December 15, 2006) ============================ Fixes: ------ 1. Problem: (CQ27424) Panic when writing to nvram.
Cause: Bug in driver when an alignment buffer is used
Change: Fixed the bug so that the alignment buffer is freed with the correct pointer.
Impact: None.
v1.4.49b (December 13, 2006) ============================ Fixes: ------ 1. Problem: (CQ27459) Driver reports link down when link is up.
Cause: Hotplug scripts can cause bnx2_open() to be called immediately after bnx2_init_one() calls register_netdev(). The initial link state set after register_netdev() may overwrite the actual link state set by the link handler on SMP systems.
Change: Move all initial state setup code to before calling register_netdev().
Cause: Bug in determining tx ring space when the tx ring is completely full.
Change: Fixed the flawed logic in bnx2_tx_avail().
Impact: None.
2. Problem: (CQ27424) Buffer overflow when writing to nvram.
Cause: Bug in driver when the beginning NVRAM offset is not 4-byte aligned.
Change: Fixed the bug to allocate enough buffer space.
Impact: None.
3. Problem: (CQ27543) Loopback failed if MAC address is changed.
Cause: Driver uses permanent MAC address for loopback which may be different from a locally administered address.
Change: Fixed by alwaysing using the current MAC address in the netdevice structure.
Impact: None.
v1.4.47b (November 02, 2006) =========================== Fixes: ------ 1. Problem: (CQ25922) 5708S does not pass PHY loopback test on some blade servers.
Cause: It takes longer (about 100msec) to link up in some backplane environments when the Serdes is set to PHY loopback mode.
Change: Increase delay loop to up to 1 sec when waiting for link up after PHY loopback. Previous wait time was 100usec.
Impact: None.
v1.4.46b (October 30, 2006) =========================== Fixes: ------ 1. Problem: (CQ25916) Device does not receive packets when configured by the Xen bridge script and when IPMI is enabled.
Cause: Firmware does not forward packets to the host when the device is in promiscuous mode in some cases.
Change: Firmware change and driver change to enable the BNX2_RPM_SORT_USER0_PROM_VLAN bit when going into promiscuous mode.
Impact: None.
v1.4.45b (October 19, 2006) =========================== Enhancement: ------------ 1. Change: Added software parallel detection on 5708S to link at 1000Mbps or 2500Mbps automatically if the link partner is forced at 2500Mbps.
Impact: None.
2. Change: Added 2500Mbps forced speed setting. Setting it requires a future version of ethtool or custom apps.
Impact: None.
3. Change: Port driver to compile on 2.6.19 kernel.
Impact: None.
Fixes: ------ 1. Problem: Driver does not complile on 2.4 kernels.
Cause: TSO symbols not defined in 2.4 kernels.
Change: Added #ifdef for compatibility.
Impact: None.
2. Problem: MSI doesn't work on 5706 when the host bridge is AMD8132.
Cause: Compatibility issue.
Change: Added code to disable MSI when 5706 is on a systems with AMD8132.
Impact: 5706 cannot use MSI on such systems.
v1.4.44b (August 10, 2006) ========================== Fixes: ------ 1. Problem: A rare tx race window exists in the tx path.
Cause: CPU re-ordering can cause the tx queue to be stopped forever when the tx ring is full in a very rare condition. See ChangeLog for more details.
Change: Fixed the race condition with memory barriers. See ChangeLog for more details.
Impact: None.
Enhancement: ------------ 1. Change: Increase default rx ring size to 255 to prevent packet drops under heavy load.
Impact: Higher memory usage.
2. Change: Port driver to run on 2.6.18 kernel.
Impact: None.
v1.4.43b (June 26, 2006) ======================= Enhancement: ------------ 1. Change: (CQ25508) Use DRV_MSG_CODE_UNLOAD_LNK_DN message on 5708 B1 and older chips so that the link will turn off after ifdown.
Impact: None.
v1.4.42b (June 2, 2006) ======================= Fixes: ------ 1. Problem: (CQ22585) WoL cannot be enabled on 5708 B2.
Cause: Hardware limitation in previous 5708 versions required driver to always disable driver WoL on 5708.
Change: With the issue fixed in B2, the driver was changed to allow 5708 B2 and above to support driver WoL.
Impact: None.
2. Problem: (CQ21779) Driver does not report dropped receive packets.
Cause: Packets dropped by firmware are reported in a scratch pad location in memory separate from other counters.
Change: Added code to report this firmware counter.
Impact: None.
Enhancements: ------------- 1. Change: (CQ24690) Allow driver to be compiled for non-running kernels.
Impact: None.
v1.4.41b (May 17, 2006) ======================= Fixes: ------ 1. Problem: Driver writes wrong data to non-buffered flash.
Cause: Bug in driver causing the unchanged portion of the page to be corrupted.
Change: Fixed bug.
Impact: None.
v1.4.40b (April 17, 2006) ========================= Enhancements: ------------- 1. Change: Combine 2 small memory allocations into 1.
Impact: None.
2. Change: Separate tx consumer and producer entries into separate cache lines for better performance.
Impact: None.
3. Change: Compress firmware data to reduce driver size.
Impact: Driver now requires zib_inflate library which should be available on most vendor kernels.
v1.4.39b (Mar. 10, 2006) ======================= Fixes: ------ 1. Problem: (CQ23181) Driver loses track of link changes in some cases.
Cause: In some cases, the status block gets a link change indication that contradicts with the MII link status. This is due to transient link signals during link changes.
Change: Add coalesce_now at the end of link change interrupt to flush out the transient behavior.
Impact: None.
2. Problem: 5708 only supports 40-bit DMA addresses.
Cause: Limitation of the built-in PCIE-to-PCIX bridge.
Change: Add workaround code to make sure all DMA addresses are less than 40 bits.
Impact: Some minor impact on performance on some 64-bits systems. There should be practically no performance impact on i386 and x86_64 systems.
3. Problem: "Copyright" deprecated in RPM spec file.
Change: Changed to "License".
Impact: Should be none on the distributions that we support.
v1.4.38b (Feb. 10, 2006) ======================= Fixes: ------ 1. Problem: Setting rx ring size to 255 causes memory allocation errors.
Cause: Multiple bugs that do not handle the full ring properly.
Change: Fixed all bugs related to full ring handling and changed maximum ring size from 4080 to 1020 after discussion with Dave Miller.
Impact: Maximum rx ring size is now smaller.
2. Problem: Compile warnings and panic on IA64.
Cause: not included.
Change: Added include .
Impact: None.
v1.4.36b (Jan. 19, 2006) ======================= Version number update.
v1.3.36 (Jan. 17, 2006) ======================= Fixes: ------ 1. Problem: (CQ22827) bnx2 does not compile on 2.6.6 and earlier kernels.
Cause: Introduced bug while fixing CQ22666.
Change: Fix compatibility code.
Impact: None.
2. Problem: (CQ22823) bnx2 reports extra .5 at the end of firmware version string.
Change: Skip the last digit in the firmware version string.
Impact: None.
3. Problem: (CQ22585) WoL still does not work on 5708.
Cause: New WoL mechanism introduced in 1.3.34 has a flaw.
Change: Removed the workaround code and disabled WoL support on 5708. During shutdown and suspend, the driver will shutdown the device and WoL will be setup by the bootcode according to the nvram's out-of-box WoL setting.
Impact: 5708 will not support driver-initiated (ethtool-intiated) WoL.
v1.3.35 (Jan. 17, 2006) ======================= Fixes: ------ 1. Problem: (CQ22666) bnx2 driver does not compile on RHEL3 U7.
Cause: if_mii() back-ported to RHEL3 U7.
Change: Adjusted the compatibility code.
Impact: None.
2. Problem: (CQ22718) UMP connection is lost after enabling WoL.
Cause: FORCE LINK was mistakenly set during WoL setup.
Change: Do not set FORCE LINK.
Impact: None.
v1.3.34 (Jan. 13, 2006) ======================= Fixes: ------ 1. Problem: (CQ22585) WoL does not work on 5708.
Cause: Internal bridge not in proper PME state.
Change: Added new firmware message to allow bootcode to help set up WoL.
Impact: None.
Enhancements: ------------- 1. Change: Added compile option to include crc32 function for RH2.4 boot kernels.
Impact: None.
2. Change: Updated TSO firmware to handle ECN.
Impact: None.
v1.3.33 (Dec. 12, 2005) ======================= Enhancements: ------------- 1. Change: Increased firmware hand-shake timeout from 50 msec to 100 msec. Also changed the delay from busy-wait udelay to non-busy-wait msleep.
Impact: None.
2. Change: Added code to read nvram size from shared memory if available. Otherwise, the size will come from the flash table which only gives the smallest size for that type of flash.
Impact: None.
3. Change: Added workaround to issue 2 separate IOs for interrupt acknowledgement. The workaround is only used for INTA (non-MSI) interrupts.
Impact: Slightly higher overhead for INTA interrupts.
v1.3.32 (Dec. 01, 2005) ======================= Enhancements: ------------- 1. Change: Added PHY loopback to the loopback selftest.
2. Change: Enabled customized pre-emphasis and other serdes control settings on 5708S backplane devices. A special PHY register will be programmed according to the NVRAM value.
Impact: None.
3. Change: Modified Makefile to check for the source symbolic link in the kbuild environment.
Impact: None.
4. Change: Improved NAPI poll processing so that all events will be processed before interrupts are re-enabled. This will reduce the number of unnecessary interrupts.
Impact: None.
5. Change: Add support for ETHTOOL_GPERMADDR (from John Linville)
Impact: None.
Fixes: ------ 1. Problem: Bug in irq handler causing extra register read.
Cause: Bug in bnx2_interrupt() reading BNX2_PCICFG_MISC_STATUS register when it is not necessary.
Change: Fixed the logic bug and added prefetch of status block in msi handler.
Impact: None.
v1.3.25 (Aug. 22, 2005) ======================= Fixes: ------ 1. Problem: Ethtool register and memory tests fail on 5708.
Cause: Some code was not merged properly many versions ago.
Change: Merged in properly code.
Impact: None.
Enhancements: ------------- 1. Change: Slow down flash clock speeds
Impact: None.
2. Change: Code re-sync'ed with upstream driver.
Impact: None.
v1.3.24 (Aug. 16, 2005) ======================= Enhancements: ------------- 1. Change: Changed all spin_lock_irqsave locks to spin_lock_bh for better overall system performance. All code requiring spin_lock runs in BH or user context.
Impact: None.
2. Change: Removed atomic operations in the transmit fast path. Code should run a bit faster as atomic operations can be quite slow.
Impact: None.
v1.3.23 (Aug. 10, 2005) ======================= Enhancements: ------------- 1. Change: Added reporting of link speed to firmware.
Impact: None.
2. Change: Added shared memory base look-up.
Impact: None.
3. Change: Possible sparse fixes (from Peter Hagervall) - use C99 struct initializers - make a few arrays and structs static - remove a few uses of literal 0 as NULL pointer - use convenience function instead of cast+dereference in bnx2_ioctl() - remove superfluous casts to u8 * in calls to readl/writel
Impact: None.
4. Change: Updated documentation with the crc32 library requirement and other minor updates.
Impact: None.
v1.3.22 (July 25, 2005) ======================= Enhancements: ------------- 1. Change: Added check for default link speed setting in shared memory. This allows some blade servers that don't support autoneg to default to forced speed to speed up link-up time.
Impact: None.
2. Change: Changed timer code to speed up the timer after serdes autoneg. This speeds up the time for parallel detection when the link partner does not autoneg. After autoneg or parallel detction completes, timer goes back to normal 1 HZ interval. With the new scheme, link should be detected up using parallel detection in less than 0.7 seconds. Autoneg normally completes in 120 msec exchanging base pages and 3 next pages.
Impact: None.
v1.3.21 (July 21, 2005) ======================= Enhancements: ------------- 1. Change: Updated firmware to properly handle TSO packets with ECN bits set.
Impact: None.
2. Change: Updated to latest rxp firmware.
Impact: None.
3. Change: Added check for the 2.5G capability in shared memory.
Impact: None.
4. Change: Expanded nvram support for 5708.
Impact: None.
Fixes: ------ 1. Problem: (CQTO1511) Downing a team of bnx2 adapters causes hang.
Cause: Deadlock when the second adapter's close routine calls flush_scheduled_work() because the linkwatch_event is scheduled on the work queue when the first adapter is closed. The linkwatch_event will try to get the rtnl_lock which is already held by the bnx2_close routine.
Change: Fixed by not calling flush_scheduled_work(). Instead, use a flag to indicate work is pending and wait until the flag is cleared.
Impact: None.
2. Problem: (CQTO1439) ethtool -S on 5708 causes oops.
Cause: A pointer is not initialized if the device is 5708.
Change: Added proper initialization.
Impact: None.
3. Problem: Some error counters are mis-reporting.
Cause: The workaround for the hw errata is not applied properly on the chips with the errata.
Change: Added proper checks for the workaround.
Impact: None.
4. Problem: High BER on 5708 SerDes.
Cause: hardware errata.
Change: Added workaround for 5708 A0 and B0.
Impact: None.
v1.3.19 (May 27, 2005) ======================= Enhancements: ------------- 1. Change: Merged 5708 code with the latest 1.1.19.
Impact: None.
Fixes: ------ 1. Problem: (CQTO1260) 5708S does not link at 1000Mbps when forced. It links at 2500Mbps when connected back-to-back with another 5708S.
Cause: 2.5G bit is still turned on.
Change: Fixed by turning off 2.5G when the speed is forced.
Impact: None.
v1.1.19 (May 26, 2005) ======================= Enhancements: ------------- 1. Change: Made significant changes to merge into the kernel. Among them, consolidate all source files into bnx2.[ch] and bnx2_fw.h, change structure style register definitions to offset based.
Impact: None.
Fixes: ------ 1. Problem: Excessive stack usage.
Cause: Use of local variable array.
Change: Fix excessive stack usage in bnx2_alloc_bad_rbuf() by replacing local variable array with kmalloc array. Also changed function to return error code, and changed some of the callers to check for the return code.
Impact: None.
2. Problem: Bug in receive checksum.
Cause: Software bug.
Change: Fix bug in rx checksum by indicating CHECKSUM_UNNECESSARY only when the hw calculated checksum is 0xffff.
Impact: None.
3. Problem: Excessive busy loop.
Cause: Software bug.
Change: Replaced one excessive udelay of 15msec with msleep since the calling context is always process.
Impact: None.
4. Problem: Need to call flush_scheduled_work() and bnx2_netif_stop().
Cause: Bug in bnx2_close().
Change: Fix bug in bnx2_close() by calling flush_scheduled_work() since we are using a work queue in netdev watchdog. Also added bnx2_netif_stop() call in bnx2_close().
Impact: None.
5. Problem: Some symbols do not have bnx2 prefix and are not static.
Change: Add bnx2_ prefix to some remaining names and mark some remaining names static.
Impact: None.
v1.1.17 (Apr. 7, 2005) ======================= Fixes: ------ 1. Problem: Driver does not compile on 2.6.12 kernel.
Cause: pci_dev->slot_name has been deprecated.
Change: replaced with pci_name.
Impact: None. All kernels supported by bnx2 including 2.4.21-*EL have pci_name defined.
v1.1.16 (Mar. 16, 2005) ======================= Fixes: ------ 1. Problem: (CQTO936 & 1004) Tx carrier and rx_byte_errors reported during normal operations.
Cause: 5706 hardware errata on these 2 statistics counters.
Change: Modified driver to skip these 2 counters.
Impact: These 2 counters will always report 0 and not the true statistics.
v1.1.15 (Mar. 09, 2005) ======================= Enhancements: ------------- 1. Change: Added code to program proper phy settings for jumbo frames on copper and serdes devices.
Impact: None.
2. Change: Changed INTx ISR to handle a valid case where INTx arrives before status block update.
Impact: None.
3. Change: Added a separate ISR for MSI to handle subtle differences between INTx and MSI.
Impact: None.
v1.1.14 (Mar. 03, 2005) ====================== Fixes: ------ 1. Problem: netdump does not work on latest RH3EL errata kernel.
Cause: #define RED_HAT_LINUX_KERNEL removed from kernel include files, causing netdump poll function to be compiled wrong for RH kernels.
Change: Changed Makefile to workaround the problem.
Impact: None.
v1.1.12 (Feb. 25, 2005) ====================== Fixes: ------ 1. Problem: (CQTO1062) Driver allows ethtool to set illegal speed/duplex on fiber cards.
Cause: Missing checks for the case where autoneg is off.
Enhancements: ------------- 1. Change: The code to handle tx queue full condition was redone to properly handle all boundary and race conditions.
Impact: Minimum tx ring size is now MAX_SKB_FRAGS+1.
2. Change: Tx timeout code was changed to work queue context. This allows netif to be shutdown gracefully before chip reset.
Impact: None.
3. Change: Added memory barriers to ISR and NAPI poll for correctness.
Impact: None.
v1.1.8 (Feb. 01, 2005) ====================== Fixes: ------ 1. Problem: (CQTO969) No interupts on a system that does not support MSI.
Cause: On this system, the MSI generated in the MSI test terminates with Master Abort which is a fatal condition for the chip.
Change: A chip reset is added when MSI test fails to bring the chip back to normal operations again (in INTx mode).
Impact: None.
Enhancements: ------------- 1. Change: Removed register 0x84 from the ethtool register test. This is an interrupt control register that should not be touched to prevent unwanted interrupts.
Impact: None.
v1.1.7 (Jan. 28, 2005) ====================== Enhancements: ------------- 1. Change: Added interrupt test when MSI is enabled. If MSI test fails, driver will fallback to INTx mode.
Impact: None.
2. Change: Added test for certain chipsets where MSI is known to fail, and disable MSI unconditionally when such chipsets are found.
Impact: None.
3. Change: Removed support for 1000 Mbps half duplex.
Impact: 1000 Mbps half duplex will no longer work.
v1.1.6 (Jan. 26, 2005) ====================== Fixes: ------ 1. Problem: (CQTO940) MTU size not set properly when device is down.
Cause: bnx2_change_mtu only handled the "up" case.
Change: Simple fix to handle the "down" case as well.
Impact: None
2. Problem: (CQTO926) 5706S does not autoneg properly after the tx cable is pulled.
Cause: If the link partner is autonegotiating, autoneg will fail when the tx cable is pulled. The software will turn off autoneg seeing that the rx cable is still attached with SIGNAL_DETECT. When the tx cable is re-attached, autoneg is still off and the link partner will not establish link.
Change: Added code to poll another PHY register to check if configs are received when autoneg is disabled.
Impact: None
Enhancements: ------------- 1. Change: Added OEM product name strings.
Impact: None.
v1.1.5 (Jan. 25, 2005) ====================== Fixes: ------ 1. Problem: PCI-X bus speed may not be detected correctly by the driver, causing failure because certain register settings are done based on bus speed.
Cause: hardware problem.
Change: Use a different register to detect PCI-X speed.
Impact: None.
v1.1.4 (Jan. 17, 2005) ====================== Fixes: ------ 1. Problem: 5706S does not reliably detect link up or down.
Cause: hardware problem.
Change: Enabled hardware workaround which is effective in A2 and newer chips only.
Impact: None.
v1.1.3 (Jan. 13, 2005) ====================== Fixes: ------ 1. Problem: netdump does not work.
Cause: poll_controller routine does not work in NAPI mode.
Change: Fixed poll_controller routine for NAPI mode.
Impact: None.
Enhancements: ------------- 1. Change: Added the new mmiowb macro which is used mainly in NUMA machines to guarantee PCI ordering.
Impact: None.
2. Change: Added OEM product name strings.
Impact: None.
3. Change: Changed ONE_TDMA workaround on systems with P64H bridge to PING_PONG_DMA on all systems using PCI.
Impact: Better performance and better compatibility on all PCI systems.
4. Change: Added "disable_msi" parameter to allow disabling MSI.
Impact: None.
5. Change: Reduced default tx coalescing parameters for better tx only performance such as ttcp.
Impact: None.
6. Change: Changed NIC detection console message to display more information.
Impact: None.
7. Change: Cleaned up some Linux .h files that are not needed.
Impact: None.
8. Change: Cleaned up the nvram routines.
Impact: None.
v1.1.2 (Nov. 11, 2004) ====================== Fixes: ------ 1. Problem: Unable to load the driver on more than 2 or 3 devices.
Cause: Default register space is too big. System fails to map the register space on the 3rd or 4th device.
Change: Changed driver to map a smaller register space as the higher registers are not needed for standard operations.
Impact: None.
v1.1.1 (Nov. 9, 2004) ====================== Fixes: ------ 1. Problem: (CQTO656) One remaining ethtool parameter can be set out of range.
Cause: Wrong upper bounds in code.
Change: Fixed upper bound.
Impact: None.
1. Problem: 5706 A1 cannot be run on a PCI bus.
Cause: Hardware errata.
Change: Added workaround to detect 5706 A1 on PCI bus and abort.
Impact: Driver will not load 5706 A1 on PCI bus.
v1.1.0 (Oct. 29, 2004) ====================== Fixes: ------ 1. Problem: (CQTO663) No link on fiber NIC set to autoneg when the link partner is set to forced speed.
Cause: No code to handle this case.
Change: Added code to check SIGNAL DETECT when autoneg fails, and turn off autoneg when appropriate. Also added code to force a link down when speed settings are changed.
Impact: None.
2. Problem: (CQTO649) ifconfig up/down can cause system to hang on 2.6 kernels using mmconfig.
Cause: Dummy read in the kernel's pci_mmcfg_write routine may cause system to hang during D3hot -> D0 transition. The PLL may lose lock during the internal D0 transition chip reset and cause the dummy read to hang.
Change: The PLL problem will be fixed in A2. Meanwhile, the driver is changed to go into D3hot only if wol is enabled.
Impact: Minor impact in increased power consumption when the driver is shutdown with wol disabled.
3. Change: Changed to use pci_get_device as pci_find_device will be deprecated soon.
Impact: None.
4. Problem: (CQTO656) Some ethtool parameters can be set out of range.
Cause: Wrong upper bounds in code or documentation.
Change: Fixed code and documentation.
Impact: None.
v1.0.15 (Oct. 15, 2004) ====================== Fixes: ------ 1. Problem: (CQTO644) Data corruption when sending FTP traffic on Dell Precision 530MT.
Cause: PCI bridge errata.
Change: Added code to enable ONE_TDMA workaround when P64H PCI bridge is detected.
Impact: Slower tx performance on systems using P64H bridge.
2. Problem: (CQTO643) Driver allows MTU to be set up to 9004.
Cause: Driver used the wrong upper bound limit.
Change: Fixed the upper bound.
Impact: None.
3. Problem: Driver does not support forced speed on 5706S.
Cause: Missing software logic.
Change: Added code to support forced 1000 Full and Half duplex.
Impact: None.
4. Change: Added workaround to disable PERR generation on 5706 A1 when it is in PCI 64-bit slot.
Impact: None.
v1.0.14 (Oct. 05, 2004) ====================== Fixes: ------ 1. Problem: Driver load/unload hangs on some machines.
Cause: Transition delay required during D3hot -> D0 transition.
Change: Added necessary delay.
Impact: None.
v1.0.12 (Oct. 04, 2004) ====================== Fixes: ------ 1. Problem: (CQTO609) New flow control parameter does not take effect until ifdown/ifup or link down/up.
Cause: New flow control settings are only configured during link up. The driver did not check flow control advertisement changes and therefore no re-negotiation and no link down.
Change: Fixed logic so that link will always go down whenever there is a change a flow control advertisement.
Impact: None.
2. Problem: (CQTO612) VLAN packet reception not working.
Cause: VLAN #define not setup properly.
Change: Fixed #define for VLAN.
Impact: None.
3. Problem: (CQTO628) WoL not functioning correctly.
Cause: Multiple problems in the WoL code.
Change: Fixed by: 1. using sort mode. 2. setting up mac address correctly.
Impact: None.
Enhancements: ------------- 1. Change: Added support for non-dword and non-aligned write access to eeprom, allowing ethtool -E to work.
Impact: None.
v1.0.11 (Sep. 24, 2004) ====================== Fixes: ------ 1. Problem: (CQTO600) Kernel panic when attempting to ftp on Fedora kernel.
Cause: skbuffs are 4-byte aligned on Fedora, causing the rx headers to be misaligned. skbuffs are 16-byte aligned on other standard kernels.
Change: Removed any assumptions about skbuff alignment and added code to align all rx skbuffs to 8-byte boundaries.
Impact: None.
Enhancements: ------------- 1. Change: Added netif_carrier_off to Driver init code so that the initial link state is off.
Impact: None.
v1.0.10 (Sep. 23, 2004) ====================== Fixes: ------ 1. Problem: (CQTO599) Driver fails to compile on RH 3.0ES.
Cause: Bug in poll_bcm5706 where bp is referenced without being defined.
Change: Fixed the minor bug.
Impact: None.
v1.0.9 (Sep. 23, 2004) ====================== Fixes: ------ 1. Problem: Jumbo frames not working reliably.
Cause: Bug in bcm5706_reuse_rx_skb.
Change: Fixed the bug so that the host address is properly copied from one BD to the other.
Impact: None.
Enhancements: ------------- 1. Change: Change the locking scheme for more reliable open/close/ioctl operations where the spinlock is needed.
Impact: None.
2. Change: Added minimum MTU size check for MTU changes.
Impact: None.
v1.0.8 (Sep. 20, 2004) ====================== Fixes: ------ 1. Problem: (CQTO561) Kernel panic on RH30EL after repeated driver load/unload.
Cause: Occasionally, the system is unable to map device registers, causing subsequent register access to fail.
Change: Added check for the return value from ioremap, and exit gracefully if it fails.
Impact: None.
2. Problem: (CQTO574) NETDEV WATCHDOG when running 5706 A1 on PCIX 133MHz slot.
Cause: Some hw register setup required for 133 Mhz.
Change: Added the register setup code.
Impact: None.
3. Problem: (CQTO468) Link does not go down after changing from 10Mbps full (forced) to 10Mbps half (forced) and vice versa when the link partner is also using forced speed.
Cause: Delay not long enough for the link to go down.
Change: Not practical to increase delay as a very long delay is needed for the link to go down. Added code to record the proper link speed and duplex when speed is forced so that ethtool will return the proper speed without the link going down. Note that the link will go down if the link partner has autoneg turned on, ensuring that the link partner will see the link change.
Impact: None.
Enhancements: ------------- 1. Change: Added power management and WOL during device close. This will allow WOL to work after Linux shutdown.
Impact: None.
2. Change: Changed driver so that ethtool will report invalid speed after ifdown.
Impact: None.
3. Change: Updated tpatfw.h
Impact: None.
v1.0.7 (Sep. 14, 2004) ====================== Fixes: ------ 1. Problem: (CQTO523) 5706 A1 hangs after a thousand iterations of load/ifup/ifdown/unload.
Cause: The driver may be servicing an interrupt within 15 msec of chip reset, causing the chip to hang. The problem was aggravated by the timer mode coalescing which created an excessive number of interrupts (hardware problem).
The Driver may also occasionally see the wrong firmware signature that will cause it to abort.
Change: Added synchronization to make sure all pending interrupts are serviced before resetting the chip. Also changed to collect mode coalescing. The firmware signature problem will be fixed in boot code.
Impact: The use of collect mode coalescing may affect performance.
2. Problem: (CQTO558) Unable to load driver on some early 2.6 kernels.
Cause: pci_dma_sync_single_for_* routines not defined on early 2.6 kernels.
Change: Added compatibility defines for earlier kernels.
Change: Added 15 msec delay after chip reset for A1.
Impact: None.
2. Problem: (CQTO468) Link does not go down after changing from 10Mbps full (forced) to 10Mbps half (forced) and vice versa.
Cause: Not enough delay after forcing link down.
Change: Added proper delay for link to go down.
Impact: None.
v1.0.5 (Sep. 02, 2004) ====================== Enhancements: ------------- 1. Change: Added support for ethtool -c, ethtool -C, ethtool -p, and firmware version for ethtool -i.
Impact: None.
Fixes: ------ 1. Problem: 5706C not advertising 1000 half duplex.
Cause: 1000 full duplex overwrites 1000 half duplex.
Change: Fixed the bug so that the 2 bits are or'ed together.
Impact: None.
2. Problem: ethtool -A does not change the flow control settings in all cases.
Cause: Flow control settings not zeroed out before setting new values.
Change: Minor bug fix to zero out the value.
Impact: None.
v1.0.4 (Sep. 02, 2004) ====================== Fixes: ------ 1. Problem: (CQTO504) Multiple NFS transfers will hang some connections.
Cause: Driver discards some receive packets when the error status is non-zero.
Change: Changed the driver to only discard receive packets when the defined error bits in the error status are non-zero.
Impact: None.
v1.0.3 (Sep. 01, 2004) ====================== Enhancements: ------------- 1. Problem: Driver does not support ethtool -t self test and ethtool -S statistics.
Change: Added ethtool self test and statistics.
Impact: None.
Fixes: ------ 1. Problem: (CQTO478) Kernel still panics when transmitting certain files using NFS after many iterations
Cause: Tx DMA stalls on certain UDP packets, causing NFS client to stall.
Change: More fixes made in firmware.
Impact: None.
v1.0.2 (Aug. 26, 2004) ====================== Enhancements: ------------- 1. Problem: Driver does not work on big endian machines.
Change: Ported and tested on SPARC64 machine.
Impact: None.
Fixes: ------ 1. Problem: (CQTO478) Kernel panics when transmitting certain files using NFS.
Cause: Tx DMA stalls on certain UDP packets, causing NFS client to stall.
Change: Fixed in firmware.
Impact: None.
2. Problem: (CQTO469) Unable to modify flow control parameters
Cause: Did not call setup_phy after the parameters are changed.
Change: Added call to setup_phy after parameters are changed.
Impact: None.
3. Problem: (CQTO467) 5706 does not autonegotiate properly after changing settings with ethtool.
Cause: This is an ethtool limitation as the proper advertising parameters are not passed to the driver properly.
Change: Implemented a new scheme to work around the problem to allow users to specify full autoneg, single speed autoneg, and fixed speed.
Impact: None.
4. Problem: ethtool -e does not work.
Cause: Various bugs in the nvram routines.
Change: Fixed and tested nvram routines on little endian and big endian machines.
Impact: None.
v1.0.1 (Aug. 18, 2004) ====================== Fixes: ------ 1. Problem: (CQTO459) 5706 NIC does not get link.
Cause: Boot code timing out in WAIT2 state before driver is ready.
Change: Moved the WAIT2 state ahead in the driver reset sequence as a temporary workaround until it is fixed in boot code.
Impact: None.
2. Problem: (CQTO463) Kernel panics when loading the driver on RH30EL (2.4.21-4.EL)
Cause: Older kernel used different API to allocate and register netdev.
Change: Added older APIs to be used on older kernels.
=============================================================================== Emulex iSCSI Device Driver for Linux ===============================================================================
Device Driver Version: 11.2.1193.12 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support
Device Driver Version: 10.2.365.0 Supported On: System x and BladeCenter
Problems Fixed: - be2iscsi rpm is failing with dependencies error - Unable to iSCSI SAN install RHEL/SLES/WIN2012R2 with UFP - Server is getting rebooted when we run IPv4+IPv6 bi-di NIC traffic simultaneously on UMC enabled interfaces
Device Driver Version: 10.2.261.1 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Write error while running traffic - System crashed after running converged IO with driver load unload in a - Possible backlog of eq might happen if _process_cq keep processing for a long time: causes fw UE - Driver memory leak resulting in "DMA: Out of SW-IOMMU space" errors in dmesg file output
Device Driver Version: 10.0.803.21 Supported On: IBM System x
Problems Fixed: - Unable to OEMSEAddTarget or OEMSEDiscoverTaget successfully and get entries in mili2d.log - Emulex drivers are not working on RHEL5 and RHEL6 errata kernel updates - IO Read/Write almost halts with 'DMA: Out of SW IOMMU space' messages while running iSCSI Multipath I/O
Device Driver Version: 4.4.175.0 Supported On: IBM Flex
Problems Fixed: - Cleaned up a cosmetic problem with warning messages during driver compile from source - System crashes when we run simultaneous IO to 6 vNIC�s with iSCSI IO - Linux kdump kernel crashes during shutdown after capturing dump, if be1iscsi driver running
Device Driver Version: 4.1.402.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - LUN is not getting detected for OEM CNA in SLES 11 SP2 64 bit OS - ioctl semaphore deadlock when running load/unload loop with target - SLES 11 SP2 GMC: Enable support for Lnx iSCSI Driver - RHEL 5.8 GA: Enable support for Lnx iSCSI Driver
Device Driver Version 4.1.334.39 Supported On: IBM System x and BladeCenter
Problems Fixed: - Emulex: Warning messages seen while building Emulex drivers on RHEL platform - Unable to load be1iscsi driver during iSCSI boot OS install - Modprobe be1iscsi hangs when system with max targets login - be1iscsi unload hangs the system - fw rebooted on 1st mbox cmd after driver load > unload > load - Failed to initialize iscsi driver - need to define DMA_32BIT_MASK / DMA_64BIT_MASK in Linux kernel 3.x.x
Integrated Management Module II (IMM2) Firmware Update Change History
Version 6.20, 1AOO78J - Critical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480, x880 - Firmware changes to address security vulnerabilities: CVE-2016-8616, CVE-2016-8617, CVE-2016-8619, CVE-2016-8624, CVE-2016-7431, CVE-2016-7433, CVE-2016-9318, CVE-2017-6214 - Additional firmware changes to address security vulnerabilities in open source packages, but for which there is no IMM2 exposure: CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843, CVE-2016-8610, CVE-2017-3731, CVE-2016-8864, CVE-2016-2776, CVE-2016-7167, CVE-2016-8615, CVE-2016-8618, CVE-2016-8621, CVE-2016-8623, CVE-2016-5419, CVE-2016-5420, CVE-2016-7141, CVE-2016-9597, CVE-2016-4658, CVE-2015-5219, CVE-2015-8139, CVE-2015-8140, CVE-2016-7426, CVE-2016-7427, CVE-2016-7428, CVE-2016-7429, CVE-2016-7434, CVE-2016-9310, CVE-2016-9311, CVE-2015-8325 - Fixed a problem where mezzanine card critical errors may not trigger call home. - Corrected the SNMP imm.mib file to work with IBM Systems Director. - Fixed a problem where an IMM2 login failure may cause the IMM2 to restart. - Fixed a problem where the IMM2 backup bank was auto promoted to an old firmware version. - Fixed a problem where settings may be lost after updating the IMM2 firmware. - Removed the Remote Presence client Java version checking. - Fixed a problem where the LXCA update job may not succeed if the server is powered off. - Fixed a problem where the Chassis Event log may be unavailable when there is more than 1100 entries. - Fixed a problem where power supply information doesn't get updated when power redundancy is lost. - Corrected a problem that may cause the fans to run at full speed. - Added an OEM IPMI command to enable/disable the NMI button for X3650 M4. - Corrected a problem on the x3850 X6 where the system may shut down because the ambient temperature is too high. - Improved the SSH/Web/CIM authentication reliability when multiple connection requests are received.
Version 6.00, 1AOO76I - Critical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480, x880 NOTE: Version 4.97 is now the minimum level required for the System x3100 M4. If the IMM2 on this system is running version 4.97 or newer, the IMM2 will not permit flashing firmware back to versions prior to 4.97. - Firmware changes to address security vulnerabilities: CVE-2016-3706, CVE-2016-1234, CVE-2016-2177, CVE-2016-2178, CVE-2016-6313, CVE-2016-6302, CVE-2015-2179, CVE-2016-2181, CVE-2016-6306, CVE-2015-8605 - Additional firmware changes to address security vulnerabilities in open source packages, but for which there is no IMM2 exposure: CVE-2016-2180, CVE-2016-2182, CVE-2016-2183, CVE-2016-6304, CVE-2015-5352, CVE-2015-6563, CVE-2015-6564, CVE-2016-1908, CVE-2016-3115, CVE-2016-3075, CVE-2016-4429, CVE-2016-2774, CVE-2016-6153, CVE-2015-8872, CVE-2016-6263 CVE-2016-4804, CVE-2016-6318, CVE-2015-2059, CVE-2015-8948, CVE-2016-6261, CVE-2016-6262 - Fixed a problem that may cause an IMM2 login to fail via SSH/GUI/CIM after an access by Director Server. - Fixed a problem where a false CPU CAT error event message may be logged. - Added support for eMMC 5.0 on x3100 M5. - Fixed an IMM2 timeout when communicating with the CMM. - Improved the PSU event reporting mechanism to prevent possible false power supply alerts on the x3500 M4, x3550 M4, and x3650 M4.
Version 5.80, 1AOO74F - Critical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480, x880 - Firmware changes to address security vulnerabilities: CVE-2016-4448, CVE-2016-2108, CVE-2016-2107, CVE-2016-2105, CVE-2016-2106, CVE-2016-2109, CVE-2015-8806, CVE-2016-4447, CVE-2016-4449, CVE-2015-8138, CVE-2015-5185, CVE-2016-3627, CVE-2016-3705, CVE-2008-5161, CVE-2015-5012, CVE-2011-1473, CVE-2016-2842, CVE-2013-7041, CVE-2013-4242, CVE-2014-3591, CVE-2015-0837 - Additional firmware changes to address security vulnerabilities in open source packages, but for which there is no IMM2 exposure: CVE-2015-8023, CVE-2016-1285, CVE-2016-1286, CVE-2015-8629, CVE-2015-8631, CVE-2016-3119, CVE-2016-0799, CVE-2015-5300, CVE-2015-7704, CVE-2015-7705, CVE-2015-7973, CVE-2015-7974, CVE-2015-7975, CVE-2015-7976, CVE-2015-7977, CVE-2015-7978, CVE-2015-7979, CVE-2015-8139, CVE-2015-8140, CVE-2015-8158, CVE-2016-1547, CVE-2016-1548, CVE-2016-4953, CVE-2016-4954, CVE-2016-4955, CVE-2016-4956, CVE-2016-4957, CVE-2016-1762, CVE-2016-1833, CVE-2016-1834, CVE-2016-1835, CVE-2016-1837, CVE-2016-1838, CVE-2016-1839, CVE-2016-1840, CVE-2016-2073, CVE-2016-4483, CVE-2015-3238 - Fixed a problem when an LDAP user attempts to restart or flash the IMM an error message may occur. - Fixed a problem where the event "0 login failures" is shown in IMM2 event log. - Fixed a problem on the HS23 that could cause a firmware update to fail when using updateXpress to update the firmware. - Added changes to format the SMTP e-mail address in square brackets. - Added changes to address security vulnerabilities caused by Cipher Block Chaining (CBC) encryption in SSH Server. - Added OpenLDAP server support for LDAP logins that use the username as the UID where the DN (Distinguished Name) has a comma "," included. - Fixed a problem where LDAP authentication to Windows Active Directory would fail when authenticating with simply the username.
Version 5.60, 1AOO72H - Critical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480, x880 - Firmware changes to address security vulnerabilities: CVE-2015-5219, CVE-2015-5300, CVE-2016-0778, CVE-2015-3194, CVE-2015-3195, CVE-2015-3196, CVE-2015-7981, CVE-2015-8126, CVE-2016-0705, CVE-2016-0797, CVE-2016-0799, CVE-2015-8472, CVE-2015-8126, CVE-2015-8710, CVE-2016-0755, CVE-2015-7547, CVE-2015-8776, CVE-2015-8777, CVE-2015-8778, CVE-2015-8779 - Added support to filter out invalid drive information from the RAID controller - Fixed a problem on the x3750 M4 that causes the IMM to report a power supply mismatch fault - Fixed a problem that causes the IMM to unexpectedly reset on the x3850 X6 and x3950 X6 - Fixed a problem with the power capping settings that causes the x3850 x6 to power off - Fixed a problem that causes the configuration restore operation to fail when the system has 12 network ports. - Added changes to make the firmware more robust and avoid hang conditions. - Added changes to enhance DSA/OneCLI IPMI-LAN access.
Version 5.41, 1AOO70I - Critical - Supports systems: x3550 M4 - Firmware improvement to address a potential reliability issue for a voltage regulator. Not updating to this level could lead to a failed system board. Please refer to tip HT 118532.
Version 5.40, 1AOO70H - Critical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480, x880 - Firmware changes to address security vulnerabilities: CVE-2015-7575, CVE-2016-0777, CVE-2016-0778 - Corrected a problem that prevented Lenovo XClarity Administrator from authenticating with the IMM2 - Fixed a problem on the x3850 X6 where the server unexpectedly reboots after an IMM2 reset - Fixed a problem on the x480 X6 that causes the CMM to report an 'unknown' IO connectivity status - Fixed a problem on the x3650 M4 that causes fan3 and fan4 to run at incorrect speeds - Fixed a problem that prevented the IMM2 gateway setting from being changed on the IMM2 web and in the UEFI menu. - Fixed a problem on the x3650 M4 where LDAP authentication does not work
Version 5.20, 1AOO68L - Critical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x240, x440, x280, x480, x880 - Firmware changes to address security vulnerabilities: CVE-2013-2207, CVE-2013-4508, CVE-2013-4559, CVE-2013-4560, CVE-2014-5352, CVE-2014-5353, CVE-2014-5355, CVE-2014-8121, CVE-2014-8176, CVE-2014-9421, CVE-2014-9422, CVE-2015-1349, CVE-2015-1781, CVE-2015-1788, CVE-2015-1789, CVE-2015-1790, CVE-2015-1791, CVE-2015-1792, CVE-2015-1799, CVE-2015-3216, CVE-2015-3405, CVE-2015-4000, CVE-2015-4171, CVE-2015-4620, CVE-2015-5477, CVE-2015-5600, CVE-2015-5722 - Re-enabled the EDH cipher for the LDAP client - Fixed a problem on x3550 M4 where MSM connectivity issue on X3650 M4 and X3550 M4 with ESXi 5.5 u2 on IMM v4.97 - Fixed a problem where setting NIST800-131A mode on the web, CLI, and SNMP is inconsistent - Fixed a problem where the signed certificate status on the web and the CLI does not match - Fixed a problem on x3650 M4 where the "NvDIMM Status & Cables" sensor does not de-assert - Fixed a problem where the DIMM's Manufacturer ID information is not displayed - Fixed a problem where the password is not changed after setting the password via OneCLI - Fixed a problem where a user cannot log using LDAP Active Directory Application Mode - Fixed a problem on x3850 X6 where the IMM2 does not detect power supply faults and over-temperature conditions - Fixed a problem on x3500 M4/x3550 M4/x3650 M4/x3650 M4 HD where the IMM2 reports power supply configuration mismatch assertion and deassertion events within seconds - Re-enabled TLS1.0/TSL1.1 support for the web and WS-MAN interfaces when the IMM2 is in NIST mode - Fixed a problem on x3100 M4/x3250 M4 where there is no alert message logged when AC power is lost
Version 4.97, 1AOO66M - NonCritical - Supported Platforms: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4 - NOTE: To avoid possible exploits of the vulnerabilities discovered with SSLv3 encryption, support for SSLv3 has been removed from the IMM2 firmware. To access the IMM2 web interface using https, users must make use of client browser versions that support TLS1.2 encryption. Refer to RETAIN Tip H214507 for details. - After applying this firmware update all subsequent self-signed certificates are generated using SHA-2 cryptographic hashes. Certificate signing requests are also generated using SHA-2 cryptographic hashes if the IMM2 is configured to run in NIST SP 800-131A Compliance mode. - Critical Fix for x3750 M4 -- Fixed issue on missing power supply redundancy lost event - Firmware changes to address security vulnerabilities: CVE-2013-2566, CVE-2013-2877, CVE-2013-4332, CVE-2013-4854, CVE-2013-6435, CVE-2014-0191, CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3508, CVE-2014-3509, CVE-2014-3510, CVE-2014-3511, CVE-2014-3513, CVE-2014-3566, CVE-2014-3567, CVE-2014-3568, CVE-2014-3569, CVE-2014-3570, CVE-2014-3571, CVE-2014-3572, CVE-2014-3634, CVE-2014-3660, CVE-2014-3683, CVE-2014-8118, CVE-2014-8275, CVE-2014-8500, CVE-2014-9293, CVE-2014-9294, CVE-2014-9295, CVE-2014-9297, CVE-2014-9298, CVE-2015-0204, CVE-2015-0205, CVE-2015-0206, CVE-2015-0235, CVE-2015-2808, CVE-2013-7423, CVE-2014-5352, CVE-2014-7817, CVE-2014-9402, CVE-2014-9421, CVE-2014-9422, CVE-2014-9423, CVE-2015-0209, CVE-2015-0286, CVE-2015-0287, CVE-2015-0288, CVE-2015-0289, CVE-2015-0292, CVE-2015-0293, CVE-2015-1472 - Fixed a problem that IMM2 unable to detect event from redundant PSU on x3250 M4 - Fixed a problem that PSU 1 and PSU 2 will show changed after hot swap on x3250 M4 - Fixed a problem that FAN will rotate in high speed when booting on 3100 M4 - Fixed a problem that IMM2 LDAP connects to AD server three time simultaneously for each login attempts with wrong password - Fixed a problem that Fan operates abnormally in S5 mode after rebooting system on x3550 M4 - Fixed a problem that "ipmitool chassis status" reporting false drive fault on System x3650 M4 - Fixed a problem that IMM firmware version 4.56 display as 4.55 in DSA log and UEFI data - Fixed a problem that IMM2 cannot log events on x3550 M4 - Fixed a problem that IMM2 may reset due to potential memory leakage - Fixed a problem that failure to send the alert of IMM2 via e-mail - Fixed a problem on IBM NeXtScale nx360 M4 for where the IMM may intermittently report an incorrect DC value to IBM NeXtScale n1200 Fan and Power Control (FPC) - Fixed a problem on NI152 x3650M4 where the IMM may report a power supply configuration mismatch error message in the system event log
Version 4.90, 1AOO66O - NonCritical - Firmware changes to address security vulnerabilities: CVE-2013-2566, CVE-2013-2877, CVE-2013-4332, CVE-2013-4854, CVE-2013-6435, CVE-2014-0191, CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3508, CVE-2014-3509, CVE-2014-3510, CVE-2014-3511, CVE-2014-3513, CVE-2014-3566, CVE-2014-3567, CVE-2014-3568, CVE-2014-3569, CVE-2014-3570, CVE-2014-3571, CVE-2014-3572, CVE-2014-3634, CVE-2014-3660, CVE-2014-3683, CVE-2014-8118, CVE-2014-8275, CVE-2014-8500, CVE-2014-9293, CVE-2014-9294, CVE-2014-9295, CVE-2014-9297, CVE-2014-9298, CVE-2015-0204, CVE-2015-0205, CVE-2015-0206, CVE-2015-0235, CVE-2015-2808 - Fixed a problem that IMM firmware version 4.56 displays as 4.55 in DSA log and UEFI data. - Fixed a problem that IMM2 may reset due to a potential memory leakage. - Fixed a cooling issue when the Fusion IO adapter is present - Fixed a problem where the IMM2 LDAP authentication attempts to connect to an AD server three times simultaneously for each login attempt with a wrong password. - Fixed a problem that may cause the IMM2 to fail to send an alert via e-mail. - To support new security requirements the IMM firmware now requires the Java remote presence client to be at version 1.8 or newer
Version 4.80, 1AOO64T - NonCritical - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - Fixed potential problem where Service Advisor not functional when routing through a proxy server
Version 4.61, 1AOO64Y - NonCritical - Fixed a problem on IBM NeXtScale nx360 M4 for intermittent IPMB IO error and ME error. - Fixed a problem on IBM NeXtScale nx360 M4 for unexpected shutdown due to CPU over temperature
Version 4.58, 1AOO64V - Critical - Critical Fix for x3630 M4, x3530 M4, x3300 M4, x3650 M4 BD -- Removed an incorrect error message sometimes displayed when certain RAID adapters are installed in certain PCIe slots
Version 4.56, 1AOO64S - Critical - Critical Fix for x3650 M4, x3650 M4 HD, x3650 M4 BD, x3500 M4, x3630 M4, x3530 M4, x3300 M4 -- Fixed issue on missing power supply redundancy lost event
Version 4.55, 1AOO64N - NonCritical - Firmware changes to address security vulnerabilities: CVE-2014-3508, CVE-2014-3509, CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3510, CVE-2014-3511, CVE-2013-2174, CVE-2013-4545, CVE-2014-0015, CVE-2014-0138, CVE-2014-0139, CVE-2014-2653, CVE-2014-2532 - Closed network port 121. - Fixed a problem of I2C error on x3500 M4 systems with use of Fairmont Raid card with FW version 23.22.0-0024 and IMM 1AOO58T - Thermal behavior enhancement on System x iDataPlex dx360 M4 - Fixed a problem that Call Home function was not working with a Proxy server
Version 4.50, 1AOO64L - NonCritical - Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-3509, CVE-2014-3506, CVE-2014-3507, CVE-2014-3505, CVE-2014-3508, CVE-2014-3510, CVE-2014-3511, CVE-2013-2174, CVE-2013-4545, CVE-2014-0015, CVE-2014-0138, CVE-2014-0139, CVE-2014-2653, CVE-2014-2532 - Fixed a problem where an erroneous event could be logged for an expansion card that would be followed by a recovery message several seconds later. - Fixed an issue with the web interface that could show a firmware update has failed if the user leaves the web interface inactive for over 20 minutes after downloading the update file. - Corrected an issue that might cause erroneous faults to be reported for the ServeRAID M5115 SAS/SATA when the server power is off. - Fixed an issue for multinode partition capable systems where when switching between partition and stand-alone modes repeatedly while also powering the nodes on and off, the IMM2 mode information could get out of sync with the server.
Version 4.35, 1AOO62W - Refresh Release - Support for refresh of the System x3650 M4 BD, Machine Type: 5466
Version 4.31, 1AOO58T - Critical - Critical Fix for x3650M4, x3550M4, x3500M4, dx360M4, x3100 M4, x3250m4, x3750M4, x3650M4 HD, x3630M4, x3530M4, x3300M4, x3250M5 -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198 - Added option to export the certificate signing request in PEM format - Various Remote Presence enhancements including: -- Support for a MAC OS-x client -- Scaled video viewer window -- ASU set up of Remote Presence hot keys -- Virtual media mounting via URL - Removed potentially sensitive information from the service data file - Fixed a problem on x3650 M4, x3550 M4, x3500 M4, x3650 M4 HD where the IMM2 may not detect a loss of power supply redundancy - Fixed a problem where the LDAP group filter does not support a full DN - Fixed a problem where the syslog alert fields "Msg Type" and "Severity" did not follow RFC 5424 - Fixed a problem where the IMM2 only supported the default network port for syslog notifications - Fixed a problem where the SNMP "sysName" query always returns the string "SNMP Service" instead of the system name - Fixed a problem where the Global Login Settings changes were lost after an IMM2 restart
Important: Before you flash the IMM2 firmware back to version 3.82 or older, set the IMM2 Security option to use the Basic Compatibility Mode. This will prevent a possible loss of access to the IMM2.
Version 4.23, 1AOO62Z - Initial Release - Adds support for System x880 X6, Machine Type: 4259, 7903
Version 4.21, 1AOO58U - NonCritical - Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198
Version 4.20, 1AOO58R - NonCritical - Fixed an issue in I2C communications that could cause CMM to report, "FPGA Host 2 Communication is offline" - Fixed a problem that required the browser cache to be cleared before accessing IMM2 web page. - Corrected a problem that caused the CMM to reporting an I/O connectivity problem with the FSM - Enhanced the IMM2 service and support data to better aid in the diagnosis of VPD issues - Added support for the S3 system sleep state - Added support for agentless monitoring of PCIe devices - Enabled a Flex compute node to be powered on sooner after installation in the chassis - Added RFC compliance checking for user input - Ensured consistency in Daylight Savings Time setting between the CMM and IMM2 - Added support for enhanced hard drive monitoring and status - Corrected an issue that caused false reports of incorrect / missing / corrupt VPD events.
Version 4.15, 1AOO58K - Suggested - Added support for the BIE (Blade IO Expansion Board) on the HS23, HS23E - Fixed a problem that prevented the AMM from controlling power when local power control is disabled on the HS23, HS23E
Version 4.10, 1AOO58F - Initial Release - Supports System x3100 M5, Machine Type: 5457
Version 4.04, 1AOO64E - NonCritical - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - Fixed potential problem where Memory Details on Critical DIMM points to a different location - Fixed potential problem for power state mismatching when one node transitions from AC disconnected to AC connected while the other node is powered up
Version 4.02, 1AOO58S - NonCritical - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - Fixed a potential problem where a single CPU and single Power Supply model may show a configuration error - Fixed a potential problem where fans running at high speed under normal operation may erroneously log a fan failure - Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198 - Fixed a power state change problem when removing a Compute book with an I/O book attached - Fixed a problem where PCIE adapters in I/O books may not show up after an OS reboot
Version 4.00, 1AOO58I - NonCritical - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - Add Scalable support. - x3950 X6 initial GA support level - Add support for enhanced hard drive monitoring and status - Fixed a potential problem that may cause the IMM to reboot in a configuration with multiple single port network cards.
Version 3.91, 1AOO58G - Critical - Supports System x3750 M4, Machine Type: 8752, 8718 - Add a feature to allow users to block power control from the power button on the x3750M4
Version 3.90, 1AOO54X - NonCritical - Added support for the IBM NeXtScale PCIe Native Expansion (NeX) Tray for IBM NeXtScale nx360 M4
Version 3.86, 1AOO56V - Critical - Critical Fix for x3500 M4 -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198
Version 3.85, 1AOO56U - Critical - Critical Fix for x220, x222, x240, x440, Flex System Manager Node -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198
Version 3.84, 1AOO56J - Critical - Critical Fix for x3300 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.83, 1AOO56I - Critical - Critical Fix for x3250 M5, nx360 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.82, 1AOO56E - Critical - Critical Fix for x3850 X6 / x3950 X6 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.81, 1AOO52Z - Critical - Critical fix: -- Corrected the x3850/x3950 x6 server to turn off power from the power supplies when a power fault occurs
Version 3.80, 1AOO52U - Initial Release - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - up to 4 CPU in one system - x3850 X6 initial GA support level
Version 3.79, 1AOO56G - Critical - Critical Fix for x240, x222, x440, x220, Flex System Manager Node -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.78, 1AOO52Y - Critical - Critical Fixes: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882) -- Fixed a potential security vulnerability with Trusted Platform Module (TPM) initialization settings (refer to security bulletin CVE-2014-0881)
Version 3.77, 1AOO56H - Critical - Critical Fix for x3630 M4, x3530 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.76, 1AOO56Q - Critical - Critical Fix for x3650 M4 BD -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198
Version 3.75, 1AOO56F - Critical - Critical Fix for x3650 M4 BD -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.74, 1AOO52R - Critical - Critical Fix: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882) - Supports System x3650 M4 BD, Machine Type: 5466
Version 3.73, 1AOO56D - Critical - Critical Fix for: dx360 M4, x3650 M4, x3550 M4, x3500 M4, x3100 M4, x3250 M4, x3750 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.71, 1AOO52W - Critical - Critical Fix for x3550 M4: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882) -- Fixed a problem system may shut down with new Mezz card installed
Version 3.70, 1AOO52Q - Critical - Critical Fix: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882)
Version 3.67, 1AOO50G - Initial Release - Supports System x3650 M4 BD, Machine Type: 5466
Version 3.65, 1AOO50D - Suggested NOTE: If you have a System x3550 M4 with the "Emulex VFA Mezz card" and a ==== single processor, don't update the IMM2 with this firmware - Critical Fix: -- Fixed a problem on the System x3650 M4 server where the system shuts down due to a false temperature event from the ambient temperature sensor - Fixed a problem where the IMM2 may erroneously report a fan fault in the x3630 M4 when the system is powering on. See RETAIN tip H207461 for the description of the original problem - Fixed a screen refresh problem where it occurs after resetting IMM2 - Fixed a firmware problem that may cause the IMM2 to reset unexpectedly - Fixed a problem where the IMM2 SNMP interface may intermittently be unavailable if the system is running VMWARE ESXi 5.x - Fixed a problem where the CPU may potentially throttle in the x3650 M4 system with two 550 watt power supplies and one hard drive backplane
Version 3.60, 1AOO50C - Suggested - Added support for the Intel IvyBridge-EP CPU on the HS23 blade - Fixed a problem where the HS23 hard drive number reported in the AMM event did not match the drive number on the physical blade enclosure - Fixed an intermittent problem where the UXSPI update utility may erroneously report that the firmware image is not meant for the HS23 system - Fixed a problem that causes the AMM web interface to not display properly when drives are removed or inserted - Fixed a problem where the IMM2 may not detect an over temperature condition for a DIMM - Corrected a problem that caused the IMM to report an "Unsupported blade/blower combination" error on HS23
Version 3.56, 1AOO50K - Critical - Fixed a Flex Systems Manager (FSM) Configuration Patterns problem where configuration deployments would fail with an activation job error message: ERROR: LDAP failed with rc=102 ERROR: LDAP failure: SYSPROF_LDAP_BIND_FAIL INFO
Version 3.55, 1AOO50E - Suggested - Fixed an issue so a fully qualified domain name can be used for a syslog collector in addition to an IP address - Fixed an issue to allow a user the ability to specify the port to use for syslog notifications, rather than only supporting the default port
Version 3.50, 1AOO50B - Suggested - Fixed an issue where the default static IPv4 address was assigned to the IMM2 management interface instead of the user configured static IPv4 address in DHCP fallback to static mode, if the DHCP server was not available - Prevent a VLAN from being configured on the IMM2 management interface for Flex nodes - Fixed a problem where the CPU throttling state recovery indication to the FSM might not be properly reported - Corrected an issue with the launch of the IMM2 Remote Console operation that required a restart of the IMM2 - Corrected the firmware to apply the inactivity timeout to web pages that automatically refresh - Updated the web browser support. The following web browsers are supported: Firefox 3.6-20 Chrome 13-26 Internet Explorer 8-10 - Added support for the S3 Sleeping State to the IMM2 user interfaces on those servers that include the S3 feature - Added changes to use the minimum TLS version setting that is provisioned by the CMM in Flex for encrypted communication - Enhanced the content of the service data file to assist in problem determination - Added a option to have the IMM2 automatically copy the firmware from its primary bank into the backup bank after the firmware has been run for a period of time and proven itself to be stable - Enhanced the IMM2 firmware to automatically restore itself without the need for user intervention if the firmware becomes corrupted - Added new commands on the command line interface to stop a serial redirection operation that is currently in progress, and to report the user names that have a serial redirection operation started - Added changes to use the DNS settings that are provisioned by the CMM in Flex to support use of an LDAP hostname for authentication - Updated the firmware to log hardware inventory change informational messages - Added support for the Service Advisor feature on stand alone rack servers to automatically call for service when a repair is needed - Added support to configure the Ethernet-over-USB IP address using ASU - Added changes to support the thermal requirements for new Solid State Drives used with the ServeRAID M5100 Series IBM Flex System Flash Kit v2 - Updated the IMM2 date and time web page on Flex nodes to only display the current date and time - Updated the SSH firmware to address various OpenSSH vulnerabilities that have been identified by security community - Added changes to support the Web Services-Management protocol
Version 3.40, 1AOO48M - Initial Release - Supports System x3250 M5, Machine Type: 5458
Version 3.37, 1AOO48P - Suggested - Added support for the IBM NeXtScale Storage Native Expansion (NeX) Tray for IBM NeXtScale nx360 M4
Version 3.36, 1AOO48Q - Critical - Fixed a problem on System x iDataPlex dx360M4 where a CIM client cannot get needed event information for asserted events
Version 3.35, 1AOO48N - Critical - Critical Fix: -- Corrected a problem on the System x3650 M4 and x3650 M4 HD servers causing the system to shut down due to an erroneous critical temperature event reported by the ambient temperature sensor
Version 3.30, 1AOO48L - NonCritical - Fixed a problem on System x iDataPlex dx360M4 where nodes shutdown due to a critical temperature event from the Ambient Temp sensor
Version 3.20, 1AOO48K - Initial Release - Supports System NeXtScale nx360 M4, Machine Type: 5455
Version 3.10, 1AOO48H - NonCritical - Added support for System x3650 M4 HD, Machine Type 5460 - Added support for newer CPUs in the System x iDataPlex dx360M4, x3500M4, x3550M4, and x3650M4 servers - Added a feature on the System x3550 M4 and x3650 M4 to fail over from the dedicated systems management network port to the shared port when the dedicated network link is not available - Fixed a problem where an NTP update message is logged every 1440 minutes - Fixed a problem where the IMM2 web interface won't accept an NTP hostname string that starts with a numeric character - Fixed a problem where the LDAP Group Filter authentication does not work as expected - Fixed a problem where the IMM2 reports 0 Watts when the System x iDataPlex dx360M4 is DC cycled or resumes from the S3 sleep state - Fixed an Ethernet problem that may cause an IMM2 failure to establish a link when the Ethernet speed and duplex settings are not configured to use auto-negotiation
Version 2.62, 1AOO56T - Critical - Critical Fix for x220, x222, x240, x440, Flex System Manager Node -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198
Version 2.61, 1AOO44V - Critical - Critical Fix for x240, x220, x440, x222, Flex System Manager Node -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 2.60, 1AOO42Y - NonCritical NOTE: For increased security, only high strength ciphers are now supported when using https.
==== Your browser must support one of the following cipher suites: | DHE-RSA-AES256-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(256) Mac=SHA256 DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 AES256-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA256 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 DHE-RSA-AES128-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(128) Mac=SHA256 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 AES128-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA256 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1
- Added support for the IBM Flex System x222 Compute Node - Improved Remote Presence (keyboard, mouse and virtual media)and in-band management (LAN-over-USB) performance - Changed the default file name for the Service Data file (First Failure Data Capture or FFDC) on the web interface to incorporate the machine type, serial number and a timestamp - Updated the IMM2 PCIe Bridge Firmware to support Windows 2012 Certification - Improved IMM2 Reliability, Availability, Serviceability (RAS) Features: - Added component and system VPD integrity checking & reporting - Enhanced Service Data collection (FFDC)
- Enhanced the configuration of UEFI settings via the CIM interface for applications like IBM Systems Director - Added Sub-manufacturer inventory support for mezz card and Sub-manufacturer inventory support for the system for IBM Systems Director - Added the UUID for the PCIe Expansion Node and the Storage Expansion Node to the SLP attributes reported by the IMM2 - Added the number of enabled CPU core and the Static power savings mode support for IBM Systems Director - Enhanced the alert recipient email notification, firmware update, event log, log out, and hardware information web pages to improve usability - Added support for IPMI & SNMPv3 accounts to be centrally managed by the Flex Chassis Management Module - Fixed a problem where an invalid configuration was erroneously reported for an unpopulated CPU socket in the IBM Flex System x440 - Enabled users to configure a longer trespass message - Increased the length of the LDAP group filter field to 511 characters - Corrected a problem with ServeRAID M5115 SAS/SATA Controller for IBM Flex Systems energy pack monitoring - Corrected a problem with ServeRAID M5115 SAS/SATA Controller for IBM Flex Systems LED management - Added IPMI command to configure the LAN-over-USB IP address
Version 2.52, 1AOO42E - Critical - Critical Fix: -- Fixed a problem on the System x3300 M4 servers causing the system to shut down due to a critical temperature event reported by the ambient temperature sensor
Version 2.50, 1AOO40Z - Suggested - Added support for the Solarflare SFN5162F MR Dual Port 10GbE SFP+ Adapter, and Solarflare SFN6122F LL Dual Port 10GbE SFP+ Adapter for System x3550 M4 and x3650 M4 NOTE: UEFI also needs to be upgraded to D7E128B (v 1.40 or newer, for the x3550 M4) or VVE128B (v1.40 or newer, for the x3650 M4) to support these cards - Added support for the Mellanox ConnectX-3 Dual Port QDR/FDR10 mezzanine card and Mellanox ConnectX-3 VPI Single-port QSFsorry.P FDR14/40GbE HCA on System x3550 M4, and x3650 M4 - Added optional Fan Zone support for single CPU systems (x3550 M4 and x3650 M4) with an installed with Qlogic Dual Port 10GbE SFP+ Embedded VFA - Fixed an intermittent problem where a Gratuitous ARP is not sent successfully - Fixed a problem where after the IMM2 firmware is flashed, there is a slight chance that the IMM2 web server can't be accessed when AC power is reapplied - Disabled the weak cipher suit used in the SSL/TLS firmware with the https protocol to avoid potential security vulnerabilities - Fixed a problem on the System x3750 M4 where the IMM2 shared mode network connection will be lost after upgrading the firmware of the onboard Emulex BE3 controller - Fixed a problem on the HS23 where the OS watchdog timer doesn't work - Fixed a problem on the HS23 where the Fault LED occasionally lights when the chassis is powered on with the BPE4 - Fixed a problem on the HS23 where the server may shut down after resetting the IMM2 - Enhanced the messaging mechanism between the BladeCenter AMM and the IMM2 - Added power management capability in the IMM2 web interface
Version 2.06, 1AOO42B - Critical - Corrected the firmware to prevent users from disabling the IPv6 interface - Fixed a problem that caused the IMM2 to reset itself after running for a period of time - Corrected the SNMP request to disable the IMM2 IPv4 interface so that it disables only IPV4, instead of both IPv4 and IPv6 - Fixed a problem that occasionally caused the server to shut down when the IMM2 is reset - Fixed a problem where the IMM2 incorrectly reported a battery voltage error - Corrected a problem where repeated frequent IMM2 resets causes the IMM2 to run the firmware in its backup partition - Corrected a problem report where the IMM2 did not report a failure to the system profiles script when the chassis UUID is unavailable
Version 2.00, 1AOO40E - Critical - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on the x3300 M4 and x3750 M4 -- IMM2 improved error reporting for missing/down CPU in invalid CPU configuration for x4440 M4 - Corrected a problem that caused 3.3V and 5V faults to be reported by IMM2 firmware level 1AOO34Z(1.85) on the HS23E blade - Eagle Ray SAS controller LED fault support improvements added for all ITE platforms
Version 1.97, 1AOO36R - Critical - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on x3650 M4, x3550 M4 and x3500 M4 - Thermal behavior enhancement on System x iDataPlex dx360 M4
Version 1.95, 1AOO36P (for System x iDataPlex servers) - Suggested - Added support for NVIDIA K1,K2,K20,K20x GPUs on System x iDataPlex dx360 M4
Version 1.88, 1AOO40A (for PureFlex System Compute Nodes) - Critical - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Corrected the Mezzanine card power fault monitoring on the Flex System x440 Compute Node - Corrected a problem with IBM Fabric Manager configuration from the Flex Chassis Management Module - Added support to retrieve configuration settings from an LDAP server - Added support for the Flex Storage Expansion Node - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state - Changed the default NTP sync interval from 3 minutes to 24 hours - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress
IMPORTANT NOTICE: For X3300 M4, it is required to upgrade both the primary and backup IMM2 firmware to Version 1.86, 1AOO40D or later. After the IMM2 is successfully updated, it is highly recommended to run the following IPMI command: Get device id (ipmitool raw 6 1) If the last two bytes returned show 0x2A 0x41 even after a reset of the IMM2, please refer to TDR-H207183 or MIGR-5092140 for more information.
Version 1.86, 1AOO40D - Critical - Critical Fix: -- Fixed a problem where the X3300 M4 system configured with a M5110/M5120 RAID card plus the "IBM ServeRAID M5100 Series 512MB/1 gigabytes (GB) Flash/RAID 5 Upgrade for IBM System x" option might have problem if AC power is removed while the system is running
Version 1.85, 1AOO34Z (for BladeCenter blades and System x Servers) - Critical - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem where a Blade Open Fabric Manager uncorrectable error can occur when booting the HS23 - Fixed a problem that IMM IPMI command periodically timed out when using HS23 in Chassis with the management network being disabled in some special configurations - Added support for the HS23 to recognize NEBS/Enterprise Mode for Telco chassis (this feature needs Advanced Management Module Firmware BPET62U or later) - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem where on rack systems that have 2 power supplies installed, the 'Redundancy Power unit has been restored' event is logged every time that the IMM2 is reset - Fixed a problem where a Fan Tach going low (lower critical) event is intermittently asserted when configuring the IMM2 to use an NTP server - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress - Fixed a problem on the HS23E that causes Preboot DSA to hang in CLI mode when a user accesses it using Serial over LAN - Fixed a problem on rack servers where ASU cannot set IMM.GRP_GroupName.1 and IMM.GRP_GroupName.2 if the string length is 16 characters or longer. The firmware was corrected to allow a maximum length of 64 characters - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state
Version 1.85, 1AOO34Y (for PureFlex System V7000 Storage Node) - Initial Release - Added support for Flex System V7000 Storage Node
Version 1.79, 1AOO36F - Suggested - Thermal behavior enhancement on System x iDataPlex dx360 M4
Version 1.78, 1AOO36E - Suggested - Thermal behavior enhancement for 115W & 95W CPU on System x iDataPlex dx360 M4 - Added support for the Intel KNC 5110p card
Version 1.77, 1AOO32X - Critical - Thermal behavior enhancement for 115W CPU on System x iDataPlex dx360 M4
Version 1.75, 1AOO32S - Suggested - Fixed a problem that a PCI uncorrectable error occurs when using HS23 with CFFh card (44W4479) in the BCS chassis - Fixed a problem where an "Unsupported blade/blower combination" error is reported when using the HS23 in the BCHT chassis configured in Enterprise mode - Fixed a problem in System x3530 M4, where the reported Active Energy Manager input/output power readings are inaccurate - Fixed a problem in System x3530 M4, x3630 M4, where an LDAP account can not login using the AD_CrossDomain tree - Fixed a problem in System x3530 M4, x3630 M4, where a user cannot use the "DNS to Find LDAP server/Extract search domain from login ID" setting from the IMM2 web to access an eDirectory server - Added support for Common Form Factor power supplies Oversubscription in System x3750 M4, Machine Types: 8722, 8733
Version 1.65, 1AOO32O - Suggested - Support the power supply Over-Subscription feature - Support the 750 Watt DC power supply for System x3650 M4,x3550 M4 - Support IBM 1.2TB High IOPS MLC Mono Adapter, IBM 2.4TB High IOPS MLC Duo Adapter for System x3650 M4, x3550 M4 - Support IBM LLM-SM Dual Port 10GbE SFP+ Adapter for System x3650 M4 - Fixed an abnormal Fan Zone recovery problem - Fixed a problem that IMM2 Email notification doesn't support an e-mail address with the underscore '_' character - Fixed a power policy "Restore" problem - Fixed a problem where the LDAP hostname can't be changed by ASU - Fixed a problem that the length of email address (for SNMP notification) is limited to 32 characters
Version 1.60, 1AOO32P - Suggested - Fixed a problem where the Chassis Management Module cannot correctly get the Mezzanine card information for the Flex System x220 Compute Node - Fixed a problem where the PreBoot DSA firmware could not be updated under VMWare ESXi 5 through the Flex System Manager's Update Manager - Fixed a problem where an IMM2 communications error can occur if an unexpected response causes VMware to spawn multiple processes when it does not receive the data it expects from the IMM2
Version 1.59, 1AOO32K - Initial Release - Supports System x3300 M4, Machine Types: 7382
Version 1.53, 1AOO30Z - Critical - Included an update to the FPGA that fixes an intermittent issue where the CPUs do not show up in a system with a RAID card installed, when the AC is removed and reapplied from the server without allowing sufficient time for the system hardware to completely discharge
Version 1.52, 1AOO34A - Suggested - Added redundant power supply and hot swap hard drive support in System x3100 M4
Version 1.51, 1AOO30Y - Critical - Support for NVIDIA Tesla K10, M2070Q, M2090 GPU cards on System x iDataPlex dx360 M4 - Fixed a problem in System x iDataPlex dx360 M4 where the password expires after creating a new user in the IMM2 web interface - Fixed a problem in System x iDataPlex dx360 M4, when the memory sensor changes from 'critical' to 'warning,' but the severity is not updated in the syslog or the email notification
Version 1.50, 1AOO30W - Suggested - Supports System HS23, Machine Types: 7875,1929 - Supports System x3650 M4, Machine Types: 7915 - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Added support for the Intel Xeon E5-2643 processor on the HS23 in BCH-R3, BCS and BCHT chassis - Fixed a problem where the IMM2 incorrectly logged an "Unsupported blade/blower combination" on the HS23 in the BC-E 8677 chassis - Fixed a power restore problem on systems that have 2 Delta power supplies installed - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where OpenLDAP Group Authentication filtering function doesn't work - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where LDAP account can not login using the AD_CrossDomain tree
Version 1.45, 1AOO28S - NonCritical - Fixed a problem in Flex System x220 where the Chassis Management Module (CMM) Command Line Interface can't display the Mezzanine card information - Fixed a problem in Flex System x220 and x240 where the prebootDSA firmware cannot be updated through Flex System Manager's Update Manager
Version 1.40, 1AOO30T - Initial Release - Supports System x3750 M4, Machine Types: 8722, 8733
Version 1.38, 1AOO30D - Initial Release - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160
Version 1.36, 1AOO30P - Initial Release - Fixed an intermittent remote media failure in system HS23E - Fixed a problem in system HS23E where remote media does not work when two or more users have concurrent remote control sessions
Version 1.34, 1AOO28Q - Initial Release - Supports Flex System Manager Node, Machine Type: 8731 - Supports Flex System x240 Compute Node, Machine Types: 7863, 8737, 8738 - Supports Flex System x220 Compute Node, Machine Types: 2585, 7906
Version 1.32, 1AOO28N - Critical - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160 - Fixed a problem that may see unexpected fan events after power on in x3100 M4 and x3250 M4 systems - Enhanced robustness on I2C bus test
Version 1.26, 1AOO26N - Initial Release - Supports System x3650 M4, Machine Types: 7915
Version 1.25, 1AOO26K - Initial Release - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Supports System x iDataPlex dx360 M4, Machine Types: 7912,7913
Version 1.22, 1AOO26O - Suggested - Supports System HS23, Machine Types: 7875,1929 Problems Fixed: - Fixed a problem where the BOFM configuration may be lost after a blade power cycle - Fixed an LED error indication that occurs on the BPE4 - Fixed a problem where the Info LED lights during the discovery stage - Fixed a problem where an ABR event is not logged - Fixed an intermittent communication problem between the AMM and IMM2 - Fixed a problem that causes the remote media function to hang when a second user attempts to mount remote media - Fixed a problem where the 'break' keyboard function doesn't work with Serial Over LAN
Version 1.21, 1AOO26L - Initial Release - Supports System HS23, Machine Types: 7875,1929
Version 1.05, 1AOO10K - Initial Release - Fixed the false alert issue in redundant PSU model
Version 1.00, 1AOO10I - Initial Release - Initial Release - Supports System x3250 M4, Machine Types: 2583,2587 - Supports System x3100 M4, Machine Types: 2582,2586
(C) Copyright International Business Machines Corporation 2008 - 2017. All rights reserved.
ibm_fw_imm2_1aoo78j-6_20_anyos_noarch_chg
=============================================================================== Emulex FCoE Device Driver for Linux ===============================================================================
Device Driver Version: 11.2.1193.12 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support
Device Driver Version: 10.2.375.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - ELS txcmplq list corruption cause crash during error injection - Cleaned up several issues around ExpressLane feature - Need a HAL workaround for upgrading 10.0 XE102/XE104 f/w to 10.2 - I/O hang on RHEL6.5 for small block (4K) random i/o on POWER8
Device Driver Version: 10.0.800.0 Supported On: IBM System x
Problems Fixed: - Low bi-di throughput seen on 1g ports of HS-23 LOM - Multiple performance improvements - Bonding driver takes approx 20 seconds to be ready
Incremental Interoperability: - RHEL 5.10 - RHEL 6.5 - XE-102 and XE-104 ASIC (OCx14xxx) - Support for set and get channels ethtool operation
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.4 and above 64-bit with KVM * SLES11 SP3 and above 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
Device Driver Version: 8.3.7.27 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Execution of internal loopback causes a crash - Issue which can cause multipath failover to not work properly
Incremental Interoperability: - IBM Flex System FC5052 2-port 16Gb FC Adapter - IBM Flex System FC5054 4-port 16Gb FC Adapter - IBM Tape unit interoperability - see SSIC for more information - SLES 11.3 on IBM System x and BladeCenter
Device Driver Version: 8.3.7.18 Supported On: IBM System x and BladeCenter
Problems Fixed: - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service - OXID Reused before RA_TOV without RRQ to recover - Intermittently storage paths will not recover after switch reboot
Device Driver Version: 8.3.6.4 Supported On: IBM Flex
Problems Fixed: - Fixed debug helper routine failed to dump CQ and EQ entries in non-MSI-X mode - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service - Fixed boot from san failure when SLI4 FC device presented on the same PCI bus - Fix ABTS recovery to be FC spec compliant - Fixed not reporting logical link speed to SCSI midlayer when QoS not enabled - Fix performance problem in pt2pt mode - Fixed SCSI host create showing wrong link speed on SLI3 HBA ports - Update text for misconfigured port messages - Fix discovery bug when swapping cables
Interoperability since previous release: - RHEL6.3 GA Kernel
Device Driver Version: 8.3.5.86 Supported On: IBM System x and BladeCenter
Problems Fixed: - Kernel panics with FCoE on HS23 in SLES 11.2 x86_64. Also requires a SLES11.2 kernel update - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service
Interoperability since previous release: - RHEL6.3 GA Kernel
Device Driver Version: 8.3.5.74 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Fixed system crash due to not providing SCSI error-handling host reset handler - Debug helper utility routines for dumping various SLI4 queues - Fix unsol abts xri lookup - Fixed issues with LPe16000 to LPe16000 discovery - Fix driver crash during back-to-back ramp events - Reregister VPI for SLI3 after cable moved to new Saturn port - Fix log message 2597 displayed when no error is detected - Fixed FCP LOG for easier Finisar trace correlation - Fix kernel panic when going into to sleep state - Fix error message displayed even when not an error - Fix Read Link status data - Fix unable to create vports on FCoE SLI4 adapter - Fix initiator sending flogi after acking flogi from target - Fix the case where an array controller does not apply FCP priority rules - Added support for handling SLI4-port XRI resource-provisioning profile change - Change default DA_ID support from disabled to enabled - Fix bug with driver unload leaving a scsi host for a vport around - Update copyright date for files modified in 2012 - Fix compilation errors on some kernels due to debugfs variable definitions - Used PCI configure space read to flush PCI function reset register write - Fixed system panic when extents enabled with large number of small blocks - Fixed system panic during EEH recovery - Fix resource leak when acc fails for received plogi - Fix SLI4 driver module load and unload test in a loop crashes the system - Fix missing CVL event causing round-robin FCF failover process to stop - Fix deadlock during adapter offline request - Fix same RPI registered multiple times after HBA reset
Device Driver Version: 8.3.5.66 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Fix SLI4 driver module load and unload test in a loop crashes the system - Fix missing CVL event causing round-robin FCF failover process to stop - Fix deadlock during adapter offline request - Fix same RPI registered multiple times after HBA reset - Fix driver handling of XRI Aborted CQE response - Fixed port and system failure in handling SLI4 FC port function reset - Fix bug with driver not sending a LOGO with vport delete - Make BA_ACC work on a fully qualified exchange - Fix for SLI4 Port delivery for BLS ABORT ACC - Fix KERNEL allocation while lock held - Incorrect usage of bghm for BlockGuard errors - Fix warning on i386 system - Fix ndlp nodelist not empty wait timeout during driver unloading - Fix mailbox and vpi memory leaks - Support character device to take a reference on the driver - Fix for FDISC failures after firmware reset or link bounce - Support debugfs for injecting T10 DIF errors - Fix SLI4 BlockGuard behavior when protection data is generated by HBA - Fix for driver using duplicate RPIs after 16Gb/s adapter port reset - Fix discovery problem when in pt2pt - Fixed failure in handling large CQ/EQ identifiers in an IOV environment - Fix Locking code raises IRQ twice - Fix driver not returning when bad ndlp found in abts error event handling - Support more driver logs in area of SLI4 port error attention and reset recovery - Fix bug with driver returning the wrong ndlp - Sync up with actual upstream lpfc driver code - Support SLI4 16Gb FC Adapter support for T10 DIF / BlockGuard - Merge from upstream: scsi: Fix up files implicitly depending on module.h inclusion - Fix driver behavior when receiving an ADISC - Fixed unbounded firmware revision string from port caused the system panic - Fix bug with driver processing dump command type 4 using 16Gb FC Adapter - Fix driver does not reset port when reset is needed during fw_dump - Fix ELS FDISC failing with local reject / invalid RPI - Changed SLI4 FC port internal loopback from outer serdes to inner internal - Fix REG_RPI fails on SLI4 HBA putting NPort into NPR state - Fix bug with driver processing an els command using 16Gb FC Adapter - Fix NMI seen due to CQE starvation - Fixed SLI4 FC port obtained link type and number dependent on link connection - Fixed SLI4 FC port internal loopback without SFP and external link/loopback plug - Fix driver incorrectly building fcpCdb during scsi command prep - Fixed FCP EQ memory check prevent initialize to single interrupt vector case - Fixed SLI4 16Gbit FC port internal and external diagnostic loopback tests - Fixed system panic during EEH recovery on SLI4 FC port - Fix FLOGI fails with invalid RPI (0x04) after connecting to a arbitrated loop - Fix ELS SCR failing with local reject / invalid RPI - Fix SLI4 port failures after firmware reset or dump - Fix port reset log messages indicate error when no error is seen - Fixed an issue where HBQ buffers are uninitialized in the base driver - Fixed missing shost lock protection on setting/clearing bit in vport->fc_flag - Fixed missing hbalock protection on setting/clearing bit in phba->link_flag - Fixed illegal state transition during driver unload - Fixed system crash on SLI4 FC port looopback diagnostic test with large buffers - Fixed a potential error path that might try to free DMA memory not allocated - Fixed SLI4 FC port Internal and External loopback diagnostic tests - Fix a crash while deleting 256 vports - Fix vport never finished discovery if switch runs out of resources - Fix kernel build warnings - Fix kernel panic when putting board in offline state twice - Fix memory leak when running hba resets to SLI-4 board - Fix driver message 3092 and 3116 to KERN_WARNING - Fix PCI read failure looks like a over temperature event - Fixed driver event reporting to mgmt on error attention due to forced dump - Fix not displaying firmware rev for BE UCNA boards - Fixed ABTS failure logic not rediscovering targets - Fix bug with driver not byte swapping extended mailbox data - Fix premature ndlp cleanup after second target LOGO - Fix Link pull causes I/O failures - Support loop for sli4 fc pass-through - No longer read fcoe parameters if board is not fcoe - Fix bug with driver passing a wrong count value - Support restore state and error log when sysfs board_mode attribute access failed - Fixed a typo in two of the log messages just introduced - Support for SLI4_CONFIG non-embedded COMN_GET_CNTL_ADDL_ATTR pass-through - Support for SLI4 FC port persistent linkdown through config region 23 - Fix for ABTS. Do not free original IOCB whenever ABTS fails - Fixed Linux driver inconsistency in reporting FC host port-state through OCM - Return an error if the mbox sysfs is called - Fix firmware upgrade attempt on unsupported adapter - Fix incomplete message number 2889 - Fix system crash when ASIC fails to initialize - Fix virtual fabrics bit set in FLOGI incorrectly - Fix bug with driver not returning extended mailbox data - Fix unsupported link speed accepted by SLI4 port - Incremented minor management version to reflect additional "protocol" sysfs attribute - Modify WQ handling to use entry_repost - Moved link type definitions to apply to all driver streams - Support a sysfs attribute "protocol" to report SLI4 port link protocol type - Support SLI4 INTF_TYPE and SLI_FAMILY as sub-field to the fwrev sysfs attribute - Support structure to support T10 DIF in SLI4 - Fix performance slowed due to too many register accesses - Fixed a warning when converting from simple_strtoul to strict_strtoul - Support Initial code to inject T10 DIF errors - Fixed a possible driver crash when cfg_fcp_eq_count is zero - Fixed non-embedded COMMON_GET_CNTL_ATTR mbox command failed with status 0x4 - Fixed null pointer dereference after clearing FCP policy rules - Changed the way of SLI4 device detecting physical port name - Fixed FCP policy exchange management rule parsing - Support check to lpfc_decode_firmware_rev to handle releases that have an 'X' - Fixed RPI leaks in ELS protocol handling - Fix kernel crash during boot with SLI4 card installed - Fixed NPIV FDISC failure on SLI4 if-type 2 ports - Fixed driver failed to follow IP reset procedure in SLI4 error attention handler - Fix sysfs lists fabric name for port that has been disconnected from fabric - Support FCP policy exchange management - Changed the timeout to 300 seconds for SLI_CONFIG (0x9B) mailbox command - Fixed fcp underrun reporting - Fixed a driver handling IP reset issue when PCI read return error - Fixed casting problem in calculating tx_words statistics - Support proper error code return for libdfc calling API to make proper decisions - Fix sli4 mailbox status code. Management software has dependencies - Fix compiler warning due to uninitialized local variable - Fix bus reset handler fails with bad failure code - Made proper error code return for libdfc calling API to make proper decisions - Made error log include PCI BAR bitmap from kernel when enable PCI device failed - Fixed sysfs API mismatch for building against SLES11 SP2 beta kernel - Fixed scsi midlayer queuecommand API mismatch for SLES11 SP2 beta kernel - Fixed ctlreg write bug not checking key string and limiting bytes to write - Fix default adapter name for the OCe15100 - Fixed incomplete scsi messages displayed - Fix cable pull failure on interface type 2 SLI-4 adapters - Fix enable_bg config parameter for SLI4 - Fixed not able to perform firmware reset through sysfs board_mode attribute - Fixed not recovering SLI port in handling error attention with RN bit set - Fixed two crash cases when unsolicted ELS ECHO_CMD is received - Fix direct connect does not come up for SLI4 FC ports - Fixed long wait when firmware reset to a SLI port without required privilege - Fix request firmware support for little endian systems - Fix driver firmware to match new firmware image format - Fixed SLI4 device firmware reset with SR-IOV virtual functions - Fix SLI4 CT handling for sequences > 4K - Fixed handling of unsolicited frames for vports - Fixed handling of CVL for vports - Fixed crash when aborting els IOs - Fix up CT and oxid/rxid for unsol rcv frames - Fixed mailbox double free panic - Support fcf priority record selection for fcf failover - Fixed compiler warning for putting large amount of memory on stack - Fixed driver build not building in debugfs even if kernel CONFIG_DEBUG_FS=y is set - Fix issue where the FC/FCoE Async Receive CQE did not scale for 16G FC adapters - FLOGI payload has Multiple N_port_ID set when lpfc_enable_npiv clear - Removed unused argument passed to the lpfc_bsg_diag_mode_enter routine - Fixed new ASIC device-mgmt BSG pass-through failed multi-buffer fw download - Support sysfs logging when writeable parameters are changed - Used PCI config space capability for sysfs get PF supported SR-IOV number of VFs - Support wait for SLI port status register for readyness following firmware reset - iDiag added SLI4 device PCI BAR memory mapped reigster access methods - Consolidated duplicating macro definitions - Fixed failure to enable PCIe AER prevent driver initialize and attach to device - Modified log messages for T10-PI processing - iDiag fixed mailbox capture and dump overlapping bitmap macro definition
Version 9.63, Build ID DSYTE2L o Problem(s) Fixed: 1. 4 Fort diagnostic tests show two sets of the same test
Version 9.63, Build ID DSYTE2K o Problem(s) Fixed: 1. preboot DSA 9.60 and 9.61 both fail CPU Stress Test with abort message 2. ML2 4 Fort diagnostic tests fail in pDSA
Version 9.61, Build ID DSYTE2E o New System Support: IBM System x3850 X6 / x3950 X6 (3837, 3839) o New Operating System support: N/A o Problem(s) Fixed: PMR Number: 00696,656,760 ---- >2TB DSA / Box line quality- any MT - Customer escalation PMR Number: 93660,999,000 ---- 3TB DSA / Box line quality- MT 3837 - Customer escalation o Enhancement: Openssl update to 1.0.1h from 1.0.1g o Limitations: N/A o Special usage: - 2014 Opal Product build
Version 9.60, Build ID DSYTD9S o New System Support: IBM System x3850 X6 / x3950 X6 (3837, 3839) o New Operating System support: N/A o Problem(s) Fixed: N/A o Enhancement: 1. MPx transition of DSA for CPU&Memory Stress Test. 2. Adding InfoCenter Hyperlinks to DSA. o Limitations: 1.After finish run all diagnostics in 25 loop with Emulex 10G options, DSA log will show abnormal, it only record Diags log one time on DSA Diagnostics Completion Log. 2.On GUI, when two ports of the machine want to connect the Extranet at the same time, the machine could not send dsa log to IBM server. you can click test internet connection to solve the problem. 3.CPU & Memory stress test only support for 1 loop. 4.System not show event log item in chassis event log & ipmi event log page when trigger SBE in standalone mode. o Special usage: - 2014 ToolsCenter 14B
Version 9.52, Build ID DSYTD3L o 13D FP hotfix for Openssl update to 1.0.1g from 1.0.1f
Version 9.51, Build ID DSYTD3H o New System Support: IBM System X3850 X6 (3837, 3839) o New Operating System support: N/A o Problem(s) Fixed: N/A o Enhancement: 1. Get standalone memory test results & SOL support for DSAp (for security efi boot) 2. UEFi Secure Boot o Limitations: N/A o Special usage: - 2013 ToolsCenter 13D FP
Version 9.50, Build ID DSYTD1N o New System Support: IBM System X3250 M5 (5458) IBM NeXtScale Node (5455) IBM System x3650 M4 BD (5466)
o Problem(s) Fixed: 1. PMR - 08641,W01,000 Unisys 9BLTCV - 7143 BOMC CD CheckPointPanel Diag test hangs 2. PMR 08699,W01,000 No LSI raw data from DSAp 9.41
o Enhancement: 1. Embedded DSAp Simplification by removing Low-Value Functionality 2. Fusion IO Raw Data Collection 3. pDSA Simplification for FoD Function & GUI Client 4. Remove Tape Diags function for both online & pDSA (Both Embed and Standalone pDSA) 5. Add warning & report in client for nonsupport systems 6. Change sFTP as the default protocol for transfer log to IBM Service o Limitations: 1. For IR controllers, there's no firmware package build version in the LSI controller page.IR controllers includes: (1). ServeRAID H1110 SATA/SAS Controller for System x (2). ServerRaid-Br10il SAS/SATA controller Expansion Card (3). Racine TLA - N2215 SAS/SATA HBA for IBM System x
2. For Software raid(C100,C105) the Fw version& Fw package version are not supported and will display "N/A" in html and blank in text report.
3. IANet_EEPROM diagnostic test record of Powerville(Onboard NIC card of Yongchun) would be inconsistent among the 4 ports in case the ethernet bus was set to ground due to the limitation of Intel CIM Provider. o Special usage: - 2013 ToolsCenter 13D
Version 9.41, Build ID DSYTC1P o New System Support: Flex System x222 Compute Node (7916) IBM System X3650 M4 HD(5460) o Enhancement: N/A o Limitations: 1. As Intel GPU's name is co-processor, DSA will show the name 'Processor' in PCI page's PCI Device table. Please do not mis-understand this item as CPU device. o Special usage: - 2013 ToolsCenter 13C
Version 9.40, Build ID DSYTB7x o Enhancement: 1. Preboot GUI redesign and enhancement--refine GUI into more customer friendly style. 2. FoD Support--FoD key re-activation. 3. pDSA proxy auto-config retrieve. o Limitations: 1. Immv1 embedded pDSA doesn not support any new drivers due to the limited image size. 2. DSA Does not support "VMware ESXi" page report for ESXi 5.x key due to "vmvisor-offline-query" limitaion . o Special usage: - 2013 ToolsCenter 13B
Version 9.30, Build ID DSYTB27 o New System Support: Flex System x440 Compute Node (7917, 2584) IBM System x3300 M4 (7382) o Problem(s) Fixed: 1. PMR - 05766,YL2,760 Aenservice appeared after running UpdateXpress & DSA. 2. PMR - 05193,W01,000 7147 - Intermittent random PSOD in vmware. multiple
o Enhancement: None o Limitations: - FIFO test of NIC diagnostics is not supported on the Intel I350 Quad Port GbE. Powerville has shared FIFO and shared FIFO registers making a test impossible if four ports are running at once. - For more limitations please refer to readme. o Special usage: - 2012 ToolsCenter 12D
Version 9.29, Build ID DSYTAB6 o New System Support: Flex System x440 Compute Node (7917, 2584) o Problem(s) Fixed: None o Enhancement: None o Limitations: - DSA implemented signature in product build. Please update IMM to 1AOO34V or later before updating pDSA, or flash failure will occur; - The user can not flash Embedded Preboot on VMware ESX3.5 prior to U4. - When flashing DSA Preboot using wflash/lflash, if you notice a build mismatch error, please make sure IMM firmware level is minimum 29B. Once you upgrade the IMM firmware to 29B or higher, DSA Preboot will continue to flash without error; - For more limitations please refer to readme. o Special usage: - NGP-4Q(12B+ FixPack3)
Version 9.28, Build ID DSYTAA4 o New System Support: x3630 M4 (7519) x3550 M4 (7383) o Problem(s) Fixed: None o Enhancement: None o Limitations: - DSA implemented signature in product build. Please update IMM to 1AOO34V or later before updating pDSA, or flash failure will occur; - The user can not flash Embedded Preboot on VMware ESX3.5 prior to U4. - When flashing DSA Preboot using wflash/lflash, if you notice a build mismatch error, please make sure IMM firmware level is minimum 29B. Once you upgrade the IMM firmware to 29B or higher, DSA Preboot will continue to flash without error; - For more limitations please refer to readme. o Special usage: - IMMV2 system 2012 4Q-LFC
Version 9.27, Build ID DSYTA7F o New System Support: None o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme o Special usage: - IMMv1 system 2012 4Q-LFC
Version 9.26, Build ID DSYTA6G o New System Support: None o Problem(s) Fixed: None o Enhancement: DSA Performance Optimization o Limitations: Refer to readme o Special usage: - 2012 ToolsCenter 12C
Version 9.21, Build ID DSYTA1U o New System Support: None o Problem(s) Fixed: 1.Recovered LSI Rawdata: "MegaCli -FwTermLog -Dsply -aALL" o Enhancement: None o Limitations: Refer to readme o Special usage: - 2012 ToolsCenter 12B Plus
Version 9.20, Build ID DSYTA0R o New System Support: x3530 M4 (7160) x3630 M4 (7158) x3750 M4 (8722, 8733) HS23E (8038, 8039) Flex System x220 Compute Node (7906, 2585) o Problem(s) Fixed: 1. PMR 05819,YL2,760 An error occured during the execution of DSA on Windows, DSA exits with an error at the eventlog plugin. o Enhancement: 1. Add HW remote presence key collection for High volume systems. o Limitations: Refer to readme o Special usage: - 2012 ToolsCenter 12B
Version 9.07, Build ID DSYT9CA o New System Support: x3750 M4 (8722, 8733) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.06, Build ID DSYT9BC o New System Support: Flex System x220 Compute Node (7906) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.05, Build ID DSYT9AA o New System Support: x3630 M4 (7158) x3530 M4 (7160) x3100 M4 Refresh1 (2582) x3250 M4 Refresh1 (2583) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.04, Build ID DSYT99E o New System Support: Flex System x240 Compute Node (8737, 8738, 7863) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.03, Build ID DSYT98I o New System Support: HS23E (8038, 8039) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.02, Build ID DSYT97C o New System Support: iDataPlex dx360 M4 server/2U chassis (7912/7913) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.01, Build ID DSYT96D o New System Support: x3500 M4 (7383) x3550 M4 (7914) x3650 M4 (7915) o Problem(s) Fixed: o Enhancement: None o Limitations: None o Special usage: None
Version 9.00, Build ID DSYT95W o New System Support: BladeCenter HS23 (7875) BladeCenter HX5 (7873, 1910) Flex System x240 Compute Node (8737, 8738, 7863) Flex System Manager Node (8735) x3500 M4 (7383) x3550 M4 (7914) x3630 M4 (7158) x3650 M4 (7915) x3690 X5 (7192, 7147) x3850 X5 / x3950 X5 (7143, 7191) o Problem(s) Fixed: 1. PMR 24817,8QG,000, PMR 30680,499,000 After kicking off DSA on one of the management nodes (x3650 M2) of SONAS 1.2(RHEL5 based), the node became unresponsive and dropped out of the cluster.
2. PMR 53575,000,834, PMR 05961,YL4,760 After running DSA, when using linux dump command on a DDS5 usb internal tape drive attached in x3650M2 backup speed becomes very slowly or failed.
3. PMR 26905,095,866 Running DSA 4.0 as well as DSA 3.4 on x3850 X5 the server is freezing, users have to reboot the server.
4. DSA 4.00 and previous version segmentation fault issue
6. PMR 15086,OTH,760 DSA 9.00 with --no-imm-lan option does not work correctly on RHEL5.3. The USB port state is changed during the execution of DSA.
o Enhancement: 1. Add GUI and CLI menu for Features on Demand (FoD) Activation Key Management o Limitations: Refer to readme. o Special usage: None
Version 4.02, Build ID DSYT92I o New System Support: iDataPlex Direct Water Cooled dx360 M4 server o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 4.01, Build ID DSYT92H o New System Support: None o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: - 2011 4Q lifecycle
Version 4.00, Build ID DSYT91S o New System Support: None o New server options support: None o Problem(s) Fixed: 1. PMR 15065,OTR,760 On Unisys ES7000 or x3850 X5, the Memory Card number with failed DIMM can not be reported in IPMI Eventlog if the Memory Card is bigger than 4.
o Enhancement: 1. Added > 1TB memory test support o Limitations: Refer to readme. o Special usage: - 2011 ToolsCenter 11D
Version 3.48, Build ID DSYT89PUS o New System Support: None o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: - 2011 3Q lifecycle
Version 3.47, Build ID DSYT89LUS o New System Support: x3100 M4 (2582) x3250 M4 (2583) o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.46, Build ID DSYT89GUS o New System Support: System x iDataPlex dx360 M3 (6391) o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.45, Build ID DSYT89EUS o New System Support: None o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: - x3850 X5 / x3950 X5 (7143, 7191) EXA scaling
Version 3.43, Build ID DSYT87HUS o New System Support: BladeCenter HX5 (7873,1910) o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.43, Build ID DSYT87FUS o New System Support: x3850 X5 / x3950 X5 (7143, 7191) x3690 X5 (7192, 7147) o Problem(s) Fixed: o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.40, Build ID DSYT85T o New System Support: BladeCenter HS22 (1911) x3650 M3 (5454) o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.30, Build ID DSYT80S o New System Support: None o Problem(s) Fixed: None o Enhancement: 1. Correct a problem with LSI MegaRAID reporting for IBM Service o Limitations: Refer to readme. o Special usage: None
Version 3.20, Build ID DSYT75X o New System Support: x3630 M3 (7377) x3690 X5 (7148, 7149) o Problem(s) Fixed: None o Enhancement: 1. Add LSI Hard Disk Drive (HDD) diagnostic back for both the onboard SAS chip and ServeRAID o Limitations: - If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831 installed, you will need one of the following: - uEFI GYE133A or greater for x3200 M3 and x3250 M3 - uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3 - uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3 - For more limitations please refer to readme o Special usage: None
Verion 3.20, Build ID DSYT75U o New System Support: x3755 M3 (7164) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Verion 3.10, Build ID DSYT70X o New System Support: x3400 M3(7378, 7379) x3500 M3(7380) x3550 M3 (7944, 4254) x3620 M3 (7376) x3650 M3 (7945, 4255) x3690 X5 (7148, 7149) x3850 X5 Standard Single-node and Multi-node models(7145, 7146) x3950 X5 Specially configured Database Engine models (7145, 7146) iDataplex dx360 M3 (6391) HS22V (7871,1949) HX5 (7872, 1909) o Problem(s) Fixed: None o Enhancement: 1. Added ServeRAID data collection o Limitations: - The following function has been temporarily removed from DSA Preboot for both the onboard SAS chip and ServeRAID: - LSI Hard Disk Drive (HDD) diagnostic - If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831 installed, you will need one of the following: - uEFI GYE133A or greater for x3200 M3 and x3250 M3 - uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3 - uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3 - For more limitations please refer to readme o Special usage: None
Version 3.02.56, Build ID DSYT56e o New System Support: None o Problem(s) Fixed: None o Enhancement: - The following systems are supported when BoMC downloads the corresponding system enablement pack: HS22V (7871,1949) x3550 M3 (7944,4254) x3650 M3 (7945,4255) x3400 M3 (7378,7379) x3500 M3 (7839) dx360 M3 (6391) o Limitations: - No HDD diagnostics available - To ensure quality and stability of the DSA code, we have reverted some display functionality of RAID information to what was shown in previous versions of DSA. This affects RAID display on the following adapters: Megaraid 8480 Serveraid MR10i Serveraid MR10is Serveraid MR10m Serveraid MR10k Serveraid M1015 Serveraid M5014 Serveraid M5015 On these adapters, the RAID information is generated from the output of separate command line tools and the format may not match other output in DSA. - For more limitations please refer to readme o Special usage: None
Version 3.00, Build ID: DSYT55a o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7327, 7328, 4251, 4252, 4261 o Limitations: - No HDD diagnostics available - For more limitations please refer to readme o Special usage: None
Version 1.16, Y4YT19AUS o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7839, 7836, 7837 o Limitations: None o Special usage: None
Version 1.15, TMYT20AUS o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7321, 6380, 7323 o Limitations: None o Special usage: None
Version 1.14, D6YT37AUS o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7946, 4198, 7947, 4199 o Limitations: None o Special usage: None
Version 1.13, P9YT48AUS o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7870, 1936, 7809 o Limitations: None o Special usage: None
Version 1.00 - Initial release
(C) Copyright International Business Machines Corporation 2008 - 2012. All rights reserved. ibm_fw_dsa_dsyte2v-9_65_anyos_anycpu_chg
=============================================================================== Emulex FC Device Driver for Linux ===============================================================================
Device Driver Version: 11.2.209.7 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support
Device Driver Version: 10.2.375.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - ELS txcmplq list corruption cause crash during error injection - Cleaned up several issues around ExpressLane feature - Need a HAL workaround for upgrading 10.0 XE102/XE104 f/w to 10.2 - I/O hang on RHEL6.5 for small block (4K) random i/o on POWER8
Device Driver Version: 10.0.800.0 Supported On: IBM System x
Problems Fixed: - Low bi-di throughput seen on 1g ports of HS-23 LOM - Multiple performance improvements - Bonding driver takes approx 20 seconds to be ready
Incremental Interoperability: - RHEL 5.10 - RHEL 6.5 - XE-102 and XE-104 ASIC (OCx14xxx) - Support for set and get channels ethtool operation
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.4 and above 64-bit with KVM * SLES11 SP3 and above 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
Device Driver Version: 8.3.7.27 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Execution of internal loopback causes a crash - Issue which can cause multipath failover to not work properly
Incremental Interoperability: - IBM Flex System FC5052 2-port 16Gb FC Adapter - IBM Flex System FC5054 4-port 16Gb FC Adapter - IBM Tape unit interoperability - see SSIC for more information - SLES 11.3 on IBM System x and BladeCenter
Device Driver Version: 8.3.7.18 Supported On: IBM System x and BladeCenter
Problems Fixed: - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service - OXID Reused before RA_TOV without RRQ to recover - Intermittently storage paths will not recover after switch reboot
Device Driver Version: 8.3.6.4 Supported On: IBM Flex
Problems Fixed: - Fixed debug helper routine failed to dump CQ and EQ entries in non-MSI-X mode - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service - Fixed boot from san failure when SLI4 FC device presented on the same PCI bus - Fix ABTS recovery to be FC spec compliant - Fixed not reporting logical link speed to SCSI midlayer when QoS not enabled - Fix performance problem in pt2pt mode - Fixed SCSI host create showing wrong link speed on SLI3 HBA ports - Update text for misconfigured port messages - Fix discovery bug when swapping cables
Interoperability since previous release: - RHEL6.3 GA Kernel
Device Driver Version: 8.3.5.86 Supported On: IBM System x and BladeCenter
Problems Fixed: - Kernel panics with FCoE on HS23 in SLES 11.2 x86_64. Also requires a SLES11.2 kernel update - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service
Interoperability since previous release: - RHEL6.3 GA Kernel
Device Driver Version: 8.3.5.74 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Fixed system crash due to not providing SCSI error-handling host reset handler - Debug helper utility routines for dumping various SLI4 queues - Fix unsol abts xri lookup - Fixed issues with LPe16000 to LPe16000 discovery - Fix driver crash during back-to-back ramp events - Reregister VPI for SLI3 after cable moved to new Saturn port - Fix log message 2597 displayed when no error is detected - Fixed FCP LOG for easier Finisar trace correlation - Fix kernel panic when going into to sleep state - Fix error message displayed even when not an error - Fix Read Link status data - Fix unable to create vports on FCoE SLI4 adapter - Fix initiator sending flogi after acking flogi from target - Fix the case where an array controller does not apply FCP priority rules - Added support for handling SLI4-port XRI resource-provisioning profile change - Change default DA_ID support from disabled to enabled - Fix bug with driver unload leaving a scsi host for a vport around - Update copyright date for files modified in 2012 - Fix compilation errors on some kernels due to debugfs variable definitions - Used PCI configure space read to flush PCI function reset register write - Fixed system panic when extents enabled with large number of small blocks - Fixed system panic during EEH recovery - Fix resource leak when acc fails for received plogi - Fix SLI4 driver module load and unload test in a loop crashes the system - Fix missing CVL event causing round-robin FCF failover process to stop - Fix deadlock during adapter offline request - Fix same RPI registered multiple times after HBA reset
Device Driver Version: 8.3.5.66 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Fix SLI4 driver module load and unload test in a loop crashes the system - Fix missing CVL event causing round-robin FCF failover process to stop - Fix deadlock during adapter offline request - Fix same RPI registered multiple times after HBA reset - Fix driver handling of XRI Aborted CQE response - Fixed port and system failure in handling SLI4 FC port function reset - Fix bug with driver not sending a LOGO with vport delete - Make BA_ACC work on a fully qualified exchange - Fix for SLI4 Port delivery for BLS ABORT ACC - Fix KERNEL allocation while lock held - Incorrect usage of bghm for BlockGuard errors - Fix warning on i386 system - Fix ndlp nodelist not empty wait timeout during driver unloading - Fix mailbox and vpi memory leaks - Support character device to take a reference on the driver - Fix for FDISC failures after firmware reset or link bounce - Support debugfs for injecting T10 DIF errors - Fix SLI4 BlockGuard behavior when protection data is generated by HBA - Fix for driver using duplicate RPIs after 16Gb/s adapter port reset - Fix discovery problem when in pt2pt - Fixed failure in handling large CQ/EQ identifiers in an IOV environment - Fix Locking code raises IRQ twice - Fix driver not returning when bad ndlp found in abts error event handling - Support more driver logs in area of SLI4 port error attention and reset recovery - Fix bug with driver returning the wrong ndlp - Sync up with actual upstream lpfc driver code - Support SLI4 16Gb FC Adapter support for T10 DIF / BlockGuard - Merge from upstream: scsi: Fix up files implicitly depending on module.h inclusion - Fix driver behavior when receiving an ADISC - Fixed unbounded firmware revision string from port caused the system panic - Fix bug with driver processing dump command type 4 using 16Gb FC Adapter - Fix driver does not reset port when reset is needed during fw_dump - Fix ELS FDISC failing with local reject / invalid RPI - Changed SLI4 FC port internal loopback from outer serdes to inner internal - Fix REG_RPI fails on SLI4 HBA putting NPort into NPR state - Fix bug with driver processing an els command using 16Gb FC Adapter - Fix NMI seen due to CQE starvation - Fixed SLI4 FC port obtained link type and number dependent on link connection - Fixed SLI4 FC port internal loopback without SFP and external link/loopback plug - Fix driver incorrectly building fcpCdb during scsi command prep - Fixed FCP EQ memory check prevent initialize to single interrupt vector case - Fixed SLI4 16Gbit FC port internal and external diagnostic loopback tests - Fixed system panic during EEH recovery on SLI4 FC port - Fix FLOGI fails with invalid RPI (0x04) after connecting to a arbitrated loop - Fix ELS SCR failing with local reject / invalid RPI - Fix SLI4 port failures after firmware reset or dump - Fix port reset log messages indicate error when no error is seen - Fixed an issue where HBQ buffers are uninitialized in the base driver - Fixed missing shost lock protection on setting/clearing bit in vport->fc_flag - Fixed missing hbalock protection on setting/clearing bit in phba->link_flag - Fixed illegal state transition during driver unload - Fixed system crash on SLI4 FC port looopback diagnostic test with large buffers - Fixed a potential error path that might try to free DMA memory not allocated - Fixed SLI4 FC port Internal and External loopback diagnostic tests - Fix a crash while deleting 256 vports - Fix vport never finished discovery if switch runs out of resources - Fix kernel build warnings - Fix kernel panic when putting board in offline state twice - Fix memory leak when running hba resets to SLI-4 board - Fix driver message 3092 and 3116 to KERN_WARNING - Fix PCI read failure looks like a over temperature event - Fixed driver event reporting to mgmt on error attention due to forced dump - Fix not displaying firmware rev for BE UCNA boards - Fixed ABTS failure logic not rediscovering targets - Fix bug with driver not byte swapping extended mailbox data - Fix premature ndlp cleanup after second target LOGO - Fix Link pull causes I/O failures - Support loop for sli4 fc pass-through - No longer read fcoe parameters if board is not fcoe - Fix bug with driver passing a wrong count value - Support restore state and error log when sysfs board_mode attribute access failed - Fixed a typo in two of the log messages just introduced - Support for SLI4_CONFIG non-embedded COMN_GET_CNTL_ADDL_ATTR pass-through - Support for SLI4 FC port persistent linkdown through config region 23 - Fix for ABTS. Do not free original IOCB whenever ABTS fails - Fixed Linux driver inconsistency in reporting FC host port-state through OCM - Return an error if the mbox sysfs is called - Fix firmware upgrade attempt on unsupported adapter - Fix incomplete message number 2889 - Fix system crash when ASIC fails to initialize - Fix virtual fabrics bit set in FLOGI incorrectly - Fix bug with driver not returning extended mailbox data - Fix unsupported link speed accepted by SLI4 port - Incremented minor management version to reflect additional "protocol" sysfs attribute - Modify WQ handling to use entry_repost - Moved link type definitions to apply to all driver streams - Support a sysfs attribute "protocol" to report SLI4 port link protocol type - Support SLI4 INTF_TYPE and SLI_FAMILY as sub-field to the fwrev sysfs attribute - Support structure to support T10 DIF in SLI4 - Fix performance slowed due to too many register accesses - Fixed a warning when converting from simple_strtoul to strict_strtoul - Support Initial code to inject T10 DIF errors - Fixed a possible driver crash when cfg_fcp_eq_count is zero - Fixed non-embedded COMMON_GET_CNTL_ATTR mbox command failed with status 0x4 - Fixed null pointer dereference after clearing FCP policy rules - Changed the way of SLI4 device detecting physical port name - Fixed FCP policy exchange management rule parsing - Support check to lpfc_decode_firmware_rev to handle releases that have an 'X' - Fixed RPI leaks in ELS protocol handling - Fix kernel crash during boot with SLI4 card installed - Fixed NPIV FDISC failure on SLI4 if-type 2 ports - Fixed driver failed to follow IP reset procedure in SLI4 error attention handler - Fix sysfs lists fabric name for port that has been disconnected from fabric - Support FCP policy exchange management - Changed the timeout to 300 seconds for SLI_CONFIG (0x9B) mailbox command - Fixed fcp underrun reporting - Fixed a driver handling IP reset issue when PCI read return error - Fixed casting problem in calculating tx_words statistics - Support proper error code return for libdfc calling API to make proper decisions - Fix sli4 mailbox status code. Management software has dependencies - Fix compiler warning due to uninitialized local variable - Fix bus reset handler fails with bad failure code - Made proper error code return for libdfc calling API to make proper decisions - Made error log include PCI BAR bitmap from kernel when enable PCI device failed - Fixed sysfs API mismatch for building against SLES11 SP2 beta kernel - Fixed scsi midlayer queuecommand API mismatch for SLES11 SP2 beta kernel - Fixed ctlreg write bug not checking key string and limiting bytes to write - Fix default adapter name for the OCe15100 - Fixed incomplete scsi messages displayed - Fix cable pull failure on interface type 2 SLI-4 adapters - Fix enable_bg config parameter for SLI4 - Fixed not able to perform firmware reset through sysfs board_mode attribute - Fixed not recovering SLI port in handling error attention with RN bit set - Fixed two crash cases when unsolicted ELS ECHO_CMD is received - Fix direct connect does not come up for SLI4 FC ports - Fixed long wait when firmware reset to a SLI port without required privilege - Fix request firmware support for little endian systems - Fix driver firmware to match new firmware image format - Fixed SLI4 device firmware reset with SR-IOV virtual functions - Fix SLI4 CT handling for sequences > 4K - Fixed handling of unsolicited frames for vports - Fixed handling of CVL for vports - Fixed crash when aborting els IOs - Fix up CT and oxid/rxid for unsol rcv frames - Fixed mailbox double free panic - Support fcf priority record selection for fcf failover - Fixed compiler warning for putting large amount of memory on stack - Fixed driver build not building in debugfs even if kernel CONFIG_DEBUG_FS=y is set - Fix issue where the FC/FCoE Async Receive CQE did not scale for 16G FC adapters - FLOGI payload has Multiple N_port_ID set when lpfc_enable_npiv clear - Removed unused argument passed to the lpfc_bsg_diag_mode_enter routine - Fixed new ASIC device-mgmt BSG pass-through failed multi-buffer fw download - Support sysfs logging when writeable parameters are changed - Used PCI config space capability for sysfs get PF supported SR-IOV number of VFs - Support wait for SLI port status register for readyness following firmware reset - iDiag added SLI4 device PCI BAR memory mapped reigster access methods - Consolidated duplicating macro definitions - Fixed failure to enable PCIe AER prevent driver initialize and attach to device - Modified log messages for T10-PI processing - iDiag fixed mailbox capture and dump overlapping bitmap macro definition
Firmware Version: 2.03x14 Boot Code Version: 11.20a6 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support - Windows 2016 Support - VMware ESXi 6.5 Support
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.02x11 Boot Code Version: 5.30a6 Supported On: System x Flex
Problems Fixed: - None
Incremental Interoperability: - Grantley based ITE
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.02x11 Boot Code Version: 5.30a3 Supported On: System x and BladeCenter
Problems Fixed: - Roll boot code version number to avoid conflict with IBM UXSPi updates
Incremental Interoperability: - Inventory support for the System x xHMC (Chassis Hardware Management Console) for IBM Rack FC HBAs - Grantley Rack Servers
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.02x11 Boot Code Version: 5.13x4 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Server intermittently fails to boot during rolling SANboot (any OS) - Fixed a boot hang associated with server BIOS change
Incremental Interoperability: - Inventory support for the Flex xHMC (Chassis Hardware Management Console)
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.01a11 Boot Code Version: 5.12a13 Supported On: IBM System x and BladeCenter
Problems Fixed: - Emulex FC Adapter does not auto-enable SAN boot mode when boot target configuration is made via IFM (BOFM) - Emulex FC configuration utility is in the wrong F1 setup screen - IBM CIOv adapter connected to Brocade 8 Gig FC BladeCenter switch intermittently Links up at less than 8 Gig
Firmware Version 2.01a3 Boot Code Version: 5.12a5 Supported On: IBM System x and BladeCenter
Incremental Interoperability: - Enhanced timeout notifications for processing abort failures.
Problems Fixed: - All multi-abort I/Os are returned on the same ring from which the ABORT_MXRI command was received. - Changed the TRCV response in the abort state to CMD RJT to enable the TRSP to be processed. - Corrected an issue with blocked TSEND operations. - Corrected a buffer leak issue with RRQ exchanges. - Corrected an issue where the TRCV IOCB was de-queued improperly causing a XFR_RDY flood. - Corrected an issue where the OXID field was not loaded in the XRI_ABORTED IOCB. - Corrected an issue in recognizing whether an EEPROM is present.
Firmware Version: 11.2.1193.34 Supported On: System x Rack, BladeCenter, and Flex
Problems Fixed: - None
Incremental Interoperability: - RHEL7 Update 3 Support - SLES12 SP2 Support - Windows 2016 Support - VMware ESXi 6.5 Support
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
- When modifying configuration values for an iSCSI target, attempting to save the target with any invalid values may result in all values for that target being cleared. If this occurs, re-add the target using only valid configuration values. Please consult the Emulex Boot Manual for a description of valid configuration values.
Firmware Version: 10.6.228.36 Supported On: System x Rack
Problems Fixed: - PSOD Heartbeat NMI in VMWare - Bandwidth and SVID are showing as N/A in PXE select utility when 2+2 adapter is in UFP mode - Improved handling of ASU/UCM deployed configurations - In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669) - FCoE initiator & target UCM settings are not shown in IMM web GUI (183090) - PXE VLAN config must be supported when multi-channel is disabled (182184) - Cannot PXE boot server when under heavy IO load (188624)
Incremental Interoperability: - SLES 11 SP4 on System x x3850 X5, x3950 X5, x3690 X5
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Problems Fixed: - iSCSI SAN Boot failed after OS installation completed in UFP and vNIC1 mode with OCe11000 adapter
Incremental Interoperability: - Grantley based ITE
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.377.18 & 10.2.377.23 Supported On: System x and BladeCenter
Problems Fixed: - PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140) - "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086) - FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561) - UE seen while booting the system after a CoreDump - When NIC traffic has run on all the 8 vNICs of an ASIC, the vnics of first port are not honoring the assigned BW - SRIOV performance & Fairness for 16VMs is low on Linux and VMware - ML2 VFA5 device name is show "N/A" under IMM web and CLI of server management>Adapters - BW changes not getting updated with vNIC1 mode - Enable 100M/10M speed in set speed for SGMII interface - UCM/vNIC2, Ports/PCI functions supporting FCoE need to be differentiated to make it easier for the user - UCM/vNIC2 ability to program VirtWWN/WWPN independent of BFS Enable - iSCSI boot not working on higher order PCI functions (PF8 11)on 4 port controllers on ARI enabled systems - Can't install Windows2012 onto the iSCSI LUN whose LUN ID is not 0 - Fixed several issues related to IBM Agentless inventory management
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.261.41 Supported On: IBM System x
Problems Fixed: - Hit BSOD during VMQ overnight traffic test with cpu affinity change - IBM VFA5 Adapter causing software panic on IBM G8246 Switch in UFP mode - LPVIDs are not getting saved in vNIC2 mode if we change mode from vNIC1 mode to vNIC2 - In MC VINC1, VNIC2, UFP modes, user should see only 4 functions per port for 2 port card
Incremental Interoperability: - Emulex VFA5 2x10 GbE SFP+ Adapter and FCoE/iSCSI SW for IBM System x - Emulex VFA5 2x10 GbE SFP+ PCIe Adapter for IBM System x - Emulex VFA5 2x10 GbE SFP+ Integrated Adapter for IBM System x
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.261.36 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - FRU VPD fields are now properly populated on CN4054 and CN4054R - Fixed UE resulting slow boot at UEFI splash screen and NIC devices removed - When using VMQ with Windows Server 2012 or 2012R2, the user may experience VM connectivity loss, packet drops, system hangs, inability to shutdown VMs and possible system crashes on shutdown. The complete solution also requires 10.2 based Windows NIC driver.
Incremental Interoperability: - Inventory support for the Flex xHMC (Chassis Hardware Management Console)
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.0.803.13 Supported On: IBM System x
Problems Fixed: - IBM Feature on Demand for storage keys now works with Optimized Boot enabled - Link detection time improved from ~70 secs on DAC cable insertion/removal
Incremental Interoperability: - Unified Fabric Protocol on IBM System x Servers
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware version: 4.6.281.26 (supported on IBM System x, BladeCenter and Flex)
Problems Fixed: - CN4054 VPD is not valid during/after IMM flash - Links go down after 497 to 498 days in VMWare - Send 'link down' to switch if UE occurs on ASIC
Incremental Interoperability: - Emulex Dual Port 10GbE SFP+ VFA IIIr for IBM System x - Emulex Dual Port 10GbE SFP+ Embedded VFA IIIr for IBM System x
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware version: 4.6.281.21 (supported on IBM System x, BladeCenter and Flex)
Problems Fixed: - OCe10 VFA CNAs stuck in "Switch Independent Mode" - Port Identification fails on Port 1 under uEFI menu for PCIe rack VFA
Incremental Interoperability: - IBM Flex System CN4054R 10Gb Virtual Fabric Adapter - IBM Ivy Bridge CPU Based Servers
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware version: 4.6.281.8 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - HW iSCSI offload is now supported in UFP Mode (UFP limited to IBM Flex) - Server may hang during boot with multichannel disabled with switch default settings. The IBM 10Gb Virtual Fabric Switch has trunking enabled and the Brocade Converged 10Gbe Switch Module has ports in "Access" mode. If the Brocade Converged 10Gbe Switch Module ports are switched to trunking mode, the hang no longer occurs. - When using Config Patterns with virtual MACs the bandwidth settings are are intermittently reset after some number of server reboots.
Incremental Interoperability: - IBM Flex System Fabric SI4093 System Interconnect Module - IBM Flex System EN6131 40Gb Ethernet Switch - IBM Flex System x222 10Gb Virtual Fabric LOM - SLES 11.3 on IBM System x and BladeCenter - Complete NIC/iSCSI/FCoE support for ASU/Config Patterns for Flex and ASU for IBM System x & BladeCenter
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers. - Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers. - When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware version: 4.6.166.7 Supported On: IBM System x and BladeCenter
Problems Fixed: - When connected to Cisco Nexus 4k and 5k switches, the virtual link may not recover on a switch port bounce (shut/no shut) in an ESXi environment. A switch port re-bounce will recover the link. - When connected to Cisco Nexus 4k and 5k switches, OneCommand Manager reports CRC's and there is poor network performance in an ESXi environment
Incremental Interoperability: - ASU/Config Pattern configuration for iSCSI and FCoE (BE3) - UFP for iSCSI (BE3) - Support for using 10Gb ports with legacy 1Gb switches installed in a BladeCenter-S chassis or MSIM/MSIM-T expansion units in a BladeCenter-H or -HT chassis - Update Express System Packs now support Linux errata kernels - ESXi 5.1
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers. - Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers. - Server may hang during boot with multichannel disabled with switch default settings. The IBM 10Gb Virtual Fabric Switch has trunking enabled and the Brocade Converged 10Gbe Switch Module has ports in "Access" mode. If the Brocade Converged 10Gbe Switch Module ports are switched to trunking mode, the hang no longer occurs. - When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 4.4.180.3 Supported On: IBM Flex
Problems Fixed: - 10Gb ports intermittenly linking at 1Gb speed with the IBM Flex System Fabric EN4093/EN4093R 10Gb Scalable Switch. - Switch Configuration after an erase configuration is not reflected after reboot - 'Logical Admin Link' not enabled after applying BOFM in Switch Agnostic mode - IBM pre-boot Diagnostics NIC physical loopback test fails in Command and GUI mode - Multiple cosmetic issues with iSCSI UEFI BIOS - 10Gb ports do not detect 'Link Down' with some switches - When adding an iSCSI hardware target in UEFI through discovery login, the boot target setting is ignored.
Interoperability since previous release: - UEFI 2.3.1 Compliance - Increased VF count in SR-IOV (was 16 VFs per port, is now 32 VFs per port) - Support for next generation 10GbaseT PHY - Expose IBM Feature On Demand licensing information in UEFI configuration utility - IBM Universal Configuration Manager for Ethernet - IBM Unified Fabric Protocol - Ability to assign Switch Agnostic VLAN IDs without intermediate reboot - Changes to Personality or Multichannel in PXESelect allows further changes to be made w/o reboot - Support for IBM Flex System Fabric CN4093 10Gb Converged Scalable Switch
Known Issues: - HW iSCSI offload is not currently supported in UFP mode
Firmware Version: 4.1.422.8 Supported On: IBM Flex
Problems Fixed: - PHY Loopback fails on 10G ports - RH 6.2 and W2k8 servers crashed after shut/no shut the switch port with FCoE connection and 50 vlans configured - DSA: NIC physical loopback test fails in Command and GUI mode - Firmware update fails to update all VPD Code Level fields - DCBX does not converge with FW 4.1.422 on Cicso 5k.
Interoperability Since Previous Release: - Support for IBM Flex System x440 10Gb Virtual Fabric LOM
Firmware Version: 4.1.422.0 Supported On: IBM Flex
Problems Fixed: - SR IOV: Unable to ping IPV6 from DUT VF to Peer VF - Reading VPD from BE3 timesout making SR IOV fail in newer kernels - 1Gb devices are being suppressed by kernel during the PCI probe in SLES11 SP2 - MAC Loopback fails when Mgmt Adapter Creation fails - Failure of MAC loopback test after firmware update and warm reboot - Suppress efat dump mailbox commands in the efat dump log - Running ethtool with BE3 takes longer than expected after cable pull - Out of Order CQEs - TRACE_LOG function not printing the messages for some of the VF's - esx4/5 issue. svc target cannot be configured properly - RSCN is not generated by switch when a driver restarts - Port Link stays up even after switch removed
Interoperability Since Previous Release: - Support for IBM Flex System EN4054 4-port 10Gb Ethernet Adapter - Support for IBM Flex System CN4054 10Gb Virtual Fabric Adapter - Support for IBM Flex System x240 10Gb Virtual Fabric LOM - Support for IBM Flex System Manager 10Gb Virtual Fabric LOM
Firmware Version: 4.2.433.3 Supported On: IBM System x and BladeCenter
Problems Fixed: - Intermittent link status with IBM Virtual Fabric Switch when set to IBM Virtual Fabric Mode - The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from OneCommand Manager. This selection is available in UEFI F1 setup. - Under high network stress, NMI errors can be seen with x3690 X5 and x3850 X5 - 10GbE ports running at 1GbE speed 10% below wirespeed at certain block sizes. - Unable to perform PXE boot with LPVID assigned to vNIC interface - 1Gb ports of HS23 do not handle tagging properly if multichannel mode enabled (pnic ok). Note: ESX driver patch also required. - Port flapping link after FW upgrade and "reboot" when connected to 10Gb PTM module (DAC)
Interoperability Since Previous Release: - Support for Emulex Virtual Fabric Adapter Advanced (BE2) for IBM BladeCenter - Support for Emulex Virtual Fabric Adapter (BE2) for IBM BladeCenter - Support for Emulex Virtual Fabric Adapter (BE2) for IBM System X
Known Issues: - All 10Gb KX4 ports must be used with 10Gb switches. They will not link at 1Gb. This applies to HS23 LOM and IBM BladeCenter VFA adapters only. - IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456
Firmware Version: 4.2.412.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - All VFS on Port 1 on optional Card unreachable from outside the host (x3750 M4) - 'Logical Admin Link' not enabled after applying BOFM in Switch Agnostic mode - IBM pre-boot Diagnostics NIC physical loopback test fails in Command and GUI mode - Multiple cosmetic issues with iSCSI UEFI BIOS - 10Gb ports do not detect 'Link Down' with some switches - 1Gb ports on HS23 LOM not able link up with IBM ICPM (FRU part 44W4486) in BCS chassis - Performance issues with specific DAC cables and SND top of rack switch
Interoperability Since Previous Release: - UEFI 2.3.1 Compliance - Increased VF count in SR-IOV (was 16 VFs per port, is now 32 VFs per port) - Support for next generation 10GbaseT PHY - Expose IBM Feature On Demand licensing information in UEFI configuration utility
Known Issues: - All 10Gb ports must be used with 10Gb switches. They will not link at 1Gb. - IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456 - Intermittent link status with IBM Virtual Fabric Switch when set to IBM Virtual Fabric Mode - The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from OneCommand Manager. This selection is available in UEFI F1 setup.
Firmware Version: 4.1.455.6 Supported On: IBM System x and BladeCenter
Problems Fixed: - Fixed an issue where ASIC randomly hangs losing network connectivity when certain commands are sent from the host. Resulting behavior varies between OS's (Yellow bangs in Windows, PSOD in VMWare) - PHY Loopback fails on 10G ports - UE and hang on LOM or Robalo when powering off Janice in UEFI or PXESelect - Loopback on HS23 now functional in DSAp - DCBX does not converge with firmware on a FCoE fabric - Control C Broken on BE2 - 7 second delay in GET_CARD_ATTRIBUTES command - Emulex VF adapter FCoE link lost on VMware 5.0 - flow control set for 10G Base T phys for autonegotiation - Dynamic link update is not working with NIC UEFI driver - Remove unused definitions in UEFI NIC - Emulex driver expects that the Login Options field be zero - "map r" displays a iSCSI BLK device when no LUNs presented - "X/x Exit without save" does not work as expected - Display proper description as part of EFI Driver Model Related Information - Intermittent "Configuration changed. reset to apply it now?" - Garbled output being displayed at the LUN configuration section. - All Emulex Configuration settings get lost after a reset - Perform additional checks when no Luns are mapped to the target - CHAP name only accepts 6 to 10 characters - Hii ???iSCSI Initiator Configuration??? showing old version screen - iSCSI name is case sensitive - iSCSI HII allows user to select first 8 LUNs as bootable. - iSCSI Boot Enable/Disable option should be port specific - LUN Configuration shows LUN 0, even if no LUNs presented to initiator.
Interoperability Since Previous Release: - Support for Emulex Virtual Fabric Adapter Advanced (CFFh, 2+2) for IBM BladeCenter
Firmware Version: 4.1.334.47 Supported On: IBM System x and BladeCenter
Problems Fixed: - NCSI transmit workaround for IBM - Issues with data reporting when BOFM enabled - Improved network performance throughput - Issues with IBM Management network performance - Logical link status for IBM mezz card shown as 'N/A' - Serial Over LAN fails when more than one blade installed with a single switch - Removed UEFI menu items for unsupported functions on a port - Issues with diagnositics in virtual NIC/UMC mode - Issues with MAC and PHY loopback on OneConnect devices - Several issues with FCoE on some OEM fabric switches
Interoperability Since Previous Release: - Support for HS23 Virtual Fabric LAN on Motherboard - Support for VFA III (95Y3762, 95Y3768), 90Y6456 - Support for IBM's Features on Demand (FOD) - Formal support for SR-IOV
Firmware Version: 4.0.1062.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - iLab Tucson - lpfc Device Resets and path failures continue after error inject. - Writes do not complete when running LIP test on BE3 port 2 - IPV6 implementations no longer experience an unrecognized routing type error. - VLAN tagging is now disabled on the OneConnect UCNA when multichannel is disabled. - UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect 10102-based UCNA. - OneConnect UCNAs no longer send and receive only double-tagged packets and discard all other packets. - PHY, MAC, and External loopback tests no longer fail on all platforms. - Firmware now returns the proper OneConnect UCNA model number. - IPV6 implementations no longer experience an unrecognized routing type error. - Installing Windows 2008 or Windows 2008 R2 on remote iSCSI disks no longer causes the system to hang. - Issues no longer occur when resetting a server configured for multipathing on VMware ESX systems. - VLAN tagging is now disabled on the OneConnect UCNA when multichannel is disabled. - UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect 10102-based UCNA. - OneConnect UCNAs no longer send and receive only double-tagged packets and discard all other packets. - An adapter hardware error no longer occurs when running I/O with LUNs on x86 platforms. - Changing from Convergence Enhanced Ethernet (CEE) to Chassis Internal Network (CIN) and then rebooting no longer fails to link-flap (CIN Fabric Login (FLOGI) now occurs). - PHY, MAC, and External loopback tests no longer fail on all platforms. - Firmware now returns the proper OneConnect UCNA model number. - DCB settings can now be configured. - (iSCSISelect) When enabling DHCP for an iSCSI initiator, the Emulex iSCSI Network Configuration utility now waits approximately 20 seconds to make a DHCP connection before returning control. - (FCoE BootBIOS) FCF CEE parameters for Boot from SAN configuration are now saved properly.
Interoperability Since Previous Release: - Added support for switch-independent multichannel mode. - Added support for IBM Virtual Fabric 10Gb RackSwitch firmware 6.8.1.0. - Added support for IBM Virtual Fabric 10G Switch Module firmware 6.8.1.0. - Added support for Fibre Channel over Ethernet (FCoE) on rack systems. - Added support for iSCSI hardware offload on rack systems. - Added support for Cisco Nexus 5000-series switches.