- Changed version to 11.2 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 11.4 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 12.0 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 11.2 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 11.4 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 12.0 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 11.2 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 11.4 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 12.0 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 11.2 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 11.4 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version to 12.0 - Updated libbrcmdfc library - Updated libbrcmemsdm library - Updated libbrcmhbaapi library - Changed version number to 6.4.12.3 - Fixed Bug 148456: Updated the spec file to use ldconfig -X - Changed version to 10.7 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 7.2, SLES12 SP1 - Changed version to 11.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 11.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.0 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 8, SLES 12 SP4, and SLES 15 SP1 - Removed support for SLES 11 SP3 and SLES 11 SP4 - Changed version to 12.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 12 SP5 - Removed support for RHEL 6 - Changed version to 12.6 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 and SLES 12 SP3 - Changed version to 12.8 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP3 - Changed version number to 6.4.12.3 - Fixed Bug 148456: Updated the spec file to use ldconfig -X - Changed version to 10.7 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 7.2, SLES12 SP1 - Changed version to 11.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 11.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.0 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 8, SLES 12 SP4, and SLES 15 SP1 - Removed support for SLES 11 SP3 and SLES 11 SP4 - Changed version to 12.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 12 SP5 - Removed support for RHEL 6 - Changed version to 12.6 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 and SLES 12 SP3 - Changed version to 12.8 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP3 - Changed version number to 6.4.12.3 - Fixed Bug 148456: Updated the spec file to use ldconfig -X - Changed version to 10.7 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 7.2, SLES12 SP1 - Changed version to 11.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 11.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.0 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 8, SLES 12 SP4, and SLES 15 SP1 - Removed support for SLES 11 SP3 and SLES 11 SP4 - Changed version to 12.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 12 SP5 - Removed support for RHEL 6 - Changed version to 12.6 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 and SLES 12 SP3 - Changed version to 12.8 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP3 - Changed version number to 6.4.12.3 - Fixed Bug 148456: Updated the spec file to use ldconfig -X - Changed version to 10.7 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 7.2, SLES12 SP1 - Changed version to 11.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 11.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.0 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 8, SLES 12 SP4, and SLES 15 SP1 - Removed support for SLES 11 SP3 and SLES 11 SP4 - Changed version to 12.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 12 SP5 - Removed support for RHEL 6 - Changed version to 12.6 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 and SLES 12 SP3 - Changed version to 12.8 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP3 - Changed version number to 6.4.12.3 - Fixed Bug 148456: Updated the spec file to use ldconfig -X - Changed version to 10.7 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 7.2, SLES12 SP1 - Changed version to 11.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 11.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.0 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Changed version to 12.2 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for RHEL 8, SLES 12 SP4, and SLES 15 SP1 - Removed support for SLES 11 SP3 and SLES 11 SP4 - Changed version to 12.4 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 12 SP5 - Removed support for RHEL 6 - Changed version to 12.6 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 and SLES 12 SP3 - Changed version to 12.8 - Updated libdfc library - Updated libemsdm library - Updated libemulexhbaapi library - Added support for SLES 15 SP3 Enablement Kit Version: 6.0.0.0-7 --------------------------------- v6.04 build41: ------------- Defect/Enhancement: Defect Problem: BSG interface fails if /tmp is mounted with tmpfs on shared memory Solution: Use /var/cache/sdmapi for BSG device creation Introduced: v6.04 build1 Impact: HW: All adapters OS: All supported Linux flavors Protocol: FC, FCoE Enablement Kit Version: 6.0.0.0-8 --------------------------------- v6.04 build45: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Add NVRAM parameter to select FCP or NVME targets Introduced: v6.04 build45 Impact: HW: ISP2071, ISP2271, ISP2261, ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC v6.04 build44: ------------- Defect/Enhancement: Defect Problem: Apps issues seen with NVME target in RHEL Solution: Detect NVME target/luns by traversing sysfs tree Introduced: v6.04 build42 Impact: HW: ISP2071, ISP2271, ISP2261, ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC v6.04 build43: ------------- Defect/Enhancement: Defect Problem: Apps issues seen with NVME target in NPIV configuration Solution: Set deafult value of NVME targets for NPIV ports Introduced: v6.04 build42 Impact: HW: ISP2071, ISP2271, ISP2261, ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC v6.04 build42: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Add NVME target support for QLogic/Marvell Apps Introduced: v6.04 build42 Impact: HW: ISP2071, ISP2271, ISP2261, ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC Enablement Kit Version: 6.0.0.0-9 --------------------------------- v6.04 build47: ------------- Defect/Enhancement: Defect Problem: Apps initialization delay seen with NPIV ports Solution: Allow reading active flash regions for NPIV ports Introduced: v6.04 build39 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC v6.04 build46: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Restrict application features for NVME targets Introduced: v6.04 build45 Impact: HW: ISP2071, ISP2271, ISP2261, ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC Enablement Kit Version: 6.0.0.0-10 ---------------------------------- v6.04 build48: ------------- Defect/Enhancement: Defect Problem: NVME targets not seen when NVME Id and Subsys Id are different Solution: Identify NVME targets using subsys Id Introduced: v6.04 build42 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC Enablement Kit Version: 6.0.0.0-11 ---------------------------------- v6.04 build49: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Allow SDGetActiveRegions API for 27xx based adapters Introduced: v6.04 build45 Impact: HW: ISP2071, ISP2271, ISP2261, ISP2871, ISP2971, ISP2A61 OS: All supported Linux flavors Protocol: FC Enablement Kit Version: 6.0.0.0-12 ---------------------------------- v6.04 build52: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Allow SCM stats for NVMe targets for Marvell/QLogic Apps Introduced: v6.04 build52 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC Defect/Enhancement: Enhancement Problem: Modalias removal request from HPE Solution: Remove modalias support from Enablement kit rpm Introduced: Day One Impact: HW: All adapters OS: All supported Linux flavors Protocol: FC v6.04 build51: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Add additional SCM stats for FCP targets for Marvell/QLogic Apps Introduced: v6.04 build51 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC Defect/Enhancement: Defect Problem: Corruption seen after flash update with some inbox drivers when BSG device creation fails Solution: Use /dev/bsg path to create BSG device creation Introduced: v6.00 build9 Impact: HW: All adapters OS: All supported Linux flavors Protocol: FC v6.04 build50: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Allow SCM stats for FCP targets for Marvell/QLogic Apps Introduced: v6.04 build50 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC Enablement Kit Version: 6.0.0.0-13 ---------------------------------- v6.04 build55: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Added MPI Firmware Dump support Introduced: v6.04 build55 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 ISP2071, ISP2271, ISP2261, ISP2871, ISP2971, ISP2A61 OS: All supported Linux flavors Protocol: FC v6.04 build54: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Added Secure remote port info support Introduced: v6.04 build54 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC v6.04 build53: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Check driver for SCM stats support before reading SCM stats Introduced: v6.04 build53 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC Enablement Kit Version: 6.0.0.0-14 ---------------------------------- v6.04 build56: ------------- Defect/Enhancement: Defect Problem: LUN QoS API returns "Not Supported" Solution: Fixed QoS value read issue in BSG path Introduced: v6.04 build21 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 ISP2071, ISP2271, ISP2261, ISP2871, ISP2971, ISP2A61, ISP2031 OS: All supported Linux flavors Protocol: FC Enablement Kit Version: 6.0.0.0-15 ---------------------------------- v6.04 build57: ------------- Defect/Enhancement: Defect Problem: Delay seen in Application bringup on some inbox drivers Solution: Do not perform retries for newer features if driver returns not supported error Introduced: v6.04 build28 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 ISP2071, ISP2271, ISP2261, ISP2871, ISP2971, ISP2A61 OS: All supported Linux flavors Protocol: FC Enablement Kit Version: 6.0.0.0-16 ---------------------------------- v6.04 build63: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Allow NVMe specific APIs for newer ISPs Introduced: v6.04 build63 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 ISP2071, ISP2271, ISP2261, ISP2871, ISP2971, ISP2A61 OS: All supported Linux flavors Protocol: FC v6.04 build62: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Added ISP FW and MPI FW lockdown bits Introduced: v6.04 build62 Impact: HW: ISP2261, ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC v6.04 build61: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Provide lockdown mode error codes to apps Introduced: v6.04 build61 Impact: HW: ISP2261, ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC v6.04 build60: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Added adapter firmware lockdown support Introduced: v6.04 build60 Impact: HW: ISP2261, ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC v6.04 build59: ------------- Defect/Enhancement: Enhancement Problem: N/A Solution: Added EP2989 support Introduced: v6.04 build59 Impact: HW: EP2989 OS: All supported Linux flavors Protocol: FC v6.04 build58: ------------- Defect/Enhancement: Defect Problem: HBA Parameters read fails for newer adapters for inbox drivers Solution: Read active HBA Parameters region set from flash Introduced: v6.04 build24 Impact: HW: ISP2081, ISP2281, ISP2089, ISP2289 OS: All supported Linux flavors Protocol: FC - Initial Development - Initial Development - Initial Development - Initial Development - Initial Development - Initial Development - Initial Development - ENHANCEMENTS - ENHANCEMENTS - ENHANCEMENTS - ENHANCEMENTS - Added RHEL 7 support - Added support for OCe14000 based adapters: 650FLB, 650M, 556FLR-SFP, CN1200E - Added RHEL 7 support - Added support for OCe14000 based adapters: 650FLB, 650M, 556FLR-SFP, CN1200E - Added RHEL 7 support - Added support for OCe14000 based adapters: 650FLB, 650M, 556FLR-SFP, CN1200E - Added RHEL 7 support - Added support for OCe14000 based adapters: 650FLB, 650M, 556FLR-SFP, CN1200E - - - - - Changed version to 12.0 - Initial build - Changed version to 12.0 - Initial build - Changed version to 10.7 - Added support for RHEL 6U8 - Added support for RHEL 7U2 - Added support for SLES12 SP1 - Changed version to 11.0 - Changed version to 11.1 - Added support for RHEL 7U3 - Added support for SLES 12 SP2 - Removed support for RHEL 6U5 - Changed version to 11.2 - Added support for RHEL 6U9 - Added support for RHEL 7U4 - Added support for SLES 12 SP3 - Removed support for RHEL 7U0 - Removed support for SLES 12 SP0 - Changed version to 11.4 - Removed support for RHEL 6U6 - Removed support for RHEL 7U1 - Added support for RHEL 7U5 - Added support for SLES 15 SP0 - Changed version to 12.0 - Removed support for RHEL 6U7 - Removed support for SLES 12 SP1 - Added support for RHEL 6U10 - Added support for RHEL 7U6 - Added support for RHEL 8U0 - Added support for SLES 12 SP4 - Added support for SLES 15 SP1 - Changed version to 12.2 - Removed support for SLES 11 SP3 - Removed support for SLES 11 SP4 - Removed support for RHEL 6U8 - Removed support for RHEL 7U2 - Removed support for RHEL 7U3 - Changed version to 12.4 - Added support for RHEL 7U7 - Added support for RHEL 8U1 - Added support for SLES 12 SP5 - Removed support for RHEL 6U9 - Removed support for RHEL 6U10 - Removed support for RHEL 7U4 - Changed version to 12.6 - Added support for RHEL 7U8 - Added support for RHEL 8U2 - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 - Removed support for SLES 12 SP3 - Changed version to 12.8 - Initial build - Changed version to 10.7 - Added support for RHEL 6U8 - Added support for RHEL 7U2 - Added support for SLES12 SP1 - Changed version to 11.0 - Changed version to 11.1 - Added support for RHEL 7U3 - Added support for SLES 12 SP2 - Removed support for RHEL 6U5 - Changed version to 11.2 - Added support for RHEL 6U9 - Added support for RHEL 7U4 - Added support for SLES 12 SP3 - Removed support for RHEL 7U0 - Removed support for SLES 12 SP0 - Changed version to 11.4 - Removed support for RHEL 6U6 - Removed support for RHEL 7U1 - Added support for RHEL 7U5 - Added support for SLES 15 SP0 - Changed version to 12.0 - Removed support for RHEL 6U7 - Removed support for SLES 12 SP1 - Added support for RHEL 6U10 - Added support for RHEL 7U6 - Added support for RHEL 8U0 - Added support for SLES 12 SP4 - Added support for SLES 15 SP1 - Changed version to 12.2 - Removed support for SLES 11 SP3 - Removed support for SLES 11 SP4 - Removed support for RHEL 6U8 - Removed support for RHEL 7U2 - Removed support for RHEL 7U3 - Changed version to 12.4 - Added support for RHEL 7U7 - Added support for RHEL 8U1 - Added support for SLES 12 SP5 - Removed support for RHEL 6U9 - Removed support for RHEL 6U10 - Removed support for RHEL 7U4 - Changed version to 12.6 - Added support for RHEL 7U8 - Added support for RHEL 8U2 - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 - Removed support for SLES 12 SP3 - Changed version to 12.8 - Initial build - Changed version to 10.7 - Added support for RHEL 6U8 - Added support for RHEL 7U2 - Added support for SLES12 SP1 - Changed version to 11.0 - Changed version to 11.1 - Added support for RHEL 7U3 - Added support for SLES 12 SP2 - Removed support for RHEL 6U5 - Changed version to 11.2 - Added support for RHEL 6U9 - Added support for RHEL 7U4 - Added support for SLES 12 SP3 - Removed support for RHEL 7U0 - Removed support for SLES 12 SP0 - Changed version to 11.4 - Removed support for RHEL 6U6 - Removed support for RHEL 7U1 - Added support for RHEL 7U5 - Added support for SLES 15 SP0 - Changed version to 12.0 - Removed support for RHEL 6U7 - Removed support for SLES 12 SP1 - Added support for RHEL 6U10 - Added support for RHEL 7U6 - Added support for RHEL 8U0 - Added support for SLES 12 SP4 - Added support for SLES 15 SP1 - Changed version to 12.2 - Removed support for SLES 11 SP3 - Removed support for SLES 11 SP4 - Removed support for RHEL 6U8 - Removed support for RHEL 7U2 - Removed support for RHEL 7U3 - Changed version to 12.4 - Added support for RHEL 7U7 - Added support for RHEL 8U1 - Added support for SLES 12 SP5 - Removed support for RHEL 6U9 - Removed support for RHEL 6U10 - Removed support for RHEL 7U4 - Changed version to 12.6 - Added support for RHEL 7U8 - Added support for RHEL 8U2 - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 - Removed support for SLES 12 SP3 - Changed version to 12.8 - Initial build - Fixed discovery of HBAs in adapter_info on Integrity servers with multiple PCI busses - Initial release with Emulex CNA support - Fix for dependency check error seen when installing with HPSUM - Removed installation check for kernel 2.6 and addded Installation check for Rhel5.3 and SLES10 SP3 onwards - Corrected Link state display information for Qlogic Adapters - Added MSA G3 support in Scsi_info.h -Perl dependancy fix for RHEL8 -Initial support added for E4 and will get updated subsequently -Fixed adpater_info code to display correct Vendor name instead of Unknown -Removed Brocade HBAs support -Removed adapter_info_nx code for E4 adapters - Fixed discovery of HBAs in adapter_info on Integrity servers with multiple PCI busses - Initial release with Emulex CNA support - Fix for dependency check error seen when installing with HPSUM - Removed installation check for kernel 2.6 and addded Installation check for Rhel5.3 and SLES10 SP3 onwards - Corrected Link state display information for Qlogic Adapters - Added MSA G3 support in Scsi_info.h -Separated code stream for RHEL and SLES -Initial support added for E4 and will get updated subsequently -Fixed adpater_info code to display correct Vendor name instead of Unknown -Removed Brocade HBAs support -Removed adapter_info_nx code for E4 adapters - Update device guid * Fixed FW update causing NVME drive missing - Fix issues - Fixed to correct the NVMe drive functionality - Correct device GUID. - - Initial Release - Customers who already installed firmware version 24.23.0-0019 do not need to update to 24.23.0-0019 (B). - Releasing support for SUSE LINUX Enterprise Server 15 OS - Added support for the Apollo 4510 system - Fixes installation issues with Intelligent Provisioning and Service Pack for ProLiant Offline. - Over-temp issue was a false IML due to a >=60C threshold, modified the threshold to >65C in new version. Please reference Customer Advisory [a00101958en_us](https://support.hpe.com/hpsc/doc/public/display?docId=emr_na- a00101958en_us) - - Fixed the following: * Fixed unexpected behavior in Active Health System (AHS) logs show World Wide Node Name (wwnn) & World Wide Port Name (wwpn) in reverse order. * Fixed unexpected behavior with HP FlexFabric 20Gb 2-port 650FLB Adapter, HP FlexFabric 20Gb 2-port 650M Adapter cards does not complete to boot to Linux SUSE Linux Enterprise Server 12 Service Pack 3(SLES12 SP3) Operating System (OS) when both adapter are enabled for Fibre Channel over Ethernet (FCoE) boot. * Microsoft Windows Server 2012 R2 Hyper-V Storage Area Network (SAN) Disconnect. * Link lost with firmware version 11.2.1263.19 * "FW not responding" message seen on card when creating Virtual Function (VF) in loop for HPE StoreFabric CN1200E-T 10GBASE-T Converged Network Adapter [NIC+ iSCSI] in Gen10 server. * HP FlexFabric 20Gb 2-port 650FLB Adapter - Loss of access to storage after Virtual Connect (VC) login redistribution * HP StoreFabric CN1200E Dual Port Converged Network Adapter does not complete to boot in Legacy Mode on Gen 9 Server * Emulex Peripheral Component Interconnect (PCI) slot Network Interface Connector (NIC) reported as device path instead of product name * Unable to disable shared memory feature in Human Interface Infrastructure (HII) menu * 650M Adapter has some info in Chinese and Japanese show garbled code under Human Interface Infrastructure (HII) Form - We have separate components to update fibre channel and converged network adapters. This is a converged network adapter update component. Updated CNA (XE100 series) firmware **Firmware** Contains: CNA (XE100 series) firmware 12.0.1280.5 - Fixed the following: UEFI: * Change Unified Extensible Firmware Interface (UEFI) support version from 2.6 to 2.7 * HPE FlexFabric 20Gb 2-port 650FLB Adapter and HPE FlexFabric 20Gb 2-port 650M Adapter does not complete to create boot source on 2nd port Firmware: * Light Emiiting Diode(LED) is in invalid state when disable the port under Unified Extensible Firmware Interface (UEFI) * Duplicate Entries found in firmware report under NIC details for few adaptors. * Full adapter name is not displayed for HPE FlexFabric 20Gb 2-port 650M Adapter in some Rom Based Setup Utility (RBSU). - We have separate components to update fibre channel and converged network adapters. This is a converged network adapter update component. Updated CNA (XE100 series) firmware **Firmware** Contains: CNA (XE100 series) firmware 12.0.1280.5 - Fixed the following: UEFI: * HPE FlexFabric 20Gb 2-port 650FLB Adapter and HPE FlexFabric 20Gb 2-port 650M Adapter does not complete to create boot source on 2nd port Firmware: * Light Emiiting Diode(LED) is in invalid state when disable the port under Unified Extensible Firmware Interface (UEFI) * Duplicate Entries found in firmware report under NIC details for few adaptors. * Full adapter name is not displayed for HPE FlexFabric 20Gb 2-port 650M Adapter in some Rom Based Setup Utility (RBSU). - We have separate components to update fibre channel and converged network adapters. This is a converged network adapter update component. Updated CNA (XE100 series) firmware **Firmware** Contains: CNA (XE100 series) firmware 12.0.1280.5 - Fixed the following: UEFI: * HPE FlexFabric 20Gb 2-port 650FLB Adapter and HPE FlexFabric 20Gb 2-port 650M Adapter does not complete to create boot source on 2nd port Firmware: * Light Emiiting Diode(LED) is in invalid state when disable the port under Unified Extensible Firmware Interface (UEFI) * Duplicate Entries found in firmware report under NIC details for few adaptors. * Full adapter name is not displayed for HPE FlexFabric 20Gb 2-port 650M Adapter in some Rom Based Setup Utility (RBSU). * On any HPE ProLiant server configured with the HPE Emulex XE-102 Based network adapter HPE FlexFabric 10Gb 2-port 556FLR-T Adapter with CNA (XE100 series) firmware 12.0.1110.0, 12.0.1110.10, or 12.0.1110.11 (or later), the network adapters may experience a "link down" state that is not recoverable by a power-cycle or reset. For more details please go through the document titled "HPE ProLiant Servers Configured With Certain HPE Emulex XE-102 Based Network Adapters May Experience Link Down Due To a Firmware Issue" at the following link:<https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00099050en_us> - Updated CNA (XE100 series) firmware This Firmware package contains following firmware versions: Adapter Speed Universal Boot Image Firmware UEFI Boot BIOS HPE FlexFabric 10Gb 2-port 556FLR-T Adapter 10Gb 12.0.1277.0 12.0.1336.0 12.0.1269.0 12.0.1171.0 HPE FlexFabric 10Gb 2-port 556FLR-SFP+ Adapter 10Gb 12.0.1277.0 12.0.1336.0 12.0.1269.0 12.0.1171.0 HPE CN1200E Dual Port Converged Network Adapter 20Gb 12.0.1277.0 12.0.1336.0 12.0.1269.0 12.0.1171.0 HPE CN1200E-T Dual Port Adapter 20Gb 12.0.1277.0 12.0.1336.0 12.0.1269.0 12.0.1171.0 - *Fixed the following:** * Fixed a behavior with internal engineering data display - - *The following fix was incorporated in this version:** * Fixed NVRAM CRC error Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p879663226/v155369/D3000_P07231-002.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following fix was incorporated in this version:** * Fixed NVRAM CRC error Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p879663226/v157942/P07231-003.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following fixes were incorporated in this version:** * Fixed TLB exception during upgrade from Rev build 1.11.000 to 0412.000 * Fixed expander bootstrap task which failed with 0xB1 error code appearing in the console due to missing NVRAM tag - Product Name * Enabled-ClusterS2D command that does not complete with SATA drive in D3610 Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p879663226/v154196/D3000_P07231-004.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * The Enabled-ClusterS2D command now completes successfully when executed on a SATA drive within a D3610 disk enclosure for a NonStop solution. * The smart carrier, which is the drive case for SAS drives, now authenticates in the D3610/D3710 drive enclosure. * Added new 7-segment error codes E0 and E1 to report issues with Fan modules A and B, respectively. These new codes only apply to the D3610/D3710 and only display when running firmware 5.04. * If the storage enclosure processor within the I/O module fails, a hard reset (power down and then power up) is executed to ensure the processor comes back online. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p879663226/v177052/D3000_P07231-006.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * The Enabled-ClusterS2D command now completes successfully when executed on a SATA drive within a D3610 disk enclosure for a NonStop solution. * The smart carrier, which is the drive case for SAS drives, now authenticates in the D3610/D3710 drive enclosure. * Added new 7-segment error codes E0 and E1 to report issues with Fan modules A and B, respectively. These new codes only apply to the D3610/D3710 and only display when running firmware 5.04. * If the storage enclosure processor within the I/O module fails, a hard reset (power down and then power up) is executed to ensure the processor comes back online. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p879663226/v191363/D3000_v5.04B.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * The Enabled-ClusterS2D command now completes successfully when executed on a SATA drive within a D3610 disk enclosure for a NonStop solution. * The smart carrier, which is the drive case for SAS drives, now authenticates in the D3610/D3710 drive enclosure. * Added new 7-segment error codes E0 and E1 to report issues with Fan modules A and B, respectively. These new codes only apply to the D3610/D3710 and only display when running firmware 5.04. * If the storage enclosure processor within the I/O module fails, a hard reset (power down and then power up) is executed to ensure the processor comes back online. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p879663226/v202692/20-D3000-Gen10RN504C_ED3.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following fixes were incorporated in this version:** * The Enabled-ClusterS2D command now completes successfully when executed on a SATA drive within a D3610 disk enclosure for a NonStop solution. * The smart carrier, which is the drive case for SAS drives, now authenticates in the D3610/D3710 drive enclosure. * Added new 7-segment error codes E0 and E1 to report issues with Fan modules A and B, respectively. These new codes only apply to the D3610/D3710 and only display when running firmware 5.04. * If the storage enclosure processor within the I/O module fails, a hard reset (power down and then power up) is executed to ensure the processor comes back online. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p879663226/v202692/20-D3000-Gen10RN504C_ED3.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following fixes were incorporated in this version:** * Temperature sensors logic inside gSEP model and SES database * When an IOM is pulled the surviving IOM reports false critical temperatures Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p1194926978/v172139/D6020_P07232-006.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 8 - *The following fixes were incorporated in this version:** * Temperature sensors logic inside gSEP model and SES database * When an IOM is pulled the surviving IOM reports false critical temperatures Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p1194926978/v177006/D6020_v274_RN.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * Temperature sensors logic inside gSEP model and SES database * When an IOM is pulled the surviving IOM reports false critical temperatures Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p1194926978/v183133/D6020_P07232-008.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * Temperature sensors logic inside gSEP model and SES database * When an IOM is pulled the surviving IOM reports false critical temperatures Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p1194926978/v191364/D6020_v2.74I.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * Temperature sensors logic inside gSEP model and SES database * When an IOM is pulled the surviving IOM reports false critical temperatures Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p1194926978/v202690/20-D6020-Gen10RN274J_ED8.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following fixes were incorporated in this version:** * Temperature sensors logic inside gSEP model and SES database * When an IOM is pulled the surviving IOM reports false critical temperatures Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p1194926978/v202690/20-D6020-Gen10RN274J_ED8.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 8 - *The following fixes were incorporated in this version:** * SAS drive LED behavior was corrected to align with the Smart Array specification, specifically: * The Activity LED of a sanitize erase drive now turns ON when connected. * The Array present LED now turns ON for the SAS drive. * The Activity LED now blinks on all drives during a SAS drive rebuild. * SATA logical drives now display as available after a simultaneous power restore to the server and the D8000. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p480571592/v168048/D8000_v0102_RN.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following fixes were incorporated in this version:** * SAS drive LED behavior was corrected to align with the Smart Array specification, specifically: * The Activity LED of a sanitize erase drive now turns ON when connected. * The Array present LED now turns ON for the SAS drive. * The Activity LED now blinks on all drives during a SAS drive rebuild. * The Serial Output Buffer (SOB) has a fixed sized for stored entries. Now, when the buffer is full, the oldest entries are cleared or committed to persistent storage (if available). For this reason, subsequent requests to read the SOB only retrieves new entries that have been logged since the last successful request to read the SOB. * The drive activity LED has been changed to a function as described in the installation and maintenance guide. * The reboot flag was changed to issue a hard reset, which enables the service delivery subsystem (ZPSDS) information be shared across (expanded across) the internal expanders to all devices attached. * The drive activity LED on the SAS disk drives was changed to support the ACTIVE_LOW signal state. The ACTIVE_LOW signal state is the default operation state for most drives. * The SCSI WRITE BUFFER MODE was changed from activate to soft reset. This change improves the host ability to detect and report whether the enclosure is going to perform a disruptive or non-disruptive activation after a firmware upgrade. * With I/O module firmware v0105 and PQI firmware 2.02 , the slot power cycle issue has been resolved by changing the power cycle SES request to return a failure when a partner slot is not connected. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p480571592/v172138/D8000_P20366-002.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * In STD INQUIRY RESPONSE, the ErrM bit was always being set. The ErrM bit indicates that the enclosure firmware detects a mismatch in any of its package versions and the firmware version of a FRU component. The issue was due to an incorrect version of PSU firmware being included and that has been fixed. * After installing the latest firmware on the enclosure I/O modules, the SES targets could not be discovered on the host. The virtual phy bit in SMP DISCOVER RESPONSE, which is used by the Microchip smartpqi HBA, was det for the virtual phy of the I/O module. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p480571592/v183134/D8000_P20366-004.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * Incorrect programming of the PHY ERROR COUNTERS parameter caused the amber LED to be lit, resulting in a false warning. The counter condition was corrected and the amber LED now functions correctly. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p480571592/v191365/D8000_v0111.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following enhancement has been added in this version:** * Added support of Rhel 7.8 * Added support of Rhel 8.2 * Added support of SLES15 SP2 - *The following fixes were incorporated in this version:** * User was not able to collect ddump logs. * Logical Fault LED remains ON even after clearing the fault using "reboot soft" * Vendor ID showed as "DEFAULT" for D8000 expander in SSACLI enclosure detail Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p480571592/v203448/20-D8000-Gen10RN0118_ED1.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - *The following fixes were incorporated in this version:** * User was not able to collect ddump logs. * Logical Fault LED remains ON even after clearing the fault using "reboot soft". * Vendor ID showed as "DEFAULT" for D8000 expander in SSACLI enclosure detail. * Fixes a problem where after upgrade, drives in slots 1 - 96 may not appear. Please refer to the _[Release Notes_](https://downloads.hpe.com/pub/softlib2/software1/pubsw- linux/p480571592/v203448/20-D8000-Gen10RN0118_ED1.html) for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. - Initial release of Firmware for HPE Persistent Memory for Gen10 Servers. - Initial release of Firmware for HPE Persistent Memory for Gen10 Servers. - Initial release of Firmware for HPE Persistent Memory for Gen10 Servers. * This product contains mainly performance improvements. * This product now supports Red Hat Enterprise Linux 8 and SUSE Linux Enterprise Server 12. - . - Initial release of Firmware for HPE Persistent Memory for Gen10 Plus Servers. - This product corrects an issue that three different capacities of Intel Optane DC Persistent Memory are identifiable with three individual device GUID. - - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the Silicon Platform Services (SPS) Firmware provides mitigation to the latest CSME security vulnerabilities, also known as Local Escalation Privilege. This vulnerability is defined in CVE-2019-0089. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision contains the latest Intel Server Platform Services (SPS) Firmware which provides mitigations for CVE-2019-11090 and CVE 2019-11109. The issues are not unique to HPE servers. **Known Issues:** None - This image contains the latest Intel Server Platform Services (SPS) Firmware which contains mitigations for a variety of security vulnerabilities. The following vulnerabilities have been addressed in this SPS release: CVE-2020-0545 and CVE-2020-0586. These issues are not unique to HPE Servers. - *Important Notes:** This version of the Server Platform Services (SPS) Firmware contains updates aligned with the Intel Product Update (IPU) version IPU.2020.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the Server Platform Services Firmware provides mitigations for security vulnerability documented as CVE-2020-8755. This security vulnerability is documented in Intel Security Advisory INTEL-SA-00391. This issue is not unique to HPE servers. **Known Issues:** None - See the release document in Download Product Binaries page from Product Summary of the firmware product. - *Important Notes:** This version of the Server Platform Services (SPS) Firmware contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the Server Platform Services (SPS) Firmware provides mitigations for SPS security vulnerabilities documented as CVE-2020-24509. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00459. These issues are not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the Server Platform Services (SPS) Firmware contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the Server Platform Services (SPS) Firmware provides mitigations for SPS security vulnerabilities documented as CVE-2021-0060. This issue is not unique to HPE servers. **Known Issues:** None - We have separate components to update fibre channel and converged network adapters. This is a fibre channel update component. **Contains:** 16/32 Gb HBA/Mezz universal boot 12.4.270.14 16 Gb HBA/Mezz universal boot 12.4.270.10 8 Gb standup/mezz firmware 2.10X6 8 Gb standup/mezz universal boot image 12.40a6 (12.4.262.0 BIOS, 12.4.153.0 UEFI) - Fix the following: Where Host Bus Adapters reporting address NACKs (No Acknowledgements) from external temperature sensors. - This is a fibre channel component. Added support for the following: * Code update to support new flash vendors Contains following firmware versions: **Adapter** **Speed** **Universal Boot Image** **Firmware** **UEFI** **Boot Bios** HPE SN1610E 32Gb Dual Port Fibre Channel Host Bus Adapter 32Gb 12.6.275.24 12.6.275.24 12.6.275.7 12.6.271.0 HPE SN1610E 32Gb Single Port Fibre Channel Host Bus Adapter 32Gb 12.6.275.24 12.6.275.24 12.6.275.7 12.6.271.0 - We have separate components to update fibre channel and converged network adapters. This is a fibre channel update component. **Contains:** 32 Gb universal boot 12.6.275.12(EFI 12.6.275.7 BOOT BIOS 12.6.271.0 Firmware 12.6.275.12) 16/32 Gb universal boot 12.6.275.12(EFI 12.6.275.7 BOOT BIOS 12.6.271.0 Firmware 12.6.275.12) 16 Gb universal boot 12.6.275.12(EFI 12.6.275.7 BOOT BIOS 12.6.271.0 Firmware 12.6.275.12) 8 Gb HBA Standup firmware 2.10X6 8 Gb standup universal boot image 12.60a4(12.6.302.0 BIOS, 12.6.284.0 UEFI) - *Added the following:-** * Added support for Distributed Management Task Force (DMTF) - Platform Level Data Model (PLDM) Firmware Update to the SN1200E, SN1600E, and SN1610E * The adapter will now reset to defaults when the user activates Hewlett Packard Enterprise (HPE) Secure Erase from Hewlett Packard Enterprise (HPE) intelligent provisioning * Added support for Fabric Performance Impact Notifications (FPIN) This Firmware package contains following firmware versions: **Adapter** **Speed** **Universal Boot Image** **Firmware** **UEFI** **Boot Bios** HPE 81E 8Gb Single Port PCIe Fibre Channel Host Bus Adapter 8Gb 12.80a3 2.10X6 12.8.183.0 12.8.9.0 HPE 82E 8Gb Dual Port PCIe Fibre Channel Host Bus Adapter 8Gb 12.80a3 2.10X6 12.8.183.0 12.8.9.0 HPE 84E 8Gb Quad Port Fibre Channel Host Bus Adapter 8Gb 12.80a3 2.10X6 12.8.183.0 12.8.9.0 HPE SN1000E 16Gb Dual Port Fibre Channel Host Bus Adapter 16Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1000E 16Gb Single Port Fibre Channel Host Bus Adapter 16Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1100E 16Gb Dual Port Fibre Channel Host Bus Adapter 16Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1100E 16Gb Single Port Fibre Channel Host Bus Adapter 16Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1100E Quad Port 16Gb Fibre Channel Host Bus Adapter 16Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1200E 16Gb Dual Port Fibre Channel Host Bus Adapter 16Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1200E 16Gb Single Port Fibre Channel Host Bus Adapter 16Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1600E 32Gb Dual Port Fibre Channel Host Bus Adapter 32Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1600E 32Gb Single Port Fibre Channel Host Bus Adapter 32Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1610E 32Gb Single Port Fibre Channel Host Bus Adapter 32Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 HPE SN1610E 32Gb Dual Port Fibre Channel Host Bus Adapter 32Gb 12.8.352.12 12.8.352.12 12.8.352.10 12.8.352.5 - *Fixed the following:** * Fixed a behavior where the SN1600E would wrongly display an unwanted message when loading Unified Extensible Firmware Interface (UEFI) driver defaults - This is a fibre channel component. Added support for the following: * Code update to support new flash vendors Contains following firmware versions: **Adapter** **Speed** **Universal Boot Image** **Firmware** **UEFI** **Boot Bios** HPE SN1610E 32Gb Dual Port Fibre Channel Host Bus Adapter 32Gb 12.8.352.24 12.8.352.24 12.8.352.10 12.8.352.5 HPE SN1610E 32Gb Single Port Fibre Channel Host Bus Adapter 32Gb 12.8.352.24 12.8.352.24 12.8.352.10 12.8.352.5 - This Firmware package contains following firmware versions: **Adapter** **Speed** **Universal Boot Image** **Firmware** **UEFI** **Boot Bios** HPE SN1200E 16Gb Dual Port Fibre Channel Host Bus Adapter 16Gb 12.8.528.12 12.8.528.12 12.8.528.10 12.8.502.0 HPE SN1200E 16Gb Single Port Fibre Channel Host Bus Adapter 16Gb 12.8.528.12 12.8.528.12 12.8.528.10 12.8.502.0 HPE SN1600E 32Gb Dual Port Fibre Channel Host Bus Adapter 32Gb 12.8.528.12 12.8.528.12 12.8.528.10 12.8.502.0 HPE SN1600E 32Gb Single Port Fibre Channel Host Bus Adapter 32Gb 12.8.528.12 12.8.528.12 12.8.528.10 12.8.502.0 HPE SN1610E 32Gb Single Port Fibre Channel Host Bus Adapter 32Gb 12.8.528.12 12.8.528.12 12.8.528.10 12.8.502.0 HPE SN1610E 32Gb Dual Port Fibre Channel Host Bus Adapter 32Gb 12.8.528.12 12.8.528.12 12.8.528.10 12.8.502.0 - This Firmware package contains following firmware versions: **Adapter** **Speed** **Universal Boot Image** **Firmware** **UEFI** **Boot Bios** HPE SN1700E 64Gb Dual Port Fibre Channel Host Bus Adapter 64Gb 12.8.528.21 12.8.528.21 12.8.528.10 12.8.502.0 HPE SN1700E 64Gb Single Port Fibre Channel Host Bus Adapter 64Gb 12.8.528.21 12.8.528.21 12.8.528.10 12.8.502.0 - - Updated the Firmware/BIOS/UEFI packages for following: * Gen6 Fibre Channel Host Bus Adapter: * Package 1.73.08 * Firmware 8.08.230 * UEFI 7.02 * BIOS 3.64 * Gen7 Fibre Channel Host Bus Adapter: * Package 02.02.18 * Firmware 09.02.20 * UEFI 7.08 * BIOS 0.0 - *Fixed the following:** In extremely rare cases, the following QLogic Fibre Channel (FC) Host Bus Adapters (HBAs), SN1100Q, SN1600Q and SN1610Q may cause the host Operating System (OS) to stop. Subsequent OS reboot may reveal some filesystem data is unavailable or inconsistent. Out of an abundance of caution, HPE updated the Firmware/BIOS/UEFI (Boot Image) packages for these adapters to eliminate possible exposure to this extremely rare but critical issue. Additional issue details will be published when they become available. - Updated the Firmware/BIOS/UEFI packages for following: * Gen4 Fibre Channel Host Bus Adapter: * Package 3.81.05 * Firmware 8.08.206 * UEFI 7.00 * BIOS 3.56 * Gen5 Fibre Channel Host Bus Adapter: * Package 6.02.01 * Firmware 8.08.230 * UEFI 7.02 * BIOS 3.43 * Gen6 Fibre Channel Host Bus Adapter: * Package 1.73.08 * Firmware 8.08.230 * UEFI 7.02 * BIOS 3.64 * Gen7 Fibre Channel Host Bus Adapter: * Package 02.02.18 * Firmware 09.02.20 * UEFI 7.08 * BIOS 0.0 - *Fixed the following:** In extremely rare cases, the following QLogic Fibre Channel (FC) Host Bus Adapters (HBAs), SN1100Q, SN1600Q and SN1610Q may cause the host Operating System (OS) to stop. Subsequent OS reboot may reveal some filesystem data is unavailable or inconsistent. Out of an abundance of caution, HPE updated the Firmware/BIOS/UEFI (Boot Image) packages for these adapters to eliminate possible exposure to this extremely rare but critical issue. For more details please go through the document titled "HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link: [https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a000947 22en_us](https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId =a00094722en_us) - Updated the Firmware/BIOS/UEFI packages for following: * Gen4 Fibre Channel Host Bus Adapter: * Package 3.81.05 * Firmware 8.08.206 * UEFI 7.00 * BIOS 3.56 * Gen5 Fibre Channel Host Bus Adapter: * Package 6.02.01 * Firmware 8.08.230 * UEFI 7.02 * BIOS 3.43 * Gen6 Fibre Channel Host Bus Adapter: * Package 1.73.08 * Firmware 8.08.230 * UEFI 7.02 * BIOS 3.64 * Gen7 Fibre Channel Host Bus Adapter: * Package 02.02.18 * Firmware 09.02.20 * UEFI 7.08 * BIOS 0.0 - *Fixed the following:** In extremely rare cases, the following QLogic Fibre Channel (FC) Host Bus Adapters (HBAs), SN1100Q, SN1600Q and SN1610Q may cause the host Operating System (OS) to stop. Subsequent OS reboot may reveal some filesystem data is unavailable or inconsistent. Out of an abundance of caution, HPE updated the Firmware/BIOS/UEFI (Boot Image) packages for these adapters to eliminate possible exposure to this extremely rare but critical issue. For more details please go through the document titled "HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link: [https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a000947 22en_us](https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId =a00094722en_us) - Updated the Firmware/BIOS/UEFI packages for 8 Gb, 16 Gb and 32 Gb products. * 8Gb Fibre Channel Host Bus Adapter: * Package 3.82.00 * Firmware 8.08.207 * UEFI 7.00 * BIOS 3.56 * 16Gb Fibre Channel Host Bus Adapter: * Package 6.03.00 * Firmware 8.08.231 * UEFI 7.02 * BIOS 3.43 * 16Gb/32Gb Fibre Channel Host Bus Adapter: * Package 1.74.07 * Firmware 9.03.00 * UEFI 7.02 * BIOS 3.64 * 32Gb Fibre Channel Host Bus Adapter: * Package 02.03.06 * Firmware 09.04.01 * UEFI 7.08 * BIOS 0.0 - *Added the following:-** * Added support for Fabric Performance Impact Notifications (FPIN) This Firmware package contains following firmware versions: Adapter Speed MBI Firmware UEFI Boot Bios HPE 81Q 8Gb PCIe Fibre Channel Host Bus Adapter 8Gb 3.82.00 8.08.207 7.00 3.56 HPE 82Q 8Gb Dual Port PCIe Fibre Channel Host Bus Adapter 8Gb 3.82.00 8.08.207 7.00 3.56 HPE 84Q 8Gb Quad Port Fibre Channel Host Bus Adapter 8Gb 3.82.00 8.08.207 7.00 3.56 HPE SN1000Q 16GB Dual Port PCIe Fibre Channel Host Bus Adapter 16Gb 6.04.04 8.08.232 7.04 3.43 HPE SN1000Q 16GB Single Port PCIe Fibre Channel Host Bus Adapter 16Gb 6.04.04 8.08.232 7.04 3.43 HPE SN1100Q 16GB Dual Port PCIe Fibre Channel Host Bus Adapter 16Gb 1.75.07 9.06.02 7.04 3.64 HPE SN1100Q 16GB Single Port PCIe Fibre Channel Host Bus Adapter 16Gb 1.75.07 9.06.02 7.04 3.64 HPE SN1600Q 32Gb Single Port Fibre Channel Host Bus Adapter 32Gb 1.75.07 9.06.02 7.04 3.64 HPE SN1600Q 32Gb Dual Port Fibre Channel Host Bus Adapter 32Gb 1.75.07 9.06.02 7.04 3.64 HPE SN1610Q 32Gb Dual Port Fibre Channel Host Bus Adapter 32Gb 02.04.07 09.06.02 7.11 0.0 HPE SN1610Q 32Gb Single Port Fibre Channel Host Bus Adapter 32Gb 02.04.07 09.06.02 7.11 0.0 - *Fixed the following:-** * Enhancements have been made to the firmware to prevent and better recover from any stoppage as described in Customer Advisory available at [https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us](https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us) * Fixed a behavior where the number of active Input/Output (IO) exchanges could be reduced under certain fabric conditions, resulting in reduced performance. - - Update device guid * Fixed FW update causing NVME drive missing - Fix issues - *Fixes submitted in version 12.27.1016:** * ZTR counters query was always set to return 0. * The adapter card was prevented from going into the bypass mode when the BMC disabled the hardware arbitration. * Performance degradation and a high packet drop occurred when SRIOV was enabled and packets went through the FDB default behaviour. * Due to the string DB not being updated after Live-Patch, the tracer could not function after Live-Patch. * Fixed a rare issue that caused other active functions to receive a malformed CQE during driver (PF or VF) unload or FLR flows. * Firmware error was observed when FLR occurred at the same time as the teardown. As a result, the teardown flow took a lock, and never released it because it was being aborted by an FLR. **Fixes submitted in version 16.27.1016:** * Fixed an issue that caused the device to perform DMA into memory already returned to the OS during the transition between the pre-boot driver to the OS driver. * Out-of-range issue when reading or writing the q_counters. * Fixed an issue that in Multi-Host adapter cards that resulted in wrong handling of PERST on auxiliary links. * ZTR counters query was always set to return 0. * The adapter card was prevented from going into the bypass mode when the BMC disabled the hardware arbitration. * A non-standard tool was required to perform the first LFWP patching when used with the GA firmware version. * Updated the OOOSLMask behaviour. Firmware now will apply OOOSLMask even if it is set to zero (OOOSLMask = 0). * Redundant page consumption in the init_hca. * The sw_reset option was not supported when ATS was enabled. * When ESWITCH_IPV4_TTL_MODIFY_ENABLE configuration was enabled in mlxconfig, there was performance degradation in small packet sizes. * Due to the string DB not being updated after Live-Patch, the tracer could not function after Live-Patch. * Fixed a rare issue that caused other active functions to receive a malformed CQE during driver (PF or VF) unload or FLR flows. * The PCI link was not getting established when the firmware was corrupted. * FW assert was triggerred and resulted in a wrong deallocation of a resource when Packet Pacing was enabled, and a QP was being destroyed. * Firmware error was observed when FLR occurred at the same time as the teardown. As a result, the teardown flow took a lock, and never released it because it was being aborted by an FLR. - *Firmware for the following devices are updated to 12.27.4000:** 825110-B21 (HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter) 825111-B21 (HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter) **New Feature and Changes in Version 12.27.4000:** * Added the following segments, as appeared in the PRM, to the Resource Dump: * PRM_QUERY_QP * PRM_QUERY_CQ * PRM_QUERY_MKEY * QUERY_VNIC_ENV **Firmware for the following devices are updated to 16.27.2008:** 879482-B21 (HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter) 872726-B21 (HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter) **New Feature and Changes in Version 16.27.2008:** **This release contains important reliability improvements and security hardening enhancements. Upgrade the firmware of the device to this release to improve the devices' firmware security and reliability.** * Improved init_hca performance in Parallel Function initialization. - *Following issues have been fixed in firmware version 16.27.2008:** * Although the effective BER (after FEC) was expected to meet the design targets (e.g. 10e-14 or lower), occasionally it was higher. * High BER occured when connecting cables of type 0.5/1m DAC to an HDR speed. * The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled. * The desched_threshold field did not work properly. * The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter. * If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again. **Following issues have been fixed in firmware version 12.27.4000:** * The device hung while running the sw reset flow under heavy stress and with many open resources. * Low PXE performance observerd while using the VSC to trigger the send_ring_doorbells. * IPoIB and DC would not work together. * DC funtionality issues. - *Firmware for the following devices are updated to 12.28.1002:** 825110-B21 (HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter) 825111-B21 (HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter) **New Feature and Changes in Version 12.28.1002:** * Increased the maximum XRQ number to 512. **Firmware for the following devices are updated to 16.29.1016:** 879482-B21 (HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter) 872726-B21 (HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter) **New Feature and Changes in Version 16.29.1016:** Added support for the following features: * Changed the default value of DCQCN's (Data center- Quantized Congestion Notification) NP parameter min_time_between_cnps to 4 on all devices to support larger scalability of cluster. * An option to allow applications to build their own QoS tree over the NIC hierarchy by connecting QPs to responder/requestor Queue Groups. * "InfiniBand" properties set to the Network Device Function Redfish object. * HW support for Flow Metering to utilize Advanced Steering Operation (ASO). HW Flow Meter allows higher scale, more accuracy, and better performance compared to the FW Flow Metering. * Trust level for VFs. Once the VF is trusted, it will get a set of trusted capabilities. * 2 new Mini CQE formats: Responder Mini CQE With Flow Tag Layout Responder Mini CQE With l3_l4_info Layout * UCX can now enable AR by exposing Out-Of-Ordering bitmask per SL with "ooo_per_sl" field in the HCA_VPORT context. It can be also queried by running the QUERY_HCA_VPORT_CONTEXT command. * Steering DP hash flow groups. * A new counter per vPort that counts the number of packets that reached the Ethernet RQ but cannot fit into the WQE due to their large size. Additionally, we added the option to control if such packet will cause "CQE with Error" or "CQE_MOCK". * PCIe Rx modifications to prevent the adapter cards from disappearing from the system. * ignore_flow_level is now enabled by the TRUST LEVEL access registry. * cq_overrun counter. The counter represents the number of times CQs enter an error state due to overflow that occur when the device tries to post a CQE into a full CQ buffer. * [Beta] Enabled the capability to allow Virtual Functions to send Pause Frames packets. * Enabled 10/25GbE auto-sensing with 3rd party when using 10/25GbE optical cables. * Hardware steering dump output used for debugging and troubleshooting. - *Following issues have been fixed in firmware version 16.29.1016:** * An issue that prevented VXLAN packets with svlan/ cvlan tag from being matched. * An issue that caused the eth_wqe_too_small counter to count ODP (On-Demand Paging) page faults. * When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs are configured, VM restart (VF/PF FLR) will take longer than when MKEY_BY_NAME is disabled. * An issue that resulted in low performance after enabling the RoCE Accelerator capability. Note: The fix is available when all ports are set as Ethernet. * On rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR. * The chassis manager calculation for Multi-Host and Socket-Direct adapter cards to allow running NC-SI commands by the chassis manager BMC. Now the chassis manager is count as BMC with index 0, regardless of how many BMC there are. * An issue that caused the device to go to down IRISC as one of the firmware semaphores could not be released when a speed change or port state change was triggered. **Following issues have been fixed in firmware version 12.28.1002:** * An issue that caused the DCR to be destroyed before the retry option managed to work when the retry timeout is too big. In this case the DCR' time-to-live was increased, and the maximum retry timeout was decreased. * Increased PHY power consumption limit to 1.5w. * An issue that caused PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr not to report port icrc errors. - *Firmware for the following devices are updated to 12.28.1002:** 825110-B21 (HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter) 825111-B21 (HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter) **New Feature and Changes in Version 12.28.1002:** * Increased the maximum XRQ number to 512. **Firmware for the following devices are updated to 16.31.1200:** 879482-B21 (HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter) 872726-B21 (HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter) **New Feature and Changes in Version 16.31.1200:** * .Added a new NVconfig per Port for a specific Finisar module which sets the port to work in AN mode and sets the module to No DME. This change does not affect the speed logic, only the FEC logic (FEC override). **Note**: If the port does not come up, switch to Force mode. - *Following issues have been fixed in firmware version 12.28.1002:** * An issue that caused the DCR to be destroyed before the retry option managed to work when the retry timeout is too big. In this case the DCR' time-to-live was increased, and the maximum retry timeout was decreased. * Increased PHY power consumption limit to 1.5w. * An issue that caused PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr not to report port icrc errors. **No fixes are included in firmware version 16.31.1200.** - *Firmware for the following devices are updated to 12.28.2006:** 825110-B21 (HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter) 825111-B21 (HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter) **New Feature and Changes in Version 12.28.2006:** * Increased the maximum XRQ number to 512. **Firmware for the following devices are updated to 16.31.1200:** 879482-B21 (HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter) 872726-B21 (HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter) **New features and changes included in version 16.31.1200:** * NIC scheduling feature support has been disabled for non-privileged functions. * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * support for Enabling/Disabling NIC and RDMA (port/partition) was included via the UEFI HII system settings. * Increased the maximum number of MSIX per VF to 127. * Asymmetrical MSIX Configuration: This feature allows the device to be configured with a different number of MSIX vectors per physical PCI functions.To use this feature, please follow these steps: * Clear NUM_PF_MSIX_VALID to disable global symmetrical MSIX configuration. * Set PF_NUM_PF_MSIX_VALID to enable asymmetrical per Physical Function MSIX configuration. * Configure PF_NUM_PF_MSIX per physical PCI function. * RDMA partitioning and RDMA counters in IB mode. * Added a new bit ("data_in_order") to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. * Enabled UID 0 to create resources with UMEM (User Memory). * Receiving and sending native IB packets from/to the software (including all headers) via raw IBL2 QPs. * RX RDMA NIC flow table on an IB port. Now the software can steer native IB packets to raw IB receive queues according to the DLID and the DQPN. * Added a new NVconfig per Port for a specific Finisar module. This new NVconfig sets the port to work in AN mode and sets the module to No DME. This change does not affect the speed logic, only the FEC logic (FEC override). **Note:** If the port does not go up, switch to Force mode. - *Following issues have been fixed in firmware version 12.28.2006:** * An issue that caused the DCR to be destroyed before the retry option managed to work when the retry timeout is too big. In this case the DCR' time-to-live was increased, and the maximum retry timeout was decreased. * Increased PHY power consumption limit to 1.5w. * An issue that caused PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr not to report port icrc errors. **The following issues have been fixed in version 16.31.1200:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * An assert that was caused when trying to open 1024 functions on the device and the maximum number of functions was 1023. * Occasional performance issues related to RC QPs using E2E-credits (not connected to SRQ and doing send/receive traffic) when the ROCE_ACCL tx_window was enabled. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * A rare issue that caused RX pipe to hang. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. * CRT_DCR with index larger than 1 << 21 occasionally collided with the CRT_SW_RESERVED address. * An issue that caused the TX queue to get into an unresponsive state when the VF rate limiter was set. **Additional Fixes included in version 16.31.1200:** * Disabled the CNP counter "rp_cnp_ignored " (triggered by OOS (out-of-sequence)) when all ports are IB. * Fixed the TMP421 sensor temperature reporting. * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. - *Fixes in version 12.28.2006:** * Fixes an issue that caused the DCR to be destroyed before the retry option managed to work when the retry timeout is too big. In this case the DCR' time-to-live was increased, and the maximum retry timeout was decreased. * Increased PHY power consumption limit to 1.5w. * Fixed n issue that caused PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr not to report port icrc errors. **The following issues have been fixed in version 16.32.1010** * Firmware got into an unresponsive state and caused unexpected behavior when connecting an optical transceiver that support RxLOS and the remote side port was down. * The link status was reported incorrectly and consequently caused the link to go down due to incorrect definition of the RX_LOS polarity in the INI. * The system got into an unresponsive state when a peer port went down while using an Optical module. * Invalid RNR timeout when trying to set it during the rts2rts_qp transition. * A fatal assert 0x81C5 occurred when calling get_vport_mad from the MAD APIs. The firmware was trying to compute the number of vPorts using a global function number. To avoid this issue, the API was updated to remove any assumption on the function number. Note: This issue is affects only IB devices. * During events, stress caused the firmware to reset the Arm host of the vPort without sending an event. Thus preventing the software from rearming the vPort as it did not receive any event, and the firmware did not send the event because the vPort had no Arm set. * The system could not create more than 128K QPs. * The GetInventory NC-SI command reported leading 0xf in firmware version when it started with 0. * PCIe lane margining capability issues. * An issue related to the sl2vl mad that caused a few msec hiccup in the transmission on an InfiniBand network when the SM sent the sl2vl mad to a node in the cluster. - *Fixes submitted in version 20.27.1016:** * The Adapter card used to get stuck in "polling" state after resetting/power cycling the card. * Fixed a PCIe PLL (Phase Locked Loop) varactor calibration logic to address potential silicone variations. * An issue that caused the ZTR (Zero Touch RoCE) counters query to always return 0. - *New Features and Changes in Version 20.27.2008:** * 200GbE speed rate is at GA level. * All Ethernet speeds at GA level including PAM4(Pulse Amplitude Modulation) vs NRZ (non-return-to-zero)and speed detection. - *The following issues have been fixed in version 20.27.2008:** * CWDM4(Coarse Wavelength Division Multiplexing) Acousto Optical Modulator(AOM) cable was not supported. * Links between ConnectX-6 adapter cards and Spectrum-2 SN3700 switch systems did not come up when using Cisco BiDi module at 100GbE link speed. * Occasionally, the link was not raised when working with split 2x100 mode with Optical cables. * The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled. * The desched_threshold field did not work properly. * The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter. * If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again. * Aligned the User Memory page to 2, e.g., the user should use 8k aligned (like 0, 8k, 16k etc., instead of 0, 4k, 12k etc.). * NRZ (non-return-to-zero) and PAM4 (Pulse amplitude modulation) Limitations in 100GbE adapter cards: * The default configuration was NRZ speeds in Auto-Neg mode. * PAM4 speeds had to be set manually (using the MFT tool - mlxlink). * PAM4 speeds had to be configured as single speeds: 50G_1x or 100G_2x. * 200G_4x optical cables (including 200G_4x splitter cable) would raise link only after manual configuration of PAM4 speeds (50G_1x or 100G_2x). * NRZ and PAM4 Limitations in 200GbE adapter cards: * The default configuration was 200G_x4 in Force mode. * NRZ speeds had to be set manually. Configuration could include multiple NRZ speeds (using the MFT tool - mlxlink). * PAM4 speeds had to be configured as single speeds: 50G_1x or 100G_2x or 200G_4x. * In Ethernet mode, at 25/50/100GbE speeds, only RS-FEC in Force mode was supported. Other user configurations were overridden. - *Firmware for the following devices are updated to 20.27.6008:** HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter - P06154-B21 HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter - P06250-B21 HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter - P06251-B21 **New Features and Changes in Version 20.27.6008:** * The following are the minimal software/firmware versions that support PAM4 link speeds when connected using Mellanox NIC to Mellanox Switch and Mellanox NIC to 3rd Party Switches: * Mellanox Onyx: 3.9.0830-038 * ConnectX-6: 20.27.2008* *Note: NICs with this firmware version support Mellanox-to-Mellanox connectivity with PAM4 link speeds. * Added support for the following features: * Enabled KP4RS FEC on Active Fiber cable up to 30m. * FDR protocol. * Enabled updating End-to-End (E2E) credit packets instantly. - *There are no new fixes in firmware version 20.27.6008.** - *Firmware for the following devices are updated to 20.29.1016:** HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter - P06154-B21 HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter - P06250-B21 HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter - P06251-B21 **New Features and Changes in Version 20.29.1016:** Added support for following features: * LinkX module burning via MFT toolset. The new capability enables direct firmware burning from the internal flash storage to reduce the bandwidth and accelerate the burning process, including burning several modules at a time. * An option to allow applications to build their own QoS tree over the NIC hierarchy by connecting QPs to responder/requestor Queue Groups. * Improved NRZ link performance (RX algorithm). * Improved NRZ link-up time (25G(G@G speeds). * Enabled the options to control different Tx sets for the same attribute when connecting a Mellanox-Mellanox vs Mellanox to 3rd party HCA. * "InfiniBand" properties set to the Network Device Function Redfish object. * Direct Packet Placement (DPP): DPP is a receive side transport service in which the Ethernet packets are scattered to the memory according to a packet sequence number (PSN) carried by the packet, and not by their arrival order. * To enable DPP offload, the software should create a special RQ by using the CREATE_RQ command, and set DPP relevant attributes. * Added trust level for VFs. Once the VF is trusted, it will get a set of trusted capabilities. * UCX can now enable AR by exposing Out-Of-Ordering bitmask per SL with "ooo_per_sl" field in the HCA_VPORT context. It can be also queried by running the QUERY_HCA_VPORT_CONTEXT command. * Enhanced IB Congestion Control to support lower minimum rate. Now it uses destination-lid to classify flows to handle larger scale, and achieve better results in GPCNeT benchmark. * Hardware steering dump output used for debugging and troubleshooting. - *The following issues have been fixed in version 20.29.1016:** * Changed the default value of DCQCN's (Data center- Quantized Congestion Notification) NP parameter min_time_between_cnps to 4 on all devices to support larger scalability of cluster. * An issue that prevented VXLAN packets with svlan/cvlan tag from being matched. * The eth_wqe_too_small counter to count ODP (On-Demand Paging) page used to fail. * An issue related to raising 100GbE link on ConnectX-6 VPI 100Gb/s adapter cards. * When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs are configured, VM restart (VF/PF FLR) will take longer than when MKEY_BY_NAME is disabled. * Low performance occurred after enabling the RoCE Accelerator capability. * On rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR. - *Firmware for the following devices are updated to 20.31.1014:** HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter - P06154-B21 HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter - P06250-B21 HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter - P06251-B21 **New features and changes included in version 20.31.1014:** * NIC scheduling feature support has been disabled for non-privileged functions. * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * Updated the NC-SI speed reporting output to support 200GbE speed. Now when running the NC-SI command, the output presents 200GbE speed as well. * support for Enabling/Disabling NIC and RDMA (port/partition) was included via the UEFI HII system settings. * Increased the maximum number of MSIX per VF to 127. * Asymmetrical MSIX Configuration: This feature allows the device to be configured with a different number of MSIX vectors per physical PCI functions.To use this feature, please follow these steps: * Clear NUM_PF_MSIX_VALID to disable global symmetrical MSIX configuration. * Set PF_NUM_PF_MSIX_VALID to enable asymmetrical per Physical Function MSIX configuration. * Configure PF_NUM_PF_MSIX per physical PCI function. * RDMA partitioning and RDMA counters in IB mode. * Added a new bit ("data_in_order") to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. * Enabled UID 0 to create resources with UMEM (User Memory). * Receiving and sending native IB packets from/to the software (including all headers) via raw IBL2 QPs. * RX RDMA NIC flow table on an IB port. Now the software can steer native IB packets to raw IB receive queues according to the DLID and the DQPN. - *The following issues have been fixed in version 20.31.1014:** * Occasional performance issues related to RC QPs using E2E-credits (not connected to SRQ and doing send/receive traffic) when the ROCE_ACCL tx_window was enabled. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * A rare issue that caused RX pipe to unresponsive state. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. * CRT_DCR with index larger than 1 << 21 occasionally collided with the CRT_SW_RESERVED address. * An issue that caused the TX queue to get into an unresponsive state when the VF rate limiter was set. * In InfiniBand non-virtualization system, due to a corrupted steering root, traffic fails after a warm reboot. **Additional Fixes included in version 20.31.1014:** * Disabled the CNP counter "rp_cnp_ignored " (triggered by OOS (out-of-sequence)) when all ports are IB. * Fixed the TMP421 sensor temperature reporting. * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. * Improved PortXmitWait IB counter accuracy. - *The following issues have been fixed in version 20.32.1010:** * System could not create more than 128K QPs. * Incorrect indication of the PCIe link down in the AER registers on PCIe switch upstream port. * Invalid RNR timeout when trying to set it during the rts2rts_qp transition. * The flash frequency on boot was lower than expected (under 50Mhz). The issue was fixed by enabling the firmware to increase it on boot2 to normal frequency. * A race condition between DC QP flush and DC packets that led to stuck slices in the hardware. To avoid such situation, firmware keeps the TCU drop set until QP flush is done. * Firmware got into an unresponsive state and caused unexpected behavior when connecting an optical transceiver that support RxLOS and the remote side port was down. * The link status was reported incorrectly and consequently caused the link to go down due to incorrect definition of the RX_LOS polarity in the INI. - *Fixes in version 2.42.5000:** * PortRcvPkts counter was prevented from being cleared after resetting it. * The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec. * The server hangs and results in NMI when running "mlxfwtop -d mt4103_pci_cr0" while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error. * In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot. * While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck. * The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed. * ibdump could not capture all MADs packets. * link did not go up after reboot. * Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions. * Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad. **Fixes in version 2.42.5044:** * Fixed an issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode **Fixes in version 2.42.5052:** * Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver's teardown. - *Firmware for the following devices are updated to 2.42.5000:** 764282-B21 764286-B21 **Firmware for the following devices are updated to 2.42.5044:** 764284-B21 764285-B21 **Firmware for the following devices are updated to 2.42.5052:** 764283-B21 **New features in firmware version 2.42.5000:** * Added support for the following features. * new TLV: CX3_GLOBAL_CONF to enable/disable timestamp on incoming packets through mlxconfig configuration. * User MAC configuration. * Automatically collecting mstdump before driver reset. * A mechanism to detect DEAD_IRISC (plastic) from TPT (iron) and raise an assert. * A new field is added to "set port" command which notifies the firmware what is the user_mtu size. * Improved the debug ability for command timeout cases **Smart Component Fixes:** * Mellanox Infiniband 544 NIC Interface Shows Incorrectly as PCI Bus:Dev.Funtion in Smart Update Manager(SUM) Report. - *Fixes in version 2.42.5000:** * PortRcvPkts counter was prevented from being cleared after resetting it. * The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec. * The server hangs and results in NMI when running "mlxfwtop -d mt4103_pci_cr0" while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error. * In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot. * While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck. * The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed. * ibdump could not capture all MADs packets. * link did not go up after reboot. * Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions. * Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad. **Fixes in version 2.42.5044:** * Fixed an issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode **Fixes in version 2.42.5052:** * Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver's teardown. - *Firmware for the following devices are updated to 2.42.5000:** 764282-B21 764286-B21 **Firmware for the following devices are updated to 2.42.5052:** 764283-B21 764284-B21 764285-B21 **New features in firmware version 2.42.5000:** * Added support for the following features. * new TLV: CX3_GLOBAL_CONF to enable/disable timestamp on incoming packets through mlxconfig configuration. * User MAC configuration. * Automatically collecting mstdump before driver reset. * A mechanism to detect DEAD_IRISC (plastic) from TPT (iron) and raise an assert. * A new field is added to "set port" command which notifies the firmware what is the user_mtu size. * Improved the debug ability for command timeout cases - *Fixes in version 2.42.5000:** * PortRcvPkts counter was prevented from being cleared after resetting it. * The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec. * The server hangs and results in NMI when running "mlxfwtop -d mt4103_pci_cr0" while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error. * In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot. * While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck. * The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed. * ibdump could not capture all MADs packets. * link did not go up after reboot. * Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions. * Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad. **Fixes in version 2.42.5052:** * Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver's teardown. - *Firmware for the following devices are updated to 2.42.5000:** 764282-B21 764286-B21 **Firmware for the following devices are updated to 2.42.5056:** 764283-B21 764284-B21 764285-B21 **New features in firmware version 2.42.5000:** * Added support for the following features. * new TLV: CX3_GLOBAL_CONF to enable/disable timestamp on incoming packets through mlxconfig configuration. * User MAC configuration. * Automatically collecting mstdump before driver reset. * A mechanism to detect DEAD_IRISC (plastic) from TPT (iron) and raise an assert. * A new field is added to "set port" command which notifies the firmware what is the user_mtu size. * Improved the debug ability for command timeout cases. - *Fixes in version 2.42.5000:** * PortRcvPkts counter was prevented from being cleared after resetting it. * The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec. * The server hangs and results in NMI when running "mlxfwtop -d mt4103_pci_cr0" while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error. * In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot. * While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck. * The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed. * ibdump could not capture all MADs packets. * link did not go up after reboot. * Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions. * Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad. **Fixes in version 2.42.5056:** * Fixed an issue that resulted in reading from invalid I/O address on handover from UEFI boot to OS boot, when a port was configured as InfiniBand on a VPI adapter device. - *Firmware for the following devices are updated to 2.42.5000:** 764282-B21 764286-B21 **Firmware for the following devices are updated to 2.42.5056:** 764283-B21 764284-B21 **Firmware for the following device is updated to 2.42.5700:** 764285-B21 **New features in firmware version 2.42.5000:** * Added support for the following features. * new TLV: CX3_GLOBAL_CONF to enable/disable timestamp on incoming packets through mlxconfig configuration. * User MAC configuration. * Automatically collecting mstdump before driver reset. * A mechanism to detect DEAD_IRISC (plastic) from TPT (iron) and raise an assert. * A new field is added to "set port" command which notifies the firmware what is the user_mtu size. * Improved the debug ability for command timeout cases. **New features and changes in firmware version 2.42.5700.** * Modified the mlx_cmd_get_mlx_link_status command return value to return "Link Type = Ethernet" in Ethernet adapter cards. - *Fixes in version 2.42.5000:** * PortRcvPkts counter was prevented from being cleared after resetting it. * The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec. * The server hangs and results in NMI when running "mlxfwtop -d mt4103_pci_cr0" while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error. * In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot. * While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck. * The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed. * ibdump could not capture all MADs packets. * link did not go up after reboot. * Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions. * Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad. **Fixes in version 2.42.5056:** * Fixed an issue that resulted in reading from invalid I/O address on handover from UEFI boot to OS boot, when a port was configured as InfiniBand on a VPI adapter device. - *Fixes in version 2.42.5000:** * PortRcvPkts counter was prevented from being cleared after resetting it. * The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec. * The server hangs and results in NMI when running "mlxfwtop -d mt4103_pci_cr0" while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error. * In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot. * While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck. * The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed. * ibdump could not capture all MADs packets. * link did not go up after reboot. * Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions. * Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad. **Fixes in version 2.42.5056:** * Fixed an issue that resulted in reading from invalid I/O address on handover from UEFI boot to OS boot, when a port was configured as InfiniBand on a VPI adapter device. - HPK2 FW version addresses an issue observed in conjunction with RHEL 8.3 installation. - This Firmware release contains various drive interoperability enhancements and code fixes accumulated since the last firmware release, as well as a change to disable MCTP over PCIe VDM function per requested of HPE, and a PHY setting change for improved compatibility with Intel Ice Lake based Gen10+ DL360 platform. * For more information, refer to HPE Customer Bulletin at the following URL: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00115201en_us - This Firmware release contains various drive interoperability enhancements and code fixes accumulated since the last firmware release, as well as a change to disable MCTP over PCIe VDM function per requested of HPE, and a PHY setting change for improved compatibility with Intel Ice Lake based Gen10+ DL360 platform. * For more information, refer to HPE Customer Bulletin at the following URL: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00115201en_us - This firmware contains a change to prevent occasional command completion times in the 4-5 second window when command is received just as the drive is transitioning from active to Idle A. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Corrects a potential data integrity issue during unaligned write commands, only found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Corrects a potential data integrity issue during unaligned write commands, only found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Reliability enhancements and VENDOR IDENTIFICATION field change from "HP" to HPE". - - This firmware includes a fix for slow performance during sequential write workloads with small queue depth. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Firmware version HPG4 prevents the occurrence of a rare issue which could lead to slow drive performance. This issue has the potential to impact all drives in configurations where the drives might be allowed to be idle for greater than 1 second. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This firmware includes a fix for slow performance during sequential write workloads with small queue depth. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This firmware has a change that allows the drive to meet the requirements for Azure Stack certification. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This firmware: Fixes the cause of internal reboots detected in the MSA system. Removes a vendor unique sense code that the controller does not handle properly. Includes changes to eliminate the cause of a potential hang condition. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - This firmware contains a fix for a data integrity issue that could occur during a power cycle while the drive is processing write commands. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fixed a timeout error and improved performance. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This update includes a fix that prevents unrecoverable read errors in highly localized write intensive workload, and a new servo code revision that improves performance under specific vibration conditions. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL 8.3 - This firmware corrects the potential for a drive to become disabled and nonfunctional during certain conditions or workloads. * After the drive is upgraded to firmware version HPK1, it cannot be downgraded to firmware version HPK0. - This firmware corrects the potential for a drive to become disabled and nonfunctional during certain conditions or workloads. * After the drive is upgraded to firmware version HPK1, it cannot be downgraded to firmware version HPK0. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fixed a timeout error and improved performance. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was only found during supplier ongoing reliability testing. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was only found during supplier ongoing reliability testing. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was only found during supplier ongoing reliability testing. - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was only found during supplier ongoing reliability testing. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Added support for RHEL 8.2 - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL:<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL:<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - VENDOR IDENTIFICATION field change from "HP" to HPE". Support for second source PMIC from IDT. - - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware fixes a potential reliability condition and the cause of a potential hang. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.4 and SLES15SP3. - This firmware mitigates a potential reliability concern. - This firmware includes a fix for slow performance during sequential write workloads with small queue depth. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - *Problems Fixed:** * HPK3 firmware resolved an issue that caused the disk activity ring, which is located on NVME SSD drive carrier, to constantly spin regardless of drive activity status. - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes. - Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.., - Added support for SLES15. - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes. - Added support for RHEL8. - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes. - Added support for SLES15SP1. - Added support for RHEL 8.2 - - Update MCTP base spec version from 1.2.0 to 1.3.0 * Change firmware to save the telemetry log buffer to smaller pages. * When reset happens, add to clear ready bit and other bits in health data according to MI 1.0a spec. - Improve overhead in handling of first packet to limit the incidence of NACKs due to lost byte from second packet. * Maintain Class Code value in a buffer area when link is down. Copy maintained Class Code from buffer to PCIe Config Space on link-up. * Change 'Percent Endurance Used' value reported in a Workload Log Page ( D6h ) to report actual endurance value. - Added support for RHEL 8.3 - Optimized T-offset setting. * Change MQES setting to 8192. * Fixed LED Behavior misaligned specs issue. * Fixed performance drop issue when 4+ SSD are installed. - Added support for RHEL 8.3 - Optimized T-offset setting. * Change MQES setting to 8192. * Fixed LED Behavior misaligned specs issue. * Fixed performance drop issue when 4+ SSD are installed. * The Idle Power Management fix to keep the drive from entering and exiting the Lower Power Idle mode too frequently. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00112800en_us - Optimized T-offset setting. * Change MQES setting to 8192. * Fixed LED Behavior misaligned specs issue. * Fixed performance drop issue when 4+ SSD are installed. * The Idle Power Management fix to keep the drive from entering and exiting the Lower Power Idle mode too frequently. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00112800en_us - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also includes emergency power off improvements. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - A low-probability, high severity corner case of sustained outer-diameter activity with emergency power off when heads are at the outer diameter prevented heads from parking/latching properly on a few drives in the field. - Added support for RHEL 8.4 and SLES15SP3. - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Fixed a rare occurrence of meta data not being saved during a sudden power loss. * Fixed an issue where a performance drop was occurring during a write same operation. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Added support for RHEL 8.2 - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Fixes a data integrity risk where a recoverable error can prevent a write command from completing properly. * Fixes a data integrity risk due to incorrect re-ordering of commands, when overlapped commands occur. * Fixes a data integrity risk during very large blocks of sequential commands with a data transfer between 1020MB and 1024MB. * Fixes a data integrity risk during a sequential read and write workload when a recovered error is encountered, which could cause incomplete data to be read. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This firmware improves potential timeouts that could occur during the write error recovery process, for drives that have head contaminant build up. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Increased Queue Size from 32 to 128 to be equal to the max number of chips. * Refresh NM SRAM area periodically only when idle as a possible work around on NM SRAM parity error. * Change the error response as 0x3 (SP_Busy) or 0x07 ( NO_SESSION_AVAILABLE) when host attempts to open another session while a session is already opened. * Disable verify compare if APP_CHK=0 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Added support for RHEL 8.3 - Modify Drive Vendor Identification String (VID) in Inquiry page from "HP" to "HPE". - - This Firmware release address below fixes and additional features: * FW Transfer Fix * Drive Failure Fix * Power Loss Protection * FW Download Fix * Reset Fix * Shutdown fix * PCIe Improvement * Random Write Improvement - - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This update improves performance for random read workloads with delays between reads. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Improvements to Product Quality and Reliability. - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Firmware fixes intermittent data corruption issue associated with unaligned sequential write operations. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Firmware fixes intermittent data corruption issue associated with unaligned sequential write operations. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Firmware fixes intermittent data corruption issue associated with unaligned sequential write operations. - Firmware fixes intermittent data corruption issue associated with unaligned sequential write operations. - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Firmware release to enable SAS4. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.4 and SLES15SP3. - Fix command timeout and uncorrectable error improvement. * Added features for SAS4 auto power swtiching and thermal requirement. - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - The issue affects SSDs with an HPE firmware version prior to HPD7 that results in SSD failure at 40,000 hours of operation (i.e., 4 years, 205 days 16 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00097382en_us>. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - The issue affects SSDs with an HPE firmware version prior to HPD7 that results in SSD failure at 40,000 hours of operation (i.e., 4 years, 205 days 16 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00097382en_us>. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - The issue affects SSDs with an HPE firmware version prior to HPD7 that results in SSD failure at 40,000 hours of operation (i.e., 4 years, 205 days 16 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL:<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00097382en_us>. - The issue affects SSDs with an HPE firmware version prior to HPD7 that results in SSD failure at 40,000 hours of operation (i.e., 4 years, 205 days 16 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL:<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00097382en_us>. - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware fixes an issue that, under extremely rare conditions, can cause a data miscompare. It eliminates causes of some potential timeouts and hangs. It also addresses some temporary performance degradation conditions. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware release provides additional protection against command timeouts. - This firmware release provides additional protection against command timeouts. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00117258en_us> - Fixed a rare occurrence of meta data not being saved during a sudden power loss. * Fixed an issue where a performance drop was occurring during a write same operation. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL:<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL:<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL:<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Drive asserts under numerous PCIe link down events without PERST# condition. * Improvement to Background Media Scan if the required host idle time never occurs. * Check PE6031 VPD content and make appropriate correction if needed. - Drive asserts under numerous PCIe link down events without PERST# condition. * Improvement to Background Media Scan if the required host idle time never occurs. * Check PE6031 VPD content and make appropriate correction if needed. - Drive asserts under numerous PCIe link down events without PERST# condition. * Improvement to Background Media Scan if the required host idle time never occurs. * Check PE6031 VPD content and make appropriate correction if needed - This FW change resolves a MCTP VDM compliance issue seen by iLO version 2.30. - This FW change resolves a MCTP VDM compliance issue seen by iLO version 2.30. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00111061en_us - This FW change resolves a MCTP VDM compliance issue seen by iLO version 2.30. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00111061en_us - This FW change resolves a MCTP VDM compliance issue seen by iLO version 2.30. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00111061en_us - This FW change resolves a MCTP VDM compliance issue seen by iLO version 2.30. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00111061en_us - Fixed a rare issue that could lead to data loss during an unexpected power loss - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Firmware version HPD3 supports NDU (non-disruptive update) firmware updates. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Removed support of UNMAP command. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also includes emergency power off improvements. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also includes emergency power off improvements. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also includes emergency power off improvements. - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also includes emergency power off improvements. - Improve overhead in handling of first packet to limit the incidence of NACKs due to lost byte from second packet. * Maintain Class Code value in a buffer area when link is down. Copy maintained Class Code from buffer to PCIe Config Space on link-up. * Change 'Percent Endurance Used' value reported in a Workload Log Page ( D6h ) to report actual endurance value. - Optimized T-offset setting. * Change MQES setting to 8192. * Fixed LED Behavior misaligned specs issue. * Fixed performance drop issue when 4+ SSD are installed. - Optimized T-offset setting. * Change MQES setting to 8192. * Fixed LED Behavior misaligned specs issue. * Fixed performance drop issue when 4+ SSD are installed. - Fixed False UECC issue at idle power mode. * Old FW download Blocking (EPK70H3Q~EPK74H3Q). * FW is changed off the option of TX data alignment for each lane. * FW is changed to clear the interrupt after TLP Complete when PCIe config read operation. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00113342en_us> - Fixed False UECC issue at idle power mode. * Old FW download Blocking (EPK70H3Q~EPK74H3Q). * FW is changed off the option of TX data alignment for each lane. * FW is changed to clear the interrupt after TLP Complete when PCIe config read operation. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00113342en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - This firmware includes a fix that changes the response to "SMART READ LOG" command from 04/80/80 to 05/26/00, which prevents the drive from incorrectly reporting an error. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - A low-probability, high severity corner case of sustained outer-diameter activity with emergency power off when heads are at the outer diameter prevented heads from parking/latching properly on a few drives in the field. - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - This firmware contains a fix for a data integrity issue that could occur during a power cycle while the drive is processing write commands. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This firmware includes a fix for slow performance during sequential write workloads with small queue depth. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Adds support for the HPE Security Log Page BBh, and improves drive reliability and responsiveness by including the latest firmware maintenance updates. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Reliability enhancements and VENDOR IDENTIFICATION field change from "HP" to HPE". - - This Firmware release address below fixes and additional features: * FW Transfer Fix * Drive Failure Fix * Power Loss Protection * FW Download Fix * Reset Fix * Shutdown fix * PCIe Improvement * Random Write Improvement - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also corrects settings preservation after a code download, and includes emergency power off improvements. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also corrects settings preservation after a code download, and includes emergency power off improvements. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also corrects settings preservation after a code download, and includes emergency power off improvements. - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also corrects settings preservation after a code download, and includes emergency power off improvements. - Added support for SLES15. * Firmware version HPD3 supports NDU (non-disruptive update) firmware updates. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - A low-probability, high severity corner case of sustained outer-diameter activity with emergency power off when heads are at the outer diameter prevented heads from parking/latching properly on a few drives in the field. - - Fixed a rare issue that could lead to data loss during an unexpected power loss - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - A low-probability, high severity corner case of sustained outer-diameter activity with emergency power off when heads are at the outer diameter prevented heads from parking/latching properly on a few drives in the field. - - Added Support for RHEL 8.2 - This is a maintenance release that contains various drive reliability enhancements and code fixes accumulated since the last initial release, as well as a change to disable MCTP over PCIe VDM function to satisfy certain HPE platform environments. - Implements FW-based VPD. * ARP setting is changed from "Capable & Discoverable" to "Fixed & Discoverable". * A minor tweak to the Foreground Media Scan (FMS) algorithm to ensure critical variables are initialized properly. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL 8.2 - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware provides a change to the Vendor ID in the VPD page that refers to HP instead of HPE. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware fixes a potential reliability condition, a rare data integrity issue and the cause of a potential hang. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.4 and SLES15SP3. - This firmware mitigates a potential reliability concern. - - Fixes a data integrity risk where stale data is mistakenly used from cache. * Fixes a data integrity risk where stale data is returned on an unaligned overlapped write-read operation. * Fixes a data integrity risk during a sequential read and write workload when a recovered error is encountered, which could cause incomplete data to be read. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - **Online firmware flashing of drives attached to an HPE Smart Array controller running in Zero Memory (ZM) mode or an HPE ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.** * **Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.** - *Problems Fixed:** * Fixed an issue where wear usage was not being reported correctly in the SmartSSD Wear Gauge Utility - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - If Power On Hours exceeds 70,000hrs, PM2R will report Hardware error (04/4C/A8) after the next Power Cycle and will not accept read/write commands. This fix will update storage location reporting when the maximum number of registrations in the Work Load Log read process reaches 70,000; the last registered 70,000th storage location will be modified to be read as the next (70,001st) storage location. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00111296en_us - If Power On Hours exceeds 70,000hrs, PM2R will report Hardware error (04/4C/A8) after the next Power Cycle and will not accept read/write commands. This fix will update storage location reporting when the maximum number of registrations in the Work Load Log read process reaches 70,000; the last registered 70,000th storage location will be modified to be read as the next (70,001st) storage location. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00111296en_us - This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Reliability enhancements and VENDOR IDENTIFICATION field change from "HP" to HPE". - - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Drive would stop responding on read retry Step 50 of Controller code correction. * In extremely rare cases, internal drive testing found that if I_T nexus loss is greater than 2 seconds, data loss might occur. If this rare condition occurs, the drive reports sense code 06/29/04 (HDD executed internal reboot), which displays on the screen and is entered in the drive log. * Drive may report sense code 02/04/02 instead of 02/04/01 if MODE SENSE and MODE SELECT command come before drive ready. The drive name will no longer display in the list, and the system will not be able to access the drive until the system is power-cycled or reset. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fixed a PSuite FwCheck L5005 error at the time of Support Service Pack for ProLiant (SPP) execution. * Fixed a L4500 error at the time of device WWN update. * Fixed a write CMD timeout at the time of SPL happens during sanitize. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - This FW release deploys an Enhanced Media Scan algorithm that addresses an issue when the host system does not provide enough idle time for drive's Foreground Media Scan to be activated, which is needed to ensure long term drive reliability. It also addresses few minor issues. - Firmware corrects an issue where the drive will be in a failed state after an unexpected power loss. When this occurs the drive will not recover after subsequent power cycles and will not be accessible by the system configuration and Host applications. * Refer Customer Bulletin for workarounds <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00042733en_us> - Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Firmware corrects an issue where the drive will be in a failed state after an unexpected power loss. When this occurs the drive will not recover after subsequent power cycles and will not be accessible by the system configuration and Host applications. - Firmware corrects an issue where the drive will be in a failed state after an unexpected power loss. When this occurs the drive will not recover after subsequent power cycles and will not be accessible by the system configuration and Host applications. * Refer Customer Bulletin for workarounds <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00042733en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fixed Store Userdata in Crash Occurred. * Fixed Log sense returned incorrect length of data. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - - Fix command timeout and uncorrectable error improvement. * Added features for SAS4 auto power swtiching and thermal requirement. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - The updates were included in a regularly scheduled 5300 maintenance release. This firmware has a security version upgrade to include TCGe SKUs and prevent a downloading of a back level firmware version of HPG0 after upgrading to HPG1. - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Enhancement improved perfromance during a raid 5 drive rebuild. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Change Vendor Identification Field (VID data) from "HP" to "HPE". - TBD - Fix to issue in bootloader download during power loss. * Improvements to error exception. * Improvements to Secure lock fix during multi-thread read tests with high freq. power cycling. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Improvements to Product Quality and Reliability. - - Added support for RHEL 8.3 - Fixed issues described in Customer Bulletin at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00111900en_us. - Added support for Intel VROC platform. - The issue affects SSDs with an HPE firmware version prior to 4ICRHPK3 that may result in SSD failure starting at 4,700 hours of operation, neither the SSD nor the data can be recovered, after the SSD failure occurs. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00111900en_us> - The issue affects SSDs with an HPE firmware version prior to 4ICRHPK3 that may result in SSD failure starting at 4,700 hours of operation, neither the SSD nor the data can be recovered, after the SSD failure occurs. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00111900en_us> - Added support for SLES15. - Fixed timing issue to pass VMWare VSAN certification. Downgrading to any previous version of firmware is not allowed. - Added support for RHEL8. - Fixed timing issue to pass VMWare VSAN certification. Downgrading to any previous version of firmware is not allowed. - Added support for RHEL8. - Fixed timing issue to pass VMWare VSAN certification. Downgrading to any previous version of firmware is not allowed. - Added support for RHEL8.2 - Added support for RHEL 8.3 - - This firmware includes a fix for an issue where the LED would continue blinking after a Sanitize operation completed. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Update MCTP base spec version from 1.2.0 to 1.3.0 * Change firmware to save the telemetry log buffer to smaller pages. * When reset happens, add to clear ready bit and other bits in health data according to MI 1.0a spec. - Improve overhead in handling of first packet to limit the incidence of NACKs due to lost byte from second packet * Maintain Class Code value in a buffer area when link is down. Copy maintained Class Code from buffer to PCIe Config Space on link-up * Change 'Percent Endurance Used' value reported in a Workload Log Page ( D6h ) to report actual endurance value - Added support for RHEL 8.3 - Optimized T-offset setting. * Change MQES setting to 8192. * Fixed LED Behavior misaligned specs issue. * Fixed performance drop issue when 4+ SSD are installed. - Added support for RHEL 8.3 - Optimized T-offset setting. * Change MQES setting to 8192. * Fixed LED Behavior misaligned specs issue. * Fixed performance drop issue when 4+ SSD are installed. * The Idle Power Management fix to keep the drive from entering and exiting the Lower Power Idle mode too frequently. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00112800en_us - Optimized T-offset setting. * Change MQES setting to 8192. * Fixed LED Behavior misaligned specs issue. * Fixed performance drop issue when 4+ SSD are installed. * The Idle Power Management fix to keep the drive from entering and exiting the Lower Power Idle mode too frequently. * For more information, refer to HPE Customer Advisory at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00112800en_us - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes - Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.., - Added support for SLES15. - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes - Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes - Added support for SLES12SP1 - Added support for RHEL 8.2 - - Improved perfromance during a raid 5 drive rebuild. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL8 - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc... - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Change Vendor Identification Field (VID data) from "HP" to "HPE". - - Fix to issue in bootloader download during power loss. * Change IDF Word 106 report 4K TU for 4/8TB drives to align with Microsoft SQL requirement. * Improvements to error exception. * Improvements to Secure lock fix during multi-thread read tests with high freq. power cycling. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc... - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Improved Product Quality and Reliability. Changed Cap Charge Timeout to 14 seconds from 4 seconds to provide additional time for cap charge in marginal power environment. - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This update improves performance for random read workloads with delays between reads. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Increased Queue Size from 32 to 128 to be equal to the max number of chips. * Refresh NM SRAM area periodically only when idle as a possible work around on NM SRAM parity error. * Change the error response as 0x3 (SP_Busy) or 0x07 ( NO_SESSION_AVAILABLE) when host attempts to open another session while a session is already opened. * Disable verify compare if APP_CHK=0. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Added support for RHEL 8.3 - Modify Drive Vendor Identification String (VID) in Inquiry page from "HP" to "HPE". - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL8. - Eliminates a potential hang on 4TB under certain pattern-dependent read conditions * Eliminates the possibility of a weak read signal under a sequenced combination of read/write conditions * Provides reliability enhancements involving head fly height dynamics * Enables download Mode 0Eh activation by Mode 0Fh - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc... - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL 8.3 - - Firmware corrects an issue where drives were not found during Power-On Self-Test device discovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Reliability enhancement for applications that write data to a narrow range of tracks. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Reliability enhancements and VENDOR IDENTIFICATION field change from "HP" to HPE". - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for Proliant and Smart Update Manager. - Added support for SLES15. - This firmware adds a feature that will periodically assess the health of the writer element of the head by verifying the data after a write operation to ensure more robust data integrity. * When performing format on drives with marginal servo flaws, it takes too long to format or format fails with 03/31 reported across the interface on subsequent commands. This firmware includes a change that moves the servo flaw characterization retries earlier in the sequence of format. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc. - Added support for RHEL 8 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc. - Added support for RHEL 8 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - Corrects a potential data integrity issue during unaligned write commands, only found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Corrects a potential data integrity issue during unaligned write commands, only found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Corrects a potential data integrity issue during unaligned write commands, only found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Reliability enhancements and VENDOR IDENTIFICATION field change from "HP" to HPE". - - Fix to issue in bootloader download during power loss. * Change IDF Word 106 report 4K TU for 4/8TB drives to align with Microsoft SQL requirement. * Improvements to error exception. * Improvements to Secure lock fix during multi-thread read tests with high freq. power cycling. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA)is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Improvements to Product Quality and Reliability. - - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fixed a timeout error and improved performance. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This update includes a fix that prevents unrecoverable read errors in highly localized write intensive workload, and a new servo code revision that improves performance under specific vibration conditions. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fixed a timeout error and improved performance. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Fixes a rare link loss issue and adds enhancements for drive reliability. * After HPG5 firmware is downloaded to the drive, the new HPG5 firmware will be active on the drive. * The new drive bootloader code will be activated after the next drive power cycle. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00072768en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Fixes a rare link loss issue and adds enhancements for drive reliability. * After HPG5 firmware is downloaded to the drive, the new HPG5 firmware will be active on the drive. * The new drive bootloader code will be activated after the next drive power cycle. * For more information, refer to HPE Customer Advisory at the following URL:<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00072768en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Fixes a rare link loss issue and adds enhancements for drive reliability. * After HPG5 firmware is downloaded to the drive, the new HPG5 firmware will be active on the drive. * The new drive bootloader code will be activated after the next drive power cycle. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00072768en_us> - Fixes a rare link loss issue and adds enhancements for drive reliability. * After HPG5 firmware is downloaded to the drive, the new HPG5 firmware will be active on the drive. * The new drive bootloader code will be activated after the next drive power cycle. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00072768en_us> - Added support for SLES15. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware includes a change to reduce response times on random read/write workloads where commands are sent at slow interval (one every few hundred milliseconds). - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - Additional improvements in MCTP functionality. * Drive fails to train in BL460 after Windows warm reset or iLO reset. - Added support for SLES15. - Fixed timing issue to pass VMWare VSAN certification. Downgrading to any previous version of firmware is not allowed. - Added support for RHEL8. - Fixed timing issue to pass VMWare VSAN certification. Downgrading to any previous version of firmware is not allowed. - Added support for RHEL8. - Fixed timing issue to pass VMWare VSAN certification. Downgrading to any previous version of firmware is not allowed. - Added support for RHEL8.2 - Added support for RHEL 8.3 - - Fix to issue in bootloader download during power loss. * Change IDF Word 106 report 4K TU for 4/8TB drives to align with Microsoft SQL requirement. * Improvements to error exception. * Improvements to Secure lock fix during multi-thread read tests with high freq. power cycling. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Improved Product Quality and Reliability. Changed Cap Charge Timeout to 14 seconds from 4 seconds to provide additional time for cap charge in marginal power environment. - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - *Enhancements/New Features:** * Improved robustness of Adjacent Track Interference (ATI) mitigation in System. - *Problems Fixed:** * Persistent Write Cache release size was miscalculated when disk write operation completed before command complete was reported to host which could result in slow sequential write performance of the drive. * Drive would stop operations when disk received COMRESET command during firmware download (DOWNLOAD MICROCODE command). NOTE: If this error occurs, data integrity is maintained and reboot is required to restart the drive operation. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware revision improves low-temperature performance and Error Correction Code (ECC) error recording for some commands. * It also improves internal logging capabilities for failure analysis. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Fixes an issue which caused the drive to become non-functional. * Fixes VPD Log D0h reported drive Sanitize times. * Adds support for Security Log Page BBh. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Fixes an issue which caused the drive to become non-functional. * Fixes VPD Log D0h reported drive Sanitize times. * Adds support for Security Log Page BBh. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Fixes an issue which caused the drive to become non-functional. * Fixes VPD Log D0h reported drive Sanitize times. * Adds support for Security Log Page BBh. - Fixes an issue which caused the drive to become non-functional. * Fixes VPD Log D0h reported drive Sanitize times. * Adds support for Security Log Page BBh. - This firmware adds a feature that will periodically assess the health of the writer element of the head by verifying the data after a write operation to ensure more robust data integrity. * When performing format on drives with marginal servo flaws, it takes too long to format or format fails with 03/31 reported across the interface on subsequent commands. This firmware includes a change that moves the servo flaw characterization retries earlier in the sequence of format. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Enhancement Improved perfromance during a raid 5 drive rebuild. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Fixes a data integrity risk where a recoverable error can prevent a write command from completing properly. * Fixes a data integrity risk due to incorrect re-ordering of commands, when overlapped commands occur. * Fixes a data integrity risk during very large blocks of sequential commands with a data transfer between 1020MB and 1024MB. * Fixes a data integrity risk during a sequential read and write workload when a recovered error is encountered, which could cause incomplete data to be read. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Firmware version HPG2 prevents the occurrence of a rare issue which could lead to slow drive performance. This issue has the potential to impact all drives in configurations where the drives might be allowed to be idle for greater than 1 second. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware includes a change to reduce response times on random read/write workloads where commands are sent at slow interval (one every few hundred milliseconds). - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added Support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - The FW version is Changed from HPG0 to HPG1. Changed the thermal throttling scheme. SMART 60 was matched with Tcase 70 and Run the thermal throttling at SMART 65. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.4 and SLES15SP3. - Support new PCB H/W with new temperature sensor. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware includes a fix that changes the response to "SMART READ LOG" command from 04/80/80 to 05/26/00, which prevents the drive from incorrectly reporting an error. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - This firmware includes a fix that changes the response to "SMART READ LOG" command from 04/80/80 to 05/26/00, which prevents the drive from incorrectly reporting an error. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Added support for RHEL8. - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also corrects settings preservation after a code download, and includes emergency power off improvements. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location.This issue was found during supplier ongoing reliability testing. * The firmware also corrects settings preservation after a code download, and includes emergency power off improvements. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also corrects settings preservation after a code download, and includes emergency power off improvements. - Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing. * The firmware also corrects settings preservation after a code download, and includes emergency power off improvements. - Fixed HPK3 drive reports incorrect Device ID issue. - Added support for VMD enabled Intel VROC platform. - Fixed HPK3 drive reports incorrect Device ID issue. - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc... - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - HPG6 introduces bug fixes, reliability enhancement and modification in SMART Attributes. Once HPG6 is downloaded, the drive cannot be changed back to an earlier firmware (eg, HPG3). - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - A low-probability, high severity corner case of sustained outer-diameter activity with emergency power off when heads are at the outer diameter prevented heads from parking/latching properly on a few drives in the field. - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Free up more DRAM for user data to improve DRAM management. * Drive would stop responding on read retry Step 50 of Controller code correction. * In extremely rare cases, internal drive testing found that if I_T nexus loss is greater than 2 seconds, data loss might occur. If this rare condition occurs, the drive reports sense code 06/29/04 (HDD executed internal reboot), which displays on the screen and is entered in the drive log. * Drive may report sense code 02/04/02 instead of 02/04/01 if MODE SENSE and MODE SELECT command come before drive ready. The drive name will no longer display in the list, and the system will not be able to access the drive until the system is power-cycled or reset. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware provides a change to the Vendor ID in the VPD page that refers to HP instead of HPE. - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware release provides additional protections against hangs in certain corner cases, and cleans up some error handling and command behavior issues. * It also fixes a firmware bug that caused significant performance degradation in abnormally long data transfers. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8 - This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing. - This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing. - Added support for RHEL8. - Fixes an issue where the SSID was not programmed correctly to the drive. This may cause issues with the drive not being identified correctly in the Integrated Lights Out Utility. - Added support for RHEL8.2 - Fixed SSD weargauge report error issue. * Fixed Assign FWState as TR_DONE_ERR at the correct location. * Prepare proper response data for Get Message Type Supported MCTP Command. * Added code to preserve current feature values cross live firmware update. * Allocate 4 bytes instead of 2 bytes for parameter code. * Changed the value for NLB equal to NSize -1. - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - VENDOR IDENTIFICATION field change from "HP" to "HPE". - - Fix to issue in bootloader download during power loss. * Change IDF Word 106 report 4K TU for 4/8TB drives to align with Microsoft SQL requirement. * Improvements to error exception. * Improvements to Secure lock fix during multi-thread read tests with high freq. power cycling. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Improved Product Quality and Reliability. Changed Cap Charge Timeout to 14 seconds from 4 seconds to provide additional time for cap charge in marginal power environment. - - HPS4 firmware release resolved a firmware timing issue which occurred during drive long self-test and resulted in a timeout condition that caused the drive to become unrecognized by the system. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc... - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc... - Added support for RHEL 8.3 - - VENDOR IDENTIFICATION field changed from "HP" to "HPE" and Reliability improvements. - *Problems Fixed:** * HPK3 firmware resolved an issue that caused the disk activity ring, which is located on NVME SSD drive carrier, to constantly spin regardless of drive activity status. - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes. - Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.., - Added support for SLES15. - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes. - Added support for RHEL8. - Fixes a potential latency issue caused by an incorrect pre-fetch algorithm. * Resolves an issue with a possible bus hang during a system reboot. * Once HPK4 is downloaded, the drive firmware cannot be changed back to an earlier firmware version (eg, HPK3 or HPK2) due to security changes. - Added support for SLES15SP1. - Added support for RHEL 8.2 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fix issue with Drive Hang on Read Retry Step 50 Controller code correction - When "command aging timer expire" AND "I_T nexus loss" occurs at the same time, HDD reports sense code, 06-29-04 Sense code correction. * Drive may report sense 02/04/02 instead of 02/04/01 if MODE SENSE and MODE SELECT command come before drive ready. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware provides a change to the Vendor ID in the VPD page that refers to HP instead of HPE. - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fixed a bug which is related to SSDs returning unexpected data when drive statistics are queried and could result in server instability. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00097984en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - PrefetchClear logic error on Write CMD. * ICRC Data Integrity improvement. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This firmware improves potential timeouts that could occur during the write error recovery process (causing the drive to internally reset), and corrects possible data mismanagement issues. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Improve overhead in handling of first packet to limit the incidence of NACKs due to lost byte from second packet * Maintain Class Code value in a buffer area when link is down. Copy maintained Class Code from buffer to PCIe Config Space on link-up * Change 'Percent Endurance Used' value reported in a Workload Log Page ( D6h ) to report actual endurance value - Optimized T-offset setting . * Change MQES setting to 8192. * Code change to set 'Slot Clock Configuration bit in Link Status register. * Fixed LED Behavior misaligned specs issue. - Optimized T-offset setting . * Change MQES setting to 8192. * Code change to set 'Slot Clock Configuration bit in Link Status register. * Fixed LED Behavior misaligned specs issue. - Fixed False UECC issue at idle power mode (12.8TB and 15.36TB only). * Apply PCLK running PHY option, PLL clock disable can be avoided in lane 0 missing case. * Old FW download Blocking. * FW is changed off the option of TX data alignment for each lane. * FW is changed to clear the interrupt after TLP Complete when PCIe config read operation. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00113342en_us> - Added support for VMD enabled Intel VROC platform - Fixed False UECC issue at idle power mode (12.8TB and 15.36TB only). * Apply PCLK running PHY option, PLL clock disable can be avoided in lane 0 missing case. * Old FW download Blocking. * FW is changed off the option of TX data alignment for each lane. * FW is changed to clear the interrupt after TLP Complete when PCIe config read operation. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00113342en_us> - Fixed False UECC issue at idle power mode (12.8TB and 15.36TB only). * Apply PCLK running PHY option, PLL clock disable can be avoided in lane 0 missing case. * Old FW download Blocking. * FW is changed off the option of TX data alignment for each lane. * FW is changed to clear the interrupt after TLP Complete when PCIe config read operation. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00113342en_us> - - This firmware includes a fix for slow performance during sequential write workloads with small queue depth. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - This firmware updates the drive to indicate NDU compliance. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours), neither the SSD nor the data can be recovered, after the SSD failure occurs. * In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously. * For more information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fixed Store Userdata in Crash Occurred * Fixed Log sense returned incorrect length of data. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to aSmart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for Proliantand Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like(B) (C) (D) etc... - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Needed to support Samsung 16G DRAM. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This release corrects logical block address mismatches that could results in partial or total data loss. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - A low-probability, high severity corner case of sustained outer-diameter activity with emergency power off when heads are at the outer diameter prevented heads from parking/latching properly on a few drives in the field. - Added support for RHEL 8.4 and SLES15SP3. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Fixes a data integrity risk where stale data is mistakenly used from cache. * Fixes a data integrity risk where stale data is returned on an unaligned overlapped write-read operation. * Fixes a data integrity risk during a sequential read and write workload when a recovered error is encountered, which could cause incomplete data to be read. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Fixes a data integrity risk where stale data is mistakenly used from cache. * Fixes a data integrity risk where stale data is returned on an unaligned overlapped write-read operation. * Fixes a data integrity risk during a sequential read and write workload when a recovered error is encountered, which could cause incomplete data to be read. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Fixes a data integrity risk where stale data is mistakenly used from cache. * Fixes a data integrity risk where stale data is returned on an unaligned overlapped write-read operation. * Fixes a data integrity risk during a sequential read and write workload when a recovered error is encountered, which could cause incomplete data to be read. - Fixes a data integrity risk where stale data is mistakenly used from cache. * Fixes a data integrity risk where stale data is returned on an unaligned overlapped write-read operation. * Fixes a data integrity risk during a sequential read and write workload when a recovered error is encountered, which could cause incomplete data to be read. - Fix to the error recovery algorithm to improve the overall reliability of the device. * Fix to insure complete support of internal logging during a sudden power off event which prevents the device entering into a degraded state. * Fixed a mishandling of error handling data during back ground media activities prevent a data issue. * Fix to correct a buffer management timing issue internal to the device allowing for a more robust internal movement of data. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Fixed an issue with performance drops during mixed workload operations. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - When SSD statistics are queried, erroneous drive temperatures may be reported. When this occurs, the system may encounter any of the two following conditions, leaving the server in an unstable state. * Server shutdown * In VMware vSAN environment, storage volume taken offline. * For important information, refer to HPE Customer Advisory at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00097984en_us> - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - PrefetchClear logic error on Write CMD. * ICRC Data Integrity improvement. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - Fix issue with drive Hang on read retry Step 50 Controller code correction - When "command aging timer expire" AND "I_T nexus loss" occurs at the same time, HDD reports sense code, 06-29-04 Sense code correction. * Drive may report sense 02/04/02 instead of 02/04/01 if MODE SENSE and MODE SELECT command come before drive ready. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - There is no compelling reason to update this firmware. Risk is that whoever looks at the Vendor ID in the VPD page will notice that it refers to HP instead of HPE. There is no functional risk if not upgraded. - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.3 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware version updates the Vendor ID in the standard inquiry to 'HPE', in previous versions it was 'HP.' - - Added support for RHEL8. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware release provides additional protections against hangs in certain corner cases, and cleans up some error handling and command behavior issues. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. * Customers who already installed latest firmware version do not need to update to sub version like (B) (C) (D) etc.. - Added support for RHEL 8.2 - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware release provides additional protections against hangs in certain corner cases, and cleans up some error handling and command behavior issues. - Online firmware flashing of drives attached to a Smart Array controller running in Zero Memory (ZM) mode or Host Bus Adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations. * Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the Service Pack for ProLiant and Smart Update Manager. - This firmware release provides additional protection against command timeouts. - This firmware release provides additional protection against command timeouts. * For more information, refer to HPE Customer Bulletin at the following URL: <https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00117258en_us> - Fixes an issue where the SSID was not programmed correctly to the drive. This may cause issues with the drive not being identified correctly in the Integrated Lights Out Utility. - Fixed SSD weargauge report error issue. * Fixed Assign FWState as TR_DONE_ERR at the correct location. * Prepare proper response data for Get Message Type Supported MCTP Command. * Added code to preserve current feature values cross live firmware update. * Allocate 4 bytes instead of 2 bytes for parameter code. * Changed the value for NLB equal to NSize -1. - - *Important Notes:** HPE Innovation Engine (IE) Firmware 0.1.4.4 has been removed from the web for the following reasons: 1\. Systems could experience a rare issue where processor and memory temperatures stop reporting, resulting in increased system fan speeds. This issue is seen during a system reboot and is only recovered by another system reset. This issue did not exist with previous versions of the Innovation Engine Firmware. 2\. Systems configured with Jitter Smoothing support could experience a rare issue where on a given boot the functionality does not function. Resetting the system typically corrects the issue. This issue did not exist with previous versions of the Innovation Engine Firmware. 3\. Systems configured with the Intel Xeon Scalable 6143 Gold and 8165 Platinum processors with HPE's Core Boosting support enabled could experience a rare issue where on a given boot the functionality does not function. Resetting the system typically corrects the issue. This issue did not exist with previous versions of the Innovation Engine Firmware. This is a new release of HPE Gen10 Innovation Engine (IE) Firmware revision 0.1.5.2 to replace IE version 0.1.4.4. If updating from IE version 0.1.4.4, follow the installation notes. If updating from an IE version prior to 0.1.4.4 please read the following note. System ROM V1.26 must be installed prior to updating to IE FW 0.1.5.2. This revision of the IE FW is required for updating the Intel Platform Service (SPS) Firmware revision 04.00.04.288 and later. It should be installed prior to updating to SPS FW 04.00.04.288 or later. SPS FW 04.00.04.288 mitigates security vulnerability CVE-2017-5706 (http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-5706) and CVE-2017-5709 (http://www.cve.mitre.org /cgi-bin/cvename.cgi?name=2017-5709). The details regarding these security vulnerabilities were published to these links on November 20,2017. These security vulnerabilities are not unique to HPE servers. **Firmware Dependencies:** System ROM V1.26 or later **Problems Fixed:** Addressed an issue where systems configured with Innovation Engine Firmware 0.1.4.4 could experience a rare issue where processor and memory temperatures stop reporting, resulting in increased system fan speeds. This issue is seen during a system reboot and is only recovered by another system reset. This issue did not exist with previous versions of the Innovation Engine Firmware. Addressed an issue where systems configured with Innovation Engine Firmware 0.1.4.4 and Jitter Smoothing support could experience a rare issue where on a given boot the functionality does not function. Resetting the system typically corrects the issue. This issue did not exist with previous versions of the Innovation Engine Firmware. Addressed an issue where systems configured with Innovation Engine Firmware 0.1.4.4 and the Intel Xeon Scalable 6143 Gold and 8165 Platinum processors with HPE's Core Boosting support enabled could experience a rare issue where on a given boot the functionality does not function. Resetting the system typically corrects the issue. This issue did not exist with previous versions of the Innovation Engine Firmware. **Known Issues:** This flash component will report the Current Revision of the Innovation Engine FW as "n/a" when updating the Innovation Engine FW. This does not affect the flash update or impact how the Innovation Engine FW operates. - *Important Notes:** None **Firmware Dependencies:** System ROM V1.26 or later **Problems Fixed:** Addressed an issue where the Integrated Lights-Out (iLO) web interface may incorrectly report the Innovation Engine is running in a degraded state. Addressed an issue where memory telemetry data may not be reported properly in the Integrated Lights-Out (iLO) web interface or through the HPE RESTful API. Addressed an issue where the Innovation Engine Firmware flash would fail if a previous flash attempt was interrupted and not completed successfully. **Known Issues:** This flash component will report the Current Revision of the Innovation Engine FW as "n/a" when updating the Innovation Engine FW. This does not affect the flash update or impact how the Innovation Engine FW operates. - *Important Notes:** Ver. 0.1.6.1(C) contains updates to the component packaging and is functionally equivalent to ver. 0.1.6.1. It is not necessary to upgrade with Revision C if a previous component Revision was used to upgrade the firmware to version 0.1.6.1. **Firmware Dependencies:** System ROM V1.26 or later **Problems Fixed:** Addressed an issue where the Integrated Lights-Out (iLO) web interface may incorrectly report the Innovation Engine is running in a degraded state. Addressed an issue where memory telemetry data may not be reported properly in the Integrated Lights-Out (iLO) web interface or through the HPE RESTful API. Addressed an issue where the Innovation Engine Firmware flash would fail if a previous flash attempt was interrupted and not completed successfully. **Known Issues:** This flash component will report the Current Revision of the Innovation Engine FW as "n/a" when updating the Innovation Engine FW. This does not affect the flash update or impact how the Innovation Engine FW operates. - Added support for Intel Xeon Scalable Performance 3200, 4200, 5200, 6200 and 8200 series processors. Added support for HPE system performance monitoring and workload performance advisor. This feature also requires Integrated Lights-Out (iLO) firmware version 1.40 or later. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an extremely rare issue where updates to the Intel Server Platform Services (SPS) firmware may fail. **Known Issues:** This flash component will report the Current Revision of the Innovation Engine FW as "n/a" when updating the Innovation Engine FW. This does not affect the flash update or impact how the Innovation Engine FW operates. - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** Added support for HPE Persistent Memory featuring Intel Optane DC Persistent Memory. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an extremely rare issue where Processor or Memory temperature reporting may not be collected properly by the platform and the system fans may be running faster than expected. This issue has been seen occasionally after a server reboot and is typically corrected with a subsequent server reboot. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an extremely rare issue where processor or memory temperature reporting may stop reporting properly or report a constant reading after servers have been operating over an extended period of time without an AC power cycle. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Address an issue where Innovation Engine (IE) Firmware may be unresponsive and iLO Firmware may report "Update Failed" after flashing the Innovation Engine (IE) Firmware via RESTful update. The flash will have been performed successfully, but the system must be reset for IE Firmware to function properly. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Innovation Engine (IE) may improperly reset every 24 hours. **Known Issues:** None - - Added Support for HPE Synergy Gen 10/Gen10 Plus Systems for addressing the following. * https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=hpesbhf04211en_us * Support for Automatic SSL Certificate Enrollment using Simple Certificate Enrollment Protocol. * Addition of DIMM Manufacture date in RedFISH output of Memory Resource. * Added monitoring of User-defined temperature threshold for PCI Zone sensors on Edgeline servers. - Fixed an issue where Network Tab page in iLO GUI doesn't refresh automatically post Server Reset. * "StructuredName" Redfish Property is hidden when the value of this field is an empty string. * Improved monitoring of temperature sensors on N3000 option cards. * Fixed an issue where iLO may become inaccessible after consecutive setting of factory defaults. * Improved power supply information reporting on Edgeline servers. * Intelligent Provisioning not accessible after a rare server reboot. - *Recommended**: For supported HPE ProLiant, Apollo Gen10 and Gen10 Plus systems. Is not supported for HPE Edgeline, Synergy Gen10 and Gen10 Plus systems. - Support for Cloud based management with Compute Ops Manager (COM). * Support for Enhanced Download Performance * This option allows to improve the performance of iLO Scriptable Virtual Media and URL based Firmware update in environments with high network latencies. * Support for NVIDIA A2 PCIE GPU card - None - Validation of LDAPv3 based authentication using OpenLDAP based directory server. * Added Support for RDE Read and Write operations. * Added Support for Firmware update using Common PLDM based Package for Direct Attached UBMs (1/2/3/4). - Deployment needs to be run twice to reflect Firmware baseline successfully. * Change in response of Redfish API causes Oneview not to fully discover the Port Map Information. * RF subscription gets exhausted in certain situations. * Oneview marks Server as "Critical" when a Critical IML event has been manually marked as repaired in iLO GUI. * iLO not able to auto recover when an IML corruption happens. * Adapter Virtualization Mode not persistent across reboots. * On Edgeline Platforms, iLO GUI doesn't render in the first attempt when IP address is used. * iLO webserver becomes unresponsive after running RIBCL scripts for modifying SSO permissions. * AMD Gen10 servers might take up to 5 mins to complete POST when encryption is enabled. * Nvidia P1000 may not be detected if installed on an EL1000 chassis. * Intel N3000 network endpoints are not properly reported on e910t servers. * ipmitool lists incorrect number of network port links. - Type-D Component Firmware update experience for Compute Ops Management. * Support for easy transition to Compute Ops Management for nodes that are currently under OneView management. - Port Status of 331i & 562FLR Network Adapter cards do not change from "unknown" to "ok" in rare occasions. * "show swid" command displays HPE Smart Array P408i-a SR Gen10 card twice. * iLO fails to send Support Events even when Embedded Remote Support has been enabled. * iLO responds with wrong Network port information during Ports collection and Network Device Functions collection. * Server boot gets stuck on POST while loading Encryption keys for secure boot. * EID Table information is retained in AHS though MCTP discovery is disabled. * Front Display Port (DP) on Universal Media bay does not work in certain instances. * Unable to adjust fan settings on Edgeline e910/e920 Thermal Configuration page. * iLO unable to authenticate users intermittently when directory authentication is enabled. - Fix for multiple security issues - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - This image contains the latest Intel Server Platform Services (SPS) Firmware which contains mitigations for a variety of security vulnerabilities. The following vulnerabilities have been addressed in this SPS release: CVE-2020-0545 and CVE-2020-0586. These issues are not unique to HPE Servers. - *Important Notes:** This version of the Server Platform Services (SPS) Firmware contains updates aligned with the Intel Product Update (IPU) version IPU.2020.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the Server Platform Services Firmware provides mitigations for security vulnerability documented as CVE-2020-8755. This security vulnerability is documented in Intel Security Advisory INTEL-SA-00391. This issue is not unique to HPE servers. **Known Issues:** None - See the release document in Download Product Binaries page from Product Summary of the firmware product. - *Important Notes:** This version of the Server Platform Services (SPS) Firmware contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the Server Platform Services (SPS) Firmware provides mitigations for SPS security vulnerabilities documented as CVE-2020-24509. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00459. These issues are not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the Server Platform Services (SPS) Firmware contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the Server Platform Services (SPS) Firmware provides mitigations for SPS security vulnerabilities documented as CVE-2021-0060. This issue is not unique to HPE servers. **Known Issues:** None - - N/A - This product now supports Red Hat Enterprise Linux 6 Update 10. - This product corrects an issue where adapters incorrectly send a NULL padded System Description LLDP (Link Layer Discovery Protocol) TLV. This product corrects an issue where an incorrect device (Network Controller) name is displayed in the RBSU. This product corrects an issue where adapters become Firmware corruption during rebooting. - This product addresses an issue where firmware is corrupted during multiple system reboots. This product addresses an LLDP message issue where adapters send incorrect System Description, System Name, Chassis ID and Management Address. - This product now remove supports Synergy and Blade Server. - This product now supports Red Hat Enterprise Linux 7.7 This product now supports SUSE Linux Enterprise Server 15 SP1 This product now supports the following network adapters. * HPE Ethernet 10Gb 2-port 537SFP+ Adapter * HPE Ethernet 10Gb 2-port 537SFP+ FLR Adapter - This product corrects wrong names of adapters which show up while doing firmware update. * This product corrects an issue about 2 ports in a port bond both being disconnected if we were just disconnecting 1 port. * This product corrects an issue about LLDP nearest bridge packet not being disabled while that option under NIC HII was disabled. * This product corrects the wrong LED behavior while attaching SFP-RJ45 tranceiver. * This product corrects an issue about firmware not being actually updated even seeing it was reported as successfully by update utility. - This product addresses a package loss issue while running under multicast UDP traffic. - This product addresses an issue where network interface could not be brought up under OS. - This product addresses an issue a packet missing problem after some amounts of multicast UDP streams transmitted. * This product addresses an issue the port identifier LED problem on HPE Ethernet 10Gb 2-port 535T Adapter . - Initial version - - This product corrects an issue where the component fails to update adapter firmware when running on ESXi 6.7. This product corrects an issue where an incorrect device (Network Controller) name is displayed in the RBSU. - This product corrects an issue where random PXE boot installation failures occur when booting in UEFI mode. - This product now remove supports Synergy and Blade Server. - This product addresses an issue where Legacy Boot Protocol(System Utilities -> System Configuration -> NIC HII menu -> BA Configuration Menu) changes from None to PXE. This product addresses an issue where it would be forced to exit System Utilities when select Port 2 & Port 3(System Utilities -> System Configuration -> NIC HII menu). - This product corrects the wrong spare number while it was originally not the same as what was written on the label of package. - This product addresses an issue about lack of information under AHS log. * This product addresses an RSOD issue which appeared intermittently during POST after having a warm reboot. * This product addresses a modification on help string of Family Firmware Version. - This product now supports Red Hat Enterprise Linux 8 update 4 and SUSE Linux Enterprise Server 15 Service Pack 3. - This product addresses an issue about lost connection under S5 if adapter was running under 1G. - This product addressed the firmware update failure problem while running the installation under Linux OS. - TBD - This product addresses an issue where LLDP are disabled. * This product addresses an issue where "Firmware Image Properties", "Device Level Configuration", and "Link Speed Status" options in NIC HII menu will disappear when F7 is pressed. * This product addresses an issue where Firmware upgrade fail in SLES15 with secureboot enabled. * This product addresses an issue where POST when ESC Is Pressed to Enter The BIOS Setup Utility with HP Ethernet 1Gb 4-port 366FLR Adapter. * This product addresses an issue where there is no VLAN function under Legacy mode. - This product addresses an WOL issue that system wakes up automatically if any magic packet being sent before system was shut down. - This product addresses an WOL issue that system wakes up automatically if any magic packet being sent before system was shut down. - This product addresses an issue where ECC error occurs when running failed recovery with HPE Ethernet 10Gb 2-port 562T Adapter and HPE Ethernet 10Gb 2-port 562FLR-T Adapter. - This product now supports Red Hat Enterprise Linux 6. - This product addresses an issue where ECC error occurs when running failed recovery with HPE Ethernet 10Gb 2-port 562T Adapter and HPE Ethernet 10Gb 2-port 562FLR-T Adapter. - This product addresses an WOL issue that system wakes up automatically if any magic packet being sent before system was shut down. - This product addresses an issue where Systems Insight Display (SID) modul is green when there's no Network connection. - This product now supports Red Hat Enterprise Linux 8 update 4 and SUSE Linux Enterprise Server 15 Service Pack 3 - TBD - *Changes and New Features in version 1.8.1.0.0 :** * Added hfi1_eprom **v10_8_0_0_13.** * Loader ROM **HfiPcieGen3Loader_1.8.1.0.0.rom** and driver EFI **HfiPcieGen3_1.8.1.0.0.efi** were added. - *Fixes included in version 1.11.0:** * **The following issue has been fixed in Unified Extensible Firmware Interafce (UEFI) ROM: **On some platforms, the hfi1 device was not showing up in BIOS/UEFI boot menus and was not available as a PXE boot device. This was caused by the platform not loading the UEFI driver for the hfi1 adapter. - Initial release. - This product now supports SUSE Linux Enterprise Server 12 SP5. * This product now supports HPE ProLiant MicroServer Gen10 Plus and HPE ProLiant XL225n Gen10 Plus. - This product now supports the following network adapters: * Intel X710-DA2 Ethernet 10Gb 2-port SFP+ OCP3 Adapter for HPE * Intel X710-DA2 Ethernet 10Gb 2-port SFP+ Adapter for HPE - This product now supports SUSE Linux Enterprise Server 15 SP2. * This product now supports Red Hat Enterprise Linux 8, Update 2 and Update 3. - This product corrects an issue where iLO returns invalid JSON response format. - This product addresses an link issue for Intel X710-DA2 Ethernet 10Gb 2-port SFP+ OCP3 Adapter for HPE. - This product now supports Red Hat Enterprise Linux 8 update 4 and SUSE Linux Enterprise Server 15 Service Pack 3 - TBD - *Fixes in version** **14.24.9000** * Fixed an issue that prevented the first iSCSI target parameters to be reset to their default values. * Fixed an issue which cause the link not to raise in the second port which was set as IB when the first port was ETH in PXE. * Fixed wrong default value of Boot-To-Target in FlexBoot configuration. * When connecting a pre-configured port with VLAN to an IB fabric, the port runs as Ethernet port with the VLAN tag. * Booting PXE using Grub2.X over HP G9/G8 servers results in system hang. * If the client gets "PXE boot menu" when contacting the DHCP, it will PXE boot first regardless of the boot priority. * If the PMM fails to allocate memory, the system hangs since FlexBoot cannot load from the expansion ROM. * In ConnectX-4, the PXE boot time measurement over TFTP Ethernet was 1:30 min for image size of 1GB, TFTP InfiniBand was 1:20 min, and iSCSI boot time measurement was 8 seconds for image size of 25 MB. * In hybrid BIOSes, if the BIOS loads legacy driver without closing the UEFI driver, the legacy driver fails to load. - *Firmware for the following device is updated to 14.26.1040:** P11338-B21 (HPE Ethernet 10Gb 2-port 548SFP+ Adapter) - *Fixes in version** **14.26.XXXX :** * Fixed an issue that caused a function to misbehave when a PCIe Transaction Layer Packet (TLP) was set with a poisoned indication. * Fixed a rare issue that resulted in "destroy mkey " command getting stuck when rebooting the hypervisor. * The total firmware reset time is increased by 1 second. - *Firmware for the following device is updated to 14.27.4000:** P11338-B21 (HPE Ethernet 10Gb 2-port 548SFP+ Adapter) **Following New features and Changes are included in version 14.27.4000:** * Added mlxconfig support for power reduction: PCI CAP AUTO_POWER_SAVE_LINK_DOWN * PCI CAP * AUTO_POWER_SAVE_LINK_DOWN * Added the following segments, as appeared in the PRM, to the Resource Dump: * PRM_QUERY_QP * PRM_QUERY_CQ * PRM_QUERY_MKEY * QUERY_VNIC_ENV - *Following issues have been fixed in version 14.27.4000:** * An issue that caused the sent packet to hang while the device entered FLR mode. * Enabled Bar configuration bytewise by applying the write_en bitmask. * A rare case where the the device froze while running the sw reset flow under heavy stress and with many open resources. * Low PXE performance while using the VSC to trigger the send_ring_doorbells. * An error that prevented the completions (CQ) from being completed due to a race condition in the firmware transport error handlers, and the error stressors, where the error stressors would hang the firmware transport error handler flow. * An issue that caused the fragmented IP packets to drop was fixed. - *Firmware for the following device is updated to 14.28.1002:** P11338-B21 (HPE Ethernet 10Gb 2-port 548SFP+ Adapter) **Following New features and Changes are included in version 14.28.1002:** * Added mlxconfig support for power reduction: PCI CAP AUTO_POWER_SAVE_LINK_DOWN * PCI CAP * AUTO_POWER_SAVE_LINK_DOWN * Added the following segments, as appeared in the PRM, to the Resource Dump: * PRM_QUERY_QP * PRM_QUERY_CQ * PRM_QUERY_MKEY * QUERY_VNIC_ENV - *Following issues have been fixed in version 14.29.1016:** * An issue that caused the sent packet to hang while the device entered FLR mode. * Enabled Bar configuration bytewise by applying the write_en bitmask. * A rare case where the the device froze while running the sw reset flow under heavy stress and with many open resources. * Low PXE performance while using the VSC to trigger the send_ring_doorbells. * An error that prevented the completions (CQ) from being completed due to a race condition in the firmware transport error handlers, and the error stressors, where the error stressors would hang the firmware transport error handler flow. * An issue that caused the fragmented IP packets to drop was fixed. - *Firmware for the following device is updated to 14.31.1014:** * P11338-B21 (HPE Ethernet 10Gb 2-port 548SFP+ Adapter) **New features and changes included in version 14.31.1014:** * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * support for Enabling/Disabling NIC and RDMA (port/partition) was included via the UEFI HII system settings. * Increased the maximum number of MSIX per VF to 127. * Added a new bit ("data_in_order") to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. - *Following issues have been fixed in version 14.31.1014:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. **Additional Fixes included in version 14.31.1014:** * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. - *The following issues have been fixed in version 14.32.1010:** * Firmware got into an unresponsive state and caused unexpected behavior when connecting an optical transceiver that support RxLOS and the remote side port was down. * The system could not create more than 128K QPs. * On rare occasions, the system got into an unresponsive state when a peer port went down while using an Optical module. * Packet Pacing rate was used if asymmetric VFs was enabled. * Incorrect RNR timeout when trying to set it during the rts2rts_qp transition. * Issue with RSS on IPSec flows in ConnectX-4 Lx led to performance degradation. In this scenario, the SPI optimization caused packets from a given host to hash to the same CPU core. The fix was to ignore SPI optimization according to l4_type in ConnectX-4 Lx adapter cards. * The GetInventory NC-SI command reported leading 0xf in firmware version when it started with 0. - *Fixes submitted in version 2.42.5044 :** * An issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode. **Following issues have been fixed in firmware version 14.27.4000:** * The sent packet hung while the device entered FLR mode. * Enabled Bar configuration bytewise by applying the write_en bitmask. * The device hung while running the sw reset flow under heavy stress and with many open resources. * The completions (CQ)completed due to a race condition in the firmware transport error handlers, and the error stressors, where the error stressors would hang the firmware transport error handler flow. * The fragmented IP packets were dropped. **Following issues have been fixed in firmware version 16.27.2008:** * Although the effective BER (after FEC) was expected to meet the design targets (e.g. 10e-14 or lower), occasionally it was higher. * High BER occured when connecting cables of type 0.5/1m DAC to an HDR speed. * The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled. * The desched_threshold field did not work properly. * The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter. * If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again. - *Firmware for the following devices are updated to 2.42.5044 :** 779799-B21 (HPE Ethernet 10G 2-port 546FLR-SFP+ Adapter) 779793-B21 (HPE Ethernet 10G 2-port 546SFP+ Adapter) **Firmware for the following devices are updated to 14.29.1016:** 817749-B21 (HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter) **Firmware for the following devices are updated to 14.29.1016:** 817753-B21 (HPE Ethernet 25Gb 2-port 640SFP28 Adapter) **Firmware for the following device is updated to 16.29.1016:** 874253-B21 (HPE Ethernet 100Gb 1-port 842QSFP28 Adapter) **New features and changes in version 14.29.1016:** Added support for the following features: * A new counter per vPort that counts the number of packets that reached the Ethernet RQ but cannot fit into the WQE due to their large size. Additionally, we added the option to control if such packet will cause "CQE with Error" or "CQE_MOCK". * cq_overrun counter: This counter represents the number of times CQs enter an error state due to overflow that occur when the device tries to post a CQE into a full CQ buffer. * Enabled the capability to allow Virtual Functions to send Pause Frames packets. * Enabled 10/25GbE auto-sensing with 3rd party when using 10/25GbE optical cables. * Hardware steering dump output used for debugging and troubleshooting. **New features and changes in version 16.29.1016:** Added support for following features: * An option to allow applications to build their own QoS tree over the NIC hierarchy by connecting QPs to responder/requestor Queue Groups. * "InfiniBand" properties set to the Network Device Function Redfish object. * HW support for Flow Metering to utilize Advanced Steering Operation (ASO). HW Flow Meter allows higher scale, more accuracy, and better performance compare to the FW Flow Metering. * Trust level for VFs. Once the VF is trusted, it will get a set of trusted capabilities. * 2 new Mini CQE formats: Responder Mini CQE With Flow Tag Layout Responder Mini CQE With l3_l4_info Layout * UCX can now enable AR by exposing Out-Of-Ordering bitmask per SL with "ooo_per_sl" field in the HCA_VPORT context. It can be also queried by running the QUERY_HCA_VPORT_CONTEXT command. * Steering DP hash flow groups. * A new counter per vPort that counts the number of packets that reached the Ethernet RQ but cannot fit into the WQE due to their large size. Additionally, we added the option to control if such packet will cause "CQE with Error" or "CQE_MOCK". * PCIe Rx modifications to prevent the adapter cards from disappearing from the system. * ignore_flow_level is now enabled by the TRUST LEVEL access registry. * cq_overrun counter. The counter represents the number of times CQs enter an error state due to overflow that occur when the device tries to post a CQE into a full CQ buffer. * [Beta] Enabled the capability to allow Virtual Functions to send Pause Frames packets. * Enabled 10/25GbE auto-sensing with 3rd party when using 10/25GbE optical cables. * Hardware steering dump output used for debugging and troubleshooting. - *ixes submitted in version 2.42.5044 :** * An issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode. **Following issues have been fixed in firmware version 14.29.1016:** * Changed the default value of DCQCN's (Data center- Quantized Congestion Notification) NP parameter min_time_between_cnps to 4 on all devices to support larger scalability of cluster. * An issue that caused packets to drop due to header size issues and/or failing checks. The issue was caused due to a Linux issue that caused VFs to set the wrong header size value in wqe_inline_header_mode input. * When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs were configured, VM restart (VF/PF FLR) will take longer than when MKEY_BY_NAME is disabled. * On rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR. * An issue that caused the device to go to dead IRISC as one of the firmware semaphores could not be released when a speed change or port state change was triggered. **Following issues have been fixed in firmware version 16.29.1016:** * Changed the default value of DCQCN's (Data center- Quantized Congestion Notification) NP parameter min_time_between_cnps to 4 on all devices to support larger scalability of cluster. * An issue that prevented VXLAN packets with svlan/ cvlan tag from being matched. * The eth_wqe_too_small counter to count ODP page used to fail. * When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs are configured, VM restart (VF/PF FLR) will take longer than when MKEY_BY_NAME is disabled. * An issue that resulted in low performance after enabling the RoCE Accelerator capability. * On rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR. * The chassis manager calculation for Multi-Host and Socket-Direct adapter cards to allow running NC-SI commands by the chassis manager BMC. Now the chassis manager is count as BMC with index 0, regardless of how many BMC there are. * An issue that caused the device to go to dead IRISC as one of the firmware semaphores could not be released when a speed change or port state change was triggered. - *Firmware for the following devices are updated to 2.42.5044 :** 779799-B21 (HPE Ethernet 10G 2-port 546FLR-SFP+ Adapter) 779793-B21 (HPE Ethernet 10G 2-port 546SFP+ Adapter) **Firmware for the following devices are updated to 14.31.1200:** 817749-B21 (HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter) 817753-B21 (HPE Ethernet 25Gb 2-port 640SFP28 Adapter) **Firmware for the following device is updated to 16.29.1016:** 874253-B21 (HPE Ethernet 100Gb 1-port 842QSFP28 Adapter) **New Features and Changes included in version 16.31.1200:** * Added a new NVconfig per Port for a specific Finisar module. This new NVconfig sets the port to work in AN mode and sets the module to No Data Management Engine (DME). This change does not affect the speed logic, only the forward error correction (FEC) logic (FEC override). **Note:** If the port does not come up, switch to Force mode. **New features and changes included in version 16.29.1016:** * An option to allow applications to build their own QoS tree over the NIC hierarchy by connecting QPs to responder/requestor Queue Groups. * "InfiniBand" properties set to the Network Device Function Redfish object. * HW support for Flow Metering to utilize Advanced Steering Operation (ASO). HW Flow Meter allows higher scale, more accuracy, and better performance compare to the FW Flow Metering. * Trust level for VFs. Once the VF is trusted, it will get a set of trusted capabilities. * 2 new Mini CQE formats: Responder Mini CQE With Flow Tag Layout Responder Mini CQE With l3_l4_info Layout * UCX can now enable AR by exposing Out-Of-Ordering bitmask per SL with "ooo_per_sl" field in the HCA_VPORT context. It can be also queried by running the QUERY_HCA_VPORT_CONTEXT command. * Steering DP hash flow groups. * A new counter per vPort that counts the number of packets that reached the Ethernet RQ but cannot fit into the WQE due to their large size. Additionally, we added the option to control if such packet will cause "CQE with Error" or "CQE_MOCK". * PCIe Rx modifications to prevent the adapter cards from disappearing from the system. * ignore_flow_level is now enabled by the TRUST LEVEL access registry. * cq_overrun counter. The counter represents the number of times CQs enter an error state due to overflow that occur when the device tries to post a CQE into a full CQ buffer. * [Beta] Enabled the capability to allow Virtual Functions to send Pause Frames packets. * Enabled 10/25GbE auto-sensing with 3rd party when using 10/25GbE optical cables. * Hardware steering dump output used for debugging and troubleshooting. - *Fixes included in firmware version 2.42.5044 :** * An issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode. **Fixes included in firmware version 14.29.1016:** * Changed the default value of DCQCN's (Data center- Quantized Congestion Notification) NP parameter min_time_between_cnps to 4 on all devices to support larger scalability of cluster. * An issue that caused packets to drop due to header size issues and/or failing checks. The issue was caused due to a Linux issue that caused VFs to set the wrong header size value in wqe_inline_header_mode input. * When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs were configured, VM restart (VF/PF FLR) will take longer than when MKEY_BY_NAME is disabled. * On rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR. * An issue that caused the device to go to dead IRISC as one of the firmware semaphores could not be released when a speed change or port state change was triggered. **No fixes are included in firmware version 14.31.1200.** - *Firmware for the following devices are updated to 2.42.5044 :** 779799-B21 (HPE Ethernet 10G 2-port 546FLR-SFP+ Adapter) 779793-B21 (HPE Ethernet 10G 2-port 546SFP+ Adapter) **Firmware for the following devices are updated to 14.31.1200:** 817749-B21 (HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter) **Firmware for the following devices are updated to 14.31.1200:** 817753-B21 (HPE Ethernet 25Gb 2-port 640SFP28 Adapter) **Firmware for the following device is updated to 16.31.1014:** 874253-B21 (HPE Ethernet 100Gb 1-port 842QSFP28 Adapter) **New features and changes in version 14.31.1200:** * NVconfig per Port for a Specific Finisar Module: Added a new NVconfig per Port for a specific Finisar module. This new NVconfig sets the port to work in AN mode and sets the module to No DME. This change does not affect the speed logic, only the FEC logic (FEC override). **Note:** If the port does not go up, switch to Force mode. **New features and changes in version 16.31.1014:** * NIC scheduling feature support has been disabled for non-privileged functions. * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * Added support for Enabling/Disabling NIC and RDMA (port/partition) via the UEFI HII system settings. **Note:** Values set in this option only take effect when is Ethernet mode. * Increased the maximum number of MSIX per VF to 127. * Asymmetrical MSIX Configuration: This feature allows the device to be configured with a different number of MSIX vectors per physical PCI functions. To use this feature, please follow these steps: * Clear NUM_PF_MSIX_VALID to disable global symmetrical MSIX configuration. * Set PF_NUM_PF_MSIX_VALID to enable asymmetrical per Physical Function MSIX configuration. * Configure PF_NUM_PF_MSIX per physical PCI function. * Support for RDMA partitioning and RDMA counters in IB mode. * A new bit ("data_in_order") was added to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. Pages are returned by the driver to the kernel without issuing the MANAGE_PAGES commands to the firmare. * Enabled UID 0 to create resources with UMEM (User Memory). * Receiving and sending native IB packets from/to the software (including all headers) via raw IBL2 QPs. * RX RDMA NIC flow table on an IB port. Now the software can steer native IB packets to raw IB receive queues according to the DLID and the DQPN. - *Fixes included in firmware version 2.42.5044 :** * An issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode. **The following issues have been fixed in version 14.31.1200:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. **Additional Fixes included in version 14.31.1200:** * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. **The following issues have been fixed in version 16.31.1014:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * An assert that was caused when trying to open 1024 functions on the device and the maximum number of functions was 1023. * Occasional performance issues related to RC QPs using E2E-credits (not connected to SRQ and doing send/receive traffic) when the ROCE_ACCL tx_window was enabled. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * A rare issue that caused RX pipe to hang. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. * CRT_DCR with index larger than 1 << 21 occasionally collided with the CRT_SW_RESERVED address. * An issue that caused the TX queue to get into an unresponsive state when the VF rate limiter was set. **Additional Fixes included in version 16.31.1014:** * Disabled the CNP counter "rp_cnp_ignored " (triggered by OOS (out-of-sequence)) when all ports are IB. * Fixed the TMP421 sensor temperature reporting. * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. - *Firmware for the following devices are updated to 2.42.5044 :** 779799-B21 (HPE Ethernet 10G 2-port 546FLR-SFP+ Adapter) 779793-B21 (HPE Ethernet 10G 2-port 546SFP+ Adapter) **Firmware for the following devices are updated to 14.31.1200:** 817749-B21 (HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter) **Firmware for the following devices are updated to 14.31.1200:** 817753-B21 (HPE Ethernet 25Gb 2-port 640SFP28 Adapter) **Firmware for the following device is updated to 16.31.1014:** 874253-B21 (HPE Ethernet 100Gb 1-port 842QSFP28 Adapter) **Updated mstflint from version 4.13 to 4.16** **New features and changes in version 14.31.1200:** * NVconfig per Port for a Specific Finisar Module: Added a new NVconfig per Port for a specific Finisar module. This new NVconfig sets the port to work in AN mode and sets the module to No DME. This change does not affect the speed logic, only the FEC logic (FEC override). **Note:** If the port does not go up, switch to Force mode. **New features and changes in version 16.31.1014:** * NIC scheduling feature support has been disabled for non-privileged functions. * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * Added support for Enabling/Disabling NIC and RDMA (port/partition) via the UEFI HII system settings. **Note:** Values set in this option only take effect when is Ethernet mode. * Increased the maximum number of MSIX per VF to 127. * Asymmetrical MSIX Configuration: This feature allows the device to be configured with a different number of MSIX vectors per physical PCI functions. To use this feature, please follow these steps: * Clear NUM_PF_MSIX_VALID to disable global symmetrical MSIX configuration. * Set PF_NUM_PF_MSIX_VALID to enable asymmetrical per Physical Function MSIX configuration. * Configure PF_NUM_PF_MSIX per physical PCI function. * Support for RDMA partitioning and RDMA counters in IB mode. * A new bit ("data_in_order") was added to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. Pages are returned by the driver to the kernel without issuing the MANAGE_PAGES commands to the firmare. * Enabled UID 0 to create resources with UMEM (User Memory). * Receiving and sending native IB packets from/to the software (including all headers) via raw IBL2 QPs. * RX RDMA NIC flow table on an IB port. Now the software can steer native IB packets to raw IB receive queues according to the DLID and the DQPN. - *Fixes included in firmware version 2.42.5044 :** * An issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode. **The following issues have been fixed in version 14.31.1200:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. **Additional Fixes included in version 14.31.1200:** * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. **The following issues have been fixed in version 16.31.1014:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * An assert that was caused when trying to open 1024 functions on the device and the maximum number of functions was 1023. * Occasional performance issues related to RC QPs using E2E-credits (not connected to SRQ and doing send/receive traffic) when the ROCE_ACCL tx_window was enabled. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * A rare issue that caused RX pipe to hang. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. * CRT_DCR with index larger than 1 << 21 occasionally collided with the CRT_SW_RESERVED address. * An issue that caused the TX queue to get into an unresponsive state when the VF rate limiter was set. **Additional Fixes included in version 16.31.1014:** * Disabled the CNP counter "rp_cnp_ignored " (triggered by OOS (out-of-sequence)) when all ports are IB. * Fixed the TMP421 sensor temperature reporting. * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. - *The following issues have been fixed in version 2.42.5044 :** * An issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode. **The following issues have been fixed in version 14.32.1010:** * Firmware got into an unresponsive state and caused unexpected behavior when connecting an optical transceiver that support RxLOS and the remote side port was down. * The system could not create more than 128K QPs. * On rare occasions, the system got into an unresponsive state when a peer port went down while using an Optical module. * Packet Pacing rate was used if asymmetric VFs was enabled. * Incorrect RNR timeout when trying to set it during the rts2rts_qp transition. * Issue with RSS on IPSec flows in ConnectX-4 Lx led to performance degradation. In this scenario, the SPI optimization caused packets from a given host to hash to the same CPU core. The fix was to ignore SPI optimization according to l4_type in ConnectX-4 Lx adapter cards. * The GetInventory NC-SI command reported leading 0xf in firmware version when it started with 0. **The following issues have been fixed in version 16.32.1010:** * Firmware got into an unresponsive state and caused unexpected behavior when connecting an optical transceiver that support RxLOS and the remote side port was down. * The link status was reported incorrectly and consequently caused the link to go down due to incorrect definition of the RX_LOS polarity in the INI. * On rare occasions, the system got into an unresponsive state when a peer port went down while using an Optical module. * Incorrect RNR timeout when trying to set it during the rts2rts_qp transition. * The system could not create more than 128K QPs. * The GetInventory NC-SI command reported leading 0xf in firmware version when it started with 0. * PCIe lane margining capability issues. - *Fixes submitted in version 12.26.1040:** * IPoIB could not to function when there were Dynamically Connected Transport (DC) CNAK Queue Pairs (QPs) active. * On rare occasions, when firmware coalesce Host stuck events occur, a async event might be delayed to be reported, and not be triggered until the next time the PCIe hangs on one of the hosts. * Renamed the GMP Mellanox Vendor Specific External Capability mask enum from IsDiagnosticCountersSupported to IsDiagnosticDataSupported. * Fixed an issue that caused a function to misbehave when a PCIe Transaction Layer Packet (TLP) was set with a poisoned indication. **Fixes submitted in version 16.26.1040:** * On rare occasions, when firmware coalesce Host stuck events occur, a async event might be delayed to be reported, and not be triggered until the next time the PCIe hangs on one of the hosts. * Unexpected queue pairs transitioned to error in lossy tests. * Limited the maximum amount of dumps created on a PF. * Renamed the GMP Mellanox Vendor Specific External Capability mask enum from IsDiagnosticCountersSupported to IsDiagnosticDataSupported. * Stability issues with RDMA over Converged Ethernet (RoCE) retransmissions under stress were affecting Zero-Touch-RoCE. * Fixed an issue that caused a function to misbehave when a PCIe Transaction Layer Packet (TLP) was set with a poisoned indication. * Large number of packets dropped when running Jumbo frames with TTL rewrite. * Limited the number of the elements in the Quality of Service (QoS) tree 2K. Note: Creating more than 250 Vport_tc for every TC is not allowed. * Queue Pair (QP) flow query was always taking port 1, Firmware will now reply the proper port, 1 or 2, for the dual port RoCE net device. * The nack counters constantly reported as "0". * In a rare scenario when the driver is executing the "2err" command and the QP is in Send Queue (SQ) drain state, the firmware might post event of broken Work Queue (WQ) instead of sending error Completion Queue Element (CQEs) on all the Work Queue Entry (WQEs). - *Firmware for the following devices are updated to 12.27.1016:** 843400-B21 (HPE Apollo A10 InfiniBand EDR (100Gb) 2-port Adapter) **Firmware for the following devices are updated to 16.27.1016:** 872723-B21 (HPE Apollo InfiniBand EDR 100Gb 2-port 841z Mezzanine Adapter) 872725-B21 (HPE InfiniBand EDR 100Gb 1-port 841QSFP28 Adapter) **Changes and New Features in firmware version 12.27.1016 and 16.27.1016:** * RoCE Selective Repeat introduces a new QP retransmission mode in RoCE: recovery from packet drop by resending the dropped packet and not only all the PSN window (Go-Back-N protocol), This new capability comes with the following limitations: * Selective repeat cannot be used with AR * Does not work with signature (T10-DIF) * Does not work with Tag Matching enabled * Allows BMC to query and control NIC over RedFish API (https://www.dmtf.org/standards/redfish). Currently, the NIC supports reading data and setting basic Ethernet and InfiniBand parameters. * Enables matching of source_vhca_port in the FDB flow for ECMP hardware offload on a single FDB. * Added support for dumping hardware steering entries (raw data) using the resource dump API. * The eth_link_down_counter now counts logical link downs as well. **Changes and New Features in firmware version 16.27.1016:** * Removed power consumption limitation. This new capability removes the necessity to disable the port due to insufficient power. When this feature is enabled, an event will be sent on every transition between the following power states: * Power limit is not advertised * Sufficient power detected * Insufficient power detected * Firmware can be now updated as well as DB strings while performing Live Firmware Patch. * Enables the device to generate events that will notify the user about any resource dumps updates. The resource dump owner (PF/ECPF) will be notified on the VF command failures by events that will contain the needed information to call the resource_dump command. The device will dump the resource in the standard resource dump sequence. * Added support for the following features: * RSS based on inner headers of GTP-U tunneled packets. * Relaxed ordering read when using the create_mkey flag. Note: This capability is not supported when using Multi-Host cards and when in PCIe-Switch mode. - *Fixes submitted in version 12.27.1016:** * ZTR counters query was always set to return 0. * The adapter card was prevented from going into the bypass mode when the BMC disabled the hardware arbitration. * Performance degradation and a high packet drop occurred when SRIOV was enabled and packets went through the FDB default behaviour. * Due to the string DB not being updated after Live-Patch, the tracer could not function after Live-Patch. * Fixed a rare issue that caused other active functions to receive a malformed CQE during driver (PF or VF) unload or FLR flows. * Firmware error was observed when FLR occurred at the same time as the teardown. As a result, the teardown flow took a lock, and never released it because it was being aborted by an FLR. **Fixes submitted in version 16.27.1016:** * Fixed an issue that caused the device to perform DMA into memory already returned to the OS during the transition between the pre-boot driver to the OS driver. * Out-of-range issue when reading or writing the q_counters. * Fixed an issue that in Multi-Host adapter cards that resulted in wrong handling of PERST on auxiliary links. * ZTR counters query was always set to return 0. * The adapter card was prevented from going into the bypass mode when the BMC disabled the hardware arbitration. * A non-standard tool was required to perform the first LFWP patching when used with the GA firmware version. * Updated the OOOSLMask behaviour. Firmware now will apply OOOSLMask even if it is set to zero (OOOSLMask = 0). * Redundant page consumption in the init_hca. * The sw_reset option was not supported when ATS was enabled. * When ESWITCH_IPV4_TTL_MODIFY_ENABLE configuration was enabled in mlxconfig, there was performance degradation in small packet sizes. * Due to the string DB not being updated after Live-Patch, the tracer could not function after Live-Patch. * Fixed a rare issue that caused other active functions to receive a malformed CQE during driver (PF or VF) unload or FLR flows. * The PCI link was not getting established when the firmware was corrupted. * FW assert was triggerred and resulted in a wrong deallocation of a resource when Packet Pacing was enabled, and a QP was being destroyed. * Firmware error was observed when FLR occurred at the same time as the teardown. As a result, the teardown flow took a lock, and never released it because it was being aborted by an FLR. - *Firmware for the following devices are updated to 12.27.4000:** 843400-B21 (HPE Apollo A10 InfiniBand EDR (100Gb) 2-port Adapter) **New Feature and Changes in Version 12.27.4000:** * Added the following segments, as appeared in the PRM, to the Resource Dump: * PRM_QUERY_QP * PRM_QUERY_CQ * PRM_QUERY_MKEY * QUERY_VNIC_ENV **Firmware for the following devices are updated to 16.27.2008:** 872723-B21 (HPE Apollo InfiniBand EDR 100Gb 2-port 841z Mezzanine Adapter) 872725-B21 (HPE InfiniBand EDR 100Gb 1-port 841QSFP28 Adapter) **New Feature and Changes in Version 16.27.2008:** **This release contains important reliability improvements and security hardening enhancements. Upgrade the firmware of the device to this release to improve the devices' firmware security and reliability.** * Improved init_hca performance in Parallel Function initialization. - *Following issues have been fixed in firmware version 16.27.2008:** * Although the effective BER (after FEC) was expected to meet the design targets (e.g. 10e-14 or lower), occasionally it was higher. * High BER occured when connecting cables of type 0.5/1m DAC to an HDR speed. * The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled. * The desched_threshold field did not work properly. * The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter. * If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again. **Following issues have been fixed in firmware version 12.27.4000:** * The device hung while running the sw reset flow under heavy stress and with many open resources. * Low PXE performance observered while using the VSC to trigger the send_ring_doorbells. * IPoIB and DC would not work together. * DC funtionality issues. - *Firmware for the following devices are updated to 12.28.1002:** 843400-B21 (HPE Apollo A10 InfiniBand EDR (100Gb) 2-port Adapter) **New Feature and Changes in Version 12.28.1002:** * Increased the maximum XRQ number to 512. **Firmware for the following devices are updated to 16.29.1016:** 872723-B21 (HPE Apollo InfiniBand EDR 100Gb 2-port 841z Mezzanine Adapter) 872725-B21 (HPE InfiniBand EDR 100Gb 1-port 841QSFP28 Adapter) **New Feature and Changes in Version 16.29.1016:** Added support for following features: * Changed the default value of DCQCN's (Data center- Quantized Congestion Notification) NP parameter min_time_between_cnps to 4 on all devices to support larger scalability of the cluster. * An option to allow applications to build their own QoS tree over the NIC hierarchy by connecting QPs to responder/requestor Queue Groups. * "InfiniBand" properties set to the Network Device Function Redfish object. * HW support for Flow Metering to utilize Advanced Steering Operation (ASO). HW Flow Meter allows higher scale, more accuracy, and better performance compared to the FW Flow Metering. * Trust level for VFs. Once the VF is trusted, it will get a set of trusted capabilities. * 2 new Mini CQE formats: Responder Mini CQE With Flow Tag Layout Responder Mini CQE With l3_l4_info Layout * UCX can now enable AR by exposing Out-Of-Ordering bitmask per SL with "ooo_per_sl" field in the HCA_VPORT context. It can be also queried by running the QUERY_HCA_VPORT_CONTEXT command. * Steering DP hash flow groups. * A new counter per vPort that counts the number of packets that reached the Ethernet RQ but cannot fit into the WQE due to their large size. Additionally, we added the option to control if such packet will cause "CQE with Error" or "CQE_MOCK". * PCIe Rx modifications to prevent the adapter cards from disappearing from the system. * ignore_flow_level is now enabled by the TRUST LEVEL access registry. * cq_overrun counter. The counter represents the number of times CQs enter an error state due to overflow that occur when the device tries to post a CQE into a full CQ buffer. * [Beta] Enabled the capability to allow Virtual Functions to send Pause Frames packets. * Enabled 10/25GbE auto-sensing with 3rd party when using 10/25GbE optical cables. * Hardware steering dump output used for debugging and troubleshooting. - *Following issues have been fixed in firmware version 16.29.1016:** * An issue that prevented VXLAN packets with svlan/ cvlan tag from being matched. * An issue that caused the eth_wqe_too_small counter to count ODP (On-Demand Paging) page faults. * When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs are configured, VM restart (VF/PF FLR) will take longer than when MKEY_BY_NAME is disabled. * Ani ssue that resulted in low performance after enabling the RoCE Accelerator capability. Note: The fix is available when all ports are set as Ethernet. * On rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR. * The chassis manager calculation for Multi-Host and Socket-Direct adapter cards to allow running NC-SI commands by the chassis manager BMC. Now the chassis manager is count as BMC with index 0, regardless of how many BMC there are. * An issue that caused the device to go to down IRISC as one of the firmware semaphores could not be released when a speed change or port state change was triggered. **Following issues have been fixed in firmware version 12.28.1002:** * An issue that caused the DCR (DC Resources) to be destroyed before the retry option managed to work when the retry timeout is too big. in this case, the DCR' time-to-live was increased, and the maximum retry timeout was decreased. * Increased PHY power consumption limit to 1.5w. * An issue that caused PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr not to report port icrc errors. - *Firmware for the following devices are updated to 12.28.2006:** 843400-B21 (HPE Apollo A10 InfiniBand EDR (100Gb) 2-port Adapter) **Firmware for the following devices are updated to 16.31.1014:** 872723-B21 (HPE Apollo InfiniBand EDR 100Gb 2-port 841z Mezzanine Adapter) 872725-B21 (HPE InfiniBand EDR 100Gb 1-port 841QSFP28 Adapter) **New features and changes in version 12.28.2006:** * Increased the maximum XRQ number to 512. **New features and changes in version 16.31.1014:** * NIC scheduling feature support has been disabled for non-privileged functions. * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * support for Enabling/Disabling NIC and RDMA (port/partition) was included via the UEFI HII system settings. * Increased the maximum number of MSIX per VF to 127. * Asymmetrical MSIX Configuration: This feature allows the device to be configured with a different number of MSIX vectors per physical PCI functions.To use this feature, please follow these steps: * Clear NUM_PF_MSIX_VALID to disable global symmetrical MSIX configuration. * Set PF_NUM_PF_MSIX_VALID to enable asymmetrical per Physical Function MSIX configuration. * Configure PF_NUM_PF_MSIX per physical PCI function. * RDMA partitioning and RDMA counters in IB mode. * Added a new bit ("data_in_order") to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. * Enabled UID 0 to create resources with UMEM (User Memory). * Receiving and sending native IB packets from/to the software (including all headers) via raw IBL2 QPs. * RX RDMA NIC flow table on an IB port. Now the software can steer native IB packets to raw IB receive queues according to the DLID and the DQPN. - *The following issues have been fixed in version 12.28.2006:** * An issue that caused the DCR (DC Resources) to be destroyed before the retry option managed to work when the retry timeout is too big. in this case, the DCR' time-to-live was increased, and the maximum retry timeout was decreased. * Increased PHY power consumption limit to 1.5w. * An issue that caused PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr not to report port icrc errors. **The following issues have been fixed in version 16.31.1014:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * An assert that was caused when trying to open 1024 functions on the device and the maximum number of functions was 1023. * Occasional performance issues related to RC QPs using E2E-credits (not connected to SRQ and doing send/receive traffic) when the ROCE_ACCL tx_window was enabled. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * A rare issue that caused RX pipe to hang. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. * CRT_DCR with index larger than 1 << 21 occasionally collided with the CRT_SW_RESERVED address. * An issue that caused the TX queue to get into an unresponsive state when the VF rate limiter was set. **Additional Fixes included in version 16.31.1014:** * Disabled the CNP counter "rp_cnp_ignored " (triggered by OOS (out-of-sequence)) when all ports are IB. * Fixed the TMP421 sensor temperature reporting. * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. - *Fixes in version 12.28.2006:** * Fixed an issue that caused the DCR (DC Resources) to be destroyed before the retry option managed to work when the retry timeout is too big. in this case, the DCR' time-to-live was increased, and the maximum retry timeout was decreased. * Increased PHY power consumption limit to 1.5w. * Fixed an issue that caused PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr not to report port icrc errors. **The following issues have been fixed in version 16.32.1010** * Firmware got into an unresponsive state and caused unexpected behavior when connecting an optical transceiver that support RxLOS and the remote side port was down. * The link status was reported incorrectly and consequently caused the link to go down due to incorrect definition of the RX_LOS polarity in the INI. * The system got into an unresponsive state when a peer port went down while using an Optical module. * Invalid RNR timeout when trying to set it during the rts2rts_qp transition. * A fatal assert 0x81C5 occurred when calling get_vport_mad from the MAD APIs. The firmware was trying to compute the number of vPorts using a global function number. To avoid this issue, the API was updated to remove any assumption on the function number. Note: This issue is affects only IB devices. * During events, stress caused the firmware to reset the Arm host of the vPort without sending an event. Thus preventing the software from rearming the vPort as it did not receive any event, and the firmware did not send the event because the vPort had no Arm set. * The system could not create more than 128K QPs. * The GetInventory NC-SI command reported leading 0xf in firmware version when it started with 0. * PCIe lane margining capability issues. * An issue related to the sl2vl mad that caused a few msec hiccup in the transmission on an InfiniBand network when the SM sent the sl2vl mad to a node in the cluster. - *Following issues have been fixed in firmware version 16.27.2008:** * Although the effective BER (after FEC) was expected to meet the design targets (e.g. 10e-14 or lower), occasionally it was higher. * High BER occured when connecting cables of type 0.5/1m DAC to an HDR speed. * The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled. * The desched_threshold field did not work properly. * The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter. * If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again. **Following issues have been fixed in firmware version 14.27.4000:** * The device hung while running the sw reset flow under heavy stress and with many open resources. * Low PXE performance observerd while using the VSC to trigger the send_ring_doorbells. * IPoIB and DC would not work together. * DC funtionality issues. - *Firmware for the following devices is updated to 14.29.1016:** P21930-B21 (HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCAT Adapter) P11341-B21 (HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter) **Firmware for the following devices is updated to 16.29.1016:** P13188-B21 (HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACAT Adapter) P21927-B21 (HPE Ethernet 100Gb 2-Port QSFP28 MCX516A-CCHT Adapter) P10112-B21 (HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter) **This release contains important reliability improvements and security hardening enhancements. Upgrade the firmware of the device to this release to improve the devices' firmware security and reliability.** **New Feature and Changes in Version 14.29.1016 and 16.29.1016:** * Ethernet wqe_too_small Mode: A per vPort that counts the number of packets that reached the Ethernet RQ but cannot fit into the WQE due to their large size. Additionally, we added the option to control if such packet will cause "CQE with Error" or "CQE_MOCK". * Hardware steering dump output used for debugging and troubleshooting. Added support for the following features: * cq_overrun counter: The counter represents the number of times CQs enter an error state due to overflow that occur when the device tries to post a CQE into a full CQ buffer. * Enabled the capability to allow Virtual Functions to send Pause Frames packets. (Beta) * Enabled 10/25GbE auto-sensing with 3rd party when using 10/25GbE optical cables. **New Feature and Changes in Version 16.29.1016:** * Hardware steering dump output used for debugging and troubleshooting. Added support for the following features: * HW support for Flow Metering to utilize Advanced Steering Operation (ASO). HW Flow Meter allows higher scale, more accuracy, and better performance compare to the FW Flow Metering. * Trust level for VFs. Once the VF is trusted, it will get a set of trusted capabilities. * 2 new Mini CQE formats: * Responder Mini CQE With Flow Tag Layout. * Responder Mini CQE With l3_l4_info Layout. * Steering DP hash flow groups. * ignore_flow_level is now enabled by the TRUST LEVEL access registry. - *Following issues have been fixed in firmware version 14.29.1016 and 16.29.1016:** * Changed the default value of DCQCN's NP parameter min_time_between_cnps to 4 on all devices to support larger scalability of cluster. * An issue that caused packets to drop due to header size issues and/or failing checks. This issue was caused due to a Linux issue that caused VFs to set the wrong header size value in wqe_inline_header_mode input. * When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs are configured, VM restart (VF/PF FLR) might take longer than when MKEY_BY_NAME was disabled. * In rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR. * An issue that caused the device to go to dead IRISC as one of the firmware semaphores could not be released when a speed change or port state change was triggered. **Following issues have been fixed in firmware version 16.29.1016:** * An issue that caused the eth_wqe_too_small counter to count ODP page faults. * A low performance was observed after enabling the RoCE Accelerator capability. - *Firmware for the following devices is updated to 14.29.1016:** P21930-B21 (HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCAT Adapter) **Firmware for the following devices is updated to 14.31.1200:** P11341-B21 (HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter) **Firmware for the following devices is updated to 16.29.1016:** P21927-B21 (HPE Ethernet 100Gb 2-Port QSFP28 MCX516A-CCHT Adapter) **This release contains important reliability improvements and security hardening enhancements. Upgrade the firmware of the device to this release to improve the devices' firmware security and reliability.** **New Feature and Changes in Version 14.29.1016 and 16.29.1016:** * Ethernet wqe_too_small Mode: A per vPort that counts the number of packets that reached the Ethernet RQ but cannot fit into the WQE due to their large size. Additionally, we added the option to control if such packet will cause "CQE with Error" or "CQE_MOCK". * Hardware steering dump output used for debugging and troubleshooting. * cq_overrun counter: The counter represents the number of times CQs enter an error state due to overflow that occur when the device tries to post a CQE into a full CQ buffer. * Enabled the capability to allow Virtual Functions to send Pause Frames packets. (Beta). * Enabled 10/25GbE auto-sensing with 3rd party when using 10/25GbE optical cables. **New Feature and Changes in Version 16.29.1016:** * Hardware steering dump output used for debugging and troubleshooting. * HW support for Flow Metering to utilize Advanced Steering Operation (ASO). HW Flow Meter allows higher scale, more accuracy, and better performance compare to the FW Flow Metering. * Trust level for VFs. Once the VF is trusted, it will get a set of trusted capabilities. * 2 new Mini CQE formats: * Responder Mini CQE With Flow Tag Layout. * Responder Mini CQE With l3_l4_info Layout. * Steering DP hash flow groups. * ignore_flow_level is now enabled by the TRUST LEVEL access registry. **New Feature and Changes in Version 14.31.1200:** * Added a new NVconfig per Port for a specific Finisar module which sets the port to work in AN mode and sets the module to No DME. This change does not affect the speed logic, only the FEC logic (FEC override). **Note**: If the port does not come up, switch to Force mode. - *Following issues have been fixed in firmware version 14.29.1016 and 16.29.1016:** * Changed the default value of DCQCN's NP parameter min_time_between_cnps to 4 on all devices to support larger scalability of cluster. * An issue that caused packets to drop due to header size issues and/or failing checks. This issue was caused due to a Linux issue that caused VFs to set the wrong header size value in wqe_inline_header_mode input. * When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs are configured, VM restart (VF/PF FLR) might take longer than when MKEY_BY_NAME was disabled. * In rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR. * An issue that caused the device to go to dead IRISC as one of the firmware semaphores could not be released when a speed change or port state change was triggered. **Following issues have been fixed in firmware version 16.29.1016:** * An issue that caused the eth_wqe_too_small counter to count ODP page faults. * A low performance was observed after enabling the RoCE Accelerator capability. **No fixes are included in firmware version 14.31.1200.** - *Firmware for the following devices is updated to 16.28.4200:** P13188-B21 (HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACAT Adapter) P10112-B21 (HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter) **New Feature and Changes in Version 16.28.4200:** **This release contains important reliability improvements and security hardening enhancements. Upgrade the firmware of the device to this release to improve the devices' firmware security and reliability.** * Enabled ASN1 and OCBB (DCi) MCTP HPE specific protocols. - *Following issues have been fixed in firmware version 16.28.4200:** * Although the effective BER (after FEC) was expected to meet the design targets (e.g. 10e-14 or lower), occasionally it was higher. * High BER occured when connecting cables of type 0.5/1m DAC to an HDR speed. * The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled. * The desched_threshold field did not work properly. * The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter. * If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again. - *Firmware for the following devices is updated to 14.31.1014:** P21930-B21 (HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCAT Adapter) **Firmware for the following devices is updated to 14.31.1200:** P11341-B21 (HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter) **Firmware for the following devices is updated to 16.31.1014:** P21927-B21 (HPE Ethernet 100Gb 2-Port QSFP28 MCX516A-CCHT Adapter) **New features and changes included in version 14.31.1014:** * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * support for Enabling/Disabling NIC and RDMA (port/partition) was included via the UEFI HII system settings. * Increased the maximum number of MSIX per VF to 127. * Added a new bit ("data_in_order") to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. **New features and changes included in version 14.31.1200:** * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * support for Enabling/Disabling NIC and RDMA (port/partition) was included via the UEFI HII system settings. * Increased the maximum number of MSIX per VF to 127. * Added a new bit ("data_in_order") to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. * Added a new NVconfig per Port for a specific Finisar module. This new NVconfig sets the port to work in AN mode and sets the module to No DME. This change does not affect the speed logic, only the FEC logic (FEC override). Note: If the port does not go up, switch to Force mode. **New features and changes included in version 16.31.1014:** * NIC scheduling feature support has been disabled for non-privileged functions. * Implemented a new NC-SI command get_debug_info to get mstdump via the NC-SI protocol to debug a device if the PCI link fails for any given reason. * support for Enabling/Disabling NIC and RDMA (port/partition) was included via the UEFI HII system settings. * Increased the maximum number of MSIX per VF to 127. * Asymmetrical MSIX Configuration: This feature allows the device to be configured with a different number of MSIX vectors per physical PCI functions.To use this feature, please follow these steps: * Clear NUM_PF_MSIX_VALID to disable global symmetrical MSIX configuration. * Set PF_NUM_PF_MSIX_VALID to enable asymmetrical per Physical Function MSIX configuration. * Configure PF_NUM_PF_MSIX per physical PCI function. * RDMA partitioning and RDMA counters in IB mode. * Added a new bit ("data_in_order") to query the QP and allow a process/library to detect when the AR is enabled. * A new flex parser to support GENEVE hardware offload and ICMP. * When the non-page-supplier-FLR funcion is initiated, the firmware triggers a page event to the page supplier to indicate that all pages should be returned for the FLR function. * Enabled UID 0 to create resources with UMEM (User Memory). * Receiving and sending native IB packets from/to the software (including all headers) via raw IBL2 QPs. * RX RDMA NIC flow table on an IB port. Now the software can steer native IB packets to raw IB receive queues according to the DLID and the DQPN. - *The following issues have been fixed in version 14.31.1014:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. **Additional Fixes included in version 14.31.1014:** * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. **The following issues have been fixed in version 14.31.1200:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. **Additional Fixes included in version 14.31.1200:** * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. **The following issues have been fixed in version 16.31.1014:** * TX PRBS was not changed even after reconfiguring it, all PRBS mode were enabled in test mode. * An assert that was caused when trying to open 1024 functions on the device and the maximum number of functions was 1023. * Occasional performance issues related to RC QPs using E2E-credits (not connected to SRQ and doing send/receive traffic) when the ROCE_ACCL tx_window was enabled. * A fatal error occurred and eventually resulted in the HCA to get into an unresponsive state when a packet was larger than a strided receive WQE that was being scattered. * A rare issue that caused RX pipe to hang. * The resource number size (a 64 bit number) was overwritten with a 32 bit number and erased the high bits when de-allocating the resource number. * CRT_DCR with index larger than 1 << 21 occasionally collided with the CRT_SW_RESERVED address. * An issue that caused the TX queue to get into an unresponsive state when the VF rate limiter was set. **Additional Fixes included in version 16.31.1014:** * Disabled the CNP counter "rp_cnp_ignored " (triggered by OOS (out-of-sequence)) when all ports are IB. * Fixed the TMP421 sensor temperature reporting. * Fixed the rate select mechanism in QSFP modules. * Fixed classification issues for "Passive" cables to be more robust. * Initialized the rate table in the static configuration so it will be configured at the link-not-up scenarios. - *The following issues have been fixed in version 14.32.1010:** * Firmware got into an unresponsive state and caused unexpected behavior when connecting an optical transceiver that support RxLOS and the remote side port was down. * The system could not create more than 128K QPs. * On rare occasions, the system got into an unresponsive state when a peer port went down while using an Optical module. * Packet Pacing rate was used if asymmetric VFs was enabled. * Incorrect RNR timeout when trying to set it during the rts2rts_qp transition. * Issue with RSS on IPSec flows in ConnectX-4 Lx led to performance degradation. In this scenario, the SPI optimization caused packets from a given host to hash to the same CPU core. The fix was to ignore SPI optimization according to l4_type in ConnectX-4 Lx adapter cards. * The GetInventory NC-SI command reported leading 0xf in firmware version when it started with 0. **The following issues have been fixed in version 16.32.1010:** * Firmware got into an unresponsive state and caused unexpected behavior when connecting an optical transceiver that support RxLOS and the remote side port was down. * The link status was reported incorrectly and consequently caused the link to go down due to incorrect definition of the RX_LOS polarity in the INI. * On rare occasions, the system got into an unresponsive state when a peer port went down while using an Optical module. * Incorrect RNR timeout when trying to set it during the rts2rts_qp transition. * The system could not create more than 128K QPs. * The GetInventory NC-SI command reported leading 0xf in firmware version when it started with 0. * PCIe lane margining capability issues. - This product corrects an issue where the WWPN information is missing in an adapter's FCoE configuration menu (under 'System Utilities'->'System Configuration' menu). This product corrects an issue where server hangs during POST when a network adapter is connected to the HPE Synergy 20Gb Interconnect Link Module. This product corrects an issue where the initiator does not stay logged into the target in an FCoE connection. This product corrects an issue where the link status continues to show as UP on the switch side even after a network adapter is disabled in the OS. - This product now supports the HPE Ethernet 10Gb 2-port 524SFP+ Adapter. - This product now supports the HPE Synergy 6820C 25/50Gb Converged Network Adapter. This product now allows modification of the settings under the 'Port Level Configuration' sub-menu under the adapter's configuration menu (located at 'System Utilities'(F9 at POST)->'System Configuration') when OneView Profile with 'manage manually' option is applied to the server. - This product corrects an issue where the firmware update fails when the first port is disabled on the network adapter. This product corrects an issue where not all devices are discovered as part of firmware update on a multi-root-complex platforms like Integrity, Superdome etc. This product corrects an issue where the system hangs during POST with red screen when iSCSI boot LUN is re-exported (after a previous unexport operation) from the iSCSI host (HPE 3PAR StoreServ Storage). This product corrects an issue where 'HPE Synergy 4820C 10/20/25Gb Converged Network Adapter' disappears after changing its link speed under its configuration menu (located at 'System Utilities'(F9 at POST)->'System Configuration'). This product corrects an issue where the configuration settings of the adapter, connected to a server managed by OneView profile, may be reset to defaults after a system reboot. - This product now remove supports Synergy and Blade Server. This product now supports Red Hat Enterprise Linux 8. - This product addresses an issue where 2nd port reports "function type: disabled" with HPE Ethernet 10Gb 2-port 524SFP+ Adapter. - This product corrects the abnormal disconnection of iLO web page while performing under Shared Networking on Flexible-LOM. * This product addresses an issue where the HPE Ethernet 10/25Gb 2-port 622FLR-SFP28 adapter and HPE Ethernet 10/25Gb 2-port 621SFP28 Adapter UMCE (Uncorrectable Machine Check Exception) was followed by Unrecoverable I/O error, Uncorrectable PCI express error on Server and one of the ports suddenly no longer can send or receive traffic. * This product addresses an issue where driver doesn't load upon booting up by correct memory relocation. - This product contains support PLDM firmware upgrade base improvements. - This product addresses an issue where the modification on string format of firmware update payload. - This product addresses the problem that the MAC being modified after Firmware update - This product corrects an issue where the link status is not updated immediately to the switch when network adapter interface is brought down in the Operating System. This product corrects an issue where not all devices are discovered as part of firmware update on a multi-root-complex platforms like Integrity, Superdome, etc. This product corrects an issue where the system hangs with red screen when attempting to update the firmware via 'Firmware Update' feature under the 'System Utilities > Embedded Applications' menu. This product corrects an issue where a firmware update fails. - This product now remove supports Synergy and Blade Server. This product now supports the following operatings systems: * Red Hat Enterprise Linux 7 Update 7 * Red Hat Enterprise Linux 8 Update 0 * SUSE Linux Enterprise Server 15 SP1 - This product addresses an incorrect local sequence number in the Link Layer Discovery Protocol (LLDP). This product addresses an issue where boot mode is not restored to the default value after a factory reset. - This product addresses an Overheat issue that system shuts down automatically due to NIC temperature exceeding threshold. - This product corrects the display problem of the adapter name under RBSU. * This products corrects some issues about the thermal reporting and temperature threadshold control of the adapter. * This product addresses an issue where unexpected UMCE(Uncorrectable Machine Check Exception) appeared when powering on the system with NPAR(Network Partitioning) enabled. - This product addresses an issue where the Firmware installation failure when enabling secure boot under SUSE Linux Enterprise Server 15 SP2. - This product addresses an issue that platform would be randomly waked up by WOL packet. - **This product addressed the firmware update failure problem which may cause NIC FW corruption.** * **This product addressed the firmware update failure problem while the platform secure boot being enabled.** - This product now supports Red Hat Enterprise Linux 8 update 4 and SUSE Linux Enterprise Server 15 Service Pack 3 - TBD - Initial release. - Initial release. - Initial release. - Initial release. - - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** Integrated Lights-Out 5 (iLO 5) Firmware version 1.15 and System ROM version 1.20 or later **Enhancements/New Features:** Added support for Dynamic Power Capping. For proper operation, please ensure that Integrated Lights-Out 5 (iLO 5) Firmware version 1.15 and System ROM version 1.20 or later are updated on the server. **Known Issues:** None - *Important Notes:** Ver. 1.0.4 (B) contains support for new server products. It is functionally equivalent to ver. 1.0.4. It is not necessary to upgrade with Revision (B) if a previous component revision was used to upgrade the firmware to ver. 1.0.4. **Firmware Dependencies:** Integrated Lights-Out 5 (iLO 5) Firmware version 1.15 and System ROM version 1.20 or later **Enhancements/New Features:** Added support for Dynamic Power Capping. For proper operation, please ensure that Integrated Lights-Out 5 (iLO 5) Firmware version 1.15 and System ROM version 1.20 or later are updated on the server. **Known Issues:** None - *Important Notes:** Ver. 1.0.4 (D) contains updates to the component packaging and is functionally equivalent to ver. 1.0.4. It is not necessary to upgrade with Revision (D) if a previous component revision was used to upgrade the firmware to ver. 1.0.4. **Firmware Dependencies:** Integrated Lights-Out 5 (iLO 5) Firmware version 1.15 and System ROM version 1.20 or later **Enhancements/New Features:** Added support for Dynamic Power Capping. For proper operation, please ensure that Integrated Lights-Out 5 (iLO 5) Firmware version 1.15 and System ROM version 1.20 or later are updated on the server. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** Added support for AMD EPYC 7002 Generation Processors. ROM version 2.00 or later is required to enable the support. This version of firmware does not include any changes for platforms with Intel Processors or AMD EPYC 7001 Generation Processors. **Known Issues:** None - *Important Notes:** Ver. 1.0.7 (B) contains updates to the component packaging and is functionally equivalent to ver. 1.0.7. It is not necessary to upgrade with Revision (B) if a previous component revision was used to upgrade the firmware to ver. 1.0.7.This is the initial version for HPE Gen10 Plus servers. **Firmware Dependencies:** For HPE ProLiant DL325/DL385 Gen10 servers, ROM version 2.00 or later is required to enable the support. iLO5 version 1.40 or above is required to upgrade to this version. **Enhancements/New Features:** Added support for AMD EPYC 7002 Generation Processors on HPE ProLiant DL325/DL385 Gen10 servers. ROM version 2.00 or later is required to enable the support. This version of firmware does not include any changes for Gen10 platforms with Intel Processors or AMD EPYC 7001 Generation Processors. iLO5 version 1.40 or above is required to upgrade to this version. This is the initial version for HPE Gen10 Plus servers. **Known Issues:** None - *Important Notes:** Ver. 1.0.7 (C) contains updates to the component packaging and is functionally equivalent to ver. 1.0.7. It is not necessary to upgrade with Revision (C) if a previous component revision was used to upgrade the firmware to ver. 1.0.7.This is the initial version for HPE Gen10 Plus servers. **Firmware Dependencies:** For HPE ProLiant DL325/DL385 Gen10 servers, ROM version 2.00 or later is required to enable the support. iLO5 version 1.40 or above is required to upgrade to this version. **Enhancements/New Features:** Added support for AMD EPYC 7002 Generation Processors on HPE ProLiant DL325/DL385 Gen10 servers. ROM version 2.00 or later is required to enable the support. This version of firmware does not include any changes for Gen10 platforms with Intel Processors or AMD EPYC 7001 Generation Processors. iLO5 version 1.40 or above is required to upgrade to this version. This is the initial version for HPE Gen10 Plus servers. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Fixed an issue of inaccurate temperature readings when the actual temperature exceeds 100 C on Proliant Gen10 Plus servers. **Known Issues:** None - The following issues are resolved in version 4.21: * Expander may reset during heavy SSACLI polling * SATA drives may take longer to spin up, not be initially detected, and then hot add later. This can prevent system boot or affect the logical drive status. - Fixes an issue where false Smart Carrier authenication errors may happen. - Added support for Gen10 plus UBM type 1/2/3 backplanes - Smart Carrier Authentication Failure issue - Added support for Gen10 plus UBM type 1/2/3 backplanes - Intermittent failures on Smart Carrier authentication - To make Valid flag is always set to true initially so that CRC check can be performed on initstring partition and test if it is really valid. - Users need to update HPE SAS 12G Expander FW version 5.12 for FW compatibility due to a specific SPI flash devices is used on the Expander card. Carry over issue resolution with reference SID8638. - 1\. In support of Micron 256Mb SPI ROM on the latest Shiner board 2\. Provided a proper downgrade restriction to ensure FW compatibility with the latest HW - - Update device guid - Fix issues - - Initial Release - Supports Drive Zoning - *Note:** If version 1.56 was previously installed, then it is not necessary to upgrade to version 1.56 (B). - Added support for SUSE Linux Enterprise Server 15 OS - - Initial Release - - 1.03 is the initial firmware release. - Added support for new 6 HDD SFF backplane. - Added support for new 6 SFF HDD backplane. - In rare circumstances after multiple, successive reboots, a system with 28 large form factor drives might become unresponsive. Firmware v1.26 resolves the issue. - **Customers who already installed firmware version 1.26 do not need to update to 1.26 (B).** - Updated to support Service Pack for ProLiant version 2017.07.0 **Note:** If version 1.26 was previously installed, then it is not necessary to upgrade to version 1.26 (B). - Enhanced debug capabilities - Enhanced debug capabilities - Added HPE Smart Array P824i-p controller support - Drive may show up missing after a system reboot. - Initial Release - Modify Product ID's to "A4200 Gen10P LFF" and "A4200 Gen10P SFF" to distinguish the generation. - The following issues have been fixed in Smart Array controller firmware v3.00: * Background surface scan might not repair media errors on 12G SAS drives in RAID 1, 5, 10, and 50 logical drives. * In some I/O workloads, the file system or application might read incorrect data from encrypted RAID 0 (with two or more physical drives) or RAID 10/10ADM (with four or more physical drives) logical drives. * A controller might hang when a Test Unit Ready command fails during SSD logical drive Rapid Parity Initialization. * During a rebuild and extreme simultaneous host I/O writes, the rebuild operation might use old data, resulting in subsequent host reads that might return old data. * A host might read incorrect data after background parity initialization finishes on a logical drive on a single array with multiple logical drives. * A controller lockup issue might occur during the repair of an unrecoverable read error (URE) on a RAID 5 volume. * A controller lockup issue might occur during SmartCache error handling. * A controller lockup issue might occur during controller boot when SmartCache is enabled. * A file system or application might read incorrect data when a coalesced host request encounters a fatal error. * A failed drive installed during controller boot is not identified as a failed drive. * The failed drive status LED is not illuminated when a good drive is replaced with a failed drive in a backplane. * In configurations with backplanes, a failed drive installed as a replacement for a previously configured RAID volume is not identified as a failed drive. * A rebuild of a logical drive created from SSD drives fails to start within 1,200 seconds. * A performance drop during 16k to 256k sequential reads with low queue depth occurs on a logical drive with cache enabled. * A controller lockup issue might occur during a simultaneous host write and background cache flush operation. * Incorrect connector information is displayed for SATA drives after certain physical events in a dual I/O module enclosure configuration. * A failed drive that is physically present in a drive bay is not reported correctly. * Devices might drop out of a configuration after multiple create or delete drive zone group commands are issued. * The drive status LED does not flash during sanitize operations if drives are attached to an expander. * Cache disable status is not updated correctly when backup power source charging times out. * The clear configuration command might not clear the configuration if SmartCache is enabled and the system was previously shut down ungracefully. * The clear configuration command fails if a SmartCache volume has multiple UREs within a SmartCache page block size. * A controller lockup issue might occur when toggling a path to an enclosure in a dual domain configuration. * The controller runs in survival mode if a temperature sensor is not detected. * The clear configuration command might report failures when it encounters an installed drive with failed status. * A performance drop occurs during sequential workloads. * A controller failure might occur when running concurrent I/O to unassigned drives and drives in a RAID logical drive. * After a reboot, a bad drive might prevent controller discovery or operating system startup. * A host request is incorrectly returned as Failed when a failed drive in a degraded volume is replaced. * Modifying the spare configuration under an active spare rebuild causes the rebuild process to stop. * Incorrect device location reporting occurs when direct-attach drives are not attached to a backplane and an enclosure management schema is not defined. * RAID volume configuration settings are not applied when a disk drive transitions from unassigned to RAID usage during runtime. * A RAID volume with a failed drive reappears after a clear configuration operation completes and the system is rebooted. * A controller might hang during a SmartCache flush task that encounters multiple unrecoverable media errors (UREs). * A response of all zeros is sent for ATA PASSTHROUGH commands, such as SMART READ DATA, through Out of Band (OOB) host transport. - Official one-off release for FW 3.21 for key customer issue fixed. - Enhanced the performance of sequential READ I/Os greater than 256KiB for cached logical drives. * Added support for user-configurable expander scan duration parameters. * Improved background consistency check to scan logical drives more efficiently. * Added support for Port Discovery Protocol host tool option to support SGPIO or UBM backplanes. - A controller lockup issue occurs when clearing the configuration of an encryption-enabled controller. * When unconfigured drives are directly attached, the PHY ID is always 0 in the ADU report or lsscsi output. * A file system or application might read incorrect data when there is pending read or write operation and an array transformation is in progress on the logical drives. * A rekey operation on a SmartCache volume pauses when the controller firmware is upgraded and the server is warm rebooted. * A SMART READ DATA command sent with an out-of-band method returns a response of all zeros. * The Maximum Connection Number calculation for an indirectly attached wide-port end-target is incorrect. * A firmware exception might occur during task management abort handling for a non-NCQ SATA command. * A controller lockup issue might occur when the PHYs fluctuate between link up/link down status. * Open frames cause an I/O timeout that results in an Open Reject Bad Destination response and a host I/O timeout. This situation causes a server node to be evicted from a cluster. * Removing a redundant fan module in an attached JBOD causes Failed JBOD status. * The controller might not respond for up to 15 minutes when a drive reports a hardware failure. * Specifying an incorrect serial number in the API when attempting to HALON flash a drive does not result in the expected error. * A SmartCache write bypass might result in a cache line getting stuck on a pending queue if the write to the primary logical drive is retried. * A controller might not respond if it is repeatedly forced between SIS (Inbox) and PQI I/O submission modes at the same time as an I/O timeout. * An issue in the write coalescing logic might cause a partially coalesced opportunity to be abandoned under high queue depth workloads. * The OS driver reports a lockup code that does not match the code provided by the firmware. * SATA drives are unnecessarily reset during a power-on self-test. * The bay number of a non-hot-plug drive is reported as 255/0xFF when the device inventory re-query API is initiated. * A controller might not respond when a clear configuration action is initiated at the same time that a degraded volume is undergoing Rapid Parity Initialization. * I/O coalescing is not enabled when DDR cache is not present or enabled. * A drive incorrectly reports failed status if it is spun down and then used to create a volume with Rapid Parity Initialization. * SmartCache metadata is lost after a new volume is created while running I/O traffic. * An abnormal volume state is observed with multiple SmartCache volumes configured using 512e drives. * A controller might not respond during volume transformation if the backup power source goes off line, is spuriously hot-removed, or indicates a cabling error. * A LUN reset issue occurs during heavy write I/O workloads on cache enabled volumes. * An incorrect spare SSD physical drive state is reported during a rebuild. * An I/O latency issue occurs during periodic disk write metadata operations. * A drive failure code might be incorrectly updated with a generic drive failure code. * When an expanding SmartCache volume is migrated to another controller after an ungraceful shutdown, the volume is not configured correctly. * A controller might not respond when an expanding volume is migrated from a controller that supports DDR cache to a controller that does not support DDR cache. * In a split mirror configuration, the cache ratio is reset to the default values after a backup cable error. * A controller might not respond after a cold boot during volume rekeying. * A controller lockup issue might occur in an HBA SAS drive dual path configuration. * A device reset command initiated by a host utility has a timeout issue in minimum power mode. * If you use the identify all LED command frequently, the command might not affect all drive LEDs. * A controller might not respond when you run the Internal Test Unit Ready command during drive hot removal or addition. * A controller lock up issue might occur when resuming a rebuild operation after a reboot. * A surface scan inconsistency check event is not logged for RAID 1 volumes. * A controller lock up issue might occur when activating a spare drive for an encrypted volume during I/Os. * A drive that failed due to read capacity is presented to the host. * A periodic background drive temperature check might skip every other minute. * A controller lock up issue might occur during expansion after multiple subsequent attempts to abort the expansion process. * An unknown error occurred during execution when Recover Cache Module in SSA. * Encryption host management commands are processed for a SmartCache volume, even though these commands do not apply to SmartCache volumes. * A host might read incorrect data after an array expansion operation. * High severity events logged when a controller is in the critical event buffer overflow condition are not prioritized. * Redundant surface scan pass complete events might be posted for the same surface scan iteration if the controller is rebooted during the scan. * During an expander firmware upgrade (reduced functionality mode), the last management device index remains open for processing I/Os, and an I/O timeout might occur. * A performance drop is observed on certain queue depths for the 4 kB sequential write workload on RAID logical volumes with SmartPath and DDR caching disabled. * A command timeout issue occurs during expander firmware upgrade with Non-Disruptive Soft Reset. - Added UBM type3 backplane support * Added support for long device model/product ID for SATA drives. - An issue where the controller might become unresponsive while waiting for a non-existent pre-fetch queue entry. * Host I/O timeouts might occur due to continuing firmware attempts to discover devices during an expander configuration. * A controller lockup problem (with code 0x1E10) might occur when a bad drive with an unsupported block size is connected into slot 0. * A Controller hangs issue when multiple hot-plug and hot remove events (drives or JBODs) were being processed. * A Controller hangs issue on DDR caching enabled logical volumes with sequential read towards the end of the volume. * A Controller hangs issue with outstanding I/Os on a degraded logical volume when the physical drive fails. * A Controller hangs issue if a host I/O and background consistency check simultaneously encounter a RAID-1 ADM stripe in which all drives have URE's on the same LBA. * A Controller hangs issue when a drive is failed from a RAID6/60 logical drive when the host issues a Clear Controller Configuration command or any other configuration change command. * The SSD data drive might be set offline (with reason code 0x37) when hot-remove and re-insert during a spare rebuild in progress. * A drive might not be exposed to the OS after reboot if the system is rebooted just after the sanitize erase finishes. * UBM backplanes are not detected properly when connected to specific ports (port 7 or above) in an expander card configuration. * A Controller hangs issue when processing idle time followed by a short burst of I/Os. * The controller might return the previous drive firmware version, after a drive firmware update on SATA drives. * The controller might fail drives (with reason code 0x49, I/O freeze timeout) during expander firmware upgrade on a multi-expander enclosure configuration. * Hot-added drive LED control fails on specific fan-out expander type external enclosure models. * sequential I/Os and the firmware coalescing logic can't get the memory. * Filesystem or application might read old data when SmartCache configurations encounter intermittent write I/O errors to a primary logical drive. - Fixed an issue where SSD SmartPath is not enabled on logical drives created on the same array in certain scenarios. * Fixed a problem where WRITE and READ fails with URE on a RAID6 volume where it could have completed successfully in certain error recovery scenarios. * Fixed a problem where events were not getting logged in certain scenarios. * Fixed an issue where a Windows memory dump process was taking longer than 30 minutes. * Fixed a problem in Gen10+ server where FAULT LED was not turning on for the drives failing during device discovery. * Fixed a problem where the critical event "Controller memory ECC error limit exceeded" was reported in the AHS IML log after upgrading to 3.53 B0 firmware build. * Fixed a problem where the host WRITE I/O failed on the SmartCache logical drive with UREs present on the primary logical drive. * Fixed an issue where the controller may be non-responsive after drive failure with SSD SmartPath enabled under a high queue depth workload. * Fixed a performance issue when the host is submitting large sequential IO streams at high queue depth. * Fixed an issue where OS filesystem is not available after making configuration changes in HII. * Fixed an issue where error was observed while selecting edit SmartCache Logical drive option when SmartCache logical drive is in Degraded mode. - Added support for DMTF PLDM Monitoring and Control for enhanced thermal monitoring * Added support for DMTF PLDM Redfish Device Enablement for Redfish Storage, StorageController, Port, Drive, Volume, & CollectionCapabilities * Added support for DMTF PLDM Redfish Device Enablement for Volume POST & DEL operations * Added support for DMTF Redfish StorageDevice.1.0.1 Events * Added support in firmware to enable logical drive transformation without backup power source on the controllers supporting data preservation. * Added support to return NCQ Priority Information for SATA drive to host. * Added support to blink the drive Predictive Failure (PF) LED during Predictive Spare Rebuilding (PSR) for drives that can be safely removed and replaced without causing a logical drive failure. * Added support to configure default setting for the drive write cache. - Fixed a rare problem where backup power status was incorrectly reporting Charging instead of Failed. * Fixed an issue where obsoleted SCSI pass through command fails. * Loss of redundant path message is incorrectly reported on logical drive failure with single domain configuration. * Fixed an issue where SmartPath may not be used after LUN Reset * Fixed a potential controller lockup 0x1BC0 during write then read I/O with drive URE's. * Fixed an issue that Apollo 4200 Gen10 plus LFF expander backplanes are not discovered by controller. * Fixed an issue that range locked SED failed with reason error erasing RAID metadata during reboot and remains failed after clear configuration. * Fixed an issue where the file system may read incorrect data from a degraded RAID 5 or 6 logical drive. * Fixed an issue where the file system or application may read incorrect data when a backup power source is discharged completely, and system power loss occurs during a transformation. * Fixed an issue where the drive Fault LED is not turned ON when firmware fails a bad HBA drive connected to an expander during device discovery or hot-plug. * Fixed an issue of auto-rebuild not starting if two drives fail at the same time on a RAID10 or RAID6 logical drive having only one "Auto-Replace Drives" spare drive. * Fixed an issue where the drive Fault LED is turned ON for a few seconds when multiple configured drives are hot removed from a SES enclosure and then hot added * Fixed an issue where rebuild did not start after multiple iterations of drive failures. * Fixed an issue where the controller might fail to discover devices after a cable is hot-added. * Fixed a potential problem of inability to delete a SmartCache write-back logical drive. * Fixed an issue where 0x1789 POST message error code is displayed as healthy and there is no information in HII when all logical drives in the controller are offline. * Fixed an issue where the last logical drive in an array cannot be deleted in UEFI configuration tool. * Fixed an issue where build method is not listed for RAID 6 array creation in UEFI configuration tool. - Fixed a rare problem where backup power status was incorrectly reporting Charging instead of Failed. * Fixed an issue where obsoleted SCSI pass through command fails. * Loss of redundant path message is incorrectly reported on logical drive failure with single domain configuration. * Fixed an issue where SmartPath may not be used after LUN Reset * Fixed a potential controller lockup 0x1BC0 during write then read I/O with drive URE's. * Fixed an issue that Apollo 4200 Gen10 plus LFF expander backplanes are not discovered by controller. * Fixed an issue that range locked SED failed with reason error erasing RAID metadata during reboot and remains failed after clear configuration. * Fixed an issue where the file system may read incorrect data from a degraded RAID 5 or 6 logical drive. * Fixed an issue where the file system or application may read incorrect data when a backup power source is discharged completely, and system power loss occurs during a transformation. * Fixed an issue where the drive Fault LED is not turned ON when firmware fails a bad HBA drive connected to an expander during device discovery or hot-plug. * Fixed an issue of auto-rebuild not starting if two drives fail at the same time on a RAID10 or RAID6 logical drive having only one "Auto-Replace Drives" spare drive. * Fixed an issue where the drive Fault LED is turned ON for a few seconds when multiple configured drives are hot removed from a SES enclosure and then hot added * Fixed an issue where rebuild did not start after multiple iterations of drive failures. * Fixed an issue where the controller might fail to discover devices after a cable is hot-added. * Fixed a potential problem of inability to delete a SmartCache write-back logical drive. * Fixed an issue where 0x1789 POST message error code is displayed as healthy and there is no information in HII when all logical drives in the controller are offline. * Fixed an issue where the last logical drive in an array cannot be deleted in UEFI configuration tool. * Fixed an issue where build method is not listed for RAID 6 array creation in UEFI configuration tool. - *Important Notes:** This revision has mitigated security vulnerability CVE-2018-3643 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3643) and CVE-2018-3655 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3655). It is anticipated that details regarding these security vulnerabilities will be published to these links on September 11,2018. These security vulnerabilities are not unique to HPE servers. **Firmware Dependencies:** HPE Gen10 system ROM version 1.26 or later HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later **Problems Fixed:** This revision has mitigated security vulnerability CVE-2018-3643 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3643) and CVE-2018-3655 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3655). It is anticipated that details regarding these security vulnerabilities will be published to these links on September 11, 2018. These security vulnerabilities are not unique to HPE servers. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** Added support for Intel Xeon Scalable Performance 3200, 4200, 5200, 6200 and 8200 series processors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an intermittent issue where an optional PCIe device may not properly report its thermal data or other telemetry data as seen through the Integrated Lights-Out (iLO) interface. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This image contains the latest Intel Server Platform Services (SPS) Firmware which contains mitigations for a variety of security vulnerabilities. The following vulnerabilities have been addressed in this SPS release: CVE-2019-11090 and CVE-2019-11109. These issues are not unique to HPE servers. **Known Issues:** None - This image contains the latest Intel Server Platform Services (SPS) Firmware which contains mitigations for security vulnerability CVE-2020-0545. This issue is not unique to HPE Servers. - This image contains the latest Intel Server Platform Services (SPS) Firmware which contains mitigations for security vulnerability CVE-2020-0545. This issue is not unique to HPE Servers. - *Important Notes:** The Ver. 04.01.04.381(B) flash component contains an updated flash image. The actual firmware is exactly the same as was delivered with the original ver. 04.01.04.381 flash component. The previous flash component had an issue that caused flashing to intermittently fail. It is not necessary to upgrade with Revision B if a previous component Revision was successfully used to upgrade the firmware to version 04.01.04.381 or for systems that originally shipped with version 04.01.04.381 firmware. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where systems configured with older versions of the Server Platform Services (SPS) Firmware, such as version 04.00.00.288 or older, may become inoperable after flashing to SPS firmware version 04.01.04.381. This releases contains an updated flash component for SPS Firmware 04.01.04.381 which allows direct flashing from older firmware versions to the latest. **Known Issues:** None - *Important Notes:** This version of the Server Platform Services (SPS) Firmware contains updates aligned with the Intel Product Update (IPU) version IPU.2020.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the Server Platform Services Firmware provides mitigations for security vulnerability documented as CVE-2020-8755. This security vulnerability is documented in Intel Security Advisory INTEL-SA-00391. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the Server Platform Services (SPS) Firmware contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This version of the Server Platform Services (SPS) Firmware addresses an issue where not all PCIe devices will be managed properly by the system when there are more than 16 PCIe devices present in the platform. This would include PCIe devices in PCIe slots or NVMe drives. This issue would typically manifest itself as iLO Firmware not properly reporting thermals from a device when a server was in this heavily loaded configuration. **Known Issues:** None - - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** Added support for Intel Optane Persistent Memory. **Known Issues:** None - - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where uncorrectable memory errors are seen when running memory intensive workloads with LRDIMMs. Address an issue that could cause a slight degradation of performance. Resolved an issue with NVMe hot add or removal which may result in an unrecoverable I/O error reported in the Integrated Management Log (IML). Addressed an issue where the UEFI Shell command GetPciRom may not display information for PCI expansion device drivers. Addressed an extremely intermittent issue with AMD Epyc 1st Gen processors that would cause a critical error and system reset. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) for dual bifurcation (quadfurcation) of PCIe Adapters to the Advanced PCIe Configuration Options. This option will allow a x16 PCIe device to be bifurcated into four x4 devices. This option would only be used for PCIe Adapters that support his level of bifurcation. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may hang during boot up after a warm reset from the OS. Addressed an issue where the Advanced Options for Secure Boot failed to export all keys. Addressed an issue where One-Button Secure Erase was not completed when SmartRAID SW RAID support is enabled. **Known Issues:** None - Added Boot time IPMI Watchdog timer support. Updated and improved thermal definition. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) in cases when they should not be logged. The system monitors corrected errors and notifies the user when action is required due to an increased risk of an Uncorrected Memory Error. Corrected Memory errors are a normal and expected occurrence and do not always indicate a higher risk of an Uncorrected Memory Error. Previous revisions of the System ROM were incorrectly logging Corrected Memory Error Threshold Events to the IML when action should not have been required, resulting in unnecessary scheduled downtime to replace DIMMs. It is recommended that the System ROM be updated to this version before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in system information page. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1021) which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12954, CVE-2020-12961, CVE-2021-26331, CVE-2021-26335, CVE-2021-26315, CVE-2020-12946, CVE-2020-12951. CVE-2021-26336, CVE-2021-26337, CVE-2021-26338, CVE-2021-26320, CVE-2020-12944, CVE-2020-12988, CVE-2021-26329, CVE-2021-26330, CVE-2021-26321, CVE-2021-26323, CVE-2021-26325, CVE-2021-26326, CVE-2021-26322, CVE-2021-26327, and CVE-2021-26312. These issues are not unique to HPE servers. Addressed an issue where in the OS does not display the true CPU Max Core Frequency. Addressed an issue with AMD EPYC 1st Generation processors that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) in cases when they should not be logged. The system monitors corrected errors and notifies the user when action is required due to an increased risk of an Uncorrected Memory Error. Corrected Memory errors are a normal and expected occurrence and do not always indicate a higher risk of an Uncorrected Memory Error. Previous revisions of the System ROM were incorrectly logging Corrected Memory Error Threshold Events to the IML when action should not have been required, resulting in unnecessary scheduled downtime to replace DIMMs. It is recommended that the System ROM be updated to this version before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where RAID volumes will be lost when using the "Restore Default Manufacturing Settings" feature. Addressed an issue where if the Administrator Password and Power-On Password are set, after clearing power-on password, Administrator Password is also cleared. Addressed and issue where a system with Microsoft BitLocker enabled may incorrectly and intermittently prompt the user to unlock drives after a graceful OS reboot. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where uncorrectable memory errors are seen when running memory intensive workloads with LRDIMMs. Address an issue that could cause a slight degradation of performance. Resolved an issue with NVMe hot add or removal which may result in an unrecoverable I/O error reported in the Integrated Management Log (IML). Addressed an issue where the UEFI Shell command GetPciRom may not display information for PCI expansion device drivers. Addressed an extremely intermittent issue with AMD Epyc 1st Gen processors that would cause a critical error and system reset. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) for dual bifurcation (quadfurcation) of PCIe Adapters to the Advanced PCIe Configuration Options. This option will allow a x16 PCIe device to be bifurcated into four x4 devices. This option would only be used for PCIe Adapters that support his level of bifurcation. Added support to increase the maximum amount of system memory to 8TB. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed a rare issue where the system may fail to boot after a warm reset. Addressed an issue where the Advanced Options for Secure Boot failed to export all keys. Addressed an issue where One-Button Secure Erase was not completed when SmartRAID SW RAID support is enabled. **Known Issues:** None - Added Boot time IPMI Watchdog timer support. Updated and improved thermal definition. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) in cases when they should not be logged. The system monitors corrected errors and notifies the user when action is required due to an increased risk of an Uncorrected Memory Error. Corrected Memory errors are a normal and expected occurrence and do not always indicate a higher risk of an Uncorrected Memory Error. Previous revisions of the System ROM were incorrectly logging Corrected Memory Error Threshold Events to the IML when action should not have been required, resulting in unnecessary scheduled downtime to replace DIMMs. It is recommended that the System ROM be updated to this version before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in system information page. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1021) which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12954, CVE-2020-12961, CVE-2021-26331, CVE-2021-26335, CVE-2021-26315, CVE-2020-12946, CVE-2020-12951. CVE-2021-26336, CVE-2021-26337, CVE-2021-26338, CVE-2021-26320, CVE-2020-12944, CVE-2020-12988, CVE-2021-26329, CVE-2021-26330, CVE-2021-26321, CVE-2021-26323, CVE-2021-26325, CVE-2021-26326, CVE-2021-26322, CVE-2021-26327, and CVE-2021-26312. These issues are not unique to HPE servers. Addressed an issue where in the OS does not display the true CPU Max Core Frequency. Addressed an issue with AMD EPYC 1st Generation processors that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) in cases when they should not be logged. The system monitors corrected errors and notifies the user when action is required due to an increased risk of an Uncorrected Memory Error. Corrected Memory errors are a normal and expected occurrence and do not always indicate a higher risk of an Uncorrected Memory Error. Previous revisions of the System ROM were incorrectly logging Corrected Memory Error Threshold Events to the IML when action should not have been required, resulting in unnecessary scheduled downtime to replace DIMMs. It is recommended that the System ROM be updated to this version before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where RAID volumes will be lost when using the "Restore Default Manufacturing Settings" feature. Addressed an issue where if the Administrator Password and Power-On Password are set, after clearing power-on password, Administrator Password is also cleared. Addressed and issue where a system with Microsoft BitLocker enabled may incorrectly and intermittently prompt the user to unlock drives after a graceful OS reboot. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the fan runs at a higher than expected speed after upgrading the firmware of HPE Smart Array E208i or E408i to version 3.0. **Known Issues:** None - Updated HPE Smart Array SR100i Gen10 Plus SW RAID UEFI driver to version v3.3.14.1004. Added a new BIOS/Platform Configuration (RBSU) option for No-Execute Protection. This option allows disabling processor No-Execution protection to work around an issue where the system hangs with a blank screen when entering Recovery mode with Windows Server 2016. This issue is not unique to HPE servers, and disabling No-Execute protection is required on any system that defaults to No-Execute enabled to address this issue. Updated OpenSSL module to version 1.1.1h. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Address an issue where the Industry Standard SMBIOS Type 17 tables will indicate the Manufacture ID as "Unknown" for LRDIMMs. Addressed a rare issue where the time zone cannot be changed successfully in BIOS/Platform Configuration (RBSU). Addressed an issue preventing array creation on HPE Smart Array SR100i Gen10 Plus SW RAID through the Redfish API. Addressed an issue where the system may become unresponsive during POST when the server is configured with 24 Xilinx NVMe drives. Addressed an issue where the AMD Fmax Boost value is inconsistent between BIOS/Platform Configuration (RBSU) and Redfish API. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) in cases when they should not be logged. The system monitors corrected errors and notifies the user when action is required due to an increased risk of an Uncorrected Memory Error. Corrected Memory errors are a normal and expected occurrence and do not always indicate a higher risk of an Uncorrected Memory Error. Previous revisions of the System ROM were incorrectly logging Corrected Memory Error Threshold Events to the IML when action should not have been required, resulting in unnecessary scheduled downtime to replace DIMMs. It is recommended that the System ROM be updated to this version before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - Added support for Microsoft Windows Server 2022. Windows Server 2022 adds a new security feature called Secured-core. Secured-core is only supported on AMD Gen 3 EPYC processors. Secured-core servers use a combination of hardware features, firmware enablement and Windows Server operating system capabilities to provide protection against malware and rootkit security exploits. Added a new BIOS/Platform Configuration (RBSU) option for Microsoft Secured- core Support. Enabling this setting makes the following policy changes and configures the corresponding options: AMD I/O Virtualization Technology enabled, TPM visible, DMA remapping enabled, AMD DRTM enabled, and Secure Boot enabled. Disabling any of these features while Secured-core is enabled can prevent Secured-core from working properly. Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in pre-boot System Utilities System Information Page. Addressed an issue with hot-adding drives after removing them from Bay 1 when using the HPE SR100i Software RAID solution for systems and the UBM4 2SFF backplane. In this situation the HDD cannot be detected after re-insertion. Addressed an issue with hot adding NVMe drives with VMware ESXi when a drive bay is empty at boot up. Drive may fail to be added. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option for Dynamic PCIe Rate Change. This option should be enabled for certain PCIe devices that change their advertised speed during training. The option is disabled by default, and should only be enabled if the system is configured with a device which is training at a less than advertised speed. Added a new BIOS/Platform Configuration (RBSU) option for MCTP Broadcast Support. This option is used to control the PCIe Management Component Transport Protocol (MCTP) support for a given slot. This option can be used to disable MCTP support to a given PCIe endpoint that may not properly support this protocol. It is recommended that this option remain enabled for full system functionality. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1021) which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12954, CVE-2020-12961, CVE-2021-26331, CVE-2021-26335, CVE-2021-26315, CVE-2020-12946, CVE-2020-12951. CVE-2021-26336, CVE-2021-26337, CVE-2021-26338, CVE-2021-26320, CVE-2020-12944, CVE-2020-12988, CVE-2021-26329, CVE-2021-26330, CVE-2021-26321, CVE-2021-26323, CVE-2021-26325, CVE-2021-26326, CVE-2021-26322, CVE-2021-26327, and CVE-2021-26312. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1007) which provides mitigation for AMD vulnerability with PSP Code Execution documented by AMD. This issue is not unique to HPE servers. Addressed an issue where in the OS does not display the true CPU Max Core Frequency. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Correctable Memory Error Threshold Events on DIMM slots 9/10/13/14/15/16 with AMD EPYC 7773/7573/7473/7373 CPU SKUs not being reported in the IML (Integrated Management Log). Addressed an issue where RAID volumes will be lost when using the "Restore Default Manufacturing Settings" feature. Addressed an issue where if the Administrator Password and Power-On Password are set, after clearing power-on password, Administrator Password is also cleared. Addressed and issue where a system with Microsoft BitLocker enabled may incorrectly and intermittently prompt the user to unlock drives after a graceful OS reboot. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the fan runs at a higher than expected speed after upgrading the firmware of HPE Smart Array E208i or E408i to version 3.0. **Known Issues:** None - Updated HPE Smart Array SR100i Gen10 Plus SW RAID UEFI driver to version v3.3.14.1004. Added a new BIOS/Platform Configuration (RBSU) option for No-Execute Protection. This option allows disabling processor No-Execution protection to work around an issue where the system hangs with a blank screen when entering Recovery mode with Windows Server 2016. This issue is not unique to HPE servers, and disabling No-Execute protection is required on any system that defaults to No-Execute enabled to address this issue. Updated OpenSSL module to version 1.1.1h. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Address an issue where the Industry Standard SMBIOS Type 17 tables will indicate the Manufacture ID as "Unknown" for LRDIMMs. Addressed a rare issue where the time zone cannot be changed successfully in BIOS/Platform Configuration (RBSU). Addressed an issue preventing array creation on HPE Smart Array SR100i Gen10 Plus SW RAID through the Redfish API. Addressed an issue where the system may become unresponsive during POST when the server is configured with 24 Xilinx NVMe drives. Addressed an issue where the AMD Fmax Boost value is inconsistent between BIOS/Platform Configuration (RBSU) and Redfish API. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) in cases when they should not be logged. The system monitors corrected errors and notifies the user when action is required due to an increased risk of an Uncorrected Memory Error. Corrected Memory errors are a normal and expected occurrence and do not always indicate a higher risk of an Uncorrected Memory Error. Previous revisions of the System ROM were incorrectly logging Corrected Memory Error Threshold Events to the IML when action should not have been required, resulting in unnecessary scheduled downtime to replace DIMMs. It is recommended that the System ROM be updated to this version before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - Added support for Microsoft Windows Server 2022. Windows Server 2022 adds a new security feature called Secured-core. Secured-core is only supported on AMD Gen 3 EPYC processors. Secured-core servers use a combination of hardware features, firmware enablement and Windows Server operating system capabilities to provide protection against malware and rootkit security exploits. Added a new BIOS/Platform Configuration (RBSU) option for Microsoft Secured- core Support. Enabling this setting makes the following policy changes and configures the corresponding options: AMD I/O Virtualization Technology enabled, TPM visible, DMA remapping enabled, AMD DRTM enabled, and Secure Boot enabled. Disabling any of these features while Secured-core is enabled can prevent Secured-core from working properly. Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in pre-boot System Utilities System Information Page. Addressed an issue with hot-adding drives after removing them from Bay 1 when using the HPE SR100i Software RAID solution for systems and the UBM4 2SFF backplane. In this situation the HDD cannot be detected after re-insertion. Addressed an issue with hot adding NVMe drives with VMware ESXi when a drive bay is empty at boot up. Drive may fail to be added. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option for Dynamic PCIe Rate Change. This option should be enabled for certain PCIe devices that change their advertised speed during training. The option is disabled by default, and should only be enabled if the system is configured with a device which is training at a less than advertised speed. Added a new BIOS/Platform Configuration (RBSU) option for MCTP Broadcast Support. This option is used to control the PCIe Management Component Transport Protocol (MCTP) support for a given slot. This option can be used to disable MCTP support to a given PCIe endpoint that may not properly support this protocol. It is recommended that this option remain enabled for full system functionality. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1021) which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12954, CVE-2020-12961, CVE-2021-26331, CVE-2021-26335, CVE-2021-26315, CVE-2020-12946, CVE-2020-12951. CVE-2021-26336, CVE-2021-26337, CVE-2021-26338, CVE-2021-26320, CVE-2020-12944, CVE-2020-12988, CVE-2021-26329, CVE-2021-26330, CVE-2021-26321, CVE-2021-26323, CVE-2021-26325, CVE-2021-26326, CVE-2021-26322, CVE-2021-26327, and CVE-2021-26312. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1007) which provides mitigation for AMD vulnerability with PSP Code Execution documented by AMD. This issue is not unique to HPE servers. Addressed an issue where in the OS does not display the true CPU Max Core Frequency. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Correctable Memory Error Threshold Events on DIMM slots 9/10/13/14/15/16 with AMD EPYC 7773/7573/7473/7373 CPU SKUs not being reported in the IML (Integrated Management Log). Addressed an issue where RAID volumes will be lost when using the "Restore Default Manufacturing Settings" feature. Addressed an issue where if the Administrator Password and Power-On Password are set, after clearing power-on password, Administrator Password is also cleared. Addressed and issue where a system with Microsoft BitLocker enabled may incorrectly and intermittently prompt the user to unlock drives after a graceful OS reboot. **Known Issues:** None - Added support for AMD EPYC 7003 processors. Added support for BIOS switches to control RAS (handles by OS/Firmware first). Added support for OCP 3.0 NIC. - *Important Notes:** None **Firmware Dependencies:** System Programable Logic CPLD version 34 **Problems Fixed:** Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** System Programable Logic CPLD version 34 **Enhancements/New Features:** Added support to the BIOS/Platform Configuration (RBSU) Time Zones to add Dublin/London (UTC+1). This support also requires the latest version of iLO Firmware, version 2.40 or later. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** System Programable Logic CPLD version 38 **Enhancements/New Features:** Added support for the 4SFF 24G x4NVMe/SAS UBM1 Storage Controller backplane. **Known Issues:** None - \- Added support for Microsoft Windows Server 2022. Windows Server 2022 adds a new security feature called Secured-core. Secured-core is only supported on AMD Gen 3 EPYC processors. Secured-core servers use a combination of hardware features, firmware enablement and Windows Server operating system capabilities to provide protection against malware and rootkit security exploits. \- Added a new BIOS/Platform Configuration (RBSU) option for Microsoft Secured-core Support. Enabling this setting makes the following policy changes and configures the corresponding options: AMD I/O Virtualization Technology enabled, TPM visible, DMA remapping enabled, AMD DRTM enabled, and Secure Boot enabled. Disabling any of these features while Secured-core is enabled can prevent Secured-core from working properly. \- Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. \- Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. \- Added support for the 4SFF 24G x4NVMe/SAS UBM1 Storage Controller backplane. \- Added an enhancement to existing processor current monitoring in order to avoid potential overcurrent shutdowns. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** \- This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. \- Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in pre-boot System Utilities System Information Page. \- Addressed an issue with hot-adding drives after removing them from Bay 1 when using the HPE SR100i Software RAID solution for systems and the UBM4 2SFF backplane. In this situation the HDD cannot be detected after re-insertion. \- Addressed an issue with hot adding a NVMe drives with VMware ESXi when a drive bay is empty at boot up. Drive may fail to be added. **Known Issues:** None - \- Added a new BIOS/Platform Configuration (RBSU) option for Dynamic PCIe Rate Change. This option should be enabled for certain PCIe devices that change their advertised speed during training. The option is disabled by default, and should only be enabled if the system is configured with a device which is training at a less than advertised speed. \- Added a new BIOS/Platform Configuration (RBSU) option for MCTP Broadcast Support. This option is used to control the PCIe Management Component Transport Protocol (MCTP) support for a given slot. This option can be used to disable MCTP support to a given PCIe endpoint that may not properly support this protocol. It is recommended that this option remain enabled for full system functionality. \- Added support for reporting CPU PPIN/Serial Number in SMBIOS. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** \- This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1021) which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12954, CVE-2020-12961, CVE-2021-26331, CVE-2021-26335, CVE-2021-26315, CVE-2020-12946, CVE-2020-12951. CVE-2021-26336, CVE-2021-26337, CVE-2021-26338, CVE-2021-26320, CVE-2020-12944, CVE-2020-12988, CVE-2021-26329, CVE-2021-26330, CVE-2021-26321, CVE-2021-26323, CVE-2021-26325, CVE-2021-26326, CVE-2021-26322, CVE-2021-26327, and CVE-2021-26312. These issues are not unique to HPE servers. \- This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1007) which provides mitigation for AMD vulnerability with PSP Code Execution documented by AMD. This issue is not unique to HPE servers. \- Addressed an issue where in the OS does not display the true CPU Max Core Frequency. \- Addressed an issue where BootMode and UefiOptimizedBoot settings are not accessible through Redfish on class 3 systems. \- Addressed an issue where the controller's name is missing in BIOS/Platform Configuration (RBSU) and One Time Boot Menu if HPE SR416i-a x16 Lanes 4GB Cache NVMe/SAS 24G Gen10 Plus Controller or HPE SR932i-p x32 Lanes 8GB Wide Cache NVMe/SAS 24G PCIe4 x16 Gen10 Plus Controller is installed. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** \- Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Correctable Memory Error Threshold Events on DIMM slots 9/10/13/14/15/16 with AMD EPYC 7773/7573/7473/7373 CPU SKUs not being reported in the IML (Integrated Management Log). Addressed an issue where RAID volumes will be lost when using the "Restore Default Manufacturing Settings" feature. Addressed an issue where if the Administrator Password and Power-On Password are set, after clearing power-on password, Administrator Password is also cleared. Addressed and issue where a system with Microsoft BitLocker enabled may incorrectly and intermittently prompt the user to unlock drives after a graceful OS reboot. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - Added support for AMD EPYC 7003 processors. Added support for Direct Liquid Cooling solution. Added support to the BIOS/Platform Configuration (RBSU) Time Zones to add Dublin/London (UTC+1). This support also requires the latest version of iLO Firmware, version 2.40 or later. Added a new BIOS/Platform Configuration (RBSU) for Platform RAS Policy to control the Platform Resiliency and Serviceability (RAS) policy. This option controls whether platform firmware or the operating system has control of corrected error handling and reporting. - *Important Notes:** None **Firmware Dependencies:** HPE ProLiant XL675d Gen10Plus CPLD version 0F HPE Apollo 6500 Gen10 Plus Chassis CPLD version 0909 **Problems Fixed:** Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. **Known Issues:** None - \- Added support for Microsoft Windows Server 2022. Windows Server 2022 adds a new security feature called Secured-core. Secured-core is only supported on AMD Gen 3 EPYC processors. Secured-core servers use a combination of hardware features, firmware enablement and Windows Server operating system capabilities to provide protection against malware and rootkit security exploits. \- Added a new BIOS/Platform Configuration (RBSU) option for Microsoft Secured-core Support. Enabling this setting makes the following policy changes and configures the corresponding options: AMD I/O Virtualization Technology enabled, TPM visible, DMA remapping enabled, AMD DRTM enabled, and Secure Boot enabled. Disabling any of these features while Secured-core is enabled can prevent Secured-core from working properly. \- Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. \- Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. \- Added an enhancement to existing processor current monitoring in order to avoid potential overcurrent shutdowns. - *Important Notes:** **Firmware Dependencies:** None **Problems Fixed:** \- This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. \- Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in pre-boot System Utilities System Information Page. \- Addressed an issue with hot-adding drives after removing them from Bay 1 when using the HPE SR100i Software RAID solution for systems and the UBM4 2SFF backplane. In this situation the HDD cannot be detected after re-insertion. \- Addressed an issue with hot adding a NVMe drives with VMware ESXi when a drive bay is empty at boot up. Drive may fail to be added. **Known Issues:** None - \- Added a new BIOS/Platform Configuration (RBSU) option for Dynamic PCIe Rate Change. This option should be enabled for certain PCIe devices that change their advertised speed during training. The option is disabled by default, and should only be enabled if the system is configured with a device which is training at a less than advertised speed. \- Added a new BIOS/Platform Configuration (RBSU) option for MCTP Broadcast Support. This option is used to control the PCIe Management Component Transport Protocol (MCTP) support for a given slot. This option can be used to disable MCTP support to a given PCIe endpoint that may not properly support this protocol. It is recommended that this option remain enabled for full system functionality. \- Added support for reporting CPU PPIN/Serial Number in SMBIOS. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** \- This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1021) which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12954, CVE-2020-12961, CVE-2021-26331, CVE-2021-26335, CVE-2021-26315, CVE-2020-12946, CVE-2020-12951. CVE-2021-26336, CVE-2021-26337, CVE-2021-26338, CVE-2021-26320, CVE-2020-12944, CVE-2020-12988, CVE-2021-26329, CVE-2021-26330, CVE-2021-26321, CVE-2021-26323, CVE-2021-26325, CVE-2021-26326, CVE-2021-26322, CVE-2021-26327, and CVE-2021-26312. These issues are not unique to HPE servers. \- This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1007) which provides mitigation for AMD vulnerability with PSP Code Execution documented by AMD. This issue is not unique to HPE servers. \- Addressed an issue where in the OS does not display the true CPU Max Core Frequency. \- Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) in cases when they should not be logged. The system monitors corrected errors and notifies the user when action is required due to an increased risk of an Uncorrected Memory Error. Corrected Memory errors are a normal and expected occurrence and do not always indicate a higher risk of an Uncorrected Memory Error. Previous revisions of the System ROM were incorrectly logging Corrected Memory Error Threshold Events to the IML when action should not have been required, resulting in unnecessary scheduled downtime to replace DIMMs. It is recommended that the System ROM be updated to this version before replacing DIMMs due to Corrected Memory Error Threshold Events. \- Addressed an issue where BootMode and UefiOptimizedBoot settings are not accessible through Redfish on class 3 systems. \- Addressed an issue where the controller's name is missing in BIOS/Platform Configuration (RBSU) and One Time Boot Menu if HPE SR416i-a x16 Lanes 4GB Cache NVMe/SAS 24G Gen10 Plus Controller or HPE SR932i-p x32 Lanes 8GB Wide Cache NVMe/SAS 24G PCIe4 x16 Gen10 Plus Controller is installed. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** \- Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Correctable Memory Error Threshold Events on DIMM slots 9/10/13/14/15/16 with AMD EPYC 7773/7573/7473/7373 CPU SKUs not being reported in the IML (Integrated Management Log). Addressed an issue where RAID volumes will be lost when using the "Restore Default Manufacturing Settings" feature. Addressed an issue where if the Administrator Password and Power-On Password are set, after clearing power-on password, Administrator Password is also cleared. Addressed and issue where a system with Microsoft BitLocker enabled may incorrectly and intermittently prompt the user to unlock drives after a graceful OS reboot. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - Added support for AMD EPYC 7003 processors. Added support to the BIOS/Platform Configuration (RBSU) Time Zones to add Dublin/London (UTC+1). This support also requires the latest version of iLO Firmware, version 2.40 or later. Added a new BIOS/Platform Configuration (RBSU) for Platform RAS Policy to control the Platform Resiliency and Serviceability (RAS) policy. This option controls whether platform firmware or the operating system has control of corrected error handling and reporting. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where PCI slot information will not be reported in SMBIOS when the HPE XL645d Gen10 Plus 12Gb NVMe 2-port Adapter is installed. **Known Issues:** None - \- Added support for Microsoft Windows Server 2022. Windows Server 2022 adds a new security feature called Secured-core. Secured-core is only supported on AMD Gen 3 EPYC processors. Secured-core servers use a combination of hardware features, firmware enablement and Windows Server operating system capabilities to provide protection against malware and rootkit security exploits. \- Added a new BIOS/Platform Configuration (RBSU) option for Microsoft Secured-core Support. Enabling this setting makes the following policy changes and configures the corresponding options: AMD I/O Virtualization Technology enabled, TPM visible, DMA remapping enabled, AMD DRTM enabled, and Secure Boot enabled. Disabling any of these features while Secured-core is enabled can prevent Secured-core from working properly. \- Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. \- Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. \- Added an enhancement to existing processor current monitoring in order to avoid potential overcurrent shutdowns. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** \- This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. \- Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in pre-boot System Utilities System Information Page. \- Addressed an issue with hot-adding drives after removing them from Bay 1 when using the HPE SR100i Software RAID solution for systems and the UBM4 2SFF backplane. In this situation the HDD cannot be detected after re-insertion. \- Addressed an issue with hot adding a NVMe drives with VMware ESXi when a drive bay is empty at boot up. Drive may fail to be added. **Known Issues:** None - \- Added a new BIOS/Platform Configuration (RBSU) option for Dynamic PCIe Rate Change. This option should be enabled for certain PCIe devices that change their advertised speed during training. The option is disabled by default, and should only be enabled if the system is configured with a device which is training at a less than advertised speed. \- Added a new BIOS/Platform Configuration (RBSU) option for MCTP Broadcast Support. This option is used to control the PCIe Management Component Transport Protocol (MCTP) support for a given slot. This option can be used to disable MCTP support to a given PCIe endpoint that may not properly support this protocol. It is recommended that this option remain enabled for full system functionality. \- Added support for reporting CPU PPIN/Serial Number in SMBIOS. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** \- This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1021) which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12954, CVE-2020-12961, CVE-2021-26331, CVE-2021-26335, CVE-2021-26315, CVE-2020-12946, CVE-2020-12951. CVE-2021-26336, CVE-2021-26337, CVE-2021-26338, CVE-2021-26320, CVE-2020-12944, CVE-2020-12988, CVE-2021-26329, CVE-2021-26330, CVE-2021-26321, CVE-2021-26323, CVE-2021-26325, CVE-2021-26326, CVE-2021-26322, CVE-2021-26327, and CVE-2021-26312. These issues are not unique to HPE servers. \- This revision of the System ROM includes the latest revision of AMD security patch (AMD-SN-1007) which provides mitigation for AMD vulnerability with PSP Code Execution documented by AMD. This issue is not unique to HPE servers. \- Addressed an issue where in the OS does not display the true CPU Max Core Frequency. \- Addressed an issue where the system would encounter an unexpected long pause during early POST during a warm boot. \- Addressed an issue where BootMode and UefiOptimizedBoot settings are not accessible through Redfish on class 3 systems. \- Addressed an issue where the controller's name is missing in BIOS/Platform Configuration (RBSU) and One Time Boot Menu if HPE SR416i-a x16 Lanes 4GB Cache NVMe/SAS 24G Gen10 Plus Controller or HPE SR932i-p x32 Lanes 8GB Wide Cache NVMe/SAS 24G PCIe4 x16 Gen10 Plus Controller is installed. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** \- Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Correctable Memory Error Threshold Events on DIMM slots 9/10/13/14/15/16 with AMD EPYC 7773/7573/7473/7373 CPU SKUs not being reported in the IML (Integrated Management Log). Addressed an issue where RAID volumes will be lost when using the "Restore Default Manufacturing Settings" feature. Addressed an issue where if the Administrator Password and Power-On Password are set, after clearing power-on password, Administrator Password is also cleared. Addressed and issue where a system with Microsoft BitLocker enabled may incorrectly and intermittently prompt the user to unlock drives after a graceful OS reboot. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092, CVE-2021-0093, CVE-2021-0144. These issues are not unique to HPE servers. This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092, CVE-2021-0093, CVE-2021-0144. These issues are not unique to HPE servers. This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** The 2.54_09-03-2021(B) flash component contains the 2.54 ROM flash image. The previous flash component had an issue that caused system upgrade to version 2.52 instead of version 2.54. For any systems where the previous flash component was utilized, the system should be updated again with this flash component to properly install the version 2.54 System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092, CVE-2021-0093, CVE-2021-0144. These issues are not unique to HPE servers. This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092, CVE-2021-0093, CVE-2021-0144. These issues are not unique to HPE servers. This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092, CVE-2021-0093, CVE-2021-0144. These issues are not unique to HPE servers. This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092. These issues are not unique to HPE servers. CVE-2021-0093, CVE-2021-0144 This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the IPMI Watchdog Timer stops after a cold boot with IPMI watch dog timer enabled in RBSU **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092. These issues are not unique to HPE servers. CVE-2021-0093, CVE-2021-0144 This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the IPMI Watchdog Timer stops after a cold boot with IPMI watch dog timer enabled in RBSU **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092, CVE-2021-0093, CVE-2021-0144. These issues are not unique to HPE servers. This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092, CVE-2021-0093, CVE-2021-0144. These issues are not unique to HPE servers. This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092, CVE-2021-0093, CVE-2021-0144. These issues are not unique to HPE servers. This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Memory Options called Refresh Watermarks. When selecting the Low Watermark setting, the memory controller will help reduce susceptibility to a DDR4 RowHammer attack. It is expected that a memory performance impact will be seen when enabling the Low Watermark setting. The default operation of the system has not changed and customers wanting to provide additional RowHammer protection should enable this setting. Added support to BIOS/Platform Configuration (RBSU) to allow importing and exporting Secure Boot signature lists as a signed binary file. This is useful to import the Microsoft revocation list binary file into the Secure Boot DBX as found on the UEFI forum at https://uefi.org/revocationlistfile. Updated the System ROM support for One Button Secure Erase functionality with the latest HPE option devices. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2020.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-8696, CVE-2020-8694 and CVE-2020-8695. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00381 and INTEL-SA-00389. The Intel microcode patches included in this release are version 0x000000DE (CPUIDs 906ED, 906EC, 906EB and 906EA). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-0593. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. These issues are not unique to HPE servers. **Known Issues:** None - Updated the language translations (non-English modes) for System Utilities. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel sightings CVE-2020-24511 and CVE-2020-24512. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00464. The Intel microcode patches included in this release are version 0x000000EA (CPUID 906ED, CPUID 906EC, CPUID 906EB and CPUID 906EA). This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8670 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the System ROM contains the fix for the Hynix 16G DDR4 DIMM compatibility issue. Please see advisory: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00115788en_us. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where systems running System ROM 2.20 (or later) and configured with an Intel Xeon E-2224 CPU and Hynix 16G DDR4 DIMM may occasionally encounter the error message "Unknown Initialization Error" in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in system information page. Addressed an issue where a PCIe device or an NVMe M.2 device may not show up correctly in iLO 5 Device Inventory or storage page. **Known Issues:** None - Improved boot time by removing unneeded delay. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where High Precision Event Timer in Windows was not showing up in device manager. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel IPU 2021.2 which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in the CVE report site. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2 which provides mitigations for security vulnerabilities CVE-2021-0092, CVE-2021-0127, CVE-2021-0156 and CVE-2021-0157. These issues are not unique to HPE servers. Fixed an issue where system boot mode changed to Legacy mode from UEFI mode after IP flash complete and system may hang when entering IP after setting to UEFI mode. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2020.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-8696, CVE-2020-8694 and CVE-2020-8695. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00381 and INTEL-SA-00389. The Intel microcode patches included in this release are version 0x000000DE (CPUIDs 906ED, 906EC, 906EB and 906EA). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-0593. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. These issues are not unique to HPE servers. **Known Issues:** None - Updated the language translations (non-English modes) for System Utilities. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel sightings CVE-2020-24511 and CVE-2020-24512. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00464. The Intel microcode patches included in this release are version 0x000000EA (CPUID 906ED, CPUID 906EC, CPUID 906EB and CPUID 906EA). This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8670 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the System ROM contains the fix for the Hynix 16G DDR4 DIMM compatibility issue. Please see advisory: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00115788en_us. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where systems running System ROM 2.20 (or later) and configured with an Intel Xeon E-2224 CPU and Hynix 16G DDR4 DIMM may occasionally encounter the error message "Unknown Initialization Error" in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in system information page. **Known Issues:** None - *Important Notes:** Ver. 2.50_07-20-2021(B) contains updates to the firmware packaging and is functionally equivalent to ver. 2.50_07-20-2021. It is not necessary to upgrade with Revision B if a previous component revision was used to upgrade the firmware to version 2.50_07-20-2021. This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. Addressed an issue with Pensando Distributed Services Platform DSC-25 Enterprise 10/25Gb 2-port SFP28 Card missing in system information page. Addressed an issue where a PCIe device or an NVMe M.2 device may not show up correctly in iLO 5 Device Inventory or storage page. **Known Issues:** None - Improved boot time by removing unneeded delay. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where High Precision Event Timer in Windows was not showing up in device manager. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel IPU 2021.2 which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in the CVE report site. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2 which provides mitigations for security vulnerabilities CVE-2021-0092, CVE-2021-0127, CVE-2021-0156 and CVE-2021-0157. These issues are not unique to HPE servers. Fixed an issue where system boot mode changed to Legacy mode from UEFI mode after IP flash complete and system may hang when entering IP after setting to UEFI mode. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions. This may result in a machine check exception in Bank 3 with MSCOD = 0080 and MCACOD = 0400h, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). This issue only impacts 2nd generation Intel Xeon Scalable Performance processors. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception when high levels of posted interrupt traffic occurs on PCIe. This may result in a machine check exception in Bank 9, 10 or 11 with MSCOD = 000Ch, as logged in the Integrated Management Log (IML). The Intel microcode patches included in this release are versions 0x02006A09 (CPUID 50654), 0x04003005 (CPUID 50656) and 0x05003005 (CPUID 50657). As part of this change, a new BIOS/Platform Configuration (RBSU) option in Advanced Performance Options has been added to allow a customer to disable this mitigation. This issue is not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. Addressed an issue where the Extended Memory Test is not run when configured in BIOS/Platform Configuration (RBSU) to Enabled. Note that this option is Disabled by default. This issue was introduced in the v2.40 revision of the System ROM. Addressed an issue where the server system fans may run higher than anticipated when a server is configured with AHCI SATA drives. Addressed an issue where a bad LRDIMM memory device could be mapped out but was not properly reported in the Integrated Memory Log (IML). This issue only impacted systems configured with LRDIMMs. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Server Availability called IPMI Watchdog Timer. When enabled, the system will start an IPMI based watchdog timer during boot which can be used to protect against a boot hang or other unexpected system boot issue. It is the responsibility of the user to disable the IPMI watchdog timer once the operating system has booted. Failure to disable the timer can result in an unexpected server reset or shutdown. Added a new BIOS/Platform Configuration (RBSU) option to Server Security called UEFI Variable Access Firmware Control. This option, when enabled, can be used to block UEFI Variable writes, such as to the UEFI Boot Order, from the Operating System or a third-party utility. HPE recommends leaving this capability disabled unless the user specifically wants to prevent the operating system's normal operation of writing to UEFI Variables, which typically occur during OS install. Updated the BIOS TPM 1.2 support for Windows 2022. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. HPE recommends that customers using Intel Optane Persistent Memory update to this version of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may experience an Unexpected Shutdown or a Bank 4 or a Bank 6 Machine Check with Intel Optane DC Persistent Memory installed and configured for Memory Mode (2LM) or Mixed Mode. This issue only impacts systems configured with Intel Optane DC Persistent Memory in one of these modes. HPE recommends updating to this version of the System ROM for any customer using Intel Optane DC Persistent Memory in Memory Mode (2LM) or Mixed Mode. This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-24511. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x02006B06 (CPUID 50654) and 0x05003103 (CPUID 50567). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12358, CVE-2020-12360, and CVE-2020-24486. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel microcode which address various functional issues documented in the Intel Technical Specification update. These issues are documented as the EIBRS Guest/Host and REP MOVS* MCE on Memory Not Access Issue. These issues are not unique to HPE servers. Addressed an issue where the server may become unresponsive during POST or take an unexpected long time to complete POST when the RBSU Extended Memory Test option was enabled. Addressed an issue where the server was allowed to boot when mixed SKUs of Intel Xeon Scalable Processors are installed. The server should display an error message and halt boot in these configurations. Addressed an issue where the System ROM was logging a mismatched power supply condition with the latest version of the HPE Power Supplies. When this issue occurred, Dynamic Power Capping and High Efficiency Power Supply Mode were also disabled. To properly mitigate this issue, iLO Firmware version 2.50 or later is also needed. **Known Issues:** None - Added Custom time server PCI riser support. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the second port of HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544 FLR-QSFP Adapter shows "null string" in RBSU system information page. This revision of the System ROM includes the EDK2 patches which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. Addressed an issue where the memory channel numbering is incorrect for Correctable Memory Errors. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled after updating the System ROM to v2.50 or later. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-0562. The Intel microcode patch included in this release is version 0x05003208 (CPUID 50567). These issues impacts 2nd Generation Intel Xeon Scalable Processors. They does NOT impact 1st Generation Intel Xeon Scalable Processors. These issues are not unique to HPE servers. Addressed an issue in which a server may fail to boot and experience a Machine Check Exception indicating "x64 Exception type 0x12: An uncorrectable machine check exception had occurred on CPU1" when a Fastcom SuperFSCC/4 PCIe card is installed. Addressed an issue where servers with an HPE NS204i-p OS Boot Device may shutdown and log a "System Overheating" error message in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2. It provides BIOS mitigations for security vulnerabilities documented as INTEL- SA-00527 (2/8) for CVE-2021-0092. These issues are not unique to HPE servers. CVE-2021-0093, CVE-2021-0144 This revision of the System ROM includes Intel Platform Update 2021.2. It provides Authenticated Code Module (ACM) mitigations for security vulnerabilities documented as INTEL-SA-00527 (2/8) for CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124. These issues are not unique to HPE servers. Addressed an issue (SIK6906) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the IPMI Watchdog Timer stops after a cold boot with IPMI watch dog timer enabled in RBSU **Known Issues:** None - *Important Notes:** This System ROM should be considered Critical for any systems using the v2.60 revision of the System ROM. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the Advanced Memory Protection (AMP) mode was incorrectly forced to Advanced ECC from HPE Fast Fault Tolerant (ADDDC) mode after updating to Sysrom ROM 01/13/2022 v2.60. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option called Enhanced Processor Performance Profile. This option provides additional processor performance profiles that can be used to improve overall performance under certain workloads. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may report an Unsupported Memory Configuration error when Intel DC Optane Persistent Memory is present with an Intel Xeon Silver 4314 processor. This issue does not impact systems configured with an Intel Xeon Gold or Platinum SKU processor. **Known Issues:** None - Added support for Microsoft Windows Server 2022. Windows Server 2022 adds a new security feature called Secured-core. Secured-core is only supported on 3rd Generation Intel Xeon Scalable Processors. Secured-core servers use a combination of hardware features, firmware enablement and Windows Server operating system capabilities to provide protection against malware and rootkit security exploits. Added a new BIOS/Platform Configuration (RBSU) option for Microsoft Secured- core Support. Enabling this setting makes the following policy changes and configures the corresponding options: Intel Virtualization Technology enabled, Intel VT-d enabled, Intel TXT Support enabled, Secure Boot enabled, TPM enabled in 2.0 mode. Disabling any of these features while Secured-core is enabled can prevent Secured-core from working properly. Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Intel VROC SATA and sSATA Controller shows as Unknown under firmware information page in RBSU. Addressed an issue where an error "Incorrect firmware file or no supported device" occurs when flashing the firmware of Intel E810 Ethernet Adapters. Addressed an issue where the server hangs when launching Embedded iPXE when IPv4 certification is enrolled and Network location is set as iPXE Auto-Start- Script. Addressed an issue where the server hangs at POST when configured with Intel Xeon Silver 4314 Processor and Intel OptaneTM Persistent Memory 200 Series installed. Addressed an issue where the server hangs when running Safe Mode boot without a DIMM installed on DIMM slot1. **Known Issues:** None - Added support for updating NVMe/SATA drive firmware managed by Intel VROC via Firmware Update page in UEFI System Utilities. Added a new BIOS/Platform Configuration (RBSU) option for PCIe HotPlug Error Control. Use this option to select PCIe (NVMe) Hot-Plug support for the platform. When Hot-Plug Surprise is selected, the platform will attempt to protect the platform from experiencing an error on a surprise removal event. This option should be selected for older Operating Systems that do not support Enhanced Downstream Port Containment (eDPC). When eDPC Firmware Control is selected, the platform firmware and OS will properly negotiate and log all hot-plug events. This option is currently not supported by all Operating Systems. When eDPC OS Control is selected hot-plug events are handled by the Operating System with no involvement by the platform. All logging of events in this mode will be limited to the Operating System only. It is important that this option be set properly based on the Operating System to ensure hot-plug events and surprise removal events are handled properly by the platform. Please consult Operating System documentation for additional details. Note it is always recommended to perform a graceful device removal from the Operating System before performing a hot-plug event. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where NVMe SSDs May Be Listed As "UEFI Misc Device" in BIOS/Platform Configuration (RBSU) "One-Time Boot Menu" if Intel NVMe VROC is Enabled (Document ID: a00113593en_us). Addressed an issue where The NVMe Storage Drives Will Not De Displayed in the Integrated Lights-Out (iLO) Pages if Intel NVMe VROC (CPU/VMD) is Enabled (Document ID: a00113587en_us). Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where I/O devices accessing memory during heavy workloads with Intel Optane Persistent Memory 200 Series installed can experience slow response times, resulting in completion timeout errors on the I/O device. This can result in a Blue Screen in Windows, a kernel panic in Linux, or a Purple Screen in VMWare. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where if the administrator password and power-on password are set, after clearing power-on password, administrator password is also cleared. Addressed an issue (https://support.hpe.com/hpesc/public/docDisplay?docId=a001 19362en_us&docLocale=en_US) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - Added support for Microsoft Windows Server 2022. Windows Server 2022 adds a new security feature called Secured-core. Secured-core is only supported on 3rd Generation Intel Xeon Scalable Processors. Secured-core servers use a combination of hardware features, firmware enablement and Windows Server operating system capabilities to provide protection against malware and rootkit security exploits. Added a new BIOS/Platform Configuration (RBSU) option for Microsoft Secured- core Support. Enabling this setting makes the following policy changes and configures the corresponding options: Intel Virtualization Technology enabled, Intel VT-d enabled, Intel TXT Support enabled, Secure Boot enabled, TPM enabled in 2.0 mode. Disabling any of these features while Secured-core is enabled can prevent Secured-core from working properly. Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Intel VROC SATA and sSATA Controller shows as Unknown under firmware information page in RBSU. Addressed an issue where an error "Incorrect firmware file or no supported device" occurs when flashing the firmware of Intel E810 Ethernet Adapters. Addressed an issue where the server hangs when launching Embedded iPXE when IPv4 certification is enrolled and Network location is set as iPXE Auto-Start- Script. Addressed an issue where the server hangs at POST when configured with Intel Xeon Silver 4314 Processor and Intel OptaneTM Persistent Memory 200 Series installed. Addressed an issue where the server hangs when running Safe Mode boot without a DIMM installed on DIMM slot1. **Known Issues:** None - Added support for updating NVMe/SATA drive firmware managed by Intel VROC via Firmware Update page in UEFI System Utilities. Added a new BIOS/Platform Configuration (RBSU) option for PCIe HotPlug Error Control. Use this option to select PCIe (NVMe) Hot-Plug support for the platform. When Hot-Plug Surprise is selected, the platform will attempt to protect the platform from experiencing an error on a surprise removal event. This option should be selected for older Operating Systems that do not support Enhanced Downstream Port Containment (eDPC). When eDPC Firmware Control is selected, the platform firmware and OS will properly negotiate and log all hot-plug events. This option is currently not supported by all Operating Systems. When eDPC OS Control is selected hot-plug events are handled by the Operating System with no involvement by the platform. All logging of events in this mode will be limited to the Operating System only. It is important that this option be set properly based on the Operating System to ensure hot-plug events and surprise removal events are handled properly by the platform. Please consult Operating System documentation for additional details. Note it is always recommended to perform a graceful device removal from the Operating System before performing a hot-plug event. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where NVMe SSDs May Be Listed As "UEFI Misc Device" in BIOS/Platform Configuration (RBSU) "One-Time Boot Menu" if Intel NVMe VROC is Enabled (Document ID: a00113593en_us). Addressed an issue where The NVMe Storage Drives Will Not De Displayed in the Integrated Lights-Out (iLO) Pages if Intel NVMe VROC (CPU/VMD) is Enabled (Document ID: a00113587en_us). Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where I/O devices accessing memory during heavy workloads with Intel Optane Persistent Memory 200 Series installed can experience slow response times, resulting in completion timeout errors on the I/O device. This can result in a Blue Screen in Windows, a kernel panic in Linux, or a Purple Screen in VMWare. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where if the administrator password and power-on password are set, after clearing power-on password, administrator password is also cleared. Addressed an issue (https://support.hpe.com/hpesc/public/docDisplay?docId=a00119362en_us) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option to Memory Options called Refresh Watermarks. When selecting the Low Watermark setting, the memory controller will help reduce susceptibility to a DDR4 RowHammer attack. It is expected that a memory performance impact will be seen when enabling the Low Watermark setting. The default operation of the system has not changed and customers wanting to provide additional RowHammer protection should enable this setting. Added support to BIOS/Platform Configuration (RBSU) to allow importing and exporting Secure Boot signature lists as a signed binary file. This is useful to import the Microsoft revocation list binary file into the Secure Boot DBX as found on the UEFI forum at https://uefi.org/revocationlistfile. Updated the System ROM support for One Button Secure Erase functionality with the latest HPE option devices. Updated the RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2020.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-8696, CVE-2020-8694 and CVE-2020-8695. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00381 and INTEL-SA-00389. The Intel microcode patches included in this release are version 0x000000DE (CPUIDs 906ED, 906EC, 906EB and 906EA). These issues are not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-0593. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. These issues are not unique to HPE servers. **Known Issues:** None - Updated the language translations (non-English modes) for System Utilities. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel sightings CVE-2020-24511 and CVE-2020-24512. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00464. The Intel microcode patches included in this release are version 0x000000EA (CPUID 906ED, CPUID 906EC, CPUID 906EB and CPUID 906EA). This issue is not unique to HPE servers. This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8670 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers. Addressed an extremely rare issue where the Real Time Clock may become corrupted on a server boot. This was typically seen as an unexpected change to the RTC Year field but could impact other parts of the Date and Time. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the System ROM contains the fix for the Hynix 16G DDR4 DIMM compatibility issue. Please see advisory: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00115788en_us. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where systems running System ROM 2.20 (or later) and configured with an Intel Xeon E-2224 CPU and Hynix 16G DDR4 DIMM may occasionally encounter the error message "Unknown Initialization Error" in the Integrated Management Log (IML). **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Tianocore Edk2 Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2019-14584, CVE-2021-28211 and CVE-2021-28210. These security vulnerabilities are documented in Tianocore Edk2 CVE details site. These issues are not unique to HPE servers. Addressed an issue with HPE Infiniband NIC missing in system information page. **Known Issues:** None - Improved boot time by removing unneeded delay. - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.1 guidance. None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where High Precision Event Timer in Windows was not showing up in device manager. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. None **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes the latest revision of the Intel IPU 2021.2 which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2021-0157. These security vulnerabilities are documented in the CVE report site. This issue is not unique to HPE servers. **Known Issues:** None - *Important Notes:** This version of the System ROM contains updates aligned with the Intel Product Update (IPU) version IPU.2021.2 guidance. **Firmware Dependencies:** None **Problems Fixed:** This revision of the System ROM includes Intel Platform Update 2021.2 which provides mitigations for security vulnerabilities CVE-2021-0092, CVE-2021-0127, CVE-2021-0156 and CVE-2021-0157. These issues are not unique to HPE servers. Fixed an issue where system boot mode changed to Legacy mode from UEFI mode after IP flash complete and system may hang when entering IP after setting to UEFI mode. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option called Enhanced Processor Performance Profile. This option provides additional processor performance profiles that can be used to improve overall performance under certain workloads. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may report an Unsupported Memory Configuration error when Intel DC Optane Persistent Memory is present with an Intel Xeon Silver 4314 processor. This issue does not impact systems configured with an Intel Xeon Gold or Platinum SKU processor. **Known Issues:** None - Added support for Microsoft Windows Server 2022. Windows Server 2022 adds a new security feature called Secured-core. Secured-core is only supported on 3rd Generation Intel Xeon Scalable Processors. Secured-core servers use a combination of hardware features, firmware enablement and Windows Server operating system capabilities to provide protection against malware and rootkit security exploits. Added a new BIOS/Platform Configuration (RBSU) option for Microsoft Secured- core Support. Enabling this setting makes the following policy changes and configures the corresponding options: Intel Virtualization Technology enabled, Intel VT-d enabled, Intel TXT Support enabled, Secure Boot enabled, TPM enabled in 2.0 mode. Disabling any of these features while Secured-core is enabled can prevent Secured-core from working properly. Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Intel VROC SATA and sSATA Controller shows as Unknown under firmware information page in RBSU. Addressed an issue where an error "Incorrect firmware file or no supported device" occurs when flashing the firmware of Intel E810 Ethernet Adapters. Addressed an issue where the server hangs when launching Embedded iPXE when IPv4 certification is enrolled and Network location is set as iPXE Auto-Start- Script. Addressed an issue where the server hangs at POST when configured with Intel Xeon Silver 4314 Processor and Intel OptaneTM Persistent Memory 200 Series installed. Addressed an issue where the server hangs when running Safe Mode boot without a DIMM installed on DIMM slot1. **Known Issues:** None - Added support for updating NVMe/SATA drive firmware managed by Intel VROC via Firmware Update page in UEFI System Utilities. Added a new BIOS/Platform Configuration (RBSU) option for PCIe HotPlug Error Control. Use this option to select PCIe (NVMe) Hot-Plug support for the platform. When Hot-Plug Surprise is selected, the platform will attempt to protect the platform from experiencing an error on a surprise removal event. This option should be selected for older Operating Systems that do not support Enhanced Downstream Port Containment (eDPC). When eDPC Firmware Control is selected, the platform firmware and OS will properly negotiate and log all hot-plug events. This option is currently not supported by all Operating Systems. When eDPC OS Control is selected hot-plug events are handled by the Operating System with no involvement by the platform. All logging of events in this mode will be limited to the Operating System only. It is important that this option be set properly based on the Operating System to ensure hot-plug events and surprise removal events are handled properly by the platform. Please consult Operating System documentation for additional details. Note it is always recommended to perform a graceful device removal from the Operating System before performing a hot-plug event. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where NVMe SSDs May Be Listed As "UEFI Misc Device" in BIOS/Platform Configuration (RBSU) "One-Time Boot Menu" if Intel NVMe VROC is Enabled (Document ID: a00113593en_us). Addressed an issue where The NVMe Storage Drives Will Not De Displayed in the Integrated Lights-Out (iLO) Pages if Intel NVMe VROC (CPU/VMD) is Enabled (Document ID: a00113587en_us). Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where I/O devices accessing memory during heavy workloads with Intel Optane Persistent Memory 200 Series installed can experience slow response times, resulting in completion timeout errors on the I/O device. This can result in a Blue Screen in Windows, a kernel panic in Linux, or a Purple Screen in VMWare. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where if the administrator password and power-on password are set, after clearing power-on password, administrator password is also cleared. Addressed an issue (https://support.hpe.com/hpesc/public/docDisplay?docId=a001 19362en_us&docLocale=en_US) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). - *Important Notes:** None **Firmware Dependencies:** None **Enhancements/New Features:** This is the initial version of the firmware. **Known Issues:** None - Added a new BIOS/Platform Configuration (RBSU) option called Enhanced Processor Performance Profile. This option provides additional processor performance profiles that can be used to improve overall performance under certain workloads. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the system may report an Unsupported Memory Configuration error when Intel DC Optane Persistent Memory is present with an Intel Xeon Silver 4314 processor. This issue does not impact systems configured with an Intel Xeon Gold or Platinum SKU processor. **Known Issues:** None - Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. Added support for updating NVMe/SATA drive firmware managed by Intel VROC via Firmware Update page in UEFI System Utilities. Added a new BIOS/Platform Configuration (RBSU) option for PCIe HotPlug Error Control. Use this option to select PCIe (NVMe) Hot-Plug support for the platform. When Hot-Plug Surprise is selected, the platform will attempt to protect the platform from experiencing an error on a surprise removal event. This option should be selected for older Operating Systems that do not support Enhanced Downstream Port Containment (eDPC). When eDPC Firmware Control is selected, the platform firmware and OS will properly negotiate and log all hot-plug events. This option is currently not supported by all Operating Systems. When eDPC OS Control is selected hot-plug events are handled by the Operating System with no involvement by the platform. All logging of events in this mode will be limited to the Operating System only. It is important that this option be set properly based on the Operating System to ensure hot-plug events and surprise removal events are handled properly by the platform. Please consult Operating System documentation for additional details. Note it is always recommended to perform a graceful device removal from the Operating System before performing a hot-plug event. - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Intel VROC SATA and sSATA Controller shows as Unknown under firmware information page in RBSU. Addressed an issue where an error "Incorrect firmware file or no supported device" occurs when flashing the firmware of Intel E810 Ethernet Adapters. Addressed an issue where the server hangs when launching Embedded iPXE when IPv4 certification is enrolled and Network location is set as iPXE Auto-Start- Script. Addressed an issue where the server hangs at POST when configured with Intel Xeon Silver 4314 Processor and Intel OptaneTM Persistent Memory 200 Series installed. Addressed an issue where the server hangs when running Safe Mode boot without a DIMM installed on DIMM slot1. Addressed an issue where NVMe SSDs May Be Listed As "UEFI Misc Device" in BIOS/Platform Configuration (RBSU) "One-Time Boot Menu" if Intel NVMe VROC is Enabled (Document ID: a00113593en_us). Addressed an issue where The NVMe Storage Drives Will Not De Displayed in the Integrated Lights-Out (iLO) Pages if Intel NVMe VROC (CPU/VMD) is Enabled (Document ID: a00113587en_us). Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - Added new RBSU option to Omit Boot Device Event in TPM PCR[4] following EDK2. Warning: changing the setting will affect TPM measurements and can impact software functionality which utilizes the TPM PCR registers such as Microsoft BitLocker. PCR[4] is the register that records the process of attempting to boot different hardware paths like from a a hard drive or CD, and what boot devices are attempted, and the Initial Program Loader (IPL) code that is loaded and executed from the device. If boot from one device fails, measurements in PCR[4] record the attempt to boot the next device or boot path. If recording which device attempted to boot is omitted with this option (i.e. enable this option), the BIOS records the event type EV_OMIT_BOOT_DEVICE_EVENTS in PCR[4], otherwise the event is not recorded. Added support for updating NVMe/SATA drive firmware managed by Intel VROC via Firmware Update page in UEFI System Utilities. Added a new BIOS/Platform Configuration (RBSU) option for PCIe HotPlug Error Control. Use this option to select PCIe (NVMe) Hot-Plug support for the platform. When Hot-Plug Surprise is selected, the platform will attempt to protect the platform from experiencing an error on a surprise removal event. This option should be selected for older Operating Systems that do not support Enhanced Downstream Port Containment (eDPC). When eDPC Firmware Control is selected, the platform firmware and OS will properly negotiate and log all hot-plug events. This option is currently not supported by all Operating Systems. When eDPC OS Control is selected hot-plug events are handled by the Operating System with no involvement by the platform. All logging of events in this mode will be limited to the Operating System only. It is important that this option be set properly based on the Operating System to ensure hot-plug events and surprise removal events are handled properly by the platform. Please consult Operating System documentation for additional details. Note it is always recommended to perform a graceful device removal from the Operating System before performing a hot-plug event. - *Important Notes:** Ver. 1.52_09-22-2021(B) contains updates to the firmware packaging and is functionally equivalent to ver. 1.52_09-22-2021. It is not necessary to upgrade with Revision B if a previous component revision was used to upgrade the firmware to version 1.52_09-22-2021. **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where Intel VROC SATA and sSATA Controller shows as Unknown under firmware information page in RBSU. Addressed an issue where an error "Incorrect firmware file or no supported device" occurs when flashing the firmware of Intel E810 Ethernet Adapters. Addressed an issue where the server hangs when launching Embedded iPXE when IPv4 certification is enrolled and Network location is set as iPXE Auto-Start- Script. Addressed an issue where the server hangs at POST when configured with Intel Xeon Silver 4314 Processor and Intel OptaneTM Persistent Memory 200 Series installed. Addressed an issue where the server hangs when running Safe Mode boot without a DIMM installed on DIMM slot1. Addressed an issue where NVMe SSDs May Be Listed As "UEFI Misc Device" in BIOS/Platform Configuration (RBSU) "One-Time Boot Menu" if Intel NVMe VROC is Enabled (Document ID: a00113593en_us). Addressed an issue where The NVMe Storage Drives Will Not De Displayed in the Integrated Lights-Out (iLO) Pages if Intel NVMe VROC (CPU/VMD) is Enabled (Document ID: a00113587en_us). Addressed an issue where Uncorrectable Memory Errors may be reported and logged to the Integrated Management Log (IML) with certain DIMMs installed and the RBSU "Extended Memory Test" option enabled. The "Extended Memory Test" option is disabled by default and this issue would only impact customers who had specifically configured this option to enabled. The reported Uncorrected Memory Errors were due to an issue with the impacted System ROM revisions and do NOT indicate an issue with the DIMMs themselves. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where I/O devices accessing memory during heavy workloads with Intel Optane Persistent Memory 200 Series installed can experience slow response times, resulting in completion timeout errors on the I/O device. This can result in a Blue Screen in Windows, a kernel panic in Linux, or a Purple Screen in VMWare. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue that can result in Corrected Memory Error Threshold Events being logged to the Integrated Management Log (IML) incorrectly. The system monitors corrected memory errors and notifies the user via a Corrected Memory Error Threshold Event when action is recommended due to an increased risk of an uncorrected memory error. Previous versions of the System ROM may log a Corrected Memory Error Threshold Event in cases where the system is not at an increased risk of an uncorrected memory error. It is strongly recommended that the System ROM be updated to this version or later before replacing DIMMs due to Corrected Memory Error Threshold Events. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where if the administrator password and power-on password are set, after clearing power-on password, administrator password is also cleared. Addressed an issue (https://support.hpe.com/hpesc/public/docDisplay?docId=a001 19362en_us&docLocale=en_US) where the systems with HPE NS204i-p NVMe OS Boot Device may shut down intermittently and may log the following System Overheating message in the Integrated Management Log (IML): "System Overheating (Temperature Sensor 47, Location I/O Board, Temperature61) ACTION:Check fans, processor heat sink and air baffles installation." Addressed an issue where the system may not automatically restart due to a hang condition during the boot process after a cold boot when the IPMI Watchdog Timer feature is enabled in the ROM-Based Setup Utility (RBSU). - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the power-on password and the administrator passwords were both cleared when clearing one or the other. With this fix the two passwords will be treated independently as intended. Removed Dynamic Power Capping Functionality option from the RBSU menu as this option is not supported on this platform. Removed TPM1.2 option from the RBSU menu as this option is not supported on this platform. **Known Issues:** None - *Important Notes:** None **Firmware Dependencies:** None **Problems Fixed:** Addressed an issue where the power-on password and the administrator passwords were both cleared when clearing one or the other. With this fix the two passwords will be treated independently as intended. Removed Dynamic Power Capping Functionality option from the RBSU menu as this option is not supported on this platform. Removed TPM1.2 option from the RBSU menu as this option is not supported on this platform. **Known Issues:** None - This driver fix unexpected error message appears in dmesg when driver is loaded. - This driver fix VF 0 does not show via sysfs, and cannot be removed. - This driver fix 1g speed i40e_aq_run_phy_activity() from f/w reports lpi statistics always as 0 - This driver fixes the issue of restoring all VF-d config on a VF reset. - This driver fixes the issue of mirror rule via VF-d. - This driver fixes the issue of VFD handler function prototypes. - This driver fixes the issue of assuming hardware is at default when that's not always true. - This driver fixes the issue of not re-initializing properly in the case of CORE reset following PF reset timeout. - This driver fixex the issue of unknown NMI received and kernel crash when adding/removing VF to namespace repeatedly. - This driver fixes the issue of running 'ifconfig ethX mtu 2000' causes physial link down and failed to auto-recover, when we have set ' ethtool --set-priv-flags eth2 link-down-on-close on'. - This driver now introduce allow_untagged VF-d attribute. - This driver now add a helper function to validate a vf based on the vf id. - This driver now add a macro for checking if prog_attached exists. - This driver now add client register/unregister to prevent vsi. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver added the "Negotiated" string into the i40e_print_link_message() function. - This driver fixes VF 0 failed opcode 3, when total cores =192( total threads =384, with Hyper threading enabled in BIOS) - This driver remove RDMA VF code from files including VF support. - This driver fixes the issue of reloading driver during resets loop causes platform to lose connection and trace call - This driver add support to expose VF stats as part of PF interface ethtool stats. - This driver fix i40e Mirrors not clear after VF remove. - This driver export LPI time duration statistic info which can be observed by ethtool -S $pf - This driver fix an error message appeared like "0000 [#1] SMP PTI" - This driver fix the package traffic queue statistics. - Add SLES15 SP2 support - This driver fix the system might hang when reset. - This driver fix kernel crash in iavf reset path. - Removes rx_fragments and rx_jabber from rx_errors to avoid rx_jabber and rx_fragments incorrectly double count. - Fixes ethtool warning message caused by incorrect data structure - Add RHEL8.4 Support - This driver fix unexpected error message appears in dmesg when driver is loaded. - This driver fix VF 0 does not show via sysfs, and cannot be removed. - This driver fix 1g speed i40e_aq_run_phy_activity() from f/w reports lpi statistics always as 0 - This driver fixes the issue of restoring all VF-d config on a VF reset. - This driver fixes the issue of mirror rule via VF-d. - This driver fixes the issue of VFD handler function prototypes. - This driver fixes the issue of assuming hardware is at default when that's not always true. - This driver fixes the issue of not re-initializing properly in the case of CORE reset following PF reset timeout. - This driver fixex the issue of unknown NMI received and kernel crash when adding/removing VF to namespace repeatedly. - This driver fixes the issue of running 'ifconfig ethX mtu 2000' causes physial link down and failed to auto-recover, when we have set ' ethtool --set-priv-flags eth2 link-down-on-close on'. - This driver now introduce allow_untagged VF-d attribute. - This driver now add a helper function to validate a vf based on the vf id. - This driver now add a macro for checking if prog_attached exists. - This driver now add client register/unregister to prevent vsi. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver added the "Negotiated" string into the i40e_print_link_message() function. - This driver fixes VF 0 failed opcode 3, when total cores =192( total threads =384, with Hyper threading enabled in BIOS) - This driver remove RDMA VF code from files including VF support. - This driver fixes the issue of reloading driver during resets loop causes platform to lose connection and trace call - This driver add support to expose VF stats as part of PF interface ethtool stats. - This driver fix i40e Mirrors not clear after VF remove. - This driver export LPI time duration statistic info which can be observed by ethtool -S $pf - This driver fix an error message appeared like "0000 [#1] SMP PTI" - This driver fix the package traffic queue statistics. - Add SLES15 SP2 support - This driver fix the system might hang when reset. - This driver fix kernel crash in iavf reset path. - Removes rx_fragments and rx_jabber from rx_errors to avoid rx_jabber and rx_fragments incorrectly double count. - Fixes ethtool warning message caused by incorrect data structure - Add RHEL8.4 Support - This driver fix unexpected error message appears in dmesg when driver is loaded. - This driver fix VF 0 does not show via sysfs, and cannot be removed. - This driver fix 1g speed i40e_aq_run_phy_activity() from f/w reports lpi statistics always as 0 - This driver fixes the issue of restoring all VF-d config on a VF reset. - This driver fixes the issue of mirror rule via VF-d. - This driver fixes the issue of VFD handler function prototypes. - This driver fixes the issue of assuming hardware is at default when that's not always true. - This driver fixes the issue of not re-initializing properly in the case of CORE reset following PF reset timeout. - This driver fixex the issue of unknown NMI received and kernel crash when adding/removing VF to namespace repeatedly. - This driver fixes the issue of running 'ifconfig ethX mtu 2000' causes physial link down and failed to auto-recover, when we have set ' ethtool --set-priv-flags eth2 link-down-on-close on'. - This driver now introduce allow_untagged VF-d attribute. - This driver now add a helper function to validate a vf based on the vf id. - This driver now add a macro for checking if prog_attached exists. - This driver now add client register/unregister to prevent vsi. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver added the "Negotiated" string into the i40e_print_link_message() function. - This driver fixes VF 0 failed opcode 3, when total cores =192( total threads =384, with Hyper threading enabled in BIOS) - This driver remove RDMA VF code from files including VF support. - This driver fixes the issue of reloading driver during resets loop causes platform to lose connection and trace call - This driver add support to expose VF stats as part of PF interface ethtool stats. - This driver fix i40e Mirrors not clear after VF remove. - This driver export LPI time duration statistic info which can be observed by ethtool -S $pf - This driver fix an error message appeared like "0000 [#1] SMP PTI" - This driver fix the package traffic queue statistics. - Add SLES15 SP2 support - This driver fix the system might hang when reset. - This driver fix kernel crash in iavf reset path. - Removes rx_fragments and rx_jabber from rx_errors to avoid rx_jabber and rx_fragments incorrectly double count. - Fixes ethtool warning message caused by incorrect data structure - Add RHEL8.4 Support - Initial package which is renamed from i40evf driver - Creating CVL SW1.1 release candidate build. - Add SLES15 SP2 support - This driver fix system freezes when trying to create TCs on VF with no more VSIs available. - Add RHEL8.3 support - Add support to compile on Linux kernel >= 5.9.0 - Initial package which is renamed from i40evf driver - Creating CVL SW1.1 release candidate build. - Add SLES15 SP2 support - This driver fix system freezes when trying to create TCs on VF with no more VSIs available. - Add RHEL8.3 support - Add support to compile on Linux kernel >= 5.9.0 - Initial package which is renamed from i40evf driver - Creating CVL SW1.1 release candidate build. - Add SLES15 SP2 support - This driver fix system freezes when trying to create TCs on VF with no more VSIs available. - Add RHEL8.3 support - Add support to compile on Linux kernel >= 5.9.0 - Added RHEL 6.8 support - Fix the issue of getting crash dump when loading igb module(modprobe igb) - Fix unable to disable the offload property in rhel6u6 - Added SLES12SP2 support - Added RHEL 7.3 support - Added SLES12SP3 support - Added RHEL 7.4 support - Fix for the issue of unable to set MTU value more than 1500 in SUSE12SP3 with Intel NICs - Fixed build on updated kernels of SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - This driver fixes an issue of driver crash with ethtool command. - This driver fixes an issue of Klocwork hits. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - Add SLES15 SP2 support - Add RHEL8.3 support. - Added RHEL 6.8 support - Fix the issue of getting crash dump when loading igb module(modprobe igb) - Fix unable to disable the offload property in rhel6u6 - Added SLES12SP2 support - Added RHEL 7.3 support - Added SLES12SP3 support - Added RHEL 7.4 support - Fix for the issue of unable to set MTU value more than 1500 in SUSE12SP3 with Intel NICs - Fixed build on updated kernels of SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - This driver fixes an issue of driver crash with ethtool command. - This driver fixes an issue of Klocwork hits. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - Add SLES15 SP2 support - Add RHEL8.3 support. - Added RHEL 6.8 support - Fix the issue of getting crash dump when loading igb module(modprobe igb) - Fix unable to disable the offload property in rhel6u6 - Added SLES12SP2 support - Added RHEL 7.3 support - Added SLES12SP3 support - Added RHEL 7.4 support - Fix for the issue of unable to set MTU value more than 1500 in SUSE12SP3 with Intel NICs - Fixed build on updated kernels of SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - This driver fixes an issue of driver crash with ethtool command. - This driver fixes an issue of Klocwork hits. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - Add SLES15 SP2 support - Add RHEL8.3 support. - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - IPv6 support for ixgbe driver - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Fix potential memory leak - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - IPv6 support for ixgbe driver - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Fix potential memory leak - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - IPv6 support for ixgbe driver - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Fix potential memory leak - This driver fixes the issue of failed to install driver on SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - Remove irqs only when they are set up - Fix guest OS crashes during VFs resets - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - This driver fixes the issue of failed to install driver on SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - Remove irqs only when they are set up - Fix guest OS crashes during VFs resets - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - This driver fixes the issue of failed to install driver on SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - Remove irqs only when they are set up - Fix guest OS crashes during VFs resets - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Initial development - Added support the HPE StoreFabric 84E 4-port Fibre Channel Host Bus Adapter - Added support for HPE StoreFabric SN1200E 1P & 2P, HPE StoreFabric SN1600E 1P & 2P - Added support for HPE Synergy 3530C - Added Obsoletes tag since the rpm has been changed from noarch to x86_64 bit - Initial development - Added support for SN1600Q 1P & 2P devices - Added support for 84Q and 3830C devices - Added Obsoletes tag since the rpm has been changed from noarch to x86_64 bit - v4.5.0 is mainly targeted for iLO 4 2.20 and iLO 3 1.80 - v4.6.0 is mainly targeted for iLO 4 2.20 and iLO 3 1.80 - v5.0.0 is mainly targeted for iLO 5 1.10 - v5.1.0 is mainly targeted for iLO 5 1.15 - v5.2.0 is mainly targeted for iLO 5 1.20 - v5.3.0 is mainly targeted for iLO 5 1.30 - Changes include to select correct libssl.so file when multiple Openssl installed (32-bit and 64-bit) - Changes to remove the low level openSSL calls. -Updated the OpenSSL API calls to support Host's OpenSSL FIPS mode. - Changes to handle multiple OpenSSL library installed. - Initial package - Fix return values and prints in VF MAC add/del flow - Fix kernel panic after transiting FW LLDP from on to off and restarting lldpad - Fix Throughput lower than expected. - Add SLES15 SP2 support - Add RHEL8u3 support - Add RHEL7u9 support - Addressing the issue of system reboot on unloading iavf driver with maxvfs enabled in switchdev mode - Initial package - Fix return values and prints in VF MAC add/del flow - Fix kernel panic after transiting FW LLDP from on to off and restarting lldpad - Fix Throughput lower than expected. - Add SLES15 SP2 support - Add RHEL8u3 support - Add RHEL7u9 support - Addressing the issue of system reboot on unloading iavf driver with maxvfs enabled in switchdev mode - Initial package - Fix return values and prints in VF MAC add/del flow - Fix kernel panic after transiting FW LLDP from on to off and restarting lldpad - Fix Throughput lower than expected. - Add SLES15 SP2 support - Add RHEL8u3 support - Add RHEL7u9 support - Addressing the issue of system reboot on unloading iavf driver with maxvfs enabled in switchdev mode - Release version 4.18.0_k4.12.14_120-1.sles12sp5 - Release version 4.18.0_k4.12.14_94.41-1.sles12sp4 - Release version 4.18.0_k5.3.18_22-1.sles15sp2 - Release version 4.18.0_k5.3.18_57-1.sles15sp3 - Added RHEL 7 support - Added support for OCe14000 based adapters: 650FLB, 650M, 556FLR-SFP, CN1200E - Added RHEL 7 support - Added support for OCe14000 based adapters: 650FLB, 650M, 556FLR-SFP, CN1200E - Added RHEL 7 support - Added support for OCe14000 based adapters: 650FLB, 650M, 556FLR-SFP, CN1200E - Added RHEL 7 support - Added support for OCe14000 based adapters: 650FLB, 650M, 556FLR-SFP, CN1200E - Built driver for rhel7 - Built driver for rhel7 - Built driver for rhel8 - Changed version to 10.7 - Added support for RHEL 6U8 - Added support for RHEL 7U2 - Added support for SLES12 SP1 - Changed version to 11.0 - Changed version to 11.1 - Added support for RHEL 7U3 - Added support for SLES 12 SP2 - Removed support for RHEL 6U5 - Changed version to 11.2 - Added support for RHEL 6U9 - Added support for RHEL 7U4 - Added support for SLES 12 SP3 - Removed support for RHEL 7U0 - Removed support for SLES 12 SP0 - Changed version to 11.4 - Removed support for RHEL 6U6 - Removed support for RHEL 7U1 - Added support for RHEL 7U5 - Added support for SLES 15 SP0 - Changed version to 12.0 - Removed support for RHEL 6U7 - Removed support for SLES 12 SP1 - Added support for RHEL 6U10 - Added support for RHEL 7U6 - Added support for RHEL 8U0 - Added support for SLES 12 SP4 - Added support for SLES 15 SP1 - Changed version to 12.2 - Removed support for SLES 11 SP3 - Removed support for SLES 11 SP4 - Removed support for RHEL 6U8 - Removed support for RHEL 7U2 - Removed support for RHEL 7U3 - Changed version to 12.4 - Added support for RHEL 7U7 - Added support for RHEL 8U1 - Added support for SLES 12 SP5 - Removed support for RHEL 6U9 - Removed support for RHEL 6U10 - Removed support for RHEL 7U4 - Changed version to 12.6 - Added support for RHEL 7U8 - Added support for RHEL 8U2 - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 - Removed support for SLES 12 SP3 - Changed version to 12.8 - Initial build - Changed version to 10.7 - Added support for RHEL 6U8 - Added support for RHEL 7U2 - Added support for SLES12 SP1 - Changed version to 11.0 - Changed version to 11.1 - Added support for RHEL 7U3 - Added support for SLES 12 SP2 - Removed support for RHEL 6U5 - Changed version to 11.2 - Added support for RHEL 6U9 - Added support for RHEL 7U4 - Added support for SLES 12 SP3 - Removed support for RHEL 7U0 - Removed support for SLES 12 SP0 - Changed version to 11.4 - Removed support for RHEL 6U6 - Removed support for RHEL 7U1 - Added support for RHEL 7U5 - Added support for SLES 15 SP0 - Changed version to 12.0 - Removed support for RHEL 6U7 - Removed support for SLES 12 SP1 - Added support for RHEL 6U10 - Added support for RHEL 7U6 - Added support for RHEL 8U0 - Added support for SLES 12 SP4 - Added support for SLES 15 SP1 - Changed version to 12.2 - Removed support for SLES 11 SP3 - Removed support for SLES 11 SP4 - Removed support for RHEL 6U8 - Removed support for RHEL 7U2 - Removed support for RHEL 7U3 - Changed version to 12.4 - Added support for RHEL 7U7 - Added support for RHEL 8U1 - Added support for SLES 12 SP5 - Removed support for RHEL 6U9 - Removed support for RHEL 6U10 - Removed support for RHEL 7U4 - Changed version to 12.6 - Added support for RHEL 7U8 - Added support for RHEL 8U2 - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 - Removed support for SLES 12 SP3 - Changed version to 12.8 - Initial build - Changed version to 10.7 - Added support for RHEL 6U8 - Added support for RHEL 7U2 - Added support for SLES12 SP1 - Changed version to 11.0 - Changed version to 11.1 - Added support for RHEL 7U3 - Added support for SLES 12 SP2 - Removed support for RHEL 6U5 - Changed version to 11.2 - Added support for RHEL 6U9 - Added support for RHEL 7U4 - Added support for SLES 12 SP3 - Removed support for RHEL 7U0 - Removed support for SLES 12 SP0 - Changed version to 11.4 - Removed support for RHEL 6U6 - Removed support for RHEL 7U1 - Added support for RHEL 7U5 - Added support for SLES 15 SP0 - Changed version to 12.0 - Removed support for RHEL 6U7 - Removed support for SLES 12 SP1 - Added support for RHEL 6U10 - Added support for RHEL 7U6 - Added support for RHEL 8U0 - Added support for SLES 12 SP4 - Added support for SLES 15 SP1 - Changed version to 12.2 - Removed support for SLES 11 SP3 - Removed support for SLES 11 SP4 - Removed support for RHEL 6U8 - Removed support for RHEL 7U2 - Removed support for RHEL 7U3 - Changed version to 12.4 - Added support for RHEL 7U7 - Added support for RHEL 8U1 - Added support for SLES 12 SP5 - Removed support for RHEL 6U9 - Removed support for RHEL 6U10 - Removed support for RHEL 7U4 - Changed version to 12.6 - Added support for RHEL 7U8 - Added support for RHEL 8U2 - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 - Removed support for SLES 12 SP3 - Changed version to 12.8 - Initial build - Changed version to 10.7 - Added support for RHEL 6U8 - Added support for RHEL 7U2 - Added support for SLES12 SP1 - Changed version to 11.0 - Changed version to 11.1 - Added support for RHEL 7U3 - Added support for SLES 12 SP2 - Removed support for RHEL 6U5 - Changed version to 11.2 - Added support for RHEL 6U9 - Added support for RHEL 7U4 - Added support for SLES 12 SP3 - Removed support for RHEL 7U0 - Removed support for SLES 12 SP0 - Changed version to 11.4 - Removed support for RHEL 6U6 - Removed support for RHEL 7U1 - Added support for RHEL 7U5 - Added support for SLES 15 SP0 - Changed version to 12.0 - Removed support for RHEL 6U7 - Removed support for SLES 12 SP1 - Added support for RHEL 6U10 - Added support for RHEL 7U6 - Added support for RHEL 8U0 - Added support for SLES 12 SP4 - Added support for SLES 15 SP1 - Changed version to 12.2 - Removed support for SLES 11 SP3 - Removed support for SLES 11 SP4 - Removed support for RHEL 6U8 - Removed support for RHEL 7U2 - Removed support for RHEL 7U3 - Changed version to 12.4 - Added support for RHEL 7U7 - Added support for RHEL 8U1 - Added support for SLES 12 SP5 - Removed support for RHEL 6U9 - Removed support for RHEL 6U10 - Removed support for RHEL 7U4 - Changed version to 12.6 - Added support for RHEL 7U8 - Added support for RHEL 8U2 - Added support for SLES 15 SP2 - Removed support for SLES 12 SP2 - Removed support for SLES 12 SP3 - Changed version to 12.8 - Initial build - This driver fix unexpected error message appears in dmesg when driver is loaded. - This driver fix VF 0 does not show via sysfs, and cannot be removed. - This driver fix 1g speed i40e_aq_run_phy_activity() from f/w reports lpi statistics always as 0 - This driver fixes the issue of restoring all VF-d config on a VF reset. - This driver fixes the issue of mirror rule via VF-d. - This driver fixes the issue of VFD handler function prototypes. - This driver fixes the issue of assuming hardware is at default when that's not always true. - This driver fixes the issue of not re-initializing properly in the case of CORE reset following PF reset timeout. - This driver fixex the issue of unknown NMI received and kernel crash when adding/removing VF to namespace repeatedly. - This driver fixes the issue of running 'ifconfig ethX mtu 2000' causes physial link down and failed to auto-recover, when we have set ' ethtool --set-priv-flags eth2 link-down-on-close on'. - This driver now introduce allow_untagged VF-d attribute. - This driver now add a helper function to validate a vf based on the vf id. - This driver now add a macro for checking if prog_attached exists. - This driver now add client register/unregister to prevent vsi. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver added the "Negotiated" string into the i40e_print_link_message() function. - This driver fixes VF 0 failed opcode 3, when total cores =192( total threads =384, with Hyper threading enabled in BIOS) - This driver remove RDMA VF code from files including VF support. - This driver fixes the issue of reloading driver during resets loop causes platform to lose connection and trace call - This driver add support to expose VF stats as part of PF interface ethtool stats. - This driver fix i40e Mirrors not clear after VF remove. - This driver export LPI time duration statistic info which can be observed by ethtool -S $pf - This driver fix an error message appeared like "0000 [#1] SMP PTI" - This driver fix the package traffic queue statistics. - Add SLES15 SP2 support - This driver fix the system might hang when reset. - This driver fix kernel crash in iavf reset path. - Removes rx_fragments and rx_jabber from rx_errors to avoid rx_jabber and rx_fragments incorrectly double count. - Fixes ethtool warning message caused by incorrect data structure - Add RHEL8.4 Support - This driver fix unexpected error message appears in dmesg when driver is loaded. - This driver fix VF 0 does not show via sysfs, and cannot be removed. - This driver fix 1g speed i40e_aq_run_phy_activity() from f/w reports lpi statistics always as 0 - This driver fixes the issue of restoring all VF-d config on a VF reset. - This driver fixes the issue of mirror rule via VF-d. - This driver fixes the issue of VFD handler function prototypes. - This driver fixes the issue of assuming hardware is at default when that's not always true. - This driver fixes the issue of not re-initializing properly in the case of CORE reset following PF reset timeout. - This driver fixex the issue of unknown NMI received and kernel crash when adding/removing VF to namespace repeatedly. - This driver fixes the issue of running 'ifconfig ethX mtu 2000' causes physial link down and failed to auto-recover, when we have set ' ethtool --set-priv-flags eth2 link-down-on-close on'. - This driver now introduce allow_untagged VF-d attribute. - This driver now add a helper function to validate a vf based on the vf id. - This driver now add a macro for checking if prog_attached exists. - This driver now add client register/unregister to prevent vsi. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver added the "Negotiated" string into the i40e_print_link_message() function. - This driver fixes VF 0 failed opcode 3, when total cores =192( total threads =384, with Hyper threading enabled in BIOS) - This driver remove RDMA VF code from files including VF support. - This driver fixes the issue of reloading driver during resets loop causes platform to lose connection and trace call - This driver add support to expose VF stats as part of PF interface ethtool stats. - This driver fix i40e Mirrors not clear after VF remove. - This driver export LPI time duration statistic info which can be observed by ethtool -S $pf - This driver fix an error message appeared like "0000 [#1] SMP PTI" - This driver fix the package traffic queue statistics. - Add SLES15 SP2 support - This driver fix the system might hang when reset. - This driver fix kernel crash in iavf reset path. - Removes rx_fragments and rx_jabber from rx_errors to avoid rx_jabber and rx_fragments incorrectly double count. - Fixes ethtool warning message caused by incorrect data structure - Add RHEL8.4 Support - This driver fix unexpected error message appears in dmesg when driver is loaded. - This driver fix VF 0 does not show via sysfs, and cannot be removed. - This driver fix 1g speed i40e_aq_run_phy_activity() from f/w reports lpi statistics always as 0 - This driver fixes the issue of restoring all VF-d config on a VF reset. - This driver fixes the issue of mirror rule via VF-d. - This driver fixes the issue of VFD handler function prototypes. - This driver fixes the issue of assuming hardware is at default when that's not always true. - This driver fixes the issue of not re-initializing properly in the case of CORE reset following PF reset timeout. - This driver fixex the issue of unknown NMI received and kernel crash when adding/removing VF to namespace repeatedly. - This driver fixes the issue of running 'ifconfig ethX mtu 2000' causes physial link down and failed to auto-recover, when we have set ' ethtool --set-priv-flags eth2 link-down-on-close on'. - This driver now introduce allow_untagged VF-d attribute. - This driver now add a helper function to validate a vf based on the vf id. - This driver now add a macro for checking if prog_attached exists. - This driver now add client register/unregister to prevent vsi. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver added the "Negotiated" string into the i40e_print_link_message() function. - This driver fixes VF 0 failed opcode 3, when total cores =192( total threads =384, with Hyper threading enabled in BIOS) - This driver remove RDMA VF code from files including VF support. - This driver fixes the issue of reloading driver during resets loop causes platform to lose connection and trace call - This driver add support to expose VF stats as part of PF interface ethtool stats. - This driver fix i40e Mirrors not clear after VF remove. - This driver export LPI time duration statistic info which can be observed by ethtool -S $pf - This driver fix an error message appeared like "0000 [#1] SMP PTI" - This driver fix the package traffic queue statistics. - Add SLES15 SP2 support - This driver fix the system might hang when reset. - This driver fix kernel crash in iavf reset path. - Removes rx_fragments and rx_jabber from rx_errors to avoid rx_jabber and rx_fragments incorrectly double count. - Fixes ethtool warning message caused by incorrect data structure - Add RHEL8.4 Support - This driver fix unexpected error message appears in dmesg when driver is loaded. - This driver fix VF 0 does not show via sysfs, and cannot be removed. - This driver fix 1g speed i40e_aq_run_phy_activity() from f/w reports lpi statistics always as 0 - This driver fixes the issue of restoring all VF-d config on a VF reset. - This driver fixes the issue of mirror rule via VF-d. - This driver fixes the issue of VFD handler function prototypes. - This driver fixes the issue of assuming hardware is at default when that's not always true. - This driver fixes the issue of not re-initializing properly in the case of CORE reset following PF reset timeout. - This driver fixex the issue of unknown NMI received and kernel crash when adding/removing VF to namespace repeatedly. - This driver fixes the issue of running 'ifconfig ethX mtu 2000' causes physial link down and failed to auto-recover, when we have set ' ethtool --set-priv-flags eth2 link-down-on-close on'. - This driver now introduce allow_untagged VF-d attribute. - This driver now add a helper function to validate a vf based on the vf id. - This driver now add a macro for checking if prog_attached exists. - This driver now add client register/unregister to prevent vsi. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver added the "Negotiated" string into the i40e_print_link_message() function. - This driver fixes VF 0 failed opcode 3, when total cores =192( total threads =384, with Hyper threading enabled in BIOS) - This driver remove RDMA VF code from files including VF support. - This driver fixes the issue of reloading driver during resets loop causes platform to lose connection and trace call - This driver add support to expose VF stats as part of PF interface ethtool stats. - This driver fix i40e Mirrors not clear after VF remove. - This driver export LPI time duration statistic info which can be observed by ethtool -S $pf - This driver fix an error message appeared like "0000 [#1] SMP PTI" - This driver fix the package traffic queue statistics. - Add SLES15 SP2 support - This driver fix the system might hang when reset. - This driver fix kernel crash in iavf reset path. - Removes rx_fragments and rx_jabber from rx_errors to avoid rx_jabber and rx_fragments incorrectly double count. - Fixes ethtool warning message caused by incorrect data structure - Add RHEL8.4 Support - Initial package which is renamed from i40evf driver - Creating CVL SW1.1 release candidate build. - Add SLES15 SP2 support - This driver fix system freezes when trying to create TCs on VF with no more VSIs available. - Add RHEL8.3 support - Add support to compile on Linux kernel >= 5.9.0 - Initial package which is renamed from i40evf driver - Creating CVL SW1.1 release candidate build. - Add SLES15 SP2 support - This driver fix system freezes when trying to create TCs on VF with no more VSIs available. - Add RHEL8.3 support - Add support to compile on Linux kernel >= 5.9.0 - Initial package which is renamed from i40evf driver - Creating CVL SW1.1 release candidate build. - Add SLES15 SP2 support - This driver fix system freezes when trying to create TCs on VF with no more VSIs available. - Add RHEL8.3 support - Add support to compile on Linux kernel >= 5.9.0 - Initial package which is renamed from i40evf driver - Creating CVL SW1.1 release candidate build. - Add SLES15 SP2 support - This driver fix system freezes when trying to create TCs on VF with no more VSIs available. - Add RHEL8.3 support - Add support to compile on Linux kernel >= 5.9.0 - Added RHEL 6.8 support - Fix the issue of getting crash dump when loading igb module(modprobe igb) - Fix unable to disable the offload property in rhel6u6 - Added SLES12SP2 support - Added RHEL 7.3 support - Added SLES12SP3 support - Added RHEL 7.4 support - Fix for the issue of unable to set MTU value more than 1500 in SUSE12SP3 with Intel NICs - Fixed build on updated kernels of SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - This driver fixes an issue of driver crash with ethtool command. - This driver fixes an issue of Klocwork hits. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - Add SLES15 SP2 support - Add RHEL8.3 support. - Added RHEL 6.8 support - Fix the issue of getting crash dump when loading igb module(modprobe igb) - Fix unable to disable the offload property in rhel6u6 - Added SLES12SP2 support - Added RHEL 7.3 support - Added SLES12SP3 support - Added RHEL 7.4 support - Fix for the issue of unable to set MTU value more than 1500 in SUSE12SP3 with Intel NICs - Fixed build on updated kernels of SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - This driver fixes an issue of driver crash with ethtool command. - This driver fixes an issue of Klocwork hits. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - Add SLES15 SP2 support - Add RHEL8.3 support. - Added RHEL 6.8 support - Fix the issue of getting crash dump when loading igb module(modprobe igb) - Fix unable to disable the offload property in rhel6u6 - Added SLES12SP2 support - Added RHEL 7.3 support - Added SLES12SP3 support - Added RHEL 7.4 support - Fix for the issue of unable to set MTU value more than 1500 in SUSE12SP3 with Intel NICs - Fixed build on updated kernels of SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - This driver fixes an issue of driver crash with ethtool command. - This driver fixes an issue of Klocwork hits. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - Add SLES15 SP2 support - Add RHEL8.3 support. - Added RHEL 6.8 support - Fix the issue of getting crash dump when loading igb module(modprobe igb) - Fix unable to disable the offload property in rhel6u6 - Added SLES12SP2 support - Added RHEL 7.3 support - Added SLES12SP3 support - Added RHEL 7.4 support - Fix for the issue of unable to set MTU value more than 1500 in SUSE12SP3 with Intel NICs - Fixed build on updated kernels of SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - This driver fixes an issue of driver crash with ethtool command. - This driver fixes an issue of Klocwork hits. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - Add SLES15 SP2 support - Add RHEL8.3 support. - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - IPv6 support for ixgbe driver - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Fix potential memory leak - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - IPv6 support for ixgbe driver - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Fix potential memory leak - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - IPv6 support for ixgbe driver - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Fix potential memory leak - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - IPv6 support for ixgbe driver - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Fix potential memory leak - This driver fixes the issue of failed to install driver on SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - Remove irqs only when they are set up - Fix guest OS crashes during VFs resets - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - This driver fixes the issue of failed to install driver on SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - Remove irqs only when they are set up - Fix guest OS crashes during VFs resets - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - This driver fixes the issue of failed to install driver on SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - Remove irqs only when they are set up - Fix guest OS crashes during VFs resets - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - This driver fixes the issue of failed to install driver on SLES12SP2 - This driver fixes the Spectre/Meltdown issue. - Added SLES15 Support. - Added RHEL6.10 Support. - Added RHEL7.5 Support. - Added RHEL7u6 Support. - Added SLES12SP4 Support. - This driver fixes the issue when configuring MTU on VF in Guest OS would be failed. - This driver fixes an issue of Infinite recursion in device shutdown path due to a corner case when PCIe link was down - Fix the issue of typo in ethtool stats - Added RHEL7u7 Support. - Added RHEL8 Support. - Added SLES15SP1 Support. - This driver use macro to handle change in nd_tx_timeout. - Remove irqs only when they are set up - Fix guest OS crashes during VFs resets - Add SLES15 SP2 support - This driver add support for new mailbox communication between PF and VF - Initial package - Fix return values and prints in VF MAC add/del flow - Fix kernel panic after transiting FW LLDP from on to off and restarting lldpad - Fix Throughput lower than expected. - Add SLES15 SP2 support - Add RHEL8u3 support - Add RHEL7u9 support - Addressing the issue of system reboot on unloading iavf driver with maxvfs enabled in switchdev mode - Initial package - Fix return values and prints in VF MAC add/del flow - Fix kernel panic after transiting FW LLDP from on to off and restarting lldpad - Fix Throughput lower than expected. - Add SLES15 SP2 support - Add RHEL8u3 support - Add RHEL7u9 support - Addressing the issue of system reboot on unloading iavf driver with maxvfs enabled in switchdev mode - Initial package - Fix return values and prints in VF MAC add/del flow - Fix kernel panic after transiting FW LLDP from on to off and restarting lldpad - Fix Throughput lower than expected. - Add SLES15 SP2 support - Add RHEL8u3 support - Add RHEL7u9 support - Addressing the issue of system reboot on unloading iavf driver with maxvfs enabled in switchdev mode - Initial package - Fix return values and prints in VF MAC add/del flow - Fix kernel panic after transiting FW LLDP from on to off and restarting lldpad - Fix Throughput lower than expected. - Add SLES15 SP2 support - Add RHEL8u3 support - Add RHEL7u9 support - Addressing the issue of system reboot on unloading iavf driver with maxvfs enabled in switchdev mode - Release version 4.18.0-1.rhel7u8 - Release version 4.18.0-1.rhel7u9 - Release version 4.18.0-1.rhel8u4 - Release version 4.18.0-1.rhel8u5 - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules -Added Linux SRIOV support -Added iSCSI & FCoE HBA support for specific HP adapters and devices -Added VC4.10 support -Added BCV support -When GRO setting changes while LRO is enabled, don't reload as LRO takes precedence. -Allow UDP tunneling offload -Enable IPGRE RSS by default -Support different GRE RSS modes. -Add RH5.10 support. -Add RH6.5 support. -FC-TAPE - Host responds early to a requested resend delay - Linux (70101) -SLES11 MEZ75 IO halt with Nexus reboot tests (70728) -SLES 11 blade loses all targets from BLOM port during fabric uplink add/remove (70187) -KVM gso and gro are not working on hv and vm as expected (70506) -SRIOV mtu toggle failure (70530) -SRIOV hv reboots on pf toggle with vfs passed through on it. (70531) -Guest OS dosent boot after attaching VF in RHEL6.3x64bit for 57840 device. (68426) -[NET]SUT reboot&MCE report when create 30th/31st VF on 57810 device on SLES11 SP2. (69263) -RH Cert - RH5 | U8 | v7-1.5-33 | 57810 | Flex Network Test failed. (70427) -BACS 16.2.0: Show ETS/Priority Tagging/PFC as operational when DCBX is disabled on the switch side. (69690) -Incorrect port value is displayed for connected/unconnected ports of 57810 for RHEL5.9 64bits. (68627) -VFs are not getting created for Broadcom adapters in RHEL5.10 OS. (71456) - added RH5.11 support. - added RH6.6 & RH6.7 support. - added RH7.0 & RH7.1 support. - added SLES11-SP4 & SLES12 support. - added VLAN filtering offload support. - added Debian GNU/Linux 7 (wheezy) support. - In RHEL7.0 and 7.1, bnx2x will be rolled back to inbox after system reboot (80071). - SRIOV : MAC address change inside VM is not allowed unless interface is down (80309). - RH7.x: Tunneling offload is not enabled (79269). - self test fails on 20G adapter (79295). - VF interface vlan-filtering stopped working (79365). - Fail to force link speed other than 20G in KR2 (77841). - Incorrect asymmetric flow-control behavior (75504). - Dynamic VF enumeration fails for 578xx adapter in SLES11 SP4 (78590). - Inner-to-outer vlan priority mapping doesn't work (RH6.x [pre 2.6.38 kernels]). - Packets from a VF with pvid configured which were sent with a different vlan were transmitted instead of being discarded. - UDP packets cannot pass to the upper application (5709). - Out of memory issue when the adapter is reset (5709). - iSCSI offload: Driver displaying incorrect remote port (77842). - FCoE offload: Initiators failed FLOGI on SLES 11 SP4 RC1 (79704). -Added Linux SRIOV support -Added iSCSI & FCoE HBA support for specific HP adapters and devices -Added VC4.10 support -Added BCV support -When GRO setting changes while LRO is enabled, don't reload as LRO takes precedence. -Allow UDP tunneling offload -Enable IPGRE RSS by default -Support different GRE RSS modes. -Add RH5.10 support. -Add RH6.5 support. -FC-TAPE - Host responds early to a requested resend delay - Linux (70101) -SLES11 MEZ75 IO halt with Nexus reboot tests (70728) -SLES 11 blade loses all targets from BLOM port during fabric uplink add/remove (70187) -KVM gso and gro are not working on hv and vm as expected (70506) -SRIOV mtu toggle failure (70530) -SRIOV hv reboots on pf toggle with vfs passed through on it. (70531) -Guest OS dosent boot after attaching VF in RHEL6.3x64bit for 57840 device. (68426) -[NET]SUT reboot&MCE report when create 30th/31st VF on 57810 device on SLES11 SP2. (69263) -RH Cert - RH5 | U8 | v7-1.5-33 | 57810 | Flex Network Test failed. (70427) -BACS 16.2.0: Show ETS/Priority Tagging/PFC as operational when DCBX is disabled on the switch side. (69690) -Incorrect port value is displayed for connected/unconnected ports of 57810 for RHEL5.9 64bits. (68627) -VFs are not getting created for Broadcom adapters in RHEL5.10 OS. (71456) - added RH5.11 support. - added RH6.6 & RH6.7 support. - added RH7.0 & RH7.1 support. - added SLES11-SP4 & SLES12 support. - added VLAN filtering offload support. - added Debian GNU/Linux 7 (wheezy) support. - In RHEL7.0 and 7.1, bnx2x will be rolled back to inbox after system reboot (80071). - SRIOV : MAC address change inside VM is not allowed unless interface is down (80309). - RH7.x: Tunneling offload is not enabled (79269). - self test fails on 20G adapter (79295). - VF interface vlan-filtering stopped working (79365). - Fail to force link speed other than 20G in KR2 (77841). - Incorrect asymmetric flow-control behavior (75504). - Dynamic VF enumeration fails for 578xx adapter in SLES11 SP4 (78590). - Inner-to-outer vlan priority mapping doesn't work (RH6.x [pre 2.6.38 kernels]). - Packets from a VF with pvid configured which were sent with a different vlan were transmitted instead of being discarded. - UDP packets cannot pass to the upper application (5709). - Out of memory issue when the adapter is reset (5709). - iSCSI offload: Driver displaying incorrect remote port (77842). - FCoE offload: Initiators failed FLOGI on SLES 11 SP4 RC1 (79704). -Added Linux SRIOV support -Added iSCSI & FCoE HBA support for specific HP adapters and devices -Added VC4.10 support -Added BCV support -When GRO setting changes while LRO is enabled, don't reload as LRO takes precedence. -Allow UDP tunneling offload -Enable IPGRE RSS by default -Support different GRE RSS modes. -Add RH5.10 support. -Add RH6.5 support. -FC-TAPE - Host responds early to a requested resend delay - Linux (70101) -SLES11 MEZ75 IO halt with Nexus reboot tests (70728) -SLES 11 blade loses all targets from BLOM port during fabric uplink add/remove (70187) -KVM gso and gro are not working on hv and vm as expected (70506) -SRIOV mtu toggle failure (70530) -SRIOV hv reboots on pf toggle with vfs passed through on it. (70531) -Guest OS dosent boot after attaching VF in RHEL6.3x64bit for 57840 device. (68426) -[NET]SUT reboot&MCE report when create 30th/31st VF on 57810 device on SLES11 SP2. (69263) -RH Cert - RH5 | U8 | v7-1.5-33 | 57810 | Flex Network Test failed. (70427) -BACS 16.2.0: Show ETS/Priority Tagging/PFC as operational when DCBX is disabled on the switch side. (69690) -Incorrect port value is displayed for connected/unconnected ports of 57810 for RHEL5.9 64bits. (68627) -VFs are not getting created for Broadcom adapters in RHEL5.10 OS. (71456) - added RH5.11 support. - added RH6.6 & RH6.7 support. - added RH7.0 & RH7.1 support. - added SLES11-SP4 & SLES12 support. - added VLAN filtering offload support. - added Debian GNU/Linux 7 (wheezy) support. - In RHEL7.0 and 7.1, bnx2x will be rolled back to inbox after system reboot (80071). - SRIOV : MAC address change inside VM is not allowed unless interface is down (80309). - RH7.x: Tunneling offload is not enabled (79269). - self test fails on 20G adapter (79295). - VF interface vlan-filtering stopped working (79365). - Fail to force link speed other than 20G in KR2 (77841). - Incorrect asymmetric flow-control behavior (75504). - Dynamic VF enumeration fails for 578xx adapter in SLES11 SP4 (78590). - Inner-to-outer vlan priority mapping doesn't work (RH6.x [pre 2.6.38 kernels]). - Packets from a VF with pvid configured which were sent with a different vlan were transmitted instead of being discarded. - UDP packets cannot pass to the upper application (5709). - Out of memory issue when the adapter is reset (5709). - iSCSI offload: Driver displaying incorrect remote port (77842). - FCoE offload: Initiators failed FLOGI on SLES 11 SP4 RC1 (79704). -Added Linux SRIOV support -Added iSCSI & FCoE HBA support for specific HP adapters and devices -Added VC4.10 support -Added BCV support -When GRO setting changes while LRO is enabled, don't reload as LRO takes precedence. -Allow UDP tunneling offload -Enable IPGRE RSS by default -Support different GRE RSS modes. -Add RH5.10 support. -Add RH6.5 support. -FC-TAPE - Host responds early to a requested resend delay - Linux (70101) -SLES11 MEZ75 IO halt with Nexus reboot tests (70728) -SLES 11 blade loses all targets from BLOM port during fabric uplink add/remove (70187) -KVM gso and gro are not working on hv and vm as expected (70506) -SRIOV mtu toggle failure (70530) -SRIOV hv reboots on pf toggle with vfs passed through on it. (70531) -Guest OS dosent boot after attaching VF in RHEL6.3x64bit for 57840 device. (68426) -[NET]SUT reboot&MCE report when create 30th/31st VF on 57810 device on SLES11 SP2. (69263) -RH Cert - RH5 | U8 | v7-1.5-33 | 57810 | Flex Network Test failed. (70427) -BACS 16.2.0: Show ETS/Priority Tagging/PFC as operational when DCBX is disabled on the switch side. (69690) -Incorrect port value is displayed for connected/unconnected ports of 57810 for RHEL5.9 64bits. (68627) -VFs are not getting created for Broadcom adapters in RHEL5.10 OS. (71456) - added RH5.11 support. - added RH6.6 & RH6.7 support. - added RH7.0 & RH7.1 support. - added SLES11-SP4 & SLES12 support. - added VLAN filtering offload support. - added Debian GNU/Linux 7 (wheezy) support. - In RHEL7.0 and 7.1, bnx2x will be rolled back to inbox after system reboot (80071). - SRIOV : MAC address change inside VM is not allowed unless interface is down (80309). - RH7.x: Tunneling offload is not enabled (79269). - self test fails on 20G adapter (79295). - VF interface vlan-filtering stopped working (79365). - Fail to force link speed other than 20G in KR2 (77841). - Incorrect asymmetric flow-control behavior (75504). - Dynamic VF enumeration fails for 578xx adapter in SLES11 SP4 (78590). - Inner-to-outer vlan priority mapping doesn't work (RH6.x [pre 2.6.38 kernels]). - Packets from a VF with pvid configured which were sent with a different vlan were transmitted instead of being discarded. - UDP packets cannot pass to the upper application (5709). - Out of memory issue when the adapter is reset (5709). - iSCSI offload: Driver displaying incorrect remote port (77842). - FCoE offload: Initiators failed FLOGI on SLES 11 SP4 RC1 (79704). - Version 8.18.18.0 - Added missing support to configure 1G speed via ethtool - Fixed calculation of number of ooo rx buffers and limit to 16K - Version 8.18.17.0-1 - iWARP - Handle flush completion on unaligned ll2 connection - Add dp_module, dp_level as modparams - Add Kconfig file for upstream builds - Version 8.18.16.0-1 - Fix missing return error code check on call to qedi_setup_int - Modify different module params - Add log message in the driver unload path - Fail all non-timesync related ioctls - Version 8.18.15.0-1 - Added wwpn and wwnn to the FCoE dev-info - Validate chap and mutual chap auth correctly - Version 8.18.14.0-1 - Fix error handling flow in TX path - Fix error handling flow in RX path - Implement get_protocol_tlv_data callback - Version 8.18.18.0 - Added missing support to configure 1G speed via ethtool - Fixed calculation of number of ooo rx buffers and limit to 16K - Version 8.18.17.0-1 - iWARP - Handle flush completion on unaligned ll2 connection - Add dp_module, dp_level as modparams - Add Kconfig file for upstream builds - Version 8.18.16.0-1 - Fix missing return error code check on call to qedi_setup_int - Modify different module params - Add log message in the driver unload path - Fail all non-timesync related ioctls - Version 8.18.15.0-1 - Added wwpn and wwnn to the FCoE dev-info - Validate chap and mutual chap auth correctly - Version 8.18.14.0-1 - Fix error handling flow in TX path - Fix error handling flow in RX path - Implement get_protocol_tlv_data callback - Version 8.18.18.0 - Added missing support to configure 1G speed via ethtool - Fixed calculation of number of ooo rx buffers and limit to 16K - Version 8.18.17.0-1 - iWARP - Handle flush completion on unaligned ll2 connection - Add dp_module, dp_level as modparams - Add Kconfig file for upstream builds - Version 8.18.16.0-1 - Fix missing return error code check on call to qedi_setup_int - Modify different module params - Add log message in the driver unload path - Fail all non-timesync related ioctls - Version 8.18.15.0-1 - Added wwpn and wwnn to the FCoE dev-info - Validate chap and mutual chap auth correctly - Version 8.18.14.0-1 - Fix error handling flow in TX path - Fix error handling flow in RX path - Implement get_protocol_tlv_data callback - Version 8.18.18.0 - Added missing support to configure 1G speed via ethtool - Fixed calculation of number of ooo rx buffers and limit to 16K - Version 8.18.17.0-1 - iWARP - Handle flush completion on unaligned ll2 connection - Add dp_module, dp_level as modparams - Add Kconfig file for upstream builds - Version 8.18.16.0-1 - Fix missing return error code check on call to qedi_setup_int - Modify different module params - Add log message in the driver unload path - Fail all non-timesync related ioctls - Version 8.18.15.0-1 - Added wwpn and wwnn to the FCoE dev-info - Validate chap and mutual chap auth correctly - Version 8.18.14.0-1 - Fix error handling flow in TX path - Fix error handling flow in RX path - Implement get_protocol_tlv_data callback - 10.02.01.00.a14-k1 BH 11/06/2020 - ER146725: eDIF another driver panic running script: ./test_target_no_unload.sh Change: qla2xxx: Fix crash in qla_nvme_abort_set_option. - ER147771: Call Trace while shutting down the adapter ports (LINK DOWN). Change: qla2xxx: Handle aborts correctly for port undergoing deletion. - ERXXXXXX: qla2xxx: Add scsi_change_queue_depth to slave configure. - 10.02.02.00.a13-k1 BH 10/28/2020 - ER147600: Cisco: rpd ELS cmd fail to fetch the speed capabilities Change: qla2xxx: Used correct rdp spec, which was broken during code clean-up. - ER147695: FC-NVMe target discovery fails when initator wwpn < target wwpn in an N2N (Direct Attach) config Change: qla2xxx: fix N2N + NVME connect retry fail - ER147832: Issue with uSCM Linux with QCC CLI for some configuration Change: qla2xxx: Show event severity only when device state is congested. - ER147824 : scmr_stat sysfs node runs out of memory Change: qla2xxx: Come up with a compact version of scmr_stat - ER147823: NVMe IO is not getting throttled up or down. Change: qla2xxx: Enable throttle control for NVMe targets for Peer Congestion. - ERXXXXXX: qla2xxx: Count tgt short term link if link comes back before dev_loss_tmo. - ERXXXXXX: qla2xxx: Correct the check for fcport while displaying target counters. - ERXXXXXX: qla2xxx: Change trigger for host short term link down to dev loss tmo. - ERXXXXXX: qla2xxx: Move an SCM log under a debug level. - ERXXXXXX: qla2xxx: Set vendor_rsp[0] value. - ERXXXXXX: qla2xxx: Make throttling messages more informative. - 10.02.02.00.a12-k1 SK 10/15/2020 - ER147625: NVMe IO's are failing with Read/Write after LIP reset. Change: qla2xxx:Return EBUSY until the remote port delete finishes. - ER147653: Target side strongswan start/stop, make initiator crashed. Change: qla2xxx: edif: v2 fix double bsg done. - ER147791: USCM: clear option is not clearing hba alarm/warning, or clear cong or nvme target stats. Change: qla2xxx: Clear Sev and NVMe Target Stats. - ER147793: USCM: Throttling has wrong throttling up info and event period is not honored. Change: qla2xxx: Fix Throttling algorithm regression. - ER147759: NVMe Admin commands are getting throttled and causing admin queue failures. Change: qla2xxx: Throttle NVMe I/O commands only. - ERXXXXXX: qla2xxx: edif: fix aes_gmac mode. - ERXXXXXX: qla2xxx: edif: v2: standardize on port_id_t for bsg api. - ERXXXXXX: qla2xxx: edif: fix 4byte align. - ERXXXXXX: qla2xxx: edif: fix ELS meta data. - ERXXXXXX: qla2xxx: Clear Congestion State/Throttling during chip Reset. - ERXXXXXX: qla2xxx: Clear SCM Severity as part of SCM Stats Clear. - 10.02.00.02.a11-k1 BH 10/09/2020 - ER147734 : Lip reset on the isolated port causes server crash Change: qla2xxx: Don't allow FW, MPI and lip reset on isolated port. - ER147479 - PPC BE RH7.6 - qla2xxx driver loading - machine crashed. Change: qla2xxx: Fixes for big endian machines - ER147646: Call Trace observed while validating a MPI Pause test scenario. Change: qla2xxx: Correct the WARN_ON check in qla_nvme_abort_set_option. - ER147615: Throttling does not work with low I/Os. Change: qla2xxx: Check and round off fractional I/Os to 1 on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: List NVMe targets under scmr_stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Don't check for port isolation during abort isp. - ERXXXXXX: qla2xxx: SCM: Turn off SCM port parameter update mailbox command. - ERXXXXXX: qla2xxx: Fix I/O failures during remote port toggle testing - 10.02.00.02.a10-k1 BH 09/25/2020 SCM Changes: - ERXXXXXX: Changes - qla2xxx: Clear Congestion state when an RSCN is received/target is torn down. qla2xxx: throttling algorithm improvement. qla2xxx: Add throttling support for NVMe targets. EDIF Changes: - ERXXXXX: LUN loss on ipsec stop/start on target side. Change: save Nport on receive of PLOGI - ERXXXXX: fix ELS receive collision between physical and NPIV hosts. Change: remove erroneous source Nport ID search. - ER147570: FCP Performance Drop in latest driver for smaller IOs size. Change: qla2xxx: Change WQ_UNBOUND to WQ_MEM_RECLAIM. WQ_MEM_RECLAIM : wq is guaranteed to have at least one execution context regardless of memory pressure. - ER147632: QLE2774: RHEL 8.2 System crashes while upgrading he FW from 9.6.0 to 9.6.1 with QCC CLI build 12 Change: qla2xxx: Fix system crash on nvme abort path by checking sp of aborting command before accessing it. - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. - ER147645: System panic while trying to capture debugfs stats for EED. Change: qla2xxx: Check rport before accessing target number. - ER147632: Fix potential stale mem access Change: remove stale sp pointer reference - CQXXXXXX: FPIN events are not readily decodable. Change: qla2xxx: Make FPIN events prints human readable. - ER146879: Add support to clear SCM Stats Change: qla2xxx: Added support to clear SCM/SCMR Stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Allow get host stat during reset and sync reset. - ERXXXXXX: qla2xxx: Set reset_cmd_err_cnt on reset failure only. - ERXXXXXX: qla2xxx: Add isolated flag and return EPERM on isolation. - ERXXXXXX: qla2xxx: Count short term link if link comes back in 10 sec. - ERXXXXXX: qla2xxx: Don't check for fw_started while posting nvme command. - ERXXXXXX: qla2xxx: Pass irq_offset to blk_mq_pci_map_queues API. - ERXXXXXX: qla2xxx: lockdown: fix stale sp access. - BZ1868688: qla2xxx: tear down session if FW say its down. - 10.02.00.02.a9-k1 BH 09/03/2020 - ER147554 - sg_reset appears hung iterating over too many Qpairs. Change - qla2xxx: limit interrupt vectors to number of cpu. - ERXXXXX - qla2xxx: klocwork: Fix Bit field 'mpi_-' has one bit and is signed. - ERXXXXX - qla2xxx: Change post del message from debug level to log level. - ERXXXXX - qla2xxx: lockdown: fixup - Change error response as per API test. - ERXXXXX - qla2xxx: Fix map_queue interface to use the correct blk-mq call. - ERXXXXX - Added Structural changes for SCM Phase 2 support. Change : qla2xxx: Update structure definitions for SCM to support backward compatibility. - 10.02.00.02.a8-k1 BH 08/30/2020 - ERXXXXXX - Fix point-to-point (N2N) device discovery issue. Change - qla2xxx: Fix point-to-point (N2N) device discovery issue. - ERXXXXXX - To wait for ABTS response on I/O timeouts for NVMe. Change - qla2xxx: To wait for ABTS response on I/O timeouts for NVMe. - ER147523 - BSG stack trace and SCM display issues. Change - SCM: Functional regression with a6 release. - ER 147413 - edif: Fix issue with DIF enable target discovery. Change - qla2xxx: edif: Fix issue with DIF enable target discovery. - ER147480 clear ASYNC_ACTIVE flag to allow relogin. Change - qla2xxx: fix stuck session. - ERXXXXXX - lockdown: add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - 10.02.00.02.a7-k1 BH 08/22/2020 - ER147495 - edif changes Change - qla2xxx: edif: fix nvme discovery failure qla2xxx: edif: fix els corruption. - ERXXXXXX - add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - ERXXXXXX: SCMR changes Change - qla2xxx: SCMR: Correct scmr_outstanding_reqs accounting. qla2xxx: SCM: Changes to segregate current_events and current_state. qla2xxx: SCMR: Increase local array size. - ER147298 : USCM "Congestion Warning" counter regression Change - qla2xxx: Correct FPIN Structure Definition (Severity). - 10.02.00.02.a6-k1 BH 08/13/2020 - ERXXXXXX - fix crash on session cleanup + unload. Change - qla2xxx: fix crash on session cleanup + unload. - ER147329 - edif changes Change - qla2xxx: edif: fix compile error. do not submit qla2xxx: edif: fix double free on ELS send failure. qla2xxx: edif: reject els if non secure device. qla2xxx: edif: reject ELS on session down. qla2xxx: edif: redefine purex dest addr to be more consistent. qla2xxx: edif: tweak debug messages. qla2xxx: edif: fix nvme+edif target connect problem. - ER147460 - issue with Diag test on QCC CLI 2.4.0 build 10 with 10.2.00.2-a5 driver Change - qla2xxx: edif: move bsg auth els into separate routine. qla2xxx: edif: Fix error in BSG ELS path that has valid response data. - ER147312 - Add support to report MPI FW state. Change - qla2xxx: Add support to report MPI FW state. qla2xxx: Fix reset of MPI firmware. qla2xxx: Fix MPI reset needed message. - 10.02.00.02.a5-k1 BH 07/31/2020 - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. Change - qla2xxx: Don't process target debugfs stats if port is isolated. - ERXXXXXX : Add SCM stats to scmr_stats node. Change - qla2xxx: Add SCM stats to scmr_stats node. - ER147419 : Fix crash due to request q pointer extraction failure. Change - qla2xxx: Latency measurement patch. - ERXXXXXX : edif: remove redundant field in port_id_t Change -qla2xxx: edif: remove redundant field in port_id_t - ER147331 : extract bbc from PLOGI template payload. Change -qla2xxx: Fix buffer-buffer credit extraction error - ERXXXXXX : Split qla2x00_configure_local_loop() Change scsi: qla2xxx: Split qla2x00_configure_local_loop() - ERXXXXXX : SCMR - Add I/O flow control. Change - qla2xxx: SCMR - Add I/O flow control. - 10.02.00.02.a4-k1 BH 07/23/2020 - ER147402 - Do not install nvme auto connect script if OS is installing it. Change - qla2xxx: auto-connect scripts are install based on nvme-cli package. - ERXXXXXX - Fixed return status of nvme fcp request. Change - qla2xxx: Set NVME status code for failed NVME FCP request. - ERXXXXXX - Multi-que support for TMF. Change - qla2xxx: Multi-que support for TMF. - ERXXXXXX ? edif changes Change - qla2xxx: edif: simplify reserve/release of sa_index. qla2xxx: edif: tweak debug log. qla2xxx: edif: adjust ELS resp length. qla2xxx: edif: send logo on app stop. qla2xxx: edif: remove prlo in session deletion. qla2xxx: edif: Fix app stop stall. - ER147298 - USCM "Congestion Warning" counter regression w/.65 driver. Change - qla2xxx: Correct fpin_descriptor definition. qla2xxx: Consolidate EDIF & SCM Purex Calls. - ERXXXXXX - Calculate avg. time taken by different components for IO completion. Change - qla2xxx: Latency measurement patch. - 10.02.00.02.a3-k1 BH 07/16/2020 - ER147348 - Observing the firmware dump while running the qaucli -g post port isolation. Change - qla2xxx: Don't check firmware state in case of chip is down. - ER147338 - SLES: Driver load failed - modprobe: ERROR: module 'qla2xxx' is unsupported Change - qla2xxx: Add support for loading external modules on SuSE. - ER147361 - System panic after enabling port isolated during TimeOutReset. Change - qla2xxx: Synchronize the update the host counters using lock. - ER147370 - Hardware Error counter not incrementing for MBX command timeout Change - qla2xxx: Update hardware error count for various error conditions. - ERXXXXXX - The change is to help in debuggging. Change - qla2xxx: Move some messages from debug to normal log level. - ER147346 - Observed a call trace after port isolation. Change - qla2xxx: Fix the call trace for flush workqueue. - ERXXXXXX - For debug purpose Change - qla2xxx: Add error counters to debugfs node - 10.02.00.02.a2-k1 AE 07/10/2020 - ERXXXXXX - qla2xxx: Fix TCM compilation issues. Change - Enabled build of tcm_qla2xxx module and fixed compile issues. - ERXXXXXX - qla2xxx: edif : Added back the app_stop wait and avoid if link is down. Change - Added wait during app stop. - ERXXXXXX - qla2xxx: Set BIT_13 for NVMe Async events. Change - Driver changes to skip SLER for Async event command. - ER147323 - qla2xxx: Correct the check for sscanf return value. Change - Driver updated to check version correctly. - ERXXXXXX - qla2xxx: v2: Add EDIF support. Change - Refactoring EDIF code for modularity. - ER147298 - Congestion Warning/Alarm counters fail to increment Change - Update driver to increment the counters for congestion signals. - 10.02.00.02.a1-k1 AE 06/29/2020 - qla2xxx: Enable IOCB throttling by default. - qla2xxx: Implementation to get and manage host, target stats and initiator port. - qla2xxx: Add SLER and PI control support. - qla2xxx: Do not log message when reading port speed via sysfs - qla2xxx: fix null pointer access. - qla2xxx: Use MPI hang trigger to do PEGTUNE halt. - qla2xxx: Reduce erroneous error in link reset path - qla2xxx: v2: fix stalled N2N reconnect. - qla2xxx: Fix warnings on SLES12SP5. - qla2xxx: Fix compilation issues on SLES15 - qla2xxx: Compilation Fixes for SLES15SP1. - qla2xxx: Debugfs compilation issue fix for RH7.6. - qla2xxx: Fix gcc test compile error output being printed. - qla2xxx: Timestamp device online and offline transitions. - qla2xxx: Add rport fields in debugfs. - qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices. - qla2xxx: Setup debugfs entries for remote ports. - qla2xxx: Fix edif related compilation issue on RH7.6. - Fixes for compilation on hpe branch - qla2xxx: Compilation fixes for RH8.2 - qla2xxx: Compilation changes for RH7.6 - qla2xxx: Fixes for compilation on RH7.x I - qla2xxx: bsg_job to bsg_job_t - qla2xxx: I Unify source code to work with newer kernels. - qla2xxx: Makefile changes from code-uni-devel-10x. - qla2xxx: qla_edif file changes to compile the driver. - qla2xxx: Fix compilation issues. - qla2xxx: Fix Makefile issue. - qla2xxx: fix compile error - qla2xxx: Use explicit LOGO in target mode - qla2xxx: Add EDIF support. - qla2xxx: Addd edif related files. - qla2xxx: Fix MPI failure AEN (8200) handling. - qla2xxx: SCM - Backport optimizations and style changes from upstream work. - qla2xxx: Fix warning in qla_attr.c file. - qla2xxx: Fix nvme compilation error. - qla2xxx: Fix crash in alloc w/GFP_KERNEL + interrupt - Author : Quinn Tran <qutran@marvell.com> qla2xxx: v2: add iocb resource tracking. - qla2xxx: Fix WARN_ON in qla_nvme_register_hba. - qla2xxx: Allow ql2xextended_error_logging special value 1 to be set anytime. - qla2xxx: Make tgt_port_database available in initiator mode. - qla2xxx: reduce noisy debug message. - qla2xxx: Fix mailbox Ch erroneous error - qla2xxx: fix login timeout. - qla2xxx: Accomodate for SCM FW attribute bit change. - qla2xxx: post FC event (FPIN) to transport FPIN handler. - qla2xxx: Hide fc_host_fpin_rcv kernel dependency. - qla2xxx: Add changes to compile across various kernels. - qla2xxx: Use active targets to update SCM stats. - qla2xxx: Move SCM functions to qla_isr to keep changes local. - qla2xxx: Code to process FLOGI ACC extended payload. - qedf: Fix compilation issue - revisit. - qla2xxx: SCM Phase 1 Implementation + 2 other patches. - qla2xxx: Enable PUREX passthru post ISP reset. - qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV. - qla2xxx: performance tweak - scsi: qla2xxx: fix fcport null pointer access. - fixup! qla2xxx: Fix unbound NVME response length. - scsi: qla2xxx: Fix unbound NVME response length - qla2xxx: Add host attribute to trigger MPI hang. - qla2xxx: ONEOFF: silent dbg messages for good path io. - qla2xxx: ONEOFF: fix pDIF detection - qla2xxx: Snoop inquiry response atleast 168 bytes to determine proprietary DIF. - qla2xxx: ONEOFF: add debug counters for T10-PI/DIF - qla2xxx: ONEOFF: add MQ support for HP3PAR propritary T10-PI - qla2xxx: HPE 3PAR private T10-PI support. - qla2xxx: Check for fabric_priority flag during login - qla2xxx: use iocb_fabric_priority flag - qla2xxx: Fix QoS name and add debug logs - qla2xxx: Correction to tests for iocb fabric and fcport qos. - qla2xxx: Use ->isp_ops->read_optrom() in qla26xx_read_qos_fcport_table(). - qla2xxx: QoS fcport table index initialization improvement. - qla2xxx: Add QoS fcport table index to speed up search. - qla2xxx: Reduce stack on qos fcport priority routines. - qla2xxx: HPE: Register FDMI QOS - qla2xxx: Add bsg interface for qos lun level bitmask. - qla2xxx: Read E2E QoS fcport priority bitmasks from flash. - qla2xxx: Abstract qos lun level mask for iocb cs_ctl field. - qla2xxx: Add fabric priority qos lun iocb mechanism. - qla2xxx: Implement CT command GFO (Get Fabric Object). - qla2xxx: Add support for fabric priority per target. - qla2xxx: fix mtcp dump collection failure. - qla2xxx: Set Nport ID for N2N - qla2xxx: Fix crash during device discovery. - qla2xxx: Handle NVME status iocb correctly. - qla2xxx: Remove restriction of FC T10-PI and NVME - qla2xxx: serialize fc_port alloc in N2N - qla2xxx: NPIV does not come up after FW dump. - qla2xxx: fix RDP respond data format bug. - qla2xxx: force semaphore on flash validation failure. - qla2xxx: add more FW debug information - qla2xxx: Revert: Disable T10-DIF feature with FC-NVMe during probe - qla2xxx: Update BPM enablement semantics. - qla2xxx: fix FW resource print error. - qla2xxx: Use a dedicated interrupt handler for 'handshake-required' ISPs. - qla2xxx: Ensure flash updates return possible failure status through bsg interface. - qla2xxx: Improved secure flash support messages - qla2xxx: fix flag passing error - qla2xxx: Use FC generic update firmware options routine for ISP27xx. - qla2xxx: Avoid setting firmware options twice in 24xx_update_fw_options. - qla2xxX: Add 16.0GT for PCI String - qla2xxx: Use FW_STARTED macro - qla2xxx: Add fixes for mailbox command - qla2xxx: Fix login IOCB flag - qla2xxx: Save rscn_gen for new fcport - qla2xxx: firmware option 3 is clobbered by speed set - qla2xxx: ISP28xx active FW region - qla2xxx: Add portname to print logs in qla24xx_logio_entry(). - qla2xxx: Correction to MB in-direction selection in qla2x00_echo_test(). - qla2xxx: Correction to selection of loopback/echo test. - qla2xxx: Use endian macros to assign static fields in fwdump header. - qla2xxx: Add Speed in SFP print information - qla2xxx: Fix RDP response size - qla2xxx: Handle cases for limiting RDP response payload length. - qla2xxx: Add deferred queue for processing ABTS and RDP. - qla2xxx: Cleanup ELS/PUREX iocb fields. - qla2xxx: Add devid's and conditionals for 28xx. - qla2xxx: Add vendor extended FDMI additions and amendments. - qla2xxx: Provide separate RDP enable. - qla2xxx: Add vendor extended RDP additions and amendments. - qla2xxx: Add changes in preparation for vendor extended FDMI/RDP. - qla2xxx: Add 2061 PCI ID - qla2xxx: Remove all DIX-0 references - qla2xxx: Add endianizer macro calls to fc host stats. - qla2xxx: Add sysfs node for D-Port Diagnostics AEN data. - qla2xxx: Move free of fcport out of interrupt context. - qla2xxx: Add beacon LED config sysfs interface. - qla2xxx: Add sysfs hooks for FC-NVMe autoconnect - 10.01.00.22-k AE 06/29/2020 - Upstream driver as part of Linux 5.6 - 10.02.01.00.a14-k1 BH 11/06/2020 - ER146725: eDIF another driver panic running script: ./test_target_no_unload.sh Change: qla2xxx: Fix crash in qla_nvme_abort_set_option. - ER147771: Call Trace while shutting down the adapter ports (LINK DOWN). Change: qla2xxx: Handle aborts correctly for port undergoing deletion. - ERXXXXXX: qla2xxx: Add scsi_change_queue_depth to slave configure. - 10.02.02.00.a13-k1 BH 10/28/2020 - ER147600: Cisco: rpd ELS cmd fail to fetch the speed capabilities Change: qla2xxx: Used correct rdp spec, which was broken during code clean-up. - ER147695: FC-NVMe target discovery fails when initator wwpn < target wwpn in an N2N (Direct Attach) config Change: qla2xxx: fix N2N + NVME connect retry fail - ER147832: Issue with uSCM Linux with QCC CLI for some configuration Change: qla2xxx: Show event severity only when device state is congested. - ER147824 : scmr_stat sysfs node runs out of memory Change: qla2xxx: Come up with a compact version of scmr_stat - ER147823: NVMe IO is not getting throttled up or down. Change: qla2xxx: Enable throttle control for NVMe targets for Peer Congestion. - ERXXXXXX: qla2xxx: Count tgt short term link if link comes back before dev_loss_tmo. - ERXXXXXX: qla2xxx: Correct the check for fcport while displaying target counters. - ERXXXXXX: qla2xxx: Change trigger for host short term link down to dev loss tmo. - ERXXXXXX: qla2xxx: Move an SCM log under a debug level. - ERXXXXXX: qla2xxx: Set vendor_rsp[0] value. - ERXXXXXX: qla2xxx: Make throttling messages more informative. - 10.02.02.00.a12-k1 SK 10/15/2020 - ER147625: NVMe IO's are failing with Read/Write after LIP reset. Change: qla2xxx:Return EBUSY until the remote port delete finishes. - ER147653: Target side strongswan start/stop, make initiator crashed. Change: qla2xxx: edif: v2 fix double bsg done. - ER147791: USCM: clear option is not clearing hba alarm/warning, or clear cong or nvme target stats. Change: qla2xxx: Clear Sev and NVMe Target Stats. - ER147793: USCM: Throttling has wrong throttling up info and event period is not honored. Change: qla2xxx: Fix Throttling algorithm regression. - ER147759: NVMe Admin commands are getting throttled and causing admin queue failures. Change: qla2xxx: Throttle NVMe I/O commands only. - ERXXXXXX: qla2xxx: edif: fix aes_gmac mode. - ERXXXXXX: qla2xxx: edif: v2: standardize on port_id_t for bsg api. - ERXXXXXX: qla2xxx: edif: fix 4byte align. - ERXXXXXX: qla2xxx: edif: fix ELS meta data. - ERXXXXXX: qla2xxx: Clear Congestion State/Throttling during chip Reset. - ERXXXXXX: qla2xxx: Clear SCM Severity as part of SCM Stats Clear. - 10.02.00.02.a11-k1 BH 10/09/2020 - ER147734 : Lip reset on the isolated port causes server crash Change: qla2xxx: Don't allow FW, MPI and lip reset on isolated port. - ER147479 - PPC BE RH7.6 - qla2xxx driver loading - machine crashed. Change: qla2xxx: Fixes for big endian machines - ER147646: Call Trace observed while validating a MPI Pause test scenario. Change: qla2xxx: Correct the WARN_ON check in qla_nvme_abort_set_option. - ER147615: Throttling does not work with low I/Os. Change: qla2xxx: Check and round off fractional I/Os to 1 on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: List NVMe targets under scmr_stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Don't check for port isolation during abort isp. - ERXXXXXX: qla2xxx: SCM: Turn off SCM port parameter update mailbox command. - ERXXXXXX: qla2xxx: Fix I/O failures during remote port toggle testing - 10.02.00.02.a10-k1 BH 09/25/2020 SCM Changes: - ERXXXXXX: Changes - qla2xxx: Clear Congestion state when an RSCN is received/target is torn down. qla2xxx: throttling algorithm improvement. qla2xxx: Add throttling support for NVMe targets. EDIF Changes: - ERXXXXX: LUN loss on ipsec stop/start on target side. Change: save Nport on receive of PLOGI - ERXXXXX: fix ELS receive collision between physical and NPIV hosts. Change: remove erroneous source Nport ID search. - ER147570: FCP Performance Drop in latest driver for smaller IOs size. Change: qla2xxx: Change WQ_UNBOUND to WQ_MEM_RECLAIM. WQ_MEM_RECLAIM : wq is guaranteed to have at least one execution context regardless of memory pressure. - ER147632: QLE2774: RHEL 8.2 System crashes while upgrading he FW from 9.6.0 to 9.6.1 with QCC CLI build 12 Change: qla2xxx: Fix system crash on nvme abort path by checking sp of aborting command before accessing it. - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. - ER147645: System panic while trying to capture debugfs stats for EED. Change: qla2xxx: Check rport before accessing target number. - ER147632: Fix potential stale mem access Change: remove stale sp pointer reference - CQXXXXXX: FPIN events are not readily decodable. Change: qla2xxx: Make FPIN events prints human readable. - ER146879: Add support to clear SCM Stats Change: qla2xxx: Added support to clear SCM/SCMR Stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Allow get host stat during reset and sync reset. - ERXXXXXX: qla2xxx: Set reset_cmd_err_cnt on reset failure only. - ERXXXXXX: qla2xxx: Add isolated flag and return EPERM on isolation. - ERXXXXXX: qla2xxx: Count short term link if link comes back in 10 sec. - ERXXXXXX: qla2xxx: Don't check for fw_started while posting nvme command. - ERXXXXXX: qla2xxx: Pass irq_offset to blk_mq_pci_map_queues API. - ERXXXXXX: qla2xxx: lockdown: fix stale sp access. - BZ1868688: qla2xxx: tear down session if FW say its down. - 10.02.00.02.a9-k1 BH 09/03/2020 - ER147554 - sg_reset appears hung iterating over too many Qpairs. Change - qla2xxx: limit interrupt vectors to number of cpu. - ERXXXXX - qla2xxx: klocwork: Fix Bit field 'mpi_-' has one bit and is signed. - ERXXXXX - qla2xxx: Change post del message from debug level to log level. - ERXXXXX - qla2xxx: lockdown: fixup - Change error response as per API test. - ERXXXXX - qla2xxx: Fix map_queue interface to use the correct blk-mq call. - ERXXXXX - Added Structural changes for SCM Phase 2 support. Change : qla2xxx: Update structure definitions for SCM to support backward compatibility. - 10.02.00.02.a8-k1 BH 08/30/2020 - ERXXXXXX - Fix point-to-point (N2N) device discovery issue. Change - qla2xxx: Fix point-to-point (N2N) device discovery issue. - ERXXXXXX - To wait for ABTS response on I/O timeouts for NVMe. Change - qla2xxx: To wait for ABTS response on I/O timeouts for NVMe. - ER147523 - BSG stack trace and SCM display issues. Change - SCM: Functional regression with a6 release. - ER 147413 - edif: Fix issue with DIF enable target discovery. Change - qla2xxx: edif: Fix issue with DIF enable target discovery. - ER147480 clear ASYNC_ACTIVE flag to allow relogin. Change - qla2xxx: fix stuck session. - ERXXXXXX - lockdown: add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - 10.02.00.02.a7-k1 BH 08/22/2020 - ER147495 - edif changes Change - qla2xxx: edif: fix nvme discovery failure qla2xxx: edif: fix els corruption. - ERXXXXXX - add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - ERXXXXXX: SCMR changes Change - qla2xxx: SCMR: Correct scmr_outstanding_reqs accounting. qla2xxx: SCM: Changes to segregate current_events and current_state. qla2xxx: SCMR: Increase local array size. - ER147298 : USCM "Congestion Warning" counter regression Change - qla2xxx: Correct FPIN Structure Definition (Severity). - 10.02.00.02.a6-k1 BH 08/13/2020 - ERXXXXXX - fix crash on session cleanup + unload. Change - qla2xxx: fix crash on session cleanup + unload. - ER147329 - edif changes Change - qla2xxx: edif: fix compile error. do not submit qla2xxx: edif: fix double free on ELS send failure. qla2xxx: edif: reject els if non secure device. qla2xxx: edif: reject ELS on session down. qla2xxx: edif: redefine purex dest addr to be more consistent. qla2xxx: edif: tweak debug messages. qla2xxx: edif: fix nvme+edif target connect problem. - ER147460 - issue with Diag test on QCC CLI 2.4.0 build 10 with 10.2.00.2-a5 driver Change - qla2xxx: edif: move bsg auth els into separate routine. qla2xxx: edif: Fix error in BSG ELS path that has valid response data. - ER147312 - Add support to report MPI FW state. Change - qla2xxx: Add support to report MPI FW state. qla2xxx: Fix reset of MPI firmware. qla2xxx: Fix MPI reset needed message. - 10.02.00.02.a5-k1 BH 07/31/2020 - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. Change - qla2xxx: Don't process target debugfs stats if port is isolated. - ERXXXXXX : Add SCM stats to scmr_stats node. Change - qla2xxx: Add SCM stats to scmr_stats node. - ER147419 : Fix crash due to request q pointer extraction failure. Change - qla2xxx: Latency measurement patch. - ERXXXXXX : edif: remove redundant field in port_id_t Change -qla2xxx: edif: remove redundant field in port_id_t - ER147331 : extract bbc from PLOGI template payload. Change -qla2xxx: Fix buffer-buffer credit extraction error - ERXXXXXX : Split qla2x00_configure_local_loop() Change scsi: qla2xxx: Split qla2x00_configure_local_loop() - ERXXXXXX : SCMR - Add I/O flow control. Change - qla2xxx: SCMR - Add I/O flow control. - 10.02.00.02.a4-k1 BH 07/23/2020 - ER147402 - Do not install nvme auto connect script if OS is installing it. Change - qla2xxx: auto-connect scripts are install based on nvme-cli package. - ERXXXXXX - Fixed return status of nvme fcp request. Change - qla2xxx: Set NVME status code for failed NVME FCP request. - ERXXXXXX - Multi-que support for TMF. Change - qla2xxx: Multi-que support for TMF. - ERXXXXXX ? edif changes Change - qla2xxx: edif: simplify reserve/release of sa_index. qla2xxx: edif: tweak debug log. qla2xxx: edif: adjust ELS resp length. qla2xxx: edif: send logo on app stop. qla2xxx: edif: remove prlo in session deletion. qla2xxx: edif: Fix app stop stall. - ER147298 - USCM "Congestion Warning" counter regression w/.65 driver. Change - qla2xxx: Correct fpin_descriptor definition. qla2xxx: Consolidate EDIF & SCM Purex Calls. - ERXXXXXX - Calculate avg. time taken by different components for IO completion. Change - qla2xxx: Latency measurement patch. - 10.02.00.02.a3-k1 BH 07/16/2020 - ER147348 - Observing the firmware dump while running the qaucli -g post port isolation. Change - qla2xxx: Don't check firmware state in case of chip is down. - ER147338 - SLES: Driver load failed - modprobe: ERROR: module 'qla2xxx' is unsupported Change - qla2xxx: Add support for loading external modules on SuSE. - ER147361 - System panic after enabling port isolated during TimeOutReset. Change - qla2xxx: Synchronize the update the host counters using lock. - ER147370 - Hardware Error counter not incrementing for MBX command timeout Change - qla2xxx: Update hardware error count for various error conditions. - ERXXXXXX - The change is to help in debuggging. Change - qla2xxx: Move some messages from debug to normal log level. - ER147346 - Observed a call trace after port isolation. Change - qla2xxx: Fix the call trace for flush workqueue. - ERXXXXXX - For debug purpose Change - qla2xxx: Add error counters to debugfs node - 10.02.00.02.a2-k1 AE 07/10/2020 - ERXXXXXX - qla2xxx: Fix TCM compilation issues. Change - Enabled build of tcm_qla2xxx module and fixed compile issues. - ERXXXXXX - qla2xxx: edif : Added back the app_stop wait and avoid if link is down. Change - Added wait during app stop. - ERXXXXXX - qla2xxx: Set BIT_13 for NVMe Async events. Change - Driver changes to skip SLER for Async event command. - ER147323 - qla2xxx: Correct the check for sscanf return value. Change - Driver updated to check version correctly. - ERXXXXXX - qla2xxx: v2: Add EDIF support. Change - Refactoring EDIF code for modularity. - ER147298 - Congestion Warning/Alarm counters fail to increment Change - Update driver to increment the counters for congestion signals. - 10.02.00.02.a1-k1 AE 06/29/2020 - qla2xxx: Enable IOCB throttling by default. - qla2xxx: Implementation to get and manage host, target stats and initiator port. - qla2xxx: Add SLER and PI control support. - qla2xxx: Do not log message when reading port speed via sysfs - qla2xxx: fix null pointer access. - qla2xxx: Use MPI hang trigger to do PEGTUNE halt. - qla2xxx: Reduce erroneous error in link reset path - qla2xxx: v2: fix stalled N2N reconnect. - qla2xxx: Fix warnings on SLES12SP5. - qla2xxx: Fix compilation issues on SLES15 - qla2xxx: Compilation Fixes for SLES15SP1. - qla2xxx: Debugfs compilation issue fix for RH7.6. - qla2xxx: Fix gcc test compile error output being printed. - qla2xxx: Timestamp device online and offline transitions. - qla2xxx: Add rport fields in debugfs. - qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices. - qla2xxx: Setup debugfs entries for remote ports. - qla2xxx: Fix edif related compilation issue on RH7.6. - Fixes for compilation on hpe branch - qla2xxx: Compilation fixes for RH8.2 - qla2xxx: Compilation changes for RH7.6 - qla2xxx: Fixes for compilation on RH7.x I - qla2xxx: bsg_job to bsg_job_t - qla2xxx: I Unify source code to work with newer kernels. - qla2xxx: Makefile changes from code-uni-devel-10x. - qla2xxx: qla_edif file changes to compile the driver. - qla2xxx: Fix compilation issues. - qla2xxx: Fix Makefile issue. - qla2xxx: fix compile error - qla2xxx: Use explicit LOGO in target mode - qla2xxx: Add EDIF support. - qla2xxx: Addd edif related files. - qla2xxx: Fix MPI failure AEN (8200) handling. - qla2xxx: SCM - Backport optimizations and style changes from upstream work. - qla2xxx: Fix warning in qla_attr.c file. - qla2xxx: Fix nvme compilation error. - qla2xxx: Fix crash in alloc w/GFP_KERNEL + interrupt - Author : Quinn Tran <qutran@marvell.com> qla2xxx: v2: add iocb resource tracking. - qla2xxx: Fix WARN_ON in qla_nvme_register_hba. - qla2xxx: Allow ql2xextended_error_logging special value 1 to be set anytime. - qla2xxx: Make tgt_port_database available in initiator mode. - qla2xxx: reduce noisy debug message. - qla2xxx: Fix mailbox Ch erroneous error - qla2xxx: fix login timeout. - qla2xxx: Accomodate for SCM FW attribute bit change. - qla2xxx: post FC event (FPIN) to transport FPIN handler. - qla2xxx: Hide fc_host_fpin_rcv kernel dependency. - qla2xxx: Add changes to compile across various kernels. - qla2xxx: Use active targets to update SCM stats. - qla2xxx: Move SCM functions to qla_isr to keep changes local. - qla2xxx: Code to process FLOGI ACC extended payload. - qedf: Fix compilation issue - revisit. - qla2xxx: SCM Phase 1 Implementation + 2 other patches. - qla2xxx: Enable PUREX passthru post ISP reset. - qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV. - qla2xxx: performance tweak - scsi: qla2xxx: fix fcport null pointer access. - fixup! qla2xxx: Fix unbound NVME response length. - scsi: qla2xxx: Fix unbound NVME response length - qla2xxx: Add host attribute to trigger MPI hang. - qla2xxx: ONEOFF: silent dbg messages for good path io. - qla2xxx: ONEOFF: fix pDIF detection - qla2xxx: Snoop inquiry response atleast 168 bytes to determine proprietary DIF. - qla2xxx: ONEOFF: add debug counters for T10-PI/DIF - qla2xxx: ONEOFF: add MQ support for HP3PAR propritary T10-PI - qla2xxx: HPE 3PAR private T10-PI support. - qla2xxx: Check for fabric_priority flag during login - qla2xxx: use iocb_fabric_priority flag - qla2xxx: Fix QoS name and add debug logs - qla2xxx: Correction to tests for iocb fabric and fcport qos. - qla2xxx: Use ->isp_ops->read_optrom() in qla26xx_read_qos_fcport_table(). - qla2xxx: QoS fcport table index initialization improvement. - qla2xxx: Add QoS fcport table index to speed up search. - qla2xxx: Reduce stack on qos fcport priority routines. - qla2xxx: HPE: Register FDMI QOS - qla2xxx: Add bsg interface for qos lun level bitmask. - qla2xxx: Read E2E QoS fcport priority bitmasks from flash. - qla2xxx: Abstract qos lun level mask for iocb cs_ctl field. - qla2xxx: Add fabric priority qos lun iocb mechanism. - qla2xxx: Implement CT command GFO (Get Fabric Object). - qla2xxx: Add support for fabric priority per target. - qla2xxx: fix mtcp dump collection failure. - qla2xxx: Set Nport ID for N2N - qla2xxx: Fix crash during device discovery. - qla2xxx: Handle NVME status iocb correctly. - qla2xxx: Remove restriction of FC T10-PI and NVME - qla2xxx: serialize fc_port alloc in N2N - qla2xxx: NPIV does not come up after FW dump. - qla2xxx: fix RDP respond data format bug. - qla2xxx: force semaphore on flash validation failure. - qla2xxx: add more FW debug information - qla2xxx: Revert: Disable T10-DIF feature with FC-NVMe during probe - qla2xxx: Update BPM enablement semantics. - qla2xxx: fix FW resource print error. - qla2xxx: Use a dedicated interrupt handler for 'handshake-required' ISPs. - qla2xxx: Ensure flash updates return possible failure status through bsg interface. - qla2xxx: Improved secure flash support messages - qla2xxx: fix flag passing error - qla2xxx: Use FC generic update firmware options routine for ISP27xx. - qla2xxx: Avoid setting firmware options twice in 24xx_update_fw_options. - qla2xxX: Add 16.0GT for PCI String - qla2xxx: Use FW_STARTED macro - qla2xxx: Add fixes for mailbox command - qla2xxx: Fix login IOCB flag - qla2xxx: Save rscn_gen for new fcport - qla2xxx: firmware option 3 is clobbered by speed set - qla2xxx: ISP28xx active FW region - qla2xxx: Add portname to print logs in qla24xx_logio_entry(). - qla2xxx: Correction to MB in-direction selection in qla2x00_echo_test(). - qla2xxx: Correction to selection of loopback/echo test. - qla2xxx: Use endian macros to assign static fields in fwdump header. - qla2xxx: Add Speed in SFP print information - qla2xxx: Fix RDP response size - qla2xxx: Handle cases for limiting RDP response payload length. - qla2xxx: Add deferred queue for processing ABTS and RDP. - qla2xxx: Cleanup ELS/PUREX iocb fields. - qla2xxx: Add devid's and conditionals for 28xx. - qla2xxx: Add vendor extended FDMI additions and amendments. - qla2xxx: Provide separate RDP enable. - qla2xxx: Add vendor extended RDP additions and amendments. - qla2xxx: Add changes in preparation for vendor extended FDMI/RDP. - qla2xxx: Add 2061 PCI ID - qla2xxx: Remove all DIX-0 references - qla2xxx: Add endianizer macro calls to fc host stats. - qla2xxx: Add sysfs node for D-Port Diagnostics AEN data. - qla2xxx: Move free of fcport out of interrupt context. - qla2xxx: Add beacon LED config sysfs interface. - qla2xxx: Add sysfs hooks for FC-NVMe autoconnect - 10.01.00.22-k AE 06/29/2020 - Upstream driver as part of Linux 5.6 - 10.02.01.01.a2-k1 BH 03/04/2021 - ERXXXXXX: qla2xxx: fixes for compilation on RHEL8.4 - ERXXXXXX: qla2xxx: Updated README file for RHEL8.4 - 10.02.01.00.a15-k1 BH 11/12/2020 ERXXXXXX: qla2xxx: Updated README file for new module parameters - 10.02.01.00.a14-k1 BH 11/06/2020 - ER146725: eDIF another driver panic running script: ./test_target_no_unload.sh Change: qla2xxx: Fix crash in qla_nvme_abort_set_option. - ER147771: Call Trace while shutting down the adapter ports (LINK DOWN). Change: qla2xxx: Handle aborts correctly for port undergoing deletion. - ERXXXXXX: qla2xxx: Add scsi_change_queue_depth to slave configure. - 10.02.02.00.a13-k1 BH 10/28/2020 - ER147600: Cisco: rpd ELS cmd fail to fetch the speed capabilities Change: qla2xxx: Used correct rdp spec, which was broken during code clean-up. - ER147695: FC-NVMe target discovery fails when initator wwpn < target wwpn in an N2N (Direct Attach) config Change: qla2xxx: fix N2N + NVME connect retry fail - ER147832: Issue with uSCM Linux with QCC CLI for some configuration Change: qla2xxx: Show event severity only when device state is congested. - ER147824 : scmr_stat sysfs node runs out of memory Change: qla2xxx: Come up with a compact version of scmr_stat - ER147823: NVMe IO is not getting throttled up or down. Change: qla2xxx: Enable throttle control for NVMe targets for Peer Congestion. - ERXXXXXX: qla2xxx: Count tgt short term link if link comes back before dev_loss_tmo. - ERXXXXXX: qla2xxx: Correct the check for fcport while displaying target counters. - ERXXXXXX: qla2xxx: Change trigger for host short term link down to dev loss tmo. - ERXXXXXX: qla2xxx: Move an SCM log under a debug level. - ERXXXXXX: qla2xxx: Set vendor_rsp[0] value. - ERXXXXXX: qla2xxx: Make throttling messages more informative. - 10.02.02.00.a12-k1 SK 10/15/2020 - ER147625: NVMe IO's are failing with Read/Write after LIP reset. Change: qla2xxx:Return EBUSY until the remote port delete finishes. - ER147653: Target side strongswan start/stop, make initiator crashed. Change: qla2xxx: edif: v2 fix double bsg done. - ER147791: USCM: clear option is not clearing hba alarm/warning, or clear cong or nvme target stats. Change: qla2xxx: Clear Sev and NVMe Target Stats. - ER147793: USCM: Throttling has wrong throttling up info and event period is not honored. Change: qla2xxx: Fix Throttling algorithm regression. - ER147759: NVMe Admin commands are getting throttled and causing admin queue failures. Change: qla2xxx: Throttle NVMe I/O commands only. - ERXXXXXX: qla2xxx: edif: fix aes_gmac mode. - ERXXXXXX: qla2xxx: edif: v2: standardize on port_id_t for bsg api. - ERXXXXXX: qla2xxx: edif: fix 4byte align. - ERXXXXXX: qla2xxx: edif: fix ELS meta data. - ERXXXXXX: qla2xxx: Clear Congestion State/Throttling during chip Reset. - ERXXXXXX: qla2xxx: Clear SCM Severity as part of SCM Stats Clear. - 10.02.00.02.a11-k1 BH 10/09/2020 - ER147734 : Lip reset on the isolated port causes server crash Change: qla2xxx: Don't allow FW, MPI and lip reset on isolated port. - ER147479 - PPC BE RH7.6 - qla2xxx driver loading - machine crashed. Change: qla2xxx: Fixes for big endian machines - ER147646: Call Trace observed while validating a MPI Pause test scenario. Change: qla2xxx: Correct the WARN_ON check in qla_nvme_abort_set_option. - ER147615: Throttling does not work with low I/Os. Change: qla2xxx: Check and round off fractional I/Os to 1 on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: List NVMe targets under scmr_stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Don't check for port isolation during abort isp. - ERXXXXXX: qla2xxx: SCM: Turn off SCM port parameter update mailbox command. - ERXXXXXX: qla2xxx: Fix I/O failures during remote port toggle testing - 10.02.00.02.a10-k1 BH 09/25/2020 SCM Changes: - ERXXXXXX: Changes - qla2xxx: Clear Congestion state when an RSCN is received/target is torn down. qla2xxx: throttling algorithm improvement. qla2xxx: Add throttling support for NVMe targets. EDIF Changes: - ERXXXXX: LUN loss on ipsec stop/start on target side. Change: save Nport on receive of PLOGI - ERXXXXX: fix ELS receive collision between physical and NPIV hosts. Change: remove erroneous source Nport ID search. - ER147570: FCP Performance Drop in latest driver for smaller IOs size. Change: qla2xxx: Change WQ_UNBOUND to WQ_MEM_RECLAIM. WQ_MEM_RECLAIM : wq is guaranteed to have at least one execution context regardless of memory pressure. - ER147632: QLE2774: RHEL 8.2 System crashes while upgrading he FW from 9.6.0 to 9.6.1 with QCC CLI build 12 Change: qla2xxx: Fix system crash on nvme abort path by checking sp of aborting command before accessing it. - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. - ER147645: System panic while trying to capture debugfs stats for EED. Change: qla2xxx: Check rport before accessing target number. - ER147632: Fix potential stale mem access Change: remove stale sp pointer reference - CQXXXXXX: FPIN events are not readily decodable. Change: qla2xxx: Make FPIN events prints human readable. - ER146879: Add support to clear SCM Stats Change: qla2xxx: Added support to clear SCM/SCMR Stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Allow get host stat during reset and sync reset. - ERXXXXXX: qla2xxx: Set reset_cmd_err_cnt on reset failure only. - ERXXXXXX: qla2xxx: Add isolated flag and return EPERM on isolation. - ERXXXXXX: qla2xxx: Count short term link if link comes back in 10 sec. - ERXXXXXX: qla2xxx: Don't check for fw_started while posting nvme command. - ERXXXXXX: qla2xxx: Pass irq_offset to blk_mq_pci_map_queues API. - ERXXXXXX: qla2xxx: lockdown: fix stale sp access. - BZ1868688: qla2xxx: tear down session if FW say its down. - 10.02.00.02.a9-k1 BH 09/03/2020 - ER147554 - sg_reset appears hung iterating over too many Qpairs. Change - qla2xxx: limit interrupt vectors to number of cpu. - ERXXXXX - qla2xxx: klocwork: Fix Bit field 'mpi_-' has one bit and is signed. - ERXXXXX - qla2xxx: Change post del message from debug level to log level. - ERXXXXX - qla2xxx: lockdown: fixup - Change error response as per API test. - ERXXXXX - qla2xxx: Fix map_queue interface to use the correct blk-mq call. - ERXXXXX - Added Structural changes for SCM Phase 2 support. Change : qla2xxx: Update structure definitions for SCM to support backward compatibility. - 10.02.00.02.a8-k1 BH 08/30/2020 - ERXXXXXX - Fix point-to-point (N2N) device discovery issue. Change - qla2xxx: Fix point-to-point (N2N) device discovery issue. - ERXXXXXX - To wait for ABTS response on I/O timeouts for NVMe. Change - qla2xxx: To wait for ABTS response on I/O timeouts for NVMe. - ER147523 - BSG stack trace and SCM display issues. Change - SCM: Functional regression with a6 release. - ER 147413 - edif: Fix issue with DIF enable target discovery. Change - qla2xxx: edif: Fix issue with DIF enable target discovery. - ER147480 clear ASYNC_ACTIVE flag to allow relogin. Change - qla2xxx: fix stuck session. - ERXXXXXX - lockdown: add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - 10.02.00.02.a7-k1 BH 08/22/2020 - ER147495 - edif changes Change - qla2xxx: edif: fix nvme discovery failure qla2xxx: edif: fix els corruption. - ERXXXXXX - add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - ERXXXXXX: SCMR changes Change - qla2xxx: SCMR: Correct scmr_outstanding_reqs accounting. qla2xxx: SCM: Changes to segregate current_events and current_state. qla2xxx: SCMR: Increase local array size. - ER147298 : USCM "Congestion Warning" counter regression Change - qla2xxx: Correct FPIN Structure Definition (Severity). - 10.02.00.02.a6-k1 BH 08/13/2020 - ERXXXXXX - fix crash on session cleanup + unload. Change - qla2xxx: fix crash on session cleanup + unload. - ER147329 - edif changes Change - qla2xxx: edif: fix compile error. do not submit qla2xxx: edif: fix double free on ELS send failure. qla2xxx: edif: reject els if non secure device. qla2xxx: edif: reject ELS on session down. qla2xxx: edif: redefine purex dest addr to be more consistent. qla2xxx: edif: tweak debug messages. qla2xxx: edif: fix nvme+edif target connect problem. - ER147460 - issue with Diag test on QCC CLI 2.4.0 build 10 with 10.2.00.2-a5 driver Change - qla2xxx: edif: move bsg auth els into separate routine. qla2xxx: edif: Fix error in BSG ELS path that has valid response data. - ER147312 - Add support to report MPI FW state. Change - qla2xxx: Add support to report MPI FW state. qla2xxx: Fix reset of MPI firmware. qla2xxx: Fix MPI reset needed message. - 10.02.00.02.a5-k1 BH 07/31/2020 - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. Change - qla2xxx: Don't process target debugfs stats if port is isolated. - ERXXXXXX : Add SCM stats to scmr_stats node. Change - qla2xxx: Add SCM stats to scmr_stats node. - ER147419 : Fix crash due to request q pointer extraction failure. Change - qla2xxx: Latency measurement patch. - ERXXXXXX : edif: remove redundant field in port_id_t Change -qla2xxx: edif: remove redundant field in port_id_t - ER147331 : extract bbc from PLOGI template payload. Change -qla2xxx: Fix buffer-buffer credit extraction error - ERXXXXXX : Split qla2x00_configure_local_loop() Change scsi: qla2xxx: Split qla2x00_configure_local_loop() - ERXXXXXX : SCMR - Add I/O flow control. Change - qla2xxx: SCMR - Add I/O flow control. - 10.02.00.02.a4-k1 BH 07/23/2020 - ER147402 - Do not install nvme auto connect script if OS is installing it. Change - qla2xxx: auto-connect scripts are install based on nvme-cli package. - ERXXXXXX - Fixed return status of nvme fcp request. Change - qla2xxx: Set NVME status code for failed NVME FCP request. - ERXXXXXX - Multi-que support for TMF. Change - qla2xxx: Multi-que support for TMF. - ERXXXXXX ? edif changes Change - qla2xxx: edif: simplify reserve/release of sa_index. qla2xxx: edif: tweak debug log. qla2xxx: edif: adjust ELS resp length. qla2xxx: edif: send logo on app stop. qla2xxx: edif: remove prlo in session deletion. qla2xxx: edif: Fix app stop stall. - ER147298 - USCM "Congestion Warning" counter regression w/.65 driver. Change - qla2xxx: Correct fpin_descriptor definition. qla2xxx: Consolidate EDIF & SCM Purex Calls. - ERXXXXXX - Calculate avg. time taken by different components for IO completion. Change - qla2xxx: Latency measurement patch. - 10.02.00.02.a3-k1 BH 07/16/2020 - ER147348 - Observing the firmware dump while running the qaucli -g post port isolation. Change - qla2xxx: Don't check firmware state in case of chip is down. - ER147338 - SLES: Driver load failed - modprobe: ERROR: module 'qla2xxx' is unsupported Change - qla2xxx: Add support for loading external modules on SuSE. - ER147361 - System panic after enabling port isolated during TimeOutReset. Change - qla2xxx: Synchronize the update the host counters using lock. - ER147370 - Hardware Error counter not incrementing for MBX command timeout Change - qla2xxx: Update hardware error count for various error conditions. - ERXXXXXX - The change is to help in debuggging. Change - qla2xxx: Move some messages from debug to normal log level. - ER147346 - Observed a call trace after port isolation. Change - qla2xxx: Fix the call trace for flush workqueue. - ERXXXXXX - For debug purpose Change - qla2xxx: Add error counters to debugfs node - 10.02.00.02.a2-k1 AE 07/10/2020 - ERXXXXXX - qla2xxx: Fix TCM compilation issues. Change - Enabled build of tcm_qla2xxx module and fixed compile issues. - ERXXXXXX - qla2xxx: edif : Added back the app_stop wait and avoid if link is down. Change - Added wait during app stop. - ERXXXXXX - qla2xxx: Set BIT_13 for NVMe Async events. Change - Driver changes to skip SLER for Async event command. - ER147323 - qla2xxx: Correct the check for sscanf return value. Change - Driver updated to check version correctly. - ERXXXXXX - qla2xxx: v2: Add EDIF support. Change - Refactoring EDIF code for modularity. - ER147298 - Congestion Warning/Alarm counters fail to increment Change - Update driver to increment the counters for congestion signals. - 10.02.00.02.a1-k1 AE 06/29/2020 - qla2xxx: Enable IOCB throttling by default. - qla2xxx: Implementation to get and manage host, target stats and initiator port. - qla2xxx: Add SLER and PI control support. - qla2xxx: Do not log message when reading port speed via sysfs - qla2xxx: fix null pointer access. - qla2xxx: Use MPI hang trigger to do PEGTUNE halt. - qla2xxx: Reduce erroneous error in link reset path - qla2xxx: v2: fix stalled N2N reconnect. - qla2xxx: Fix warnings on SLES12SP5. - qla2xxx: Fix compilation issues on SLES15 - qla2xxx: Compilation Fixes for SLES15SP1. - qla2xxx: Debugfs compilation issue fix for RH7.6. - qla2xxx: Fix gcc test compile error output being printed. - qla2xxx: Timestamp device online and offline transitions. - qla2xxx: Add rport fields in debugfs. - qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices. - qla2xxx: Setup debugfs entries for remote ports. - qla2xxx: Fix edif related compilation issue on RH7.6. - Fixes for compilation on hpe branch - qla2xxx: Compilation fixes for RH8.2 - qla2xxx: Compilation changes for RH7.6 - qla2xxx: Fixes for compilation on RH7.x I - qla2xxx: bsg_job to bsg_job_t - qla2xxx: I Unify source code to work with newer kernels. - qla2xxx: Makefile changes from code-uni-devel-10x. - qla2xxx: qla_edif file changes to compile the driver. - qla2xxx: Fix compilation issues. - qla2xxx: Fix Makefile issue. - qla2xxx: fix compile error - qla2xxx: Use explicit LOGO in target mode - qla2xxx: Add EDIF support. - qla2xxx: Addd edif related files. - qla2xxx: Fix MPI failure AEN (8200) handling. - qla2xxx: SCM - Backport optimizations and style changes from upstream work. - qla2xxx: Fix warning in qla_attr.c file. - qla2xxx: Fix nvme compilation error. - qla2xxx: Fix crash in alloc w/GFP_KERNEL + interrupt - Author : Quinn Tran <qutran@marvell.com> qla2xxx: v2: add iocb resource tracking. - qla2xxx: Fix WARN_ON in qla_nvme_register_hba. - qla2xxx: Allow ql2xextended_error_logging special value 1 to be set anytime. - qla2xxx: Make tgt_port_database available in initiator mode. - qla2xxx: reduce noisy debug message. - qla2xxx: Fix mailbox Ch erroneous error - qla2xxx: fix login timeout. - qla2xxx: Accomodate for SCM FW attribute bit change. - qla2xxx: post FC event (FPIN) to transport FPIN handler. - qla2xxx: Hide fc_host_fpin_rcv kernel dependency. - qla2xxx: Add changes to compile across various kernels. - qla2xxx: Use active targets to update SCM stats. - qla2xxx: Move SCM functions to qla_isr to keep changes local. - qla2xxx: Code to process FLOGI ACC extended payload. - qedf: Fix compilation issue - revisit. - qla2xxx: SCM Phase 1 Implementation + 2 other patches. - qla2xxx: Enable PUREX passthru post ISP reset. - qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV. - qla2xxx: performance tweak - scsi: qla2xxx: fix fcport null pointer access. - fixup! qla2xxx: Fix unbound NVME response length. - scsi: qla2xxx: Fix unbound NVME response length - qla2xxx: Add host attribute to trigger MPI hang. - qla2xxx: ONEOFF: silent dbg messages for good path io. - qla2xxx: ONEOFF: fix pDIF detection - qla2xxx: Snoop inquiry response atleast 168 bytes to determine proprietary DIF. - qla2xxx: ONEOFF: add debug counters for T10-PI/DIF - qla2xxx: ONEOFF: add MQ support for HP3PAR propritary T10-PI - qla2xxx: HPE 3PAR private T10-PI support. - qla2xxx: Check for fabric_priority flag during login - qla2xxx: use iocb_fabric_priority flag - qla2xxx: Fix QoS name and add debug logs - qla2xxx: Correction to tests for iocb fabric and fcport qos. - qla2xxx: Use ->isp_ops->read_optrom() in qla26xx_read_qos_fcport_table(). - qla2xxx: QoS fcport table index initialization improvement. - qla2xxx: Add QoS fcport table index to speed up search. - qla2xxx: Reduce stack on qos fcport priority routines. - qla2xxx: HPE: Register FDMI QOS - qla2xxx: Add bsg interface for qos lun level bitmask. - qla2xxx: Read E2E QoS fcport priority bitmasks from flash. - qla2xxx: Abstract qos lun level mask for iocb cs_ctl field. - qla2xxx: Add fabric priority qos lun iocb mechanism. - qla2xxx: Implement CT command GFO (Get Fabric Object). - qla2xxx: Add support for fabric priority per target. - qla2xxx: fix mtcp dump collection failure. - qla2xxx: Set Nport ID for N2N - qla2xxx: Fix crash during device discovery. - qla2xxx: Handle NVME status iocb correctly. - qla2xxx: Remove restriction of FC T10-PI and NVME - qla2xxx: serialize fc_port alloc in N2N - qla2xxx: NPIV does not come up after FW dump. - qla2xxx: fix RDP respond data format bug. - qla2xxx: force semaphore on flash validation failure. - qla2xxx: add more FW debug information - qla2xxx: Revert: Disable T10-DIF feature with FC-NVMe during probe - qla2xxx: Update BPM enablement semantics. - qla2xxx: fix FW resource print error. - qla2xxx: Use a dedicated interrupt handler for 'handshake-required' ISPs. - qla2xxx: Ensure flash updates return possible failure status through bsg interface. - qla2xxx: Improved secure flash support messages - qla2xxx: fix flag passing error - qla2xxx: Use FC generic update firmware options routine for ISP27xx. - qla2xxx: Avoid setting firmware options twice in 24xx_update_fw_options. - qla2xxX: Add 16.0GT for PCI String - qla2xxx: Use FW_STARTED macro - qla2xxx: Add fixes for mailbox command - qla2xxx: Fix login IOCB flag - qla2xxx: Save rscn_gen for new fcport - qla2xxx: firmware option 3 is clobbered by speed set - qla2xxx: ISP28xx active FW region - qla2xxx: Add portname to print logs in qla24xx_logio_entry(). - qla2xxx: Correction to MB in-direction selection in qla2x00_echo_test(). - qla2xxx: Correction to selection of loopback/echo test. - qla2xxx: Use endian macros to assign static fields in fwdump header. - qla2xxx: Add Speed in SFP print information - qla2xxx: Fix RDP response size - qla2xxx: Handle cases for limiting RDP response payload length. - qla2xxx: Add deferred queue for processing ABTS and RDP. - qla2xxx: Cleanup ELS/PUREX iocb fields. - qla2xxx: Add devid's and conditionals for 28xx. - qla2xxx: Add vendor extended FDMI additions and amendments. - qla2xxx: Provide separate RDP enable. - qla2xxx: Add vendor extended RDP additions and amendments. - qla2xxx: Add changes in preparation for vendor extended FDMI/RDP. - qla2xxx: Add 2061 PCI ID - qla2xxx: Remove all DIX-0 references - qla2xxx: Add endianizer macro calls to fc host stats. - qla2xxx: Add sysfs node for D-Port Diagnostics AEN data. - qla2xxx: Move free of fcport out of interrupt context. - qla2xxx: Add beacon LED config sysfs interface. - qla2xxx: Add sysfs hooks for FC-NVMe autoconnect - 10.01.00.22-k AE 06/29/2020 - Upstream driver as part of Linux 5.6 - 10.02.06.03-k1 BH 12/04/2021 - FCD-886: Hard Lockup on Unload/Load task with serial log enabled Changes: qla2xxx: readme: known issue when serial console and logging is enabled. Documented on README file. - FCD-926: lockdown: lower debug severity messages Changes: Lower the severity of various log messages. - FCD-868: lockdown: "Unsupported Firmware" message Changes: Fix this issue by reading value at bits level from variable. - 10.02.06.03.a1-k1 BH 10/18/2021 - FCD-701: Fix device reconnect in loop topology Changes: qla2xxx: Taking the main login path that acquires device handle. - FCD-704: The external flag for tcm_qla2xxx was not set. Changes: qla2xxx: Add tcm_qla2xxx to externally supported module list. - FCD-774: Source driver gives compilation error on RHEL8.5 Changes: qla2xxx: Offending code on tcm_qla2xxx module has been removed - 10.02.06.02-k1 BH 08/11/2021 - FCD-511: Path does not go into "Marginal" state on receiving FPIN-LI Change: qla2xxx: Pass the LI events to the scsi_transport_fc - 10.02.06.01-k1 BH 07/27/2021 - ERXXXXXX: qla2xxx: Check for firmware capability before creating QPair. Change: Move the check for FW attributes to right location. This check is specific for ISP25XX. - 10.02.06.00-k1 BH 07/21/2021 - ERXXXXXX: qla2xxx: Version number is changed from 10.02.06.00.a1-k1 to 10.02.06.00-k1 - 10.02.06.00.a1-k1 BH 06/29/2021 - FCD-297: Fix NVME session down detection Change: qla2xxx: Session tear down and allow relogin to re-drive the connection under condition - ER148553/FCD-156: Fix NVME retry Change: qla2xxx: Alternate back and forth on every PRLI failure until login retry count has depleted or it is succeeded. - FCD-316: System crash when number of CPUs forced to 2 - Change: qla2xxx: Sync queue idx with queue_pair_map idx. This fix needs both commits released on 10.02.05.00-k and 10.02.06.00.a1-k against FCD-316 - ERXXXXXX: qla2xxx: Readme: Update OS details that supports NVMe BFS. - ERXXXXXX: qla2xxx: Readme: Remove workaround of forcing of INTa mode for kdump kernel. - ERXXXXXX: qla2xxx: Readme: Update OS details that supports NVMe BFS. - FCD-316: System crash when number of CPUs forced to 2 Changes : qla2xxx: prevents unbalanced QP allocation where nr_hw_queues is two less than the number of CPUs. This fix needs both commits released on 10.02.05.00-k and 10.02.06.00.a1-k against FCD-316 - FCD-268: Multiple USCM ELS are sent - FCD-280: Fix issues reported by running a few Jammer tests Changes: qla2xxx: Retry the USCM ELS 3 times when there are failures. - FCD-172: build.sh: Fix udev script installation error - ER148402: Install restrictions when binary rpm is already installed. Changes: qla2xxx: Updated README file for documentation - ERXXXXXX: qla2xxx: Support kdump kernel for NVMe BFS. - ERXXXXXX: qla2xxx: Update README file for building kdump initrd in NVMe BFS. - ER148402: Disallow install if qla2xxx rpm is installed. Changes: qla2xxx: Prevent install from source if rpm is installed. - FCD-230: Add additional debug logs Changes: qla2xxx: Add additional logs to differentiate between FW driver and driver driven ELS -FCD-XXXX: Changes to support kdump kernel. Changes: qla2xxx: Don't allocate fw dump for kexec kernel and Allocate single Q for kexec kernel. - FCD-227: Linux Driver order of RDF to follow EDC ELS - FCD-225 - Qaucli fails to list scm stats for Qlipper - FCD-172: fix udev rule Changes: qla2xxx: permission of the rule file set to 644 - ER148529: NVMe initiator connected to brocade fabric are down Changes: qla2xxx: Fix hang on NVME command timeouts. - ER148531: SN1600Q/SN1610Q, Gen10PlusSnap4 - Async-login failed errors on BFS boot-up-QXCR1001796980 Changes: qla2xxx: Suppress unnecessary log messages during login - ER148578: Observed that initiator is sending prli type 0x8 for for nvme ports Changes: qla2xxx: fix NVME | FCP personality change. - ER148141: Driver vmkmgt: Don't differentiate Signals and FPIN's for the Congestion counters when they detected. Changes: qla2xxx: Split congestion warnings and alarms based on signals and FPINs - ERXXXXXX: Add support for marginal path. Changes: qla2xxx: Added support for eh_should_retry_cmd callback in qla2xxx host template. - ERXXXXXX: scsi: qla2xxx: Flush all sessions on zone disable - ERXXXXXX: scsi: qla2xxx: Fix memory size truncation - ERXXXXXX: scsi: qla2xxx: Fix a NULL pointer dereference in an error path - ERXXXXXX: qla2xxx: fix sparse warning. - ERXXXXXX: qla2xxx: edif: do secure plogi when auth app is present - ERXXXXXX: qla2xxx: Add license. - ERXXXXXX: qla2xxx: USCM - Do not send EDC/RDF ELS when firmware has already sent it - ERXXXXXX: qla2xxx: Inclusion words are applied on release note and readme file - ERXXXXXX: qla2xxx: edif: add N2N support for EDIF - ERXXXXXX: qla2xxx: Updated drelease.notes header - ERXXXXXX: qla2xxx: Fix hang during NVME session tear down. - ERXXXXXX: qla2xxx: USCM: Cleaned up a few debug messages - ERXXXXXX: qla2xxx: edif: fix edif enable flag - ER148546: USCM: QCC Cong Mgmt not available on port with FW:v9.07.00 and DVR:v10.02.05.00.a6-k Changes: qla2xxx: setting the flags to indicate to the application that the RDF is complete and SCM is supported. - ERXXXXXX: Add heartbeat check Changes: qla2xxx: Use 'no-op' mailbox command to check to see if FW is still responsive. - ERXXXXXX: DEBUG: simulate FW hang. Changes: qla2xxx: Driver will detect the hang and recover via hearbeat check. - ERXXXXXX: qla2xxx: Check for FW attributes before enabling MQ. - ERXXXXXX: qla2xxx: USCM Handle ELS errors from switch by retrying 3 times - ERXXXXXX: scsi: qla2xxx: Correct the supported speeds for 16G Mezz card. - ER148472: With NPIV ports, link bounce causes loss of strongSwan session at the target. Changes: qla2xxx: : fix npiv create errorneous error qla2xxx: EDIF: reject AUTH ELS on session down. qla2xxx: edif: Fix stale session - ER148478: System Crash while NPIV RAW IO ON VPORT LUNS on SLES15 SP3 + QLE 2692 + R7525 Changes: qla2xxx: fix unsafe removal from link list. - ERXXXXXX: qla2xxx: USCM - Send EDC and RDF ELS from the driver - ER147707: Device recovery not happening and OS hungs on qla2xxx Changes: qla2xxx: v2: fix crash in PCIe error handling - ER148123: Issue with Max secure connection with override_lower_limits Changes: qla2xxx: v2: fix stuck session - ER148402: SLES, Driver Install location is inconsistent. Changes: qla2xxx: Fix driver install location for SLES - ER148123: Issue with Max secure connection with override_lower_limits set and rekey/reauth with240/480-luns disconnected after 2 hr traffi Changes: qla2xxx: edif: doorbell tweak - ER148448: Issue w.r.t qaucli, where Remote type "Unknown" for eDIF env. for qaucli2.4.0.build 20 Changes: qla2xxx: fix port type info - ER148433: The log does not show a valid data rate while the link speed is 64G. Changes: qla2xxx: fix debug print of 64G link speed. - ER147650: 'show fdmi? command does not list ? OS Name and Version? parameter for SLES12SP4-QXCR1001771822 Changes: qla2xxx: Show OS name and version in FDMI-1 - ER147707: Device recovery not happening and OS hungs on qla2xxx Changes: qla2xxx: fix mailbox recovery during PCIE error qla2xxx: v2: fix crash in PCIe error handling - ERXXXXXX: qla2xxx: Changes to support FCP2 Target. - ERXXXXXX: qla2xxx: include AER debug mask to default - ERXXXXXX: qla2xxx: fixes for compilation on RH8.4 - ERXXXXXX: qla2xxx: Do logout even if fabric scan retries got exhausted. - 10.02.05.00.a1-k1 BH 02/27/2021 - EDIF Changes: - ER148247: issue with nvme-npiv env, once we delete npivs, after a while, it is reducing strongswan connections. Change: free sa index during npiv delete - ER148123: Issue with Max secure connection with override_lower_limits set and rekey/reauth with240/480-luns disconnected after 2 hr traffi Change: adjust online|offline notification to app and tweak LOGO on session down. - ERXXXXXX: qla2xxx: edif: tweak log message - ERXXXXXX: qla2xxx: edif: Redundant code (already set in qla_edb_node_alloc) - ER147707: qla2xxx: Device recovery not happening and OS hungs on qla2xxx Change: Fix RISC RESET completion polling. - ER148111: qla2xxx: FCPowerKit reflects huge delays in CMDlets execution. Change: Check lockdown functionality before requesting lockdown feature. - ER148277: USCM: Linux Peer showing misleading 'Congested, throttling down, permitted: 1', prior to 'Reached low watermark, permitted: 2': - Change: Fix misleading debug message - ERXXXXXX: adjust request/respond queue size for 28xx - ERXXXXXX: qla2xxx: Change %p to %px in the log messages. - 10.02.01.00.a15-k1 BH 11/12/2020 ERXXXXXX: qla2xxx: Updated README file for new module parameters - 10.02.01.00.a14-k1 BH 11/06/2020 - ER146725: eDIF another driver panic running script: ./test_target_no_unload.sh Change: qla2xxx: Fix crash in qla_nvme_abort_set_option. - ER147771: Call Trace while shutting down the adapter ports (LINK DOWN). Change: qla2xxx: Handle aborts correctly for port undergoing deletion. - ERXXXXXX: qla2xxx: Add scsi_change_queue_depth to slave configure. - 10.02.01.00.a13-k1 BH 10/28/2020 - ER147600: Cisco: rpd ELS cmd fail to fetch the speed capabilities Change: qla2xxx: Used correct rdp spec, which was broken during code clean-up. - ER147695: FC-NVMe target discovery fails when initator wwpn < target wwpn in an N2N (Direct Attach) config Change: qla2xxx: fix N2N + NVME connect retry fail - ER147832: Issue with uSCM Linux with QCC CLI for some configuration Change: qla2xxx: Show event severity only when device state is congested. - ER147824 : scmr_stat sysfs node runs out of memory Change: qla2xxx: Come up with a compact version of scmr_stat - ER147823: NVMe IO is not getting throttled up or down. Change: qla2xxx: Enable throttle control for NVMe targets for Peer Congestion. - ERXXXXXX: qla2xxx: Count tgt short term link if link comes back before dev_loss_tmo. - ERXXXXXX: qla2xxx: Correct the check for fcport while displaying target counters. - ERXXXXXX: qla2xxx: Change trigger for host short term link down to dev loss tmo. - ERXXXXXX: qla2xxx: Move an SCM log under a debug level. - ERXXXXXX: qla2xxx: Set vendor_rsp[0] value. - ERXXXXXX: qla2xxx: Make throttling messages more informative. - 10.02.01.00.a12-k1 SK 10/15/2020 - ER147625: NVMe IO's are failing with Read/Write after LIP reset. Change: qla2xxx:Return EBUSY until the remote port delete finishes. - ER147653: Target side strongswan start/stop, make initiator crashed. Change: qla2xxx: edif: v2 fix double bsg done. - ER147791: USCM: clear option is not clearing hba alarm/warning, or clear cong or nvme target stats. Change: qla2xxx: Clear Sev and NVMe Target Stats. - ER147793: USCM: Throttling has wrong throttling up info and event period is not honored. Change: qla2xxx: Fix Throttling algorithm regression. - ER147759: NVMe Admin commands are getting throttled and causing admin queue failures. Change: qla2xxx: Throttle NVMe I/O commands only. - ERXXXXXX: qla2xxx: edif: fix aes_gmac mode. - ERXXXXXX: qla2xxx: edif: v2: standardize on port_id_t for bsg api. - ERXXXXXX: qla2xxx: edif: fix 4byte align. - ERXXXXXX: qla2xxx: edif: fix ELS meta data. - ERXXXXXX: qla2xxx: Clear Congestion State/Throttling during chip Reset. - ERXXXXXX: qla2xxx: Clear SCM Severity as part of SCM Stats Clear. - 10.02.00.02.a11-k1 BH 10/09/2020 - ER147734 : Lip reset on the isolated port causes server crash Change: qla2xxx: Don't allow FW, MPI and lip reset on isolated port. - ER147479 - PPC BE RH7.6 - qla2xxx driver loading - machine crashed. Change: qla2xxx: Fixes for big endian machines - ER147646: Call Trace observed while validating a MPI Pause test scenario. Change: qla2xxx: Correct the WARN_ON check in qla_nvme_abort_set_option. - ER147615: Throttling does not work with low I/Os. Change: qla2xxx: Check and round off fractional I/Os to 1 on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: List NVMe targets under scmr_stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Don't check for port isolation during abort isp. - ERXXXXXX: qla2xxx: SCM: Turn off SCM port parameter update mailbox command. - ERXXXXXX: qla2xxx: Fix I/O failures during remote port toggle testing - 10.02.00.02.a10-k1 BH 09/25/2020 SCM Changes: - ERXXXXXX: Changes - qla2xxx: Clear Congestion state when an RSCN is received/target is torn down. qla2xxx: throttling algorithm improvement. qla2xxx: Add throttling support for NVMe targets. EDIF Changes: - ERXXXXX: LUN loss on ipsec stop/start on target side. Change: save Nport on receive of PLOGI - ERXXXXX: fix ELS receive collision between physical and NPIV hosts. Change: remove erroneous source Nport ID search. - ER147570: FCP Performance Drop in latest driver for smaller IOs size. Change: qla2xxx: Change WQ_UNBOUND to WQ_MEM_RECLAIM. WQ_MEM_RECLAIM : wq is guaranteed to have at least one execution context regardless of memory pressure. - ER147632: QLE2774: RHEL 8.2 System crashes while upgrading he FW from 9.6.0 to 9.6.1 with QCC CLI build 12 Change: qla2xxx: Fix system crash on nvme abort path by checking sp of aborting command before accessing it. - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. - ER147645: System panic while trying to capture debugfs stats for EED. Change: qla2xxx: Check rport before accessing target number. - ER147632: Fix potential stale mem access Change: remove stale sp pointer reference - CQXXXXXX: FPIN events are not readily decodable. Change: qla2xxx: Make FPIN events prints human readable. - ER146879: Add support to clear SCM Stats Change: qla2xxx: Added support to clear SCM/SCMR Stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Allow get host stat during reset and sync reset. - ERXXXXXX: qla2xxx: Set reset_cmd_err_cnt on reset failure only. - ERXXXXXX: qla2xxx: Add isolated flag and return EPERM on isolation. - ERXXXXXX: qla2xxx: Count short term link if link comes back in 10 sec. - ERXXXXXX: qla2xxx: Don't check for fw_started while posting nvme command. - ERXXXXXX: qla2xxx: Pass irq_offset to blk_mq_pci_map_queues API. - ERXXXXXX: qla2xxx: lockdown: fix stale sp access. - BZ1868688: qla2xxx: tear down session if FW say its down. - 10.02.00.02.a9-k1 BH 09/03/2020 - ER147554 - sg_reset appears hung iterating over too many Qpairs. Change - qla2xxx: limit interrupt vectors to number of cpu. - ERXXXXX - qla2xxx: klocwork: Fix Bit field 'mpi_-' has one bit and is signed. - ERXXXXX - qla2xxx: Change post del message from debug level to log level. - ERXXXXX - qla2xxx: lockdown: fixup - Change error response as per API test. - ERXXXXX - qla2xxx: Fix map_queue interface to use the correct blk-mq call. - ERXXXXX - Added Structural changes for SCM Phase 2 support. Change : qla2xxx: Update structure definitions for SCM to support backward compatibility. - 10.02.00.02.a8-k1 BH 08/30/2020 - ERXXXXXX - Fix point-to-point (N2N) device discovery issue. Change - qla2xxx: Fix point-to-point (N2N) device discovery issue. - ERXXXXXX - To wait for ABTS response on I/O timeouts for NVMe. Change - qla2xxx: To wait for ABTS response on I/O timeouts for NVMe. - ER147523 - BSG stack trace and SCM display issues. Change - SCM: Functional regression with a6 release. - ER 147413 - edif: Fix issue with DIF enable target discovery. Change - qla2xxx: edif: Fix issue with DIF enable target discovery. - ER147480 clear ASYNC_ACTIVE flag to allow relogin. Change - qla2xxx: fix stuck session. - ERXXXXXX - lockdown: add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - 10.02.00.02.a7-k1 BH 08/22/2020 - ER147495 - edif changes Change - qla2xxx: edif: fix nvme discovery failure qla2xxx: edif: fix els corruption. - ER147478 - SLES 15sp1 10.02...a6-k compile warning Change - qla2xxx: Compilation changes for sles15sp1 - ERXXXXXX - add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support qla2xxx: lockdown: fix compile problem. do not submit - ERXXXXXX: SCMR changes Change - qla2xxx: SCMR: Correct scmr_outstanding_reqs accounting. qla2xxx: SCM: Changes to separate current_events and current_state. qla2xxx: SCMR: Increase local array size. - ER147298 : USCM "Congestion Warning" counter regression Change - qla2xxx: Correct FPIN Structure Definition (Severity). - 10.02.00.02.a6-k1 BH 08/13/2020 - ERXXXXXX - fix crash on session cleanup + unload. Change - qla2xxx: fix crash on session cleanup + unload. - ER147329 - edif changes Change - qla2xxx: edif: fix compile error. do not submit qla2xxx: edif: fix double free on ELS send failure. qla2xxx: edif: reject els if non secure device. qla2xxx: edif: reject ELS on session down. qla2xxx: edif: redefine purex dest addr to be more consistent. qla2xxx: edif: tweak debug messages. qla2xxx: edif: fix nvme+edif target connect problem. - ER147460 - issue with Diag test on QCC CLI 2.4.0 build 10 with 10.2.00.2-a5 driver Change - qla2xxx: edif: move bsg auth els into separate routine. qla2xxx: edif: Fix error in BSG ELS path that has valid response data. - ER147312 - Add support to report MPI FW state. Change - qla2xxx: Add support to report MPI FW state. qla2xxx: Fix reset of MPI firmware. qla2xxx: Fix MPI reset needed message. - ER147437 - With a5 driver observed warning messages. Change - qla2xxx: Compilation changes for Citrix, rhel and sles. - 10.02.00.02.a5-k1 BH 07/31/2020 - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. Change - qla2xxx: Don't process target debugfs stats if port is isolated. - ERXXXXXX : Add SCM stats to scmr_stats node. Change - qla2xxx: Add SCM stats to scmr_stats node. - ER147419 : Fix crash due to request q pointer extraction failure. Change - qla2xxx: Latency measurement patch. - ERXXXXXX : edif: remove redundant field in port_id_t Change -qla2xxx: edif: remove redundant field in port_id_t - ER147331 - extract bbc from PLOGI template payload. Change -qla2xxx: Fix buffer-buffer credit extraction error - ERXXXXXX : Split qla2x00_configure_local_loop() Change scsi: qla2xxx: Split qla2x00_configure_local_loop() - ERXXXXXX : SCMR - Add I/O flow control. Change - qla2xxx: SCMR - Add I/O flow control. - 10.02.00.02.a4-k1 BH 07/23/2020 - ER147402 - Do not install nvme auto connect script if OS is installing it. Change - qla2xxx: auto-connect scripts are install based on nvme-cli package. - ERXXXXXX - Fixed return status of nvme fcp request. Change - qla2xxx: Set NVME status code for failed NVME FCP request. - ERXXXXXX - Multi-que support for TMF. Change - qla2xxx: Multi-que support for TMF. - ERXXXXXX ? edif changes Change - qla2xxx: edif: simplify reserve/release of sa_index. qla2xxx: edif: tweak debug log. qla2xxx: edif: adjust ELS resp length. qla2xxx: edif: send logo on app stop. qla2xxx: edif: remove prlo in session deletion. qla2xxx: edif: Fix app stop stall. - ER147298 - USCM "Congestion Warning" counter regression w/.65 driver. Change - qla2xxx: Correct fpin_descriptor definition. qla2xxx: Consolidate EDIF & SCM Purex Calls. - ERXXXXXX - Calculate avg. time taken by different components for IO completion. Change - qla2xxx: Latency measurement patch. - 10.02.00.02.a3-k1 BH 07/16/2020 - ER147348 - Observing firmware dump while running qaucli -g post port isolation. Change - qla2xxx: Don't check firmware state in case of chip is down. - ER147338 - SLES: Driver load failed - modprobe: ERROR: module 'qla2xxx' is unsupported. Change - qla2xxx: Add support for loading external modules on SuSE. - ER147361 - System panic after enabling port isolated during TimeOutReset. Change - qla2xxx: Synchronize the update the host counters using lock. - ER147370 - Hardware Error counter not incrementing for MBX command timeout. Change - qla2xxx: Update hardware error count for various error conditions. - ERXXXXXX - The change is to help in debuggging. Change - qla2xxx: Move some messages from debug to normal log level. - ER147346 - Observed a call trace after port isolation. Change - qla2xxx: Fix the call trace for flush workqueue. - ERXXXXXX - For debug purpose. Change - qla2xxx: Add error counters to debugfs node. - 10.02.00.02.a2-k1 AE 07/10/2020 - ERXXXXXX - qla2xxx: Fix TCM compilation issues. Change - Enabled build of tcm_qla2xxx module and fixed compile issues. - ERXXXXXX - qla2xxx: edif : Added back the app_stop wait and avoid if link is down. Change - Added wait during app stop. - ERXXXXXX - qla2xxx: Set BIT_13 for NVMe Async events. Change - Driver changes to skip SLER for Async event command. - ER147323 - qla2xxx: Correct the check for sscanf return value. Change - Driver updated to check version correctly. - ERXXXXXX - qla2xxx: v2: Add EDIF support. Change - Refactoring EDIF code for modularity. - ER147298 - Congestion Warning/Alarm counters fail to increment Change - Update driver to increment the counters for congestion signals. - 10.02.00.02.a1-k1 AE 06/29/2020 - qla2xxx: Enable IOCB throttling by default. - qla2xxx: Implementation to get and manage host, target stats and initiator port. - qla2xxx: Add SLER and PI control support. - qla2xxx: Do not log message when reading port speed via sysfs - qla2xxx: fix null pointer access. - qla2xxx: Use MPI hang trigger to do PEGTUNE halt. - qla2xxx: Reduce erroneous error in link reset path - qla2xxx: v2: fix stalled N2N reconnect. - qla2xxx: Fix warnings on SLES12SP5. - qla2xxx: Fix compilation issues on SLES15 - qla2xxx: Compilation Fixes for SLES15SP1. - qla2xxx: Debugfs compilation issue fix for RH7.6. - qla2xxx: Fix gcc test compile error output being printed. - qla2xxx: Timestamp device online and offline transitions. - qla2xxx: Add rport fields in debugfs. - qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices. - qla2xxx: Setup debugfs entries for remote ports. - qla2xxx: Fix edif related compilation issue on RH7.6. - Fixes for compilation on hpe branch - qla2xxx: Compilation fixes for RH8.2 - qla2xxx: Compilation changes for RH7.6 - qla2xxx: Fixes for compilation on RH7.x I - qla2xxx: bsg_job to bsg_job_t - qla2xxx: I Unify source code to work with newer kernels. - qla2xxx: Makefile changes from code-uni-devel-10x. - qla2xxx: qla_edif file changes to compile the driver. - qla2xxx: Fix compilation issues. - qla2xxx: Fix Makefile issue. - qla2xxx: fix compile error - qla2xxx: Use explicit LOGO in target mode - qla2xxx: Add EDIF support. - qla2xxx: Addd edif related files. - qla2xxx: Fix MPI failure AEN (8200) handling. - qla2xxx: SCM - Backport optimizations and style changes from upstream work. - qla2xxx: Fix warning in qla_attr.c file. - qla2xxx: Fix nvme compilation error. - qla2xxx: Fix crash in alloc w/GFP_KERNEL + interrupt - Author : Quinn Tran <qutran@marvell.com> qla2xxx: v2: add iocb resource tracking. - qla2xxx: Fix WARN_ON in qla_nvme_register_hba. - qla2xxx: Allow ql2xextended_error_logging special value 1 to be set anytime. - qla2xxx: Make tgt_port_database available in initiator mode. - qla2xxx: reduce noisy debug message. - qla2xxx: Fix mailbox Ch erroneous error - qla2xxx: fix login timeout. - qla2xxx: Accomodate for SCM FW attribute bit change. - qla2xxx: post FC event (FPIN) to transport FPIN handler. - qla2xxx: Hide fc_host_fpin_rcv kernel dependency. - qla2xxx: Add changes to compile across various kernels. - qla2xxx: Use active targets to update SCM stats. - qla2xxx: Move SCM functions to qla_isr to keep changes local. - qla2xxx: Code to process FLOGI ACC extended payload. - qedf: Fix compilation issue - revisit. - qla2xxx: SCM Phase 1 Implementation + 2 other patches. - qla2xxx: Enable PUREX passthru post ISP reset. - qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV. - qla2xxx: performance tweak - scsi: qla2xxx: fix fcport null pointer access. - fixup! qla2xxx: Fix unbound NVME response length. - scsi: qla2xxx: Fix unbound NVME response length - qla2xxx: Add host attribute to trigger MPI hang. - qla2xxx: ONEOFF: silent dbg messages for good path io. - qla2xxx: ONEOFF: fix pDIF detection - qla2xxx: Snoop inquiry response atleast 168 bytes to determine proprietary DIF. - qla2xxx: ONEOFF: add debug counters for T10-PI/DIF - qla2xxx: ONEOFF: add MQ support for HP3PAR propritary T10-PI - qla2xxx: HPE 3PAR private T10-PI support. - qla2xxx: Check for fabric_priority flag during login - qla2xxx: use iocb_fabric_priority flag - qla2xxx: Fix QoS name and add debug logs - qla2xxx: Correction to tests for iocb fabric and fcport qos. - qla2xxx: Use ->isp_ops->read_optrom() in qla26xx_read_qos_fcport_table(). - qla2xxx: QoS fcport table index initialization improvement. - qla2xxx: Add QoS fcport table index to speed up search. - qla2xxx: Reduce stack on qos fcport priority routines. - qla2xxx: HPE: Register FDMI QOS - qla2xxx: Add bsg interface for qos lun level bitmask. - qla2xxx: Read E2E QoS fcport priority bitmasks from flash. - qla2xxx: Abstract qos lun level mask for iocb cs_ctl field. - qla2xxx: Add fabric priority qos lun iocb mechanism. - qla2xxx: Implement CT command GFO (Get Fabric Object). - qla2xxx: Add support for fabric priority per target. - qla2xxx: fix mtcp dump collection failure. - qla2xxx: Set Nport ID for N2N - qla2xxx: Fix crash during device discovery. - qla2xxx: Handle NVME status iocb correctly. - qla2xxx: Remove restriction of FC T10-PI and NVME - qla2xxx: serialize fc_port alloc in N2N - qla2xxx: NPIV does not come up after FW dump. - qla2xxx: fix RDP respond data format bug. - qla2xxx: force semaphore on flash validation failure. - qla2xxx: add more FW debug information - qla2xxx: Revert: Disable T10-DIF feature with FC-NVMe during probe - qla2xxx: Update BPM enablement semantics. - qla2xxx: fix FW resource print error. - qla2xxx: Use a dedicated interrupt handler for 'handshake-required' ISPs. - qla2xxx: Ensure flash updates return possible failure status through bsg interface. - qla2xxx: Improved secure flash support messages - qla2xxx: fix flag passing error - qla2xxx: Use FC generic update firmware options routine for ISP27xx. - qla2xxx: Avoid setting firmware options twice in 24xx_update_fw_options. - qla2xxX: Add 16.0GT for PCI String - qla2xxx: Use FW_STARTED macro - qla2xxx: Add fixes for mailbox command - qla2xxx: Fix login IOCB flag - qla2xxx: Save rscn_gen for new fcport - qla2xxx: firmware option 3 is clobbered by speed set - qla2xxx: ISP28xx active FW region - qla2xxx: Add portname to print logs in qla24xx_logio_entry(). - qla2xxx: Correction to MB in-direction selection in qla2x00_echo_test(). - qla2xxx: Correction to selection of loopback/echo test. - qla2xxx: Use endian macros to assign static fields in fwdump header. - qla2xxx: Add Speed in SFP print information - qla2xxx: Fix RDP response size - qla2xxx: Handle cases for limiting RDP response payload length. - qla2xxx: Add deferred queue for processing ABTS and RDP. - qla2xxx: Cleanup ELS/PUREX iocb fields. - qla2xxx: Add devid's and conditionals for 28xx. - qla2xxx: Add vendor extended FDMI additions and amendments. - qla2xxx: Provide separate RDP enable. - qla2xxx: Add vendor extended RDP additions and amendments. - qla2xxx: Add changes in preparation for vendor extended FDMI/RDP. - qla2xxx: Add 2061 PCI ID - qla2xxx: Remove all DIX-0 references - qla2xxx: Add endianizer macro calls to fc host stats. - qla2xxx: Add sysfs node for D-Port Diagnostics AEN data. - qla2xxx: Move free of fcport out of interrupt context. - qla2xxx: Add beacon LED config sysfs interface. - qla2xxx: Add sysfs hooks for FC-NVMe autoconnect - 10.01.00.22-k AE 06/29/2020 - Upstream driver as part of Linux 5.6 - Add workaround for 5762 MRRS (Severity:Medium) - Update copyright year to 2017 (Severity:Minor) - Add support for RHEL 7.4 and SLES12SP2 (Severity:Medium) - Add support to notify min/max MTUs through min_mtu & max_mtu (Severity:Medium) - Add support to overide clock for 5762 (Severity:Medium) - Backport upstream patches (Severity:Medium) - Add PHY reset workaround in change MTU path for 5717/19/20 (Severity:Medium) - Update the copyright (Severity:Minor) - Add SLES 15 support (Severity:Medium) - Add RHEL 7.5 support (Severity:Medium) - Fix RHEL 6.4 compilation (Severity:Medium) - Add Ubuntu 18.04 support (Severity:Minor) - Fix race between tg3_get_stats64() and tg3_free_consistent() (Severity:Minor) - Avoid usleep_range() with holding spin lock (Severity:Minor) - Add private ioctl support for register read/write (Severity:Medium) - Add RHEL 8.0 support (Severity:Medium) - Fix Panic with SLES12SP3 (Severity:Minor) - Add workaround for 5762 MRRS (Severity:Medium) - Update copyright year to 2017 (Severity:Minor) - Add support for RHEL 7.4 and SLES12SP2 (Severity:Medium) - Add support to notify min/max MTUs through min_mtu & max_mtu (Severity:Medium) - Add support to overide clock for 5762 (Severity:Medium) - Backport upstream patches (Severity:Medium) - Add PHY reset workaround in change MTU path for 5717/19/20 (Severity:Medium) - Update the copyright (Severity:Minor) - Add SLES 15 support (Severity:Medium) - Add RHEL 7.5 support (Severity:Medium) - Fix RHEL 6.4 compilation (Severity:Medium) - Add Ubuntu 18.04 support (Severity:Minor) - Fix race between tg3_get_stats64() and tg3_free_consistent() (Severity:Minor) - Avoid usleep_range() with holding spin lock (Severity:Minor) - Add private ioctl support for register read/write (Severity:Medium) - Add RHEL 8.0 support (Severity:Medium) - Fix Panic with SLES12SP3 (Severity:Minor) - Add workaround for 5762 MRRS (Severity:Medium) - Update copyright year to 2017 (Severity:Minor) - Add support for RHEL 7.4 and SLES12SP2 (Severity:Medium) - Add support to notify min/max MTUs through min_mtu & max_mtu (Severity:Medium) - Add support to overide clock for 5762 (Severity:Medium) - Backport upstream patches (Severity:Medium) - Add PHY reset workaround in change MTU path for 5717/19/20 (Severity:Medium) - Update the copyright (Severity:Minor) - Add SLES 15 support (Severity:Medium) - Add RHEL 7.5 support (Severity:Medium) - Fix RHEL 6.4 compilation (Severity:Medium) - Add Ubuntu 18.04 support (Severity:Minor) - Fix race between tg3_get_stats64() and tg3_free_consistent() (Severity:Minor) - Avoid usleep_range() with holding spin lock (Severity:Minor) - Add private ioctl support for register read/write (Severity:Medium) - Add RHEL 8.0 support (Severity:Medium) - Fix Panic with SLES12SP3 (Severity:Minor) - Add workaround for 5762 MRRS (Severity:Medium) - Update copyright year to 2017 (Severity:Minor) - Add support for RHEL 7.4 and SLES12SP2 (Severity:Medium) - Add support to notify min/max MTUs through min_mtu & max_mtu (Severity:Medium) - Add support to overide clock for 5762 (Severity:Medium) - Backport upstream patches (Severity:Medium) - Add PHY reset workaround in change MTU path for 5717/19/20 (Severity:Medium) - Update the copyright (Severity:Minor) - Add SLES 15 support (Severity:Medium) - Add RHEL 7.5 support (Severity:Medium) - Fix RHEL 6.4 compilation (Severity:Medium) - Add Ubuntu 18.04 support (Severity:Minor) - Fix race between tg3_get_stats64() and tg3_free_consistent() (Severity:Minor) - Avoid usleep_range() with holding spin lock (Severity:Minor) - Add private ioctl support for register read/write (Severity:Medium) - Add RHEL 8.0 support (Severity:Medium) - Fix Panic with SLES12SP3 (Severity:Minor) - Release version 4.18.0-106.rhel7u8 - Release version 4.18.0-106.rhel7u9 - Release version 4.18.0-106.rhel8u4 - Release version 4.18.0-106.rhel8u5 - Release version 4.18.0-106.sles12sp4 - Release version 4.18.0-106.sles12sp5 - Release version 4.18.0-106.sles15sp2 - Release version 4.18.0-106.sles15sp3 - Release version 4.9-OFED.4.9.4.0.8.1.rhel7u8 - Release version 4.9-OFED.4.9.4.0.8.1.rhel7u9 - Release version 4.9-OFED.4.9.4.0.8.1.rhel8u4 - Release version 4.9-OFED.4.9.4.0.8.1.sles12sp4 - Release version 4.9-OFED.4.9.4.0.8.1.sles12sp5 - Release version 4.9-OFED.4.9.4.0.8.1.sles15sp2 - Release version 4.9-OFED.4.9.4.0.8.1.sles15sp3 - Release version 5.5-OFED.5.5.1.0.3.1.rhel7u8 - Release version 5.5-OFED.5.5.1.0.3.1.rhel7u9 - Release version 5.5-OFED.5.5.1.0.3.1.rhel8u4 - Release version 5.5-OFED.5.5.1.0.3.1.rhel8u5 - Release version 5.5-OFED.5.5.1.0.3.1.sles12sp4 - Release version 5.5-OFED.5.5.1.0.3.1.sles12sp5 - Release version 5.5-OFED.5.5.1.0.3.1.sles15sp2 - Release version 5.5-OFED.5.5.1.0.3.1.sles15sp3 - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules - Added nfsrdma support - Added ibdev2netdev script - Support install macro that removes RPM_BUILD_ROOT - Add mlx4_fc and mlx4_vnic support - Add KMP support - Add weak updates support - Remove FC support - Use one spec for KMP and non-KMP OS's. - Add QoS utils. - Renamed kernel-ib package to mlnx-ofa_kernel-modules -Added Linux SRIOV support -Added iSCSI & FCoE HBA support for specific HP adapters and devices -Added VC4.10 support -Added BCV support -When GRO setting changes while LRO is enabled, don't reload as LRO takes precedence. -Allow UDP tunneling offload -Enable IPGRE RSS by default -Support different GRE RSS modes. -Add RH5.10 support. -Add RH6.5 support. -FC-TAPE - Host responds early to a requested resend delay - Linux (70101) -SLES11 MEZ75 IO halt with Nexus reboot tests (70728) -SLES 11 blade loses all targets from BLOM port during fabric uplink add/remove (70187) -KVM gso and gro are not working on hv and vm as expected (70506) -SRIOV mtu toggle failure (70530) -SRIOV hv reboots on pf toggle with vfs passed through on it. (70531) -Guest OS dosent boot after attaching VF in RHEL6.3x64bit for 57840 device. (68426) -[NET]SUT reboot&MCE report when create 30th/31st VF on 57810 device on SLES11 SP2. (69263) -RH Cert - RH5 | U8 | v7-1.5-33 | 57810 | Flex Network Test failed. (70427) -BACS 16.2.0: Show ETS/Priority Tagging/PFC as operational when DCBX is disabled on the switch side. (69690) -Incorrect port value is displayed for connected/unconnected ports of 57810 for RHEL5.9 64bits. (68627) -VFs are not getting created for Broadcom adapters in RHEL5.10 OS. (71456) - added RH5.11 support. - added RH6.6 & RH6.7 support. - added RH7.0 & RH7.1 support. - added SLES11-SP4 & SLES12 support. - added VLAN filtering offload support. - added Debian GNU/Linux 7 (wheezy) support. - In RHEL7.0 and 7.1, bnx2x will be rolled back to inbox after system reboot (80071). - SRIOV : MAC address change inside VM is not allowed unless interface is down (80309). - RH7.x: Tunneling offload is not enabled (79269). - self test fails on 20G adapter (79295). - VF interface vlan-filtering stopped working (79365). - Fail to force link speed other than 20G in KR2 (77841). - Incorrect asymmetric flow-control behavior (75504). - Dynamic VF enumeration fails for 578xx adapter in SLES11 SP4 (78590). - Inner-to-outer vlan priority mapping doesn't work (RH6.x [pre 2.6.38 kernels]). - Packets from a VF with pvid configured which were sent with a different vlan were transmitted instead of being discarded. - UDP packets cannot pass to the upper application (5709). - Out of memory issue when the adapter is reset (5709). - iSCSI offload: Driver displaying incorrect remote port (77842). - FCoE offload: Initiators failed FLOGI on SLES 11 SP4 RC1 (79704). -Added Linux SRIOV support -Added iSCSI & FCoE HBA support for specific HP adapters and devices -Added VC4.10 support -Added BCV support -When GRO setting changes while LRO is enabled, don't reload as LRO takes precedence. -Allow UDP tunneling offload -Enable IPGRE RSS by default -Support different GRE RSS modes. -Add RH5.10 support. -Add RH6.5 support. -FC-TAPE - Host responds early to a requested resend delay - Linux (70101) -SLES11 MEZ75 IO halt with Nexus reboot tests (70728) -SLES 11 blade loses all targets from BLOM port during fabric uplink add/remove (70187) -KVM gso and gro are not working on hv and vm as expected (70506) -SRIOV mtu toggle failure (70530) -SRIOV hv reboots on pf toggle with vfs passed through on it. (70531) -Guest OS dosent boot after attaching VF in RHEL6.3x64bit for 57840 device. (68426) -[NET]SUT reboot&MCE report when create 30th/31st VF on 57810 device on SLES11 SP2. (69263) -RH Cert - RH5 | U8 | v7-1.5-33 | 57810 | Flex Network Test failed. (70427) -BACS 16.2.0: Show ETS/Priority Tagging/PFC as operational when DCBX is disabled on the switch side. (69690) -Incorrect port value is displayed for connected/unconnected ports of 57810 for RHEL5.9 64bits. (68627) -VFs are not getting created for Broadcom adapters in RHEL5.10 OS. (71456) - added RH5.11 support. - added RH6.6 & RH6.7 support. - added RH7.0 & RH7.1 support. - added SLES11-SP4 & SLES12 support. - added VLAN filtering offload support. - added Debian GNU/Linux 7 (wheezy) support. - In RHEL7.0 and 7.1, bnx2x will be rolled back to inbox after system reboot (80071). - SRIOV : MAC address change inside VM is not allowed unless interface is down (80309). - RH7.x: Tunneling offload is not enabled (79269). - self test fails on 20G adapter (79295). - VF interface vlan-filtering stopped working (79365). - Fail to force link speed other than 20G in KR2 (77841). - Incorrect asymmetric flow-control behavior (75504). - Dynamic VF enumeration fails for 578xx adapter in SLES11 SP4 (78590). - Inner-to-outer vlan priority mapping doesn't work (RH6.x [pre 2.6.38 kernels]). - Packets from a VF with pvid configured which were sent with a different vlan were transmitted instead of being discarded. - UDP packets cannot pass to the upper application (5709). - Out of memory issue when the adapter is reset (5709). - iSCSI offload: Driver displaying incorrect remote port (77842). - FCoE offload: Initiators failed FLOGI on SLES 11 SP4 RC1 (79704). -Added Linux SRIOV support -Added iSCSI & FCoE HBA support for specific HP adapters and devices -Added VC4.10 support -Added BCV support -When GRO setting changes while LRO is enabled, don't reload as LRO takes precedence. -Allow UDP tunneling offload -Enable IPGRE RSS by default -Support different GRE RSS modes. -Add RH5.10 support. -Add RH6.5 support. -FC-TAPE - Host responds early to a requested resend delay - Linux (70101) -SLES11 MEZ75 IO halt with Nexus reboot tests (70728) -SLES 11 blade loses all targets from BLOM port during fabric uplink add/remove (70187) -KVM gso and gro are not working on hv and vm as expected (70506) -SRIOV mtu toggle failure (70530) -SRIOV hv reboots on pf toggle with vfs passed through on it. (70531) -Guest OS dosent boot after attaching VF in RHEL6.3x64bit for 57840 device. (68426) -[NET]SUT reboot&MCE report when create 30th/31st VF on 57810 device on SLES11 SP2. (69263) -RH Cert - RH5 | U8 | v7-1.5-33 | 57810 | Flex Network Test failed. (70427) -BACS 16.2.0: Show ETS/Priority Tagging/PFC as operational when DCBX is disabled on the switch side. (69690) -Incorrect port value is displayed for connected/unconnected ports of 57810 for RHEL5.9 64bits. (68627) -VFs are not getting created for Broadcom adapters in RHEL5.10 OS. (71456) - added RH5.11 support. - added RH6.6 & RH6.7 support. - added RH7.0 & RH7.1 support. - added SLES11-SP4 & SLES12 support. - added VLAN filtering offload support. - added Debian GNU/Linux 7 (wheezy) support. - In RHEL7.0 and 7.1, bnx2x will be rolled back to inbox after system reboot (80071). - SRIOV : MAC address change inside VM is not allowed unless interface is down (80309). - RH7.x: Tunneling offload is not enabled (79269). - self test fails on 20G adapter (79295). - VF interface vlan-filtering stopped working (79365). - Fail to force link speed other than 20G in KR2 (77841). - Incorrect asymmetric flow-control behavior (75504). - Dynamic VF enumeration fails for 578xx adapter in SLES11 SP4 (78590). - Inner-to-outer vlan priority mapping doesn't work (RH6.x [pre 2.6.38 kernels]). - Packets from a VF with pvid configured which were sent with a different vlan were transmitted instead of being discarded. - UDP packets cannot pass to the upper application (5709). - Out of memory issue when the adapter is reset (5709). - iSCSI offload: Driver displaying incorrect remote port (77842). - FCoE offload: Initiators failed FLOGI on SLES 11 SP4 RC1 (79704). - Version 8.18.18.0 - Added missing support to configure 1G speed via ethtool - Fixed calculation of number of ooo rx buffers and limit to 16K - Version 8.18.17.0-1 - iWARP - Handle flush completion on unaligned ll2 connection - Add dp_module, dp_level as modparams - Add Kconfig file for upstream builds - Version 8.18.16.0-1 - Fix missing return error code check on call to qedi_setup_int - Modify different module params - Add log message in the driver unload path - Fail all non-timesync related ioctls - Version 8.18.15.0-1 - Added wwpn and wwnn to the FCoE dev-info - Validate chap and mutual chap auth correctly - Version 8.18.14.0-1 - Fix error handling flow in TX path - Fix error handling flow in RX path - Implement get_protocol_tlv_data callback - Version 8.18.18.0 - Added missing support to configure 1G speed via ethtool - Fixed calculation of number of ooo rx buffers and limit to 16K - Version 8.18.17.0-1 - iWARP - Handle flush completion on unaligned ll2 connection - Add dp_module, dp_level as modparams - Add Kconfig file for upstream builds - Version 8.18.16.0-1 - Fix missing return error code check on call to qedi_setup_int - Modify different module params - Add log message in the driver unload path - Fail all non-timesync related ioctls - Version 8.18.15.0-1 - Added wwpn and wwnn to the FCoE dev-info - Validate chap and mutual chap auth correctly - Version 8.18.14.0-1 - Fix error handling flow in TX path - Fix error handling flow in RX path - Implement get_protocol_tlv_data callback - Version 8.18.18.0 - Added missing support to configure 1G speed via ethtool - Fixed calculation of number of ooo rx buffers and limit to 16K - Version 8.18.17.0-1 - iWARP - Handle flush completion on unaligned ll2 connection - Add dp_module, dp_level as modparams - Add Kconfig file for upstream builds - Version 8.18.16.0-1 - Fix missing return error code check on call to qedi_setup_int - Modify different module params - Add log message in the driver unload path - Fail all non-timesync related ioctls - Version 8.18.15.0-1 - Added wwpn and wwnn to the FCoE dev-info - Validate chap and mutual chap auth correctly - Version 8.18.14.0-1 - Fix error handling flow in TX path - Fix error handling flow in RX path - Implement get_protocol_tlv_data callback - 10.02.01.00.a14-k1 BH 11/06/2020 - ER146725: eDIF another driver panic running script: ./test_target_no_unload.sh Change: qla2xxx: Fix crash in qla_nvme_abort_set_option. - ER147771: Call Trace while shutting down the adapter ports (LINK DOWN). Change: qla2xxx: Handle aborts correctly for port undergoing deletion. - ERXXXXXX: qla2xxx: Add scsi_change_queue_depth to slave configure. - 10.02.02.00.a13-k1 BH 10/28/2020 - ER147600: Cisco: rpd ELS cmd fail to fetch the speed capabilities Change: qla2xxx: Used correct rdp spec, which was broken during code clean-up. - ER147695: FC-NVMe target discovery fails when initator wwpn < target wwpn in an N2N (Direct Attach) config Change: qla2xxx: fix N2N + NVME connect retry fail - ER147832: Issue with uSCM Linux with QCC CLI for some configuration Change: qla2xxx: Show event severity only when device state is congested. - ER147824 : scmr_stat sysfs node runs out of memory Change: qla2xxx: Come up with a compact version of scmr_stat - ER147823: NVMe IO is not getting throttled up or down. Change: qla2xxx: Enable throttle control for NVMe targets for Peer Congestion. - ERXXXXXX: qla2xxx: Count tgt short term link if link comes back before dev_loss_tmo. - ERXXXXXX: qla2xxx: Correct the check for fcport while displaying target counters. - ERXXXXXX: qla2xxx: Change trigger for host short term link down to dev loss tmo. - ERXXXXXX: qla2xxx: Move an SCM log under a debug level. - ERXXXXXX: qla2xxx: Set vendor_rsp[0] value. - ERXXXXXX: qla2xxx: Make throttling messages more informative. - 10.02.02.00.a12-k1 SK 10/15/2020 - ER147625: NVMe IO's are failing with Read/Write after LIP reset. Change: qla2xxx:Return EBUSY until the remote port delete finishes. - ER147653: Target side strongswan start/stop, make initiator crashed. Change: qla2xxx: edif: v2 fix double bsg done. - ER147791: USCM: clear option is not clearing hba alarm/warning, or clear cong or nvme target stats. Change: qla2xxx: Clear Sev and NVMe Target Stats. - ER147793: USCM: Throttling has wrong throttling up info and event period is not honored. Change: qla2xxx: Fix Throttling algorithm regression. - ER147759: NVMe Admin commands are getting throttled and causing admin queue failures. Change: qla2xxx: Throttle NVMe I/O commands only. - ERXXXXXX: qla2xxx: edif: fix aes_gmac mode. - ERXXXXXX: qla2xxx: edif: v2: standardize on port_id_t for bsg api. - ERXXXXXX: qla2xxx: edif: fix 4byte align. - ERXXXXXX: qla2xxx: edif: fix ELS meta data. - ERXXXXXX: qla2xxx: Clear Congestion State/Throttling during chip Reset. - ERXXXXXX: qla2xxx: Clear SCM Severity as part of SCM Stats Clear. - 10.02.00.02.a11-k1 BH 10/09/2020 - ER147734 : Lip reset on the isolated port causes server crash Change: qla2xxx: Don't allow FW, MPI and lip reset on isolated port. - ER147479 - PPC BE RH7.6 - qla2xxx driver loading - machine crashed. Change: qla2xxx: Fixes for big endian machines - ER147646: Call Trace observed while validating a MPI Pause test scenario. Change: qla2xxx: Correct the WARN_ON check in qla_nvme_abort_set_option. - ER147615: Throttling does not work with low I/Os. Change: qla2xxx: Check and round off fractional I/Os to 1 on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: List NVMe targets under scmr_stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Don't check for port isolation during abort isp. - ERXXXXXX: qla2xxx: SCM: Turn off SCM port parameter update mailbox command. - ERXXXXXX: qla2xxx: Fix I/O failures during remote port toggle testing - 10.02.00.02.a10-k1 BH 09/25/2020 SCM Changes: - ERXXXXXX: Changes - qla2xxx: Clear Congestion state when an RSCN is received/target is torn down. qla2xxx: throttling algorithm improvement. qla2xxx: Add throttling support for NVMe targets. EDIF Changes: - ERXXXXX: LUN loss on ipsec stop/start on target side. Change: save Nport on receive of PLOGI - ERXXXXX: fix ELS receive collision between physical and NPIV hosts. Change: remove erroneous source Nport ID search. - ER147570: FCP Performance Drop in latest driver for smaller IOs size. Change: qla2xxx: Change WQ_UNBOUND to WQ_MEM_RECLAIM. WQ_MEM_RECLAIM : wq is guaranteed to have at least one execution context regardless of memory pressure. - ER147632: QLE2774: RHEL 8.2 System crashes while upgrading he FW from 9.6.0 to 9.6.1 with QCC CLI build 12 Change: qla2xxx: Fix system crash on nvme abort path by checking sp of aborting command before accessing it. - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. - ER147645: System panic while trying to capture debugfs stats for EED. Change: qla2xxx: Check rport before accessing target number. - ER147632: Fix potential stale mem access Change: remove stale sp pointer reference - CQXXXXXX: FPIN events are not readily decodable. Change: qla2xxx: Make FPIN events prints human readable. - ER146879: Add support to clear SCM Stats Change: qla2xxx: Added support to clear SCM/SCMR Stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Allow get host stat during reset and sync reset. - ERXXXXXX: qla2xxx: Set reset_cmd_err_cnt on reset failure only. - ERXXXXXX: qla2xxx: Add isolated flag and return EPERM on isolation. - ERXXXXXX: qla2xxx: Count short term link if link comes back in 10 sec. - ERXXXXXX: qla2xxx: Don't check for fw_started while posting nvme command. - ERXXXXXX: qla2xxx: Pass irq_offset to blk_mq_pci_map_queues API. - ERXXXXXX: qla2xxx: lockdown: fix stale sp access. - BZ1868688: qla2xxx: tear down session if FW say its down. - 10.02.00.02.a9-k1 BH 09/03/2020 - ER147554 - sg_reset appears hung iterating over too many Qpairs. Change - qla2xxx: limit interrupt vectors to number of cpu. - ERXXXXX - qla2xxx: klocwork: Fix Bit field 'mpi_-' has one bit and is signed. - ERXXXXX - qla2xxx: Change post del message from debug level to log level. - ERXXXXX - qla2xxx: lockdown: fixup - Change error response as per API test. - ERXXXXX - qla2xxx: Fix map_queue interface to use the correct blk-mq call. - ERXXXXX - Added Structural changes for SCM Phase 2 support. Change : qla2xxx: Update structure definitions for SCM to support backward compatibility. - 10.02.00.02.a8-k1 BH 08/30/2020 - ERXXXXXX - Fix point-to-point (N2N) device discovery issue. Change - qla2xxx: Fix point-to-point (N2N) device discovery issue. - ERXXXXXX - To wait for ABTS response on I/O timeouts for NVMe. Change - qla2xxx: To wait for ABTS response on I/O timeouts for NVMe. - ER147523 - BSG stack trace and SCM display issues. Change - SCM: Functional regression with a6 release. - ER 147413 - edif: Fix issue with DIF enable target discovery. Change - qla2xxx: edif: Fix issue with DIF enable target discovery. - ER147480 clear ASYNC_ACTIVE flag to allow relogin. Change - qla2xxx: fix stuck session. - ERXXXXXX - lockdown: add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - 10.02.00.02.a7-k1 BH 08/22/2020 - ER147495 - edif changes Change - qla2xxx: edif: fix nvme discovery failure qla2xxx: edif: fix els corruption. - ERXXXXXX - add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - ERXXXXXX: SCMR changes Change - qla2xxx: SCMR: Correct scmr_outstanding_reqs accounting. qla2xxx: SCM: Changes to segregate current_events and current_state. qla2xxx: SCMR: Increase local array size. - ER147298 : USCM "Congestion Warning" counter regression Change - qla2xxx: Correct FPIN Structure Definition (Severity). - 10.02.00.02.a6-k1 BH 08/13/2020 - ERXXXXXX - fix crash on session cleanup + unload. Change - qla2xxx: fix crash on session cleanup + unload. - ER147329 - edif changes Change - qla2xxx: edif: fix compile error. do not submit qla2xxx: edif: fix double free on ELS send failure. qla2xxx: edif: reject els if non secure device. qla2xxx: edif: reject ELS on session down. qla2xxx: edif: redefine purex dest addr to be more consistent. qla2xxx: edif: tweak debug messages. qla2xxx: edif: fix nvme+edif target connect problem. - ER147460 - issue with Diag test on QCC CLI 2.4.0 build 10 with 10.2.00.2-a5 driver Change - qla2xxx: edif: move bsg auth els into separate routine. qla2xxx: edif: Fix error in BSG ELS path that has valid response data. - ER147312 - Add support to report MPI FW state. Change - qla2xxx: Add support to report MPI FW state. qla2xxx: Fix reset of MPI firmware. qla2xxx: Fix MPI reset needed message. - 10.02.00.02.a5-k1 BH 07/31/2020 - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. Change - qla2xxx: Don't process target debugfs stats if port is isolated. - ERXXXXXX : Add SCM stats to scmr_stats node. Change - qla2xxx: Add SCM stats to scmr_stats node. - ER147419 : Fix crash due to request q pointer extraction failure. Change - qla2xxx: Latency measurement patch. - ERXXXXXX : edif: remove redundant field in port_id_t Change -qla2xxx: edif: remove redundant field in port_id_t - ER147331 : extract bbc from PLOGI template payload. Change -qla2xxx: Fix buffer-buffer credit extraction error - ERXXXXXX : Split qla2x00_configure_local_loop() Change scsi: qla2xxx: Split qla2x00_configure_local_loop() - ERXXXXXX : SCMR - Add I/O flow control. Change - qla2xxx: SCMR - Add I/O flow control. - 10.02.00.02.a4-k1 BH 07/23/2020 - ER147402 - Do not install nvme auto connect script if OS is installing it. Change - qla2xxx: auto-connect scripts are install based on nvme-cli package. - ERXXXXXX - Fixed return status of nvme fcp request. Change - qla2xxx: Set NVME status code for failed NVME FCP request. - ERXXXXXX - Multi-que support for TMF. Change - qla2xxx: Multi-que support for TMF. - ERXXXXXX ? edif changes Change - qla2xxx: edif: simplify reserve/release of sa_index. qla2xxx: edif: tweak debug log. qla2xxx: edif: adjust ELS resp length. qla2xxx: edif: send logo on app stop. qla2xxx: edif: remove prlo in session deletion. qla2xxx: edif: Fix app stop stall. - ER147298 - USCM "Congestion Warning" counter regression w/.65 driver. Change - qla2xxx: Correct fpin_descriptor definition. qla2xxx: Consolidate EDIF & SCM Purex Calls. - ERXXXXXX - Calculate avg. time taken by different components for IO completion. Change - qla2xxx: Latency measurement patch. - 10.02.00.02.a3-k1 BH 07/16/2020 - ER147348 - Observing the firmware dump while running the qaucli -g post port isolation. Change - qla2xxx: Don't check firmware state in case of chip is down. - ER147338 - SLES: Driver load failed - modprobe: ERROR: module 'qla2xxx' is unsupported Change - qla2xxx: Add support for loading external modules on SuSE. - ER147361 - System panic after enabling port isolated during TimeOutReset. Change - qla2xxx: Synchronize the update the host counters using lock. - ER147370 - Hardware Error counter not incrementing for MBX command timeout Change - qla2xxx: Update hardware error count for various error conditions. - ERXXXXXX - The change is to help in debuggging. Change - qla2xxx: Move some messages from debug to normal log level. - ER147346 - Observed a call trace after port isolation. Change - qla2xxx: Fix the call trace for flush workqueue. - ERXXXXXX - For debug purpose Change - qla2xxx: Add error counters to debugfs node - 10.02.00.02.a2-k1 AE 07/10/2020 - ERXXXXXX - qla2xxx: Fix TCM compilation issues. Change - Enabled build of tcm_qla2xxx module and fixed compile issues. - ERXXXXXX - qla2xxx: edif : Added back the app_stop wait and avoid if link is down. Change - Added wait during app stop. - ERXXXXXX - qla2xxx: Set BIT_13 for NVMe Async events. Change - Driver changes to skip SLER for Async event command. - ER147323 - qla2xxx: Correct the check for sscanf return value. Change - Driver updated to check version correctly. - ERXXXXXX - qla2xxx: v2: Add EDIF support. Change - Refactoring EDIF code for modularity. - ER147298 - Congestion Warning/Alarm counters fail to increment Change - Update driver to increment the counters for congestion signals. - 10.02.00.02.a1-k1 AE 06/29/2020 - qla2xxx: Enable IOCB throttling by default. - qla2xxx: Implementation to get and manage host, target stats and initiator port. - qla2xxx: Add SLER and PI control support. - qla2xxx: Do not log message when reading port speed via sysfs - qla2xxx: fix null pointer access. - qla2xxx: Use MPI hang trigger to do PEGTUNE halt. - qla2xxx: Reduce erroneous error in link reset path - qla2xxx: v2: fix stalled N2N reconnect. - qla2xxx: Fix warnings on SLES12SP5. - qla2xxx: Fix compilation issues on SLES15 - qla2xxx: Compilation Fixes for SLES15SP1. - qla2xxx: Debugfs compilation issue fix for RH7.6. - qla2xxx: Fix gcc test compile error output being printed. - qla2xxx: Timestamp device online and offline transitions. - qla2xxx: Add rport fields in debugfs. - qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices. - qla2xxx: Setup debugfs entries for remote ports. - qla2xxx: Fix edif related compilation issue on RH7.6. - Fixes for compilation on hpe branch - qla2xxx: Compilation fixes for RH8.2 - qla2xxx: Compilation changes for RH7.6 - qla2xxx: Fixes for compilation on RH7.x I - qla2xxx: bsg_job to bsg_job_t - qla2xxx: I Unify source code to work with newer kernels. - qla2xxx: Makefile changes from code-uni-devel-10x. - qla2xxx: qla_edif file changes to compile the driver. - qla2xxx: Fix compilation issues. - qla2xxx: Fix Makefile issue. - qla2xxx: fix compile error - qla2xxx: Use explicit LOGO in target mode - qla2xxx: Add EDIF support. - qla2xxx: Addd edif related files. - qla2xxx: Fix MPI failure AEN (8200) handling. - qla2xxx: SCM - Backport optimizations and style changes from upstream work. - qla2xxx: Fix warning in qla_attr.c file. - qla2xxx: Fix nvme compilation error. - qla2xxx: Fix crash in alloc w/GFP_KERNEL + interrupt - Author : Quinn Tran <qutran@marvell.com> qla2xxx: v2: add iocb resource tracking. - qla2xxx: Fix WARN_ON in qla_nvme_register_hba. - qla2xxx: Allow ql2xextended_error_logging special value 1 to be set anytime. - qla2xxx: Make tgt_port_database available in initiator mode. - qla2xxx: reduce noisy debug message. - qla2xxx: Fix mailbox Ch erroneous error - qla2xxx: fix login timeout. - qla2xxx: Accomodate for SCM FW attribute bit change. - qla2xxx: post FC event (FPIN) to transport FPIN handler. - qla2xxx: Hide fc_host_fpin_rcv kernel dependency. - qla2xxx: Add changes to compile across various kernels. - qla2xxx: Use active targets to update SCM stats. - qla2xxx: Move SCM functions to qla_isr to keep changes local. - qla2xxx: Code to process FLOGI ACC extended payload. - qedf: Fix compilation issue - revisit. - qla2xxx: SCM Phase 1 Implementation + 2 other patches. - qla2xxx: Enable PUREX passthru post ISP reset. - qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV. - qla2xxx: performance tweak - scsi: qla2xxx: fix fcport null pointer access. - fixup! qla2xxx: Fix unbound NVME response length. - scsi: qla2xxx: Fix unbound NVME response length - qla2xxx: Add host attribute to trigger MPI hang. - qla2xxx: ONEOFF: silent dbg messages for good path io. - qla2xxx: ONEOFF: fix pDIF detection - qla2xxx: Snoop inquiry response atleast 168 bytes to determine proprietary DIF. - qla2xxx: ONEOFF: add debug counters for T10-PI/DIF - qla2xxx: ONEOFF: add MQ support for HP3PAR propritary T10-PI - qla2xxx: HPE 3PAR private T10-PI support. - qla2xxx: Check for fabric_priority flag during login - qla2xxx: use iocb_fabric_priority flag - qla2xxx: Fix QoS name and add debug logs - qla2xxx: Correction to tests for iocb fabric and fcport qos. - qla2xxx: Use ->isp_ops->read_optrom() in qla26xx_read_qos_fcport_table(). - qla2xxx: QoS fcport table index initialization improvement. - qla2xxx: Add QoS fcport table index to speed up search. - qla2xxx: Reduce stack on qos fcport priority routines. - qla2xxx: HPE: Register FDMI QOS - qla2xxx: Add bsg interface for qos lun level bitmask. - qla2xxx: Read E2E QoS fcport priority bitmasks from flash. - qla2xxx: Abstract qos lun level mask for iocb cs_ctl field. - qla2xxx: Add fabric priority qos lun iocb mechanism. - qla2xxx: Implement CT command GFO (Get Fabric Object). - qla2xxx: Add support for fabric priority per target. - qla2xxx: fix mtcp dump collection failure. - qla2xxx: Set Nport ID for N2N - qla2xxx: Fix crash during device discovery. - qla2xxx: Handle NVME status iocb correctly. - qla2xxx: Remove restriction of FC T10-PI and NVME - qla2xxx: serialize fc_port alloc in N2N - qla2xxx: NPIV does not come up after FW dump. - qla2xxx: fix RDP respond data format bug. - qla2xxx: force semaphore on flash validation failure. - qla2xxx: add more FW debug information - qla2xxx: Revert: Disable T10-DIF feature with FC-NVMe during probe - qla2xxx: Update BPM enablement semantics. - qla2xxx: fix FW resource print error. - qla2xxx: Use a dedicated interrupt handler for 'handshake-required' ISPs. - qla2xxx: Ensure flash updates return possible failure status through bsg interface. - qla2xxx: Improved secure flash support messages - qla2xxx: fix flag passing error - qla2xxx: Use FC generic update firmware options routine for ISP27xx. - qla2xxx: Avoid setting firmware options twice in 24xx_update_fw_options. - qla2xxX: Add 16.0GT for PCI String - qla2xxx: Use FW_STARTED macro - qla2xxx: Add fixes for mailbox command - qla2xxx: Fix login IOCB flag - qla2xxx: Save rscn_gen for new fcport - qla2xxx: firmware option 3 is clobbered by speed set - qla2xxx: ISP28xx active FW region - qla2xxx: Add portname to print logs in qla24xx_logio_entry(). - qla2xxx: Correction to MB in-direction selection in qla2x00_echo_test(). - qla2xxx: Correction to selection of loopback/echo test. - qla2xxx: Use endian macros to assign static fields in fwdump header. - qla2xxx: Add Speed in SFP print information - qla2xxx: Fix RDP response size - qla2xxx: Handle cases for limiting RDP response payload length. - qla2xxx: Add deferred queue for processing ABTS and RDP. - qla2xxx: Cleanup ELS/PUREX iocb fields. - qla2xxx: Add devid's and conditionals for 28xx. - qla2xxx: Add vendor extended FDMI additions and amendments. - qla2xxx: Provide separate RDP enable. - qla2xxx: Add vendor extended RDP additions and amendments. - qla2xxx: Add changes in preparation for vendor extended FDMI/RDP. - qla2xxx: Add 2061 PCI ID - qla2xxx: Remove all DIX-0 references - qla2xxx: Add endianizer macro calls to fc host stats. - qla2xxx: Add sysfs node for D-Port Diagnostics AEN data. - qla2xxx: Move free of fcport out of interrupt context. - qla2xxx: Add beacon LED config sysfs interface. - qla2xxx: Add sysfs hooks for FC-NVMe autoconnect - 10.01.00.22-k AE 06/29/2020 - Upstream driver as part of Linux 5.6 - 10.02.01.00.a14-k1 BH 11/06/2020 - ER146725: eDIF another driver panic running script: ./test_target_no_unload.sh Change: qla2xxx: Fix crash in qla_nvme_abort_set_option. - ER147771: Call Trace while shutting down the adapter ports (LINK DOWN). Change: qla2xxx: Handle aborts correctly for port undergoing deletion. - ERXXXXXX: qla2xxx: Add scsi_change_queue_depth to slave configure. - 10.02.02.00.a13-k1 BH 10/28/2020 - ER147600: Cisco: rpd ELS cmd fail to fetch the speed capabilities Change: qla2xxx: Used correct rdp spec, which was broken during code clean-up. - ER147695: FC-NVMe target discovery fails when initator wwpn < target wwpn in an N2N (Direct Attach) config Change: qla2xxx: fix N2N + NVME connect retry fail - ER147832: Issue with uSCM Linux with QCC CLI for some configuration Change: qla2xxx: Show event severity only when device state is congested. - ER147824 : scmr_stat sysfs node runs out of memory Change: qla2xxx: Come up with a compact version of scmr_stat - ER147823: NVMe IO is not getting throttled up or down. Change: qla2xxx: Enable throttle control for NVMe targets for Peer Congestion. - ERXXXXXX: qla2xxx: Count tgt short term link if link comes back before dev_loss_tmo. - ERXXXXXX: qla2xxx: Correct the check for fcport while displaying target counters. - ERXXXXXX: qla2xxx: Change trigger for host short term link down to dev loss tmo. - ERXXXXXX: qla2xxx: Move an SCM log under a debug level. - ERXXXXXX: qla2xxx: Set vendor_rsp[0] value. - ERXXXXXX: qla2xxx: Make throttling messages more informative. - 10.02.02.00.a12-k1 SK 10/15/2020 - ER147625: NVMe IO's are failing with Read/Write after LIP reset. Change: qla2xxx:Return EBUSY until the remote port delete finishes. - ER147653: Target side strongswan start/stop, make initiator crashed. Change: qla2xxx: edif: v2 fix double bsg done. - ER147791: USCM: clear option is not clearing hba alarm/warning, or clear cong or nvme target stats. Change: qla2xxx: Clear Sev and NVMe Target Stats. - ER147793: USCM: Throttling has wrong throttling up info and event period is not honored. Change: qla2xxx: Fix Throttling algorithm regression. - ER147759: NVMe Admin commands are getting throttled and causing admin queue failures. Change: qla2xxx: Throttle NVMe I/O commands only. - ERXXXXXX: qla2xxx: edif: fix aes_gmac mode. - ERXXXXXX: qla2xxx: edif: v2: standardize on port_id_t for bsg api. - ERXXXXXX: qla2xxx: edif: fix 4byte align. - ERXXXXXX: qla2xxx: edif: fix ELS meta data. - ERXXXXXX: qla2xxx: Clear Congestion State/Throttling during chip Reset. - ERXXXXXX: qla2xxx: Clear SCM Severity as part of SCM Stats Clear. - 10.02.00.02.a11-k1 BH 10/09/2020 - ER147734 : Lip reset on the isolated port causes server crash Change: qla2xxx: Don't allow FW, MPI and lip reset on isolated port. - ER147479 - PPC BE RH7.6 - qla2xxx driver loading - machine crashed. Change: qla2xxx: Fixes for big endian machines - ER147646: Call Trace observed while validating a MPI Pause test scenario. Change: qla2xxx: Correct the WARN_ON check in qla_nvme_abort_set_option. - ER147615: Throttling does not work with low I/Os. Change: qla2xxx: Check and round off fractional I/Os to 1 on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: List NVMe targets under scmr_stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Don't check for port isolation during abort isp. - ERXXXXXX: qla2xxx: SCM: Turn off SCM port parameter update mailbox command. - ERXXXXXX: qla2xxx: Fix I/O failures during remote port toggle testing - 10.02.00.02.a10-k1 BH 09/25/2020 SCM Changes: - ERXXXXXX: Changes - qla2xxx: Clear Congestion state when an RSCN is received/target is torn down. qla2xxx: throttling algorithm improvement. qla2xxx: Add throttling support for NVMe targets. EDIF Changes: - ERXXXXX: LUN loss on ipsec stop/start on target side. Change: save Nport on receive of PLOGI - ERXXXXX: fix ELS receive collision between physical and NPIV hosts. Change: remove erroneous source Nport ID search. - ER147570: FCP Performance Drop in latest driver for smaller IOs size. Change: qla2xxx: Change WQ_UNBOUND to WQ_MEM_RECLAIM. WQ_MEM_RECLAIM : wq is guaranteed to have at least one execution context regardless of memory pressure. - ER147632: QLE2774: RHEL 8.2 System crashes while upgrading he FW from 9.6.0 to 9.6.1 with QCC CLI build 12 Change: qla2xxx: Fix system crash on nvme abort path by checking sp of aborting command before accessing it. - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. - ER147645: System panic while trying to capture debugfs stats for EED. Change: qla2xxx: Check rport before accessing target number. - ER147632: Fix potential stale mem access Change: remove stale sp pointer reference - CQXXXXXX: FPIN events are not readily decodable. Change: qla2xxx: Make FPIN events prints human readable. - ER146879: Add support to clear SCM Stats Change: qla2xxx: Added support to clear SCM/SCMR Stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Allow get host stat during reset and sync reset. - ERXXXXXX: qla2xxx: Set reset_cmd_err_cnt on reset failure only. - ERXXXXXX: qla2xxx: Add isolated flag and return EPERM on isolation. - ERXXXXXX: qla2xxx: Count short term link if link comes back in 10 sec. - ERXXXXXX: qla2xxx: Don't check for fw_started while posting nvme command. - ERXXXXXX: qla2xxx: Pass irq_offset to blk_mq_pci_map_queues API. - ERXXXXXX: qla2xxx: lockdown: fix stale sp access. - BZ1868688: qla2xxx: tear down session if FW say its down. - 10.02.00.02.a9-k1 BH 09/03/2020 - ER147554 - sg_reset appears hung iterating over too many Qpairs. Change - qla2xxx: limit interrupt vectors to number of cpu. - ERXXXXX - qla2xxx: klocwork: Fix Bit field 'mpi_-' has one bit and is signed. - ERXXXXX - qla2xxx: Change post del message from debug level to log level. - ERXXXXX - qla2xxx: lockdown: fixup - Change error response as per API test. - ERXXXXX - qla2xxx: Fix map_queue interface to use the correct blk-mq call. - ERXXXXX - Added Structural changes for SCM Phase 2 support. Change : qla2xxx: Update structure definitions for SCM to support backward compatibility. - 10.02.00.02.a8-k1 BH 08/30/2020 - ERXXXXXX - Fix point-to-point (N2N) device discovery issue. Change - qla2xxx: Fix point-to-point (N2N) device discovery issue. - ERXXXXXX - To wait for ABTS response on I/O timeouts for NVMe. Change - qla2xxx: To wait for ABTS response on I/O timeouts for NVMe. - ER147523 - BSG stack trace and SCM display issues. Change - SCM: Functional regression with a6 release. - ER 147413 - edif: Fix issue with DIF enable target discovery. Change - qla2xxx: edif: Fix issue with DIF enable target discovery. - ER147480 clear ASYNC_ACTIVE flag to allow relogin. Change - qla2xxx: fix stuck session. - ERXXXXXX - lockdown: add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - 10.02.00.02.a7-k1 BH 08/22/2020 - ER147495 - edif changes Change - qla2xxx: edif: fix nvme discovery failure qla2xxx: edif: fix els corruption. - ERXXXXXX - add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - ERXXXXXX: SCMR changes Change - qla2xxx: SCMR: Correct scmr_outstanding_reqs accounting. qla2xxx: SCM: Changes to segregate current_events and current_state. qla2xxx: SCMR: Increase local array size. - ER147298 : USCM "Congestion Warning" counter regression Change - qla2xxx: Correct FPIN Structure Definition (Severity). - 10.02.00.02.a6-k1 BH 08/13/2020 - ERXXXXXX - fix crash on session cleanup + unload. Change - qla2xxx: fix crash on session cleanup + unload. - ER147329 - edif changes Change - qla2xxx: edif: fix compile error. do not submit qla2xxx: edif: fix double free on ELS send failure. qla2xxx: edif: reject els if non secure device. qla2xxx: edif: reject ELS on session down. qla2xxx: edif: redefine purex dest addr to be more consistent. qla2xxx: edif: tweak debug messages. qla2xxx: edif: fix nvme+edif target connect problem. - ER147460 - issue with Diag test on QCC CLI 2.4.0 build 10 with 10.2.00.2-a5 driver Change - qla2xxx: edif: move bsg auth els into separate routine. qla2xxx: edif: Fix error in BSG ELS path that has valid response data. - ER147312 - Add support to report MPI FW state. Change - qla2xxx: Add support to report MPI FW state. qla2xxx: Fix reset of MPI firmware. qla2xxx: Fix MPI reset needed message. - 10.02.00.02.a5-k1 BH 07/31/2020 - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. Change - qla2xxx: Don't process target debugfs stats if port is isolated. - ERXXXXXX : Add SCM stats to scmr_stats node. Change - qla2xxx: Add SCM stats to scmr_stats node. - ER147419 : Fix crash due to request q pointer extraction failure. Change - qla2xxx: Latency measurement patch. - ERXXXXXX : edif: remove redundant field in port_id_t Change -qla2xxx: edif: remove redundant field in port_id_t - ER147331 : extract bbc from PLOGI template payload. Change -qla2xxx: Fix buffer-buffer credit extraction error - ERXXXXXX : Split qla2x00_configure_local_loop() Change scsi: qla2xxx: Split qla2x00_configure_local_loop() - ERXXXXXX : SCMR - Add I/O flow control. Change - qla2xxx: SCMR - Add I/O flow control. - 10.02.00.02.a4-k1 BH 07/23/2020 - ER147402 - Do not install nvme auto connect script if OS is installing it. Change - qla2xxx: auto-connect scripts are install based on nvme-cli package. - ERXXXXXX - Fixed return status of nvme fcp request. Change - qla2xxx: Set NVME status code for failed NVME FCP request. - ERXXXXXX - Multi-que support for TMF. Change - qla2xxx: Multi-que support for TMF. - ERXXXXXX ? edif changes Change - qla2xxx: edif: simplify reserve/release of sa_index. qla2xxx: edif: tweak debug log. qla2xxx: edif: adjust ELS resp length. qla2xxx: edif: send logo on app stop. qla2xxx: edif: remove prlo in session deletion. qla2xxx: edif: Fix app stop stall. - ER147298 - USCM "Congestion Warning" counter regression w/.65 driver. Change - qla2xxx: Correct fpin_descriptor definition. qla2xxx: Consolidate EDIF & SCM Purex Calls. - ERXXXXXX - Calculate avg. time taken by different components for IO completion. Change - qla2xxx: Latency measurement patch. - 10.02.00.02.a3-k1 BH 07/16/2020 - ER147348 - Observing the firmware dump while running the qaucli -g post port isolation. Change - qla2xxx: Don't check firmware state in case of chip is down. - ER147338 - SLES: Driver load failed - modprobe: ERROR: module 'qla2xxx' is unsupported Change - qla2xxx: Add support for loading external modules on SuSE. - ER147361 - System panic after enabling port isolated during TimeOutReset. Change - qla2xxx: Synchronize the update the host counters using lock. - ER147370 - Hardware Error counter not incrementing for MBX command timeout Change - qla2xxx: Update hardware error count for various error conditions. - ERXXXXXX - The change is to help in debuggging. Change - qla2xxx: Move some messages from debug to normal log level. - ER147346 - Observed a call trace after port isolation. Change - qla2xxx: Fix the call trace for flush workqueue. - ERXXXXXX - For debug purpose Change - qla2xxx: Add error counters to debugfs node - 10.02.00.02.a2-k1 AE 07/10/2020 - ERXXXXXX - qla2xxx: Fix TCM compilation issues. Change - Enabled build of tcm_qla2xxx module and fixed compile issues. - ERXXXXXX - qla2xxx: edif : Added back the app_stop wait and avoid if link is down. Change - Added wait during app stop. - ERXXXXXX - qla2xxx: Set BIT_13 for NVMe Async events. Change - Driver changes to skip SLER for Async event command. - ER147323 - qla2xxx: Correct the check for sscanf return value. Change - Driver updated to check version correctly. - ERXXXXXX - qla2xxx: v2: Add EDIF support. Change - Refactoring EDIF code for modularity. - ER147298 - Congestion Warning/Alarm counters fail to increment Change - Update driver to increment the counters for congestion signals. - 10.02.00.02.a1-k1 AE 06/29/2020 - qla2xxx: Enable IOCB throttling by default. - qla2xxx: Implementation to get and manage host, target stats and initiator port. - qla2xxx: Add SLER and PI control support. - qla2xxx: Do not log message when reading port speed via sysfs - qla2xxx: fix null pointer access. - qla2xxx: Use MPI hang trigger to do PEGTUNE halt. - qla2xxx: Reduce erroneous error in link reset path - qla2xxx: v2: fix stalled N2N reconnect. - qla2xxx: Fix warnings on SLES12SP5. - qla2xxx: Fix compilation issues on SLES15 - qla2xxx: Compilation Fixes for SLES15SP1. - qla2xxx: Debugfs compilation issue fix for RH7.6. - qla2xxx: Fix gcc test compile error output being printed. - qla2xxx: Timestamp device online and offline transitions. - qla2xxx: Add rport fields in debugfs. - qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices. - qla2xxx: Setup debugfs entries for remote ports. - qla2xxx: Fix edif related compilation issue on RH7.6. - Fixes for compilation on hpe branch - qla2xxx: Compilation fixes for RH8.2 - qla2xxx: Compilation changes for RH7.6 - qla2xxx: Fixes for compilation on RH7.x I - qla2xxx: bsg_job to bsg_job_t - qla2xxx: I Unify source code to work with newer kernels. - qla2xxx: Makefile changes from code-uni-devel-10x. - qla2xxx: qla_edif file changes to compile the driver. - qla2xxx: Fix compilation issues. - qla2xxx: Fix Makefile issue. - qla2xxx: fix compile error - qla2xxx: Use explicit LOGO in target mode - qla2xxx: Add EDIF support. - qla2xxx: Addd edif related files. - qla2xxx: Fix MPI failure AEN (8200) handling. - qla2xxx: SCM - Backport optimizations and style changes from upstream work. - qla2xxx: Fix warning in qla_attr.c file. - qla2xxx: Fix nvme compilation error. - qla2xxx: Fix crash in alloc w/GFP_KERNEL + interrupt - Author : Quinn Tran <qutran@marvell.com> qla2xxx: v2: add iocb resource tracking. - qla2xxx: Fix WARN_ON in qla_nvme_register_hba. - qla2xxx: Allow ql2xextended_error_logging special value 1 to be set anytime. - qla2xxx: Make tgt_port_database available in initiator mode. - qla2xxx: reduce noisy debug message. - qla2xxx: Fix mailbox Ch erroneous error - qla2xxx: fix login timeout. - qla2xxx: Accomodate for SCM FW attribute bit change. - qla2xxx: post FC event (FPIN) to transport FPIN handler. - qla2xxx: Hide fc_host_fpin_rcv kernel dependency. - qla2xxx: Add changes to compile across various kernels. - qla2xxx: Use active targets to update SCM stats. - qla2xxx: Move SCM functions to qla_isr to keep changes local. - qla2xxx: Code to process FLOGI ACC extended payload. - qedf: Fix compilation issue - revisit. - qla2xxx: SCM Phase 1 Implementation + 2 other patches. - qla2xxx: Enable PUREX passthru post ISP reset. - qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV. - qla2xxx: performance tweak - scsi: qla2xxx: fix fcport null pointer access. - fixup! qla2xxx: Fix unbound NVME response length. - scsi: qla2xxx: Fix unbound NVME response length - qla2xxx: Add host attribute to trigger MPI hang. - qla2xxx: ONEOFF: silent dbg messages for good path io. - qla2xxx: ONEOFF: fix pDIF detection - qla2xxx: Snoop inquiry response atleast 168 bytes to determine proprietary DIF. - qla2xxx: ONEOFF: add debug counters for T10-PI/DIF - qla2xxx: ONEOFF: add MQ support for HP3PAR propritary T10-PI - qla2xxx: HPE 3PAR private T10-PI support. - qla2xxx: Check for fabric_priority flag during login - qla2xxx: use iocb_fabric_priority flag - qla2xxx: Fix QoS name and add debug logs - qla2xxx: Correction to tests for iocb fabric and fcport qos. - qla2xxx: Use ->isp_ops->read_optrom() in qla26xx_read_qos_fcport_table(). - qla2xxx: QoS fcport table index initialization improvement. - qla2xxx: Add QoS fcport table index to speed up search. - qla2xxx: Reduce stack on qos fcport priority routines. - qla2xxx: HPE: Register FDMI QOS - qla2xxx: Add bsg interface for qos lun level bitmask. - qla2xxx: Read E2E QoS fcport priority bitmasks from flash. - qla2xxx: Abstract qos lun level mask for iocb cs_ctl field. - qla2xxx: Add fabric priority qos lun iocb mechanism. - qla2xxx: Implement CT command GFO (Get Fabric Object). - qla2xxx: Add support for fabric priority per target. - qla2xxx: fix mtcp dump collection failure. - qla2xxx: Set Nport ID for N2N - qla2xxx: Fix crash during device discovery. - qla2xxx: Handle NVME status iocb correctly. - qla2xxx: Remove restriction of FC T10-PI and NVME - qla2xxx: serialize fc_port alloc in N2N - qla2xxx: NPIV does not come up after FW dump. - qla2xxx: fix RDP respond data format bug. - qla2xxx: force semaphore on flash validation failure. - qla2xxx: add more FW debug information - qla2xxx: Revert: Disable T10-DIF feature with FC-NVMe during probe - qla2xxx: Update BPM enablement semantics. - qla2xxx: fix FW resource print error. - qla2xxx: Use a dedicated interrupt handler for 'handshake-required' ISPs. - qla2xxx: Ensure flash updates return possible failure status through bsg interface. - qla2xxx: Improved secure flash support messages - qla2xxx: fix flag passing error - qla2xxx: Use FC generic update firmware options routine for ISP27xx. - qla2xxx: Avoid setting firmware options twice in 24xx_update_fw_options. - qla2xxX: Add 16.0GT for PCI String - qla2xxx: Use FW_STARTED macro - qla2xxx: Add fixes for mailbox command - qla2xxx: Fix login IOCB flag - qla2xxx: Save rscn_gen for new fcport - qla2xxx: firmware option 3 is clobbered by speed set - qla2xxx: ISP28xx active FW region - qla2xxx: Add portname to print logs in qla24xx_logio_entry(). - qla2xxx: Correction to MB in-direction selection in qla2x00_echo_test(). - qla2xxx: Correction to selection of loopback/echo test. - qla2xxx: Use endian macros to assign static fields in fwdump header. - qla2xxx: Add Speed in SFP print information - qla2xxx: Fix RDP response size - qla2xxx: Handle cases for limiting RDP response payload length. - qla2xxx: Add deferred queue for processing ABTS and RDP. - qla2xxx: Cleanup ELS/PUREX iocb fields. - qla2xxx: Add devid's and conditionals for 28xx. - qla2xxx: Add vendor extended FDMI additions and amendments. - qla2xxx: Provide separate RDP enable. - qla2xxx: Add vendor extended RDP additions and amendments. - qla2xxx: Add changes in preparation for vendor extended FDMI/RDP. - qla2xxx: Add 2061 PCI ID - qla2xxx: Remove all DIX-0 references - qla2xxx: Add endianizer macro calls to fc host stats. - qla2xxx: Add sysfs node for D-Port Diagnostics AEN data. - qla2xxx: Move free of fcport out of interrupt context. - qla2xxx: Add beacon LED config sysfs interface. - qla2xxx: Add sysfs hooks for FC-NVMe autoconnect - 10.01.00.22-k AE 06/29/2020 - Upstream driver as part of Linux 5.6 - 10.02.01.00.a14-k1 BH 11/06/2020 - ER146725: eDIF another driver panic running script: ./test_target_no_unload.sh Change: qla2xxx: Fix crash in qla_nvme_abort_set_option. - ER147771: Call Trace while shutting down the adapter ports (LINK DOWN). Change: qla2xxx: Handle aborts correctly for port undergoing deletion. - ERXXXXXX: qla2xxx: Add scsi_change_queue_depth to slave configure. - 10.02.02.00.a13-k1 BH 10/28/2020 - ER147600: Cisco: rpd ELS cmd fail to fetch the speed capabilities Change: qla2xxx: Used correct rdp spec, which was broken during code clean-up. - ER147695: FC-NVMe target discovery fails when initator wwpn < target wwpn in an N2N (Direct Attach) config Change: qla2xxx: fix N2N + NVME connect retry fail - ER147832: Issue with uSCM Linux with QCC CLI for some configuration Change: qla2xxx: Show event severity only when device state is congested. - ER147824 : scmr_stat sysfs node runs out of memory Change: qla2xxx: Come up with a compact version of scmr_stat - ER147823: NVMe IO is not getting throttled up or down. Change: qla2xxx: Enable throttle control for NVMe targets for Peer Congestion. - ERXXXXXX: qla2xxx: Count tgt short term link if link comes back before dev_loss_tmo. - ERXXXXXX: qla2xxx: Correct the check for fcport while displaying target counters. - ERXXXXXX: qla2xxx: Change trigger for host short term link down to dev loss tmo. - ERXXXXXX: qla2xxx: Move an SCM log under a debug level. - ERXXXXXX: qla2xxx: Set vendor_rsp[0] value. - ERXXXXXX: qla2xxx: Make throttling messages more informative. - 10.02.02.00.a12-k1 SK 10/15/2020 - ER147625: NVMe IO's are failing with Read/Write after LIP reset. Change: qla2xxx:Return EBUSY until the remote port delete finishes. - ER147653: Target side strongswan start/stop, make initiator crashed. Change: qla2xxx: edif: v2 fix double bsg done. - ER147791: USCM: clear option is not clearing hba alarm/warning, or clear cong or nvme target stats. Change: qla2xxx: Clear Sev and NVMe Target Stats. - ER147793: USCM: Throttling has wrong throttling up info and event period is not honored. Change: qla2xxx: Fix Throttling algorithm regression. - ER147759: NVMe Admin commands are getting throttled and causing admin queue failures. Change: qla2xxx: Throttle NVMe I/O commands only. - ERXXXXXX: qla2xxx: edif: fix aes_gmac mode. - ERXXXXXX: qla2xxx: edif: v2: standardize on port_id_t for bsg api. - ERXXXXXX: qla2xxx: edif: fix 4byte align. - ERXXXXXX: qla2xxx: edif: fix ELS meta data. - ERXXXXXX: qla2xxx: Clear Congestion State/Throttling during chip Reset. - ERXXXXXX: qla2xxx: Clear SCM Severity as part of SCM Stats Clear. - 10.02.00.02.a11-k1 BH 10/09/2020 - ER147734 : Lip reset on the isolated port causes server crash Change: qla2xxx: Don't allow FW, MPI and lip reset on isolated port. - ER147479 - PPC BE RH7.6 - qla2xxx driver loading - machine crashed. Change: qla2xxx: Fixes for big endian machines - ER147646: Call Trace observed while validating a MPI Pause test scenario. Change: qla2xxx: Correct the WARN_ON check in qla_nvme_abort_set_option. - ER147615: Throttling does not work with low I/Os. Change: qla2xxx: Check and round off fractional I/Os to 1 on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: List NVMe targets under scmr_stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Don't check for port isolation during abort isp. - ERXXXXXX: qla2xxx: SCM: Turn off SCM port parameter update mailbox command. - ERXXXXXX: qla2xxx: Fix I/O failures during remote port toggle testing - 10.02.00.02.a10-k1 BH 09/25/2020 SCM Changes: - ERXXXXXX: Changes - qla2xxx: Clear Congestion state when an RSCN is received/target is torn down. qla2xxx: throttling algorithm improvement. qla2xxx: Add throttling support for NVMe targets. EDIF Changes: - ERXXXXX: LUN loss on ipsec stop/start on target side. Change: save Nport on receive of PLOGI - ERXXXXX: fix ELS receive collision between physical and NPIV hosts. Change: remove erroneous source Nport ID search. - ER147570: FCP Performance Drop in latest driver for smaller IOs size. Change: qla2xxx: Change WQ_UNBOUND to WQ_MEM_RECLAIM. WQ_MEM_RECLAIM : wq is guaranteed to have at least one execution context regardless of memory pressure. - ER147632: QLE2774: RHEL 8.2 System crashes while upgrading he FW from 9.6.0 to 9.6.1 with QCC CLI build 12 Change: qla2xxx: Fix system crash on nvme abort path by checking sp of aborting command before accessing it. - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. - ER147645: System panic while trying to capture debugfs stats for EED. Change: qla2xxx: Check rport before accessing target number. - ER147632: Fix potential stale mem access Change: remove stale sp pointer reference - CQXXXXXX: FPIN events are not readily decodable. Change: qla2xxx: Make FPIN events prints human readable. - ER146879: Add support to clear SCM Stats Change: qla2xxx: Added support to clear SCM/SCMR Stats on ISP 27xx/28xx Series Adapters - ERXXXXXX: qla2xxx: Allow get host stat during reset and sync reset. - ERXXXXXX: qla2xxx: Set reset_cmd_err_cnt on reset failure only. - ERXXXXXX: qla2xxx: Add isolated flag and return EPERM on isolation. - ERXXXXXX: qla2xxx: Count short term link if link comes back in 10 sec. - ERXXXXXX: qla2xxx: Don't check for fw_started while posting nvme command. - ERXXXXXX: qla2xxx: Pass irq_offset to blk_mq_pci_map_queues API. - ERXXXXXX: qla2xxx: lockdown: fix stale sp access. - BZ1868688: qla2xxx: tear down session if FW say its down. - 10.02.00.02.a9-k1 BH 09/03/2020 - ER147554 - sg_reset appears hung iterating over too many Qpairs. Change - qla2xxx: limit interrupt vectors to number of cpu. - ERXXXXX - qla2xxx: klocwork: Fix Bit field 'mpi_-' has one bit and is signed. - ERXXXXX - qla2xxx: Change post del message from debug level to log level. - ERXXXXX - qla2xxx: lockdown: fixup - Change error response as per API test. - ERXXXXX - qla2xxx: Fix map_queue interface to use the correct blk-mq call. - ERXXXXX - Added Structural changes for SCM Phase 2 support. Change : qla2xxx: Update structure definitions for SCM to support backward compatibility. - 10.02.00.02.a8-k1 BH 08/30/2020 - ERXXXXXX - Fix point-to-point (N2N) device discovery issue. Change - qla2xxx: Fix point-to-point (N2N) device discovery issue. - ERXXXXXX - To wait for ABTS response on I/O timeouts for NVMe. Change - qla2xxx: To wait for ABTS response on I/O timeouts for NVMe. - ER147523 - BSG stack trace and SCM display issues. Change - SCM: Functional regression with a6 release. - ER 147413 - edif: Fix issue with DIF enable target discovery. Change - qla2xxx: edif: Fix issue with DIF enable target discovery. - ER147480 clear ASYNC_ACTIVE flag to allow relogin. Change - qla2xxx: fix stuck session. - ERXXXXXX - lockdown: add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - 10.02.00.02.a7-k1 BH 08/22/2020 - ER147495 - edif changes Change - qla2xxx: edif: fix nvme discovery failure qla2xxx: edif: fix els corruption. - ERXXXXXX - add mpi flash lock down support Change - qla2xxx: lockdown: add mpi flash lock down support - ERXXXXXX: SCMR changes Change - qla2xxx: SCMR: Correct scmr_outstanding_reqs accounting. qla2xxx: SCM: Changes to segregate current_events and current_state. qla2xxx: SCMR: Increase local array size. - ER147298 : USCM "Congestion Warning" counter regression Change - qla2xxx: Correct FPIN Structure Definition (Severity). - 10.02.00.02.a6-k1 BH 08/13/2020 - ERXXXXXX - fix crash on session cleanup + unload. Change - qla2xxx: fix crash on session cleanup + unload. - ER147329 - edif changes Change - qla2xxx: edif: fix compile error. do not submit qla2xxx: edif: fix double free on ELS send failure. qla2xxx: edif: reject els if non secure device. qla2xxx: edif: reject ELS on session down. qla2xxx: edif: redefine purex dest addr to be more consistent. qla2xxx: edif: tweak debug messages. qla2xxx: edif: fix nvme+edif target connect problem. - ER147460 - issue with Diag test on QCC CLI 2.4.0 build 10 with 10.2.00.2-a5 driver Change - qla2xxx: edif: move bsg auth els into separate routine. qla2xxx: edif: Fix error in BSG ELS path that has valid response data. - ER147312 - Add support to report MPI FW state. Change - qla2xxx: Add support to report MPI FW state. qla2xxx: Fix reset of MPI firmware. qla2xxx: Fix MPI reset needed message. - 10.02.00.02.a5-k1 BH 07/31/2020 - ER147418: server crash seen when trying to capture the debugfs stat on isolated port. Change - qla2xxx: Don't process target debugfs stats if port is isolated. - ERXXXXXX : Add SCM stats to scmr_stats node. Change - qla2xxx: Add SCM stats to scmr_stats node. - ER147419 : Fix crash due to request q pointer extraction failure. Change - qla2xxx: Latency measurement patch. - ERXXXXXX : edif: remove redundant field in port_id_t Change -qla2xxx: edif: remove redundant field in port_id_t - ER147331 : extract bbc from PLOGI template payload. Change -qla2xxx: Fix buffer-buffer credit extraction error - ERXXXXXX : Split qla2x00_configure_local_loop() Change scsi: qla2xxx: Split qla2x00_configure_local_loop() - ERXXXXXX : SCMR - Add I/O flow control. Change - qla2xxx: SCMR - Add I/O flow control. - 10.02.00.02.a4-k1 BH 07/23/2020 - ER147402 - Do not install nvme auto connect script if OS is installing it. Change - qla2xxx: auto-connect scripts are install based on nvme-cli package. - ERXXXXXX - Fixed return status of nvme fcp request. Change - qla2xxx: Set NVME status code for failed NVME FCP request. - ERXXXXXX - Multi-que support for TMF. Change - qla2xxx: Multi-que support for TMF. - ERXXXXXX ? edif changes Change - qla2xxx: edif: simplify reserve/release of sa_index. qla2xxx: edif: tweak debug log. qla2xxx: edif: adjust ELS resp length. qla2xxx: edif: send logo on app stop. qla2xxx: edif: remove prlo in session deletion. qla2xxx: edif: Fix app stop stall. - ER147298 - USCM "Congestion Warning" counter regression w/.65 driver. Change - qla2xxx: Correct fpin_descriptor definition. qla2xxx: Consolidate EDIF & SCM Purex Calls. - ERXXXXXX - Calculate avg. time taken by different components for IO completion. Change - qla2xxx: Latency measurement patch. - 10.02.00.02.a3-k1 BH 07/16/2020 - ER147348 - Observing the firmware dump while running the qaucli -g post port isolation. Change - qla2xxx: Don't check firmware state in case of chip is down. - ER147338 - SLES: Driver load failed - modprobe: ERROR: module 'qla2xxx' is unsupported Change - qla2xxx: Add support for loading external modules on SuSE. - ER147361 - System panic after enabling port isolated during TimeOutReset. Change - qla2xxx: Synchronize the update the host counters using lock. - ER147370 - Hardware Error counter not incrementing for MBX command timeout Change - qla2xxx: Update hardware error count for various error conditions. - ERXXXXXX - The change is to help in debuggging. Change - qla2xxx: Move some messages from debug to normal log level. - ER147346 - Observed a call trace after port isolation. Change - qla2xxx: Fix the call trace for flush workqueue. - ERXXXXXX - For debug purpose Change - qla2xxx: Add error counters to debugfs node - 10.02.00.02.a2-k1 AE 07/10/2020 - ERXXXXXX - qla2xxx: Fix TCM compilation issues. Change - Enabled build of tcm_qla2xxx module and fixed compile issues. - ERXXXXXX - qla2xxx: edif : Added back the app_stop wait and avoid if link is down. Change - Added wait during app stop. - ERXXXXXX - qla2xxx: Set BIT_13 for NVMe Async events. Change - Driver changes to skip SLER for Async event command. - ER147323 - qla2xxx: Correct the check for sscanf return value. Change - Driver updated to check version correctly. - ERXXXXXX - qla2xxx: v2: Add EDIF support. Change - Refactoring EDIF code for modularity. - ER147298 - Congestion Warning/Alarm counters fail to increment Change - Update driver to increment the counters for congestion signals. - 10.02.00.02.a1-k1 AE 06/29/2020 - qla2xxx: Enable IOCB throttling by default. - qla2xxx: Implementation to get and manage host, target stats and initiator port. - qla2xxx: Add SLER and PI control support. - qla2xxx: Do not log message when reading port speed via sysfs - qla2xxx: fix null pointer access. - qla2xxx: Use MPI hang trigger to do PEGTUNE halt. - qla2xxx: Reduce erroneous error in link reset path - qla2xxx: v2: fix stalled N2N reconnect. - qla2xxx: Fix warnings on SLES12SP5. - qla2xxx: Fix compilation issues on SLES15 - qla2xxx: Compilation Fixes for SLES15SP1. - qla2xxx: Debugfs compilation issue fix for RH7.6. - qla2xxx: Fix gcc test compile error output being printed. - qla2xxx: Timestamp device online and offline transitions. - qla2xxx: Add rport fields in debugfs. - qla2xxx: Allow dev_loss_tmo setting for FC-NVMe devices. - qla2xxx: Setup debugfs entries for remote ports. - qla2xxx: Fix edif related compilation issue on RH7.6. - Fixes for compilation on hpe branch - qla2xxx: Compilation fixes for RH8.2 - qla2xxx: Compilation changes for RH7.6 - qla2xxx: Fixes for compilation on RH7.x I - qla2xxx: bsg_job to bsg_job_t - qla2xxx: I Unify source code to work with newer kernels. - qla2xxx: Makefile changes from code-uni-devel-10x. - qla2xxx: qla_edif file changes to compile the driver. - qla2xxx: Fix compilation issues. - qla2xxx: Fix Makefile issue. - qla2xxx: fix compile error - qla2xxx: Use explicit LOGO in target mode - qla2xxx: Add EDIF support. - qla2xxx: Addd edif related files. - qla2xxx: Fix MPI failure AEN (8200) handling. - qla2xxx: SCM - Backport optimizations and style changes from upstream work. - qla2xxx: Fix warning in qla_attr.c file. - qla2xxx: Fix nvme compilation error. - qla2xxx: Fix crash in alloc w/GFP_KERNEL + interrupt - Author : Quinn Tran <qutran@marvell.com> qla2xxx: v2: add iocb resource tracking. - qla2xxx: Fix WARN_ON in qla_nvme_register_hba. - qla2xxx: Allow ql2xextended_error_logging special value 1 to be set anytime. - qla2xxx: Make tgt_port_database available in initiator mode. - qla2xxx: reduce noisy debug message. - qla2xxx: Fix mailbox Ch erroneous error - qla2xxx: fix login timeout. - qla2xxx: Accomodate for SCM FW attribute bit change. - qla2xxx: post FC event (FPIN) to transport FPIN handler. - qla2xxx: Hide fc_host_fpin_rcv kernel dependency. - qla2xxx: Add changes to compile across various kernels. - qla2xxx: Use active targets to update SCM stats. - qla2xxx: Move SCM functions to qla_isr to keep changes local. - qla2xxx: Code to process FLOGI ACC extended payload. - qedf: Fix compilation issue - revisit. - qla2xxx: SCM Phase 1 Implementation + 2 other patches. - qla2xxx: Enable PUREX passthru post ISP reset. - qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV. - qla2xxx: performance tweak - scsi: qla2xxx: fix fcport null pointer access. - fixup! qla2xxx: Fix unbound NVME response length. - scsi: qla2xxx: Fix unbound NVME response length - qla2xxx: Add host attribute to trigger MPI hang. - qla2xxx: ONEOFF: silent dbg messages for good path io. - qla2xxx: ONEOFF: fix pDIF detection - qla2xxx: Snoop inquiry response atleast 168 bytes to determine proprietary DIF. - qla2xxx: ONEOFF: add debug counters for T10-PI/DIF - qla2xxx: ONEOFF: add MQ support for HP3PAR propritary T10-PI - qla2xxx: HPE 3PAR private T10-PI support. - qla2xxx: Check for fabric_priority flag during login - qla2xxx: use iocb_fabric_priority flag - qla2xxx: Fix QoS name and add debug logs - qla2xxx: Correction to tests for iocb fabric and fcport qos. - qla2xxx: Use ->isp_ops->read_optrom() in qla26xx_read_qos_fcport_table(). - qla2xxx: QoS fcport table index initialization improvement. - qla2xxx: Add QoS fcport table index to speed up search. - qla2xxx: Reduce stack on qos fcport priority routines. - qla2xxx: HPE: Register FDMI QOS - qla2xxx: Add bsg interface for qos lun level bitmask. - qla2xxx: Read E2E QoS fcport priority bitmasks from flash. - qla2xxx: Abstract qos lun level mask for iocb cs_ctl field. - qla2xxx: Add fabric priority qos lun iocb mechanism. - qla2xxx: Implement CT command GFO (Get Fabric Object). - qla2xxx: Add support for fabric priority per target. - qla2xxx: fix mtcp dump collection failure. - qla2xxx: Set Nport ID for N2N - qla2xxx: Fix crash during device discovery. - qla2xxx: Handle NVME status iocb correctly. - qla2xxx: Remove restriction of FC T10-PI and NVME - qla2xxx: serialize fc_port alloc in N2N - qla2xxx: NPIV does not come up after FW dump. - qla2xxx: fix RDP respond data format bug. - qla2xxx: force semaphore on flash validation failure. - qla2xxx: add more FW debug information - qla2xxx: Revert: Disable T10-DIF feature with FC-NVMe during probe - qla2xxx: Update BPM enablement semantics. - qla2xxx: fix FW resource print error. - qla2xxx: Use a dedicated interrupt handler for 'handshake-required' ISPs. - qla2xxx: Ensure flash updates return possible failure status through bsg interface. - qla2xxx: Improved secure flash support messages - qla2xxx: fix flag passing error - qla2xxx: Use FC generic update firmware options routine for ISP27xx. - qla2xxx: Avoid setting firmware options twice in 24xx_update_fw_options. - qla2xxX: Add 16.0GT for PCI String - qla2xxx: Use FW_STARTED macro - qla2xxx: Add fixes for mailbox command - qla2xxx: Fix login IOCB flag - qla2xxx: Save rscn_gen for new fcport - qla2xxx: firmware option 3 is clobbered by speed set - qla2xxx: ISP28xx active FW region - qla2xxx: Add portname to print logs in qla24xx_logio_entry(). - qla2xxx: Correction to MB in-direction selection in qla2x00_echo_test(). - qla2xxx: Correction to selection of loopback/echo test. - qla2xxx: Use endian macros to assign static fields in fwdump header. - qla2xxx: Add Speed in SFP print information - qla2xxx: Fix RDP response size - qla2xxx: Handle cases for limiting RDP response payload length. - qla2xxx: Add deferred queue for processing ABTS and RDP. - qla2xxx: Cleanup ELS/PUREX iocb fields. - qla2xxx: Add devid's and conditionals for 28xx. - qla2xxx: Add vendor extended FDMI additions and amendments. - qla2xxx: Provide separate RDP enable. - qla2xxx: Add vendor extended RDP additions and amendments. - qla2xxx: Add changes in preparation for vendor extended FDMI/RDP. - qla2xxx: Add 2061 PCI ID - qla2xxx: Remove all DIX-0 references - qla2xxx: Add endianizer macro calls to fc host stats. - qla2xxx: Add sysfs node for D-Port Diagnostics AEN data. - qla2xxx: Move free of fcport out of interrupt context. - qla2xxx: Add beacon LED config sysfs interface. - qla2xxx: Add sysfs hooks for FC-NVMe autoconnect - 10.01.00.22-k AE 06/29/2020 - Upstream driver as part of Linux 5.6 - Please see user documentation for details. (Severity: Low) - Please see user documentation for details. (Severity: Low) - Please see user documentation for details. (Severity: Low) - Add workaround for MRRS of 5762 (Severity:Medium) - Add support for RHEL 7.4 and SLES12SP2 (Severity:Medium) - Add support to notify min/max MTUs through min_mtu & max_mtu (Severity:Medium) - Add support to overide clock for 5762 (Severity:Medium) - Backport upstream patches (Severity:Medium) - Add PHY reset workaround in change MTU path for 5717/19/20 (Severity:Medium) - Update the copyright (Severity:Minor) - Add SLES 15 support (Severity:Medium) - Add RHEL 7.5 support (Severity:Medium) - Fix RHEL 6.4 compilation (Severity:Medium) - Add Ubuntu 18.04 support (Severity:Minor) - Fix race between tg3_get_stats64() and tg3_free_consistent() (Severity:Minor) - Avoid usleep_range() with holding spin lock (Severity:Minor) - Add private ioctl support for register read/write (Severity:Medium) - Add RHEL 8.0 support (Severity:Medium) - Fix Panic with SLES12SP3 (Severity:Minor) - Add workaround for MRRS of 5762 (Severity:Medium) - Add support for RHEL 7.4 and SLES12SP2 (Severity:Medium) - Add support to notify min/max MTUs through min_mtu & max_mtu (Severity:Medium) - Add support to overide clock for 5762 (Severity:Medium) - Backport upstream patches (Severity:Medium) - Add PHY reset workaround in change MTU path for 5717/19/20 (Severity:Medium) - Update the copyright (Severity:Minor) - Add SLES 15 support (Severity:Medium) - Add RHEL 7.5 support (Severity:Medium) - Fix RHEL 6.4 compilation (Severity:Medium) - Add Ubuntu 18.04 support (Severity:Minor) - Fix race between tg3_get_stats64() and tg3_free_consistent() (Severity:Minor) - Avoid usleep_range() with holding spin lock (Severity:Minor) - Add private ioctl support for register read/write (Severity:Medium) - Add RHEL 8.0 support (Severity:Medium) - Fix Panic with SLES12SP3 (Severity:Minor) - Add workaround for MRRS of 5762 (Severity:Medium) - Add support for RHEL 7.4 and SLES12SP2 (Severity:Medium) - Add support to notify min/max MTUs through min_mtu & max_mtu (Severity:Medium) - Add support to overide clock for 5762 (Severity:Medium) - Backport upstream patches (Severity:Medium) - Add PHY reset workaround in change MTU path for 5717/19/20 (Severity:Medium) - Update the copyright (Severity:Minor) - Add SLES 15 support (Severity:Medium) - Add RHEL 7.5 support (Severity:Medium) - Fix RHEL 6.4 compilation (Severity:Medium) - Add Ubuntu 18.04 support (Severity:Minor) - Fix race between tg3_get_stats64() and tg3_free_consistent() (Severity:Minor) - Avoid usleep_range() with holding spin lock (Severity:Minor) - Add private ioctl support for register read/write (Severity:Medium) - Add RHEL 8.0 support (Severity:Medium) - Fix Panic with SLES12SP3 (Severity:Minor)