Firmware Dependencies:

Problems Fixed:

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

Ver. 1.60(B) contains updates to the component packaging and is functionally equivalent to ver. 1.60. It is not necessary to upgrade with Revision B if a previous component Revision was used to upgrade the firmware to version 1.60.

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for Variant 2 of the Side Channel Analysis vulnerability, also known as Spectre. The revision of the microcode included in this System ROM does NOT have issues with more frequent reboots and unpredictable system behavior which impacted the previous Intel microcode which was part of the Spectre Variant 2 mitigation. Additional information is available from Intel’s Security Exploit Newsroom, https://newsroom.intel.com/press-kits/security-exploits-intel-products/.

Firmware Dependencies:

None

Problems Fixed:

Updated the Intel processor microcode to the latest version.

Known Issues:

None

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for Variant 2 of the Side Channel Analysis vulnerability, also known as Spectre. The revision of the microcode included in this System ROM does NOT have issues with more frequent reboots and unpredictable system behavior which impacted the previous Intel microcode which was part of the Spectre Variant 2 mitigation. Additional information is available from Intel’s Security Exploit Newsroom, https://newsroom.intel.com/press-kits/security-exploits-intel-products/.

Firmware Dependencies:

None

Problems Fixed:

Updated the Intel processor microcode to the latest version.

Known Issues:

None

• 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.

• 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 Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• An issue where injecting EEH (Extended Error Handlng) may cause extra Kernel prints, such as: “EEH: Might be infinite loop in mlx5_core driver” was fixed.
• RPM-based OSs with non-default kernels, using repositories after re-creating the installer (using --add-kernel-support) were resulting in improper installation of the drivers.
• A typo in perftest package where help messages wrongly displayed the conversion result between Gb/s and MB/s (20^2 instead of 2^20).
• When one of the LAG slaves went down, LAG deactivation failed, ultimately causing bandwidth degradation.
• The mlx5 driver maintains a subdirectory for every open eth port in /sys/kernel/debug/. For the default network namespace, the sub-directory name is the name of the interface, like "eth8". The new convention for the network interfaces moved to the non-default network namespaces is the interfaces name followed by "@" and the port's PCI ID. For example: "eth8@0000:af:00.3".
• "openibd" script load used to fail when esp6_offload module did not load successfully.
• Added dependency of package mpi-selectors on perl-Getopt-Long system package. On minimal installs of RPM-based OSs, installing mpi-selectros will also install the required system package perl-Getopt-Long.
• During certain rare scenarios, due to Rx page not being replenished, the same page fragment mistakenly became assigned to two different Rx descriptors.
• Driver load issue existed with Errata-kernel on SLES15 SP1.
• An issue in the Hairpin feature which prevented adding hairpin flows using TC tool was fixed.
• WQ (Work Queue) queue flushing was not handled properly in the event of EEH.
• A rare kernel crash scenario when exiting an application that uses RMPP mads intensively.
• A possible kernel crash scenario when AER/slot reset in done in parallel to user space commands execution.
• Added missing ECN (Explicit Congestion Notification) configuration under sysfs for PFs in SwitchDev mode.
• When firmware response time to commands became very long, some commands failed upon timeout. The driver may have then triggered a timeout completion on the wrong entry, leading to a NULL pointer call trace.
• Added driver support for kernels with the old XDP_REDIRECT infrastructure that uses the following NetDev operations: .ndo_xdp_flush and .ndo_xdp_xmit.
• Usage of --excludedocs Open MPI RPM option resulted in the removal of non-documentation related files.
• Disabled automated loading of some modules through udev triggers to preserve the startup process of previous MLNX_OFED versions.
• Reference count (refcount) for RDMA connection ID (cm_id) was not incremented in rdma_resolve_addr() function, resulting in a cm_id use-after-free access. A fix was applied to increment the cm_id refcount
• A race condition which caused kernel panic when moving two ports to SwitchDev mode at the same time.
• Allowed accessing sysfs hardware counters in SwitchDev mode
• Function smp_processor_id() is called in the RX page recycle flow to determine the core to run on. This is intended to run in NAPI context. However, due to a bug in backporting, the RX page recycle was mistakenly called also in the RQ close flow when not needed.
• Port link state was automatically changed (without admin state involvement) to "UP" after reboot.
• ConnectX-3 adapter cards froze when running over SLES 11 OS.
• RDMA CM (Remote Direct Memory Access Communation Manager) connection failed when port space was small.
• Traffic mirroring with OVS (Open VSwitch)offload and non-offload over VxLAN interface is now supported. Note: For kernel 4.9, make sure to use a dedicated OVS version.
• When working with VF LAG while the bond device is in active-active mode, running fwreset would result in unequal traffic on both PFs, and PFs would not reach line rate.
• When bond was created over VF (Virtuaal Function) netdevices in SwitchDev mode, the VF netdevice would be treated as representor netdevice. This caused the mlx5_core driver to crash in case it received netdevice events related to bond device.
• An issue where following a bad affinity occurrence in VF LAG mode, traffic was sent after the port went up/down in the switch.
• Added support for VLAN (Virtual Local Area Network) header rewrite on CentOS 7.2 OS.

• An issue where injecting EEH (Extended Error Handlng) may cause extra Kernel prints, such as: “EEH: Might be infinite loop in mlx5_core driver” was fixed.
• RPM-based OSs with non-default kernels, using repositories after re-creating the installer (using --add-kernel-support) were resulting in improper installation of the drivers.
• A typo in perftest package where help messages wrongly displayed the conversion result between Gb/s and MB/s (20^2 instead of 2^20).
• When one of the LAG slaves went down, LAG deactivation failed, ultimately causing bandwidth degradation.
• The mlx5 driver maintains a subdirectory for every open eth port in /sys/kernel/debug/. For the default network namespace, the sub-directory name is the name of the interface, like "eth8". The new convention for the network interfaces moved to the non-default network namespaces is the interfaces name followed by "@" and the port's PCI ID. For example: "eth8@0000:af:00.3".
• "openibd" script load used to fail when esp6_offload module did not load successfully.
• Added dependency of package mpi-selectors on perl-Getopt-Long system package. On minimal installs of RPM-based OSs, installing mpi-selectros will also install the required system package perl-Getopt-Long.
• During certain rare scenarios, due to Rx page not being replenished, the same page fragment mistakenly became assigned to two different Rx descriptors.
• Driver load issue existed with Errata-kernel on SLES15 SP1.
• An issue in the Hairpin feature which prevented adding hairpin flows using TC tool was fixed.
• WQ (Work Queue) queue flushing was not handled properly in the event of EEH.
• A rare kernel crash scenario when exiting an application that uses RMPP mads intensively.
• A possible kernel crash scenario when AER/slot reset in done in parallel to user space commands execution.
• Added missing ECN (Explicit Congestion Notification) configuration under sysfs for PFs in SwitchDev mode.
• When firmware response time to commands became very long, some commands failed upon timeout. The driver may have then triggered a timeout completion on the wrong entry, leading to a NULL pointer call trace.
• Added driver support for kernels with the old XDP_REDIRECT infrastructure that uses the following NetDev operations: .ndo_xdp_flush and .ndo_xdp_xmit.
• Usage of --excludedocs Open MPI RPM option resulted in the removal of non-documentation related files.
• Disabled automated loading of some modules through udev triggers to preserve the startup process of previous MLNX_OFED versions.
• Reference count (refcount) for RDMA connection ID (cm_id) was not incremented in rdma_resolve_addr() function, resulting in a cm_id use-after-free access. A fix was applied to increment the cm_id refcount
• A race condition which caused kernel panic when moving two ports to SwitchDev mode at the same time.
• Allowed accessing sysfs hardware counters in SwitchDev mode
• Function smp_processor_id() is called in the RX page recycle flow to determine the core to run on. This is intended to run in NAPI context. However, due to a bug in backporting, the RX page recycle was mistakenly called also in the RQ close flow when not needed.
• Port link state was automatically changed (without admin state involvement) to "UP" after reboot.
• ConnectX-3 adapter cards froze when running over SLES 11 OS.
• RDMA CM (Remote Direct Memory Access Communation Manager) connection failed when port space was small.
• Traffic mirroring with OVS (Open VSwitch)offload and non-offload over VxLAN interface is now supported. Note: For kernel 4.9, make sure to use a dedicated OVS version.
• When working with VF LAG while the bond device is in active-active mode, running fwreset would result in unequal traffic on both PFs, and PFs would not reach line rate.
• When bond was created over VF (Virtuaal Function) netdevices in SwitchDev mode, the VF netdevice would be treated as representor netdevice. This caused the mlx5_core driver to crash in case it received netdevice events related to bond device.
• An issue where following a bad affinity occurrence in VF LAG mode, traffic was sent after the port went up/down in the switch.
• Added support for VLAN (Virtual Local Area Network) header rewrite on CentOS 7.2 OS.

• 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
• "iperf3" and "iperf3 -l 512"  issue fixed from having traffic for virtio hardware offload solution .

• 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.

• 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.

• 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 for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.

• 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 for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.

Firmware Dependencies:

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 50567). 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 50567). 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:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the chassis name was not being reported for inventory control.

Known Issues:

• An issue where the system hangs when resuming from hibernation. 

• An issue where the enclosure identifier field corresponding to the physical devices became empty in lsscsi/sysfs during device rescan. 

• An issue to display topology using PHY numbers 

• An issue where the driver did not export valid SAS initiator_port_protocols and target_port_protocols to sysfs. 

• An issue where the driver would cause a kernel panic if it got an invalid response from the controller. 

• An issue where the LUN reset, system shutdown, system suspend, system hibernate, controller offline, and I/O requests could reach the controller when they are not required. 

• An issue where after modifying the logical volume size, lsblk command still shows up previous size of logical volume. 

• An issue where during the device discovery, the driver issued an INQUIRY to physical devices, and these requests could get lost due to broken devices, loss of signal issues, etc. This would cause device discovery to get hung. 

• One port of an Fibre Channel adapter could not complete to reconnect to storage after storage upgrade if the host system had been online for over 3 months
• Turning on 3PAR Persistent Checksum after the host operating system was running would not result in Persistent Checksum being enabled between the adapter and 3PAR array.
• Virtual Machines (VMs) could not access certain storage arrays when those arrays were attached to the VM using N-Port ID Virtualization (NPIV)

• An issue where the system hangs when resuming from hibernation. 

• An issue where the enclosure identifier field corresponding to the physical devices became empty in lsscsi/sysfs during device rescan. 

• An issue to display topology using PHY numbers 

• An issue where the driver did not export valid SAS initiator_port_protocols and target_port_protocols to sysfs. 

• An issue where the driver would cause a kernel panic if it got an invalid response from the controller. 

• An issue where the LUN reset, system shutdown, system suspend, system hibernate, controller offline, and I/O requests could reach the controller when they are not required. 

• An issue where after modifying the logical volume size, lsblk command still shows up previous size of logical volume. 

• An issue where during the device discovery, the driver issued an INQUIRY to physical devices, and these requests could get lost due to broken devices, loss of signal issues, etc. This would cause device discovery to get hung. 

1. Multipath message appears with storage port reset, node reboot and panic
2. Port login does not complete with storage port reset activity
3. Multipath command does not respond
4. Fix SCSI error-handling when I/O completes after an abort completion which may cause system to terminate unexpectedly
5. Please refer advisory at https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

This product addresses an issue where boot mode is not restored to the default value after a factory reset.

This product addresses an issue where the F1 help messages "Number of VFs per PF" and "Legacy Boot Protocol" option display incorrectly in Japanese and Simplified Chinese languages.

• Addressed issue where the HPE Synergy 3820C 10/20Gb Converged Network Adapter was showing not supported
• Corrected invalid utf8mb4 char in database

•  the hp-snmp-agents service version 10.9.0 on an HPE ProLiant Gen9 Server or an HPE Synergy Gen9 Compute Node may experience a segfault after installation or restart of the hp-snmp-agents service. cmahostd or cmapeerd process will be killed after the segfault.  Pleaer review customer advisory a00098957en_us for additional details.
• The OS version reported by hp-snmp-agents reported a mismatch with the newer Linux OS distros. i.e., "SUSE Linux Enterprise Server 12" v.s "SUSE Linux Enterprise Server 12 SP5" 

Ver. 1.0.9(J) contains updates to the component packaging and is functionally equivalent to ver. 1.0.9. It is not necessary to upgrade with Revision J if a previous component Revision was used to upgrade the firmware to version 1.0.9.

Firmware Dependencies:

None

Problems Fixed:

Addresses an issue in which the minimum power capping value was incorrectly being calculated on certain systems. This fix increases the accuracy of the minimum capping value set during POST.

Known Issues:

None

Ver. 1.0.9(J) contains updates to the component packaging and is functionally equivalent to ver. 1.0.9. It is not necessary to upgrade with Revision J if a previous component Revision was used to upgrade the firmware to version 1.0.9.

Firmware Dependencies:

None

Problems Fixed:

Addresses an issue in which the minimum power capping value was incorrectly being calculated on certain systems. This fix increases the accuracy of the minimum capping value set during POST.

Known Issues:

None

• TBD
• TBD

• Modified the loop initial values in hpasmcli from 2 to 0.
• Modifications to check the read and write variables to match RBSU in Legacy and UEFI mode
• Updated the hpasmcli check string to correctly report the impitool information.
• Remove the redundant serial embedded and com ports
• Addressed IML message size limitation from 36 to 212 bytes
• Support for hp-health in OS security boot
• Added supporting “quote mark” in SET NAME command
• Enabled to set PXE as boot first 

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 Intel microcode. The Intel microcode patches included in this release are versions 0x00000044 (CPUID 306F2) and 0x00B00003A (CPUID 406F1).

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

• Addressed a small amount of memory leak as outlined in the Customer Advisory, a00053824en_us
• A customer may experience where smad may periodically report: No response from iLO for Hello.  After losing connection with iLO, the subagent may experience high CPU utilization for trying the reconnection. This issue is documented in Customer Advisory https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00111063en_us. 
• The cpqIde service not able to start while the AMSD configuration is agent mode.
• Addressed buffer overflow issues in select corner cases.
• Metadata update to address new AMD servers not listed in the supported platforms list. 

• Addressed a small amount of memory leak as outlined in the Customer Advisory, a00053824en_us
• A customer may experience where smad may periodically report: No response from iLO for Hello.  After losing connection with iLO, the subagent may experience high CPU utilization for trying the reconnection. This issue is documented in Customer Advisory https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00111063en_us. 
• The cpqIde service not able to start while the AMSD configuration is agent mode.
• Addressed buffer overflow issues in select corner cases.

• 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.

• 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 Dependencies:

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 50567). 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 50567). 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:

• Fixed a behavior with internal engineering data displays

VMware: MPK73H5Q Firmware For VMware Operating Systems, https://www.hpe.com/global/swpublishing/MTX-bc5a85e2da894acc87edff7b07

Windows: MPK73H5Q Firmware for Windows Operating Systems, https://www.hpe.com/global/swpublishing/MTX-eb2b1b0ee298477fb52d02948f

Linux: MPK73H5Q Firmware for Linux Operating Systems, https://www.hpe.com/global/swpublishing/MTX-c2d518c8671942018d4084aa37

Version MPK73H5Q will be available soon in Service Pack for ProLiant. For more information, refer to HPE Customer Bulletin at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00112800en_us. This Smart Component provides firmware for the following drive models: MZXL5800HBHQ-000, MZXL51T6HBJR-000, MZXL53T2HBLS-000, MZXL56T4HALA-000, MZXL512THALA-000, MZXL5960HBHQ-000, MZXL51T9HBJR-000, MZXL53T8HBLS-000, MZXL57T6HALA-000 and MZXL515THALA-000

Working version MPK73H5Q resolves the following 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 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.

This product addresses an iSCSI discovery failure with VLAN.

This product addresses an issue where an iSCSI portal is discovered with invalid an VLAN ID.

Firmware Dependencies:

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 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 50567). 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:

• An issue where the system hangs when resuming from hibernation. 

• An issue where the enclosure identifier field corresponding to the physical devices became empty in lsscsi/sysfs during device rescan. 

• An issue to display topology using PHY numbers 

• An issue where the driver did not export valid SAS initiator_port_protocols and target_port_protocols to sysfs. 

• An issue where the driver would cause a kernel panic if it got an invalid response from the controller. 

• An issue where the LUN reset, system shutdown, system suspend, system hibernate, controller offline, and I/O requests could reach the controller when they are not required. 

• An issue where after modifying the logical volume size, lsblk command still shows up previous size of logical volume. 

• An issue where during the device discovery, the driver issued an INQUIRY to physical devices, and these requests could get lost due to broken devices, loss of signal issues, etc. This would cause device discovery to get hung. 

• Addressed a small amount of memory leak as documented in the Customer Advisory, a00053824en_us
•  NVMe drive information is now available in the CPQSE.

• Added the warning message for users to restart hp-ams service when iLo reset more than twice. This issue is documented in Customer Advisory a00099805en_us.  
• When the server detects the physical network cable is plugged or unplugged, hp-ams will send out a trap to notify the administrator about the physical network status change.

• 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.

• 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.

• Enhancements have been made to the firmware to prevent and better recover from the unexpected behavior described in Customer Advisory 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=a00094722en_us

• Address unexpected behavior when Fibre Channel adapters were simultaneously running traffic to an array which supports 3PAR Persistent Checksum AND another array which is running T10-PI (also known as T10-DIF) or no block checksum technology at all
• Fibre Channel adapter firmware versions were not showing up as expected in the AHS log.
• Port statistics counters would sometimes not update in the event of Loss of Signal or Loss of Sync
• link downs would occur during specific frame sequences used by the HPE XP8 array after array-side link loss

HPE Ethernet 10Gb 2-port BaseT QL41132HLRJ Adapter
HPE Ethernet 10Gb 2-port BaseT QL41132HQRJ OCP3 Adapter

• 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.

• 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.

-Removed action over FAULT_SENSED bit due to incorrect algorithm.

-Removed action over FAULT_SENSED bit due to incorrect algorithm.

• The "esxcli network sriovnic vf stats" command was not supported.When running this command on a "vmknic", a failure message was displayed.

• IPv6 as inner packet was not supported.

• The "esxcli network sriovnic vf stats" command was not supported.When running this command on a "vmknic", a failure message was displayed.

• IPv6 as inner packet was not supported.

1. 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.
2. An issue that prevented VXLAN packets with svlan/cvlan tag from being matched.
3. The eth_wqe_too_small counter to count ODP (On-Demand Paging) page used to fail.
4. An issue related to raising 100GbE link on ConnectX-6 VPI 100Gb/s adapter cards.
5. 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.
6. Low performance occurred after enabling the RoCE Accelerator capability.
7. On rare cases, a fatal error related to errors from the PCI transport layer might be reported during FLR.

Firmware Dependencies:

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 50567). 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 50567). 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:

• Traffic for virtio hardware offload solution was prevented from "iperf3" in Windows Operating System.
• Traffic for virtio hardware offload solution was prevented from "iperf3 -i 512".
• The struct virtio_net_hdr was not set properly by the virtio hardware offload solution. The following message appeared in dmesg during traffic: "bad gso: type xx, size: xx".
• When MKEY_BY_NAME was enabled by NVCONFIG and a large number of VFs were configured, VM restart (VF/PF FLR) might had taken longer than that of when MKEY_BY_NAME was disabled.
• TCP/IP traffic received by the guest kernel with version higher than 4.10 were unstable because of corrupted GSO header. The following message could be seen from dmegs: "bad gso: type: xx, size: xxxx".
• Enabling the RoCE Accelerator capability resulted in low performance
  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.

• Encapsulated RoCE traffic to drop when IB padding was required.
• PortXmitWait HW counter to count when not expected due to an inaccuracy in the counter.
• On dual-port device after Rx buffer modification the Physical Function on the second port got restored although no expected.  The Rx buffer changes when all Physical Functions resets over one port (through reboot /driver restart / FLR) while there were active Physical Functions over the second port.
• Previous Shared Buffer modifications being overrun after performing Shared Buffer modifications such as SBPR, SBPM, SBCM, the PFCC Flow Control).

Firmware Dependencies:

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 50567). 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 50567). 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:

• An issue where injecting EEH (Extended Error Handlng) may cause extra Kernel prints, such as: “EEH: Might be infinite loop in mlx5_core driver” was fixed.
• RPM-based OSs with non-default kernels, using repositories after re-creating the installer (using --add-kernel-support) were resulting in improper installation of the drivers.
• A typo in perftest package where help messages wrongly displayed the conversion result between Gb/s and MB/s (20^2 instead of 2^20).
• When one of the LAG slaves went down, LAG deactivation failed, ultimately causing bandwidth degradation.
• The mlx5 driver maintains a subdirectory for every open eth port in /sys/kernel/debug/. For the default network namespace, the sub-directory name is the name of the interface, like "eth8". The new convention for the network interfaces moved to the non-default network namespaces is the interfaces name followed by "@" and the port's PCI ID. For example: "eth8@0000:af:00.3".
• "openibd" script load used to fail when esp6_offload module did not load successfully.
• Added dependency of package mpi-selectors on perl-Getopt-Long system package. On minimal installs of RPM-based OSs, installing mpi-selectros will also install the required system package perl-Getopt-Long.
• During certain rare scenarios, due to Rx page not being replenished, the same page fragment mistakenly became assigned to two different Rx descriptors.
• Driver load issue existed with Errata-kernel on SLES15 SP1.
• An issue in the Hairpin feature which prevented adding hairpin flows using TC tool was fixed.
• WQ (Work Queue) queue flushing was not handled properly in the event of EEH.
• A rare kernel crash scenario when exiting an application that uses RMPP mads intensively.
• A possible kernel crash scenario when AER/slot reset in done in parallel to user space commands execution.
• Added missing ECN (Explicit Congestion Notification) configuration under sysfs for PFs in SwitchDev mode.
• When firmware response time to commands became very long, some commands failed upon timeout. The driver may have then triggered a timeout completion on the wrong entry, leading to a NULL pointer call trace.
• Added driver support for kernels with the old XDP_REDIRECT infrastructure that uses the following NetDev operations: .ndo_xdp_flush and .ndo_xdp_xmit.
• Usage of --excludedocs Open MPI RPM option resulted in the removal of non-documentation related files.
• Disabled automated loading of some modules through udev triggers to preserve the startup process of previous MLNX_OFED versions.
• Reference count (refcount) for RDMA connection ID (cm_id) was not incremented in rdma_resolve_addr() function, resulting in a cm_id use-after-free access. A fix was applied to increment the cm_id refcount
• A race condition which caused kernel panic when moving two ports to SwitchDev mode at the same time.
• Allowed accessing sysfs hardware counters in SwitchDev mode
• Function smp_processor_id() is called in the RX page recycle flow to determine the core to run on. This is intended to run in NAPI context. However, due to a bug in backporting, the RX page recycle was mistakenly called also in the RQ close flow when not needed.
• Port link state was automatically changed (without admin state involvement) to "UP" after reboot.
• ConnectX-3 adapter cards froze when running over SLES 11 OS.
• RDMA CM (Remote Direct Memory Access Communation Manager) connection failed when port space was small.
• Traffic mirroring with OVS (Open VSwitch)offload and non-offload over VxLAN interface is now supported. Note: For kernel 4.9, make sure to use a dedicated OVS version.
• When working with VF LAG while the bond device is in active-active mode, running fwreset would result in unequal traffic on both PFs, and PFs would not reach line rate.
• When bond was created over VF (Virtuaal Function) netdevices in SwitchDev mode, the VF netdevice would be treated as representor netdevice. This caused the mlx5_core driver to crash in case it received netdevice events related to bond device.
• An issue where following a bad affinity occurrence in VF LAG mode, traffic was sent after the port went up/down in the switch.
• Added support for VLAN (Virtual Local Area Network) header rewrite on CentOS 7.2 OS.

• An issue where injecting EEH (Extended Error Handlng) may cause extra Kernel prints, such as: “EEH: Might be infinite loop in mlx5_core driver” was fixed.
• RPM-based OSs with non-default kernels, using repositories after re-creating the installer (using --add-kernel-support) were resulting in improper installation of the drivers.
• A typo in perftest package where help messages wrongly displayed the conversion result between Gb/s and MB/s (20^2 instead of 2^20).
• When one of the LAG slaves went down, LAG deactivation failed, ultimately causing bandwidth degradation.
• The mlx5 driver maintains a subdirectory for every open eth port in /sys/kernel/debug/. For the default network namespace, the sub-directory name is the name of the interface, like "eth8". The new convention for the network interfaces moved to the non-default network namespaces is the interfaces name followed by "@" and the port's PCI ID. For example: "eth8@0000:af:00.3".
• "openibd" script load used to fail when esp6_offload module did not load successfully.
• Added dependency of package mpi-selectors on perl-Getopt-Long system package. On minimal installs of RPM-based OSs, installing mpi-selectros will also install the required system package perl-Getopt-Long.
• During certain rare scenarios, due to Rx page not being replenished, the same page fragment mistakenly became assigned to two different Rx descriptors.
• Driver load issue existed with Errata-kernel on SLES15 SP1.
• An issue in the Hairpin feature which prevented adding hairpin flows using TC tool was fixed.
• WQ (Work Queue) queue flushing was not handled properly in the event of EEH.
• A rare kernel crash scenario when exiting an application that uses RMPP mads intensively.
• A possible kernel crash scenario when AER/slot reset in done in parallel to user space commands execution.
• Added missing ECN (Explicit Congestion Notification) configuration under sysfs for PFs in SwitchDev mode.
• When firmware response time to commands became very long, some commands failed upon timeout. The driver may have then triggered a timeout completion on the wrong entry, leading to a NULL pointer call trace.
• Added driver support for kernels with the old XDP_REDIRECT infrastructure that uses the following NetDev operations: .ndo_xdp_flush and .ndo_xdp_xmit.
• Usage of --excludedocs Open MPI RPM option resulted in the removal of non-documentation related files.
• Disabled automated loading of some modules through udev triggers to preserve the startup process of previous MLNX_OFED versions.
• Reference count (refcount) for RDMA connection ID (cm_id) was not incremented in rdma_resolve_addr() function, resulting in a cm_id use-after-free access. A fix was applied to increment the cm_id refcount
• A race condition which caused kernel panic when moving two ports to SwitchDev mode at the same time.
• Allowed accessing sysfs hardware counters in SwitchDev mode
• Function smp_processor_id() is called in the RX page recycle flow to determine the core to run on. This is intended to run in NAPI context. However, due to a bug in backporting, the RX page recycle was mistakenly called also in the RQ close flow when not needed.
• Port link state was automatically changed (without admin state involvement) to "UP" after reboot.
• ConnectX-3 adapter cards froze when running over SLES 11 OS.
• RDMA CM (Remote Direct Memory Access Communation Manager) connection failed when port space was small.
• Traffic mirroring with OVS (Open VSwitch)offload and non-offload over VxLAN interface is now supported. Note: For kernel 4.9, make sure to use a dedicated OVS version.
• When working with VF LAG while the bond device is in active-active mode, running fwreset would result in unequal traffic on both PFs, and PFs would not reach line rate.
• When bond was created over VF (Virtuaal Function) netdevices in SwitchDev mode, the VF netdevice would be treated as representor netdevice. This caused the mlx5_core driver to crash in case it received netdevice events related to bond device.
• An issue where following a bad affinity occurrence in VF LAG mode, traffic was sent after the port went up/down in the switch.
• Added support for VLAN (Virtual Local Area Network) header rewrite on CentOS 7.2 OS.

Firmware Dependencies:

Problems Fixed:

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

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 50567). 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 50567). 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:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the chassis name was not being reported for inventory control.

Known Issues:

• Clearing min_rate on all SR-IOV legacy VFs after setting min_rate to at least one of the VFs did not disable QoS min_rate.
• An empty /usr/src/mlnx-ofa_kernel/default is now no longer created.
• An issue where installing packages through a repository failed after generation of metapackages using --add-kernel-support. The failure occurred due to excessive and incorrect Obsolete headers in those metapackages.Enabled installation of mlnx-ofa_kernel package to /bin/python3 instead of / usr/bin/python3 on RHEL 8.x systems.
• All IPoIB offload packets were wrongly counted as rx_csum_complete. These packets are now identified as rx_csum_unnecessary packets.
• mlx5dv_dr_rule_destroy segmentation fault could happen in rare cases with multiple rules on the same matcher with a different number of actions. This could happen after reusing an already deleted rule memory with less actions.
• An issue of moving to SwitchDev mode after configuring DSCP (Differentiated Service Code Point).
• Global traffic class configuration did not take effect on DC QPs (Dynamically Connected Queue Pairs).
• ib_send_bw traffic frequently dropped to zero when RDMA CM was used, because of incorrect min_rnr_timer setting on the responder side. The min_rnr_timer setting is now aligned with the setting in non-RDMA CM cases.
• Traffic did not pass over VFs with VST QinQ feature is enabled.
• When traffic was sent over Geneve VLAN with Tx VLAN offload enabled and TSO (TCP Segmentation Offload) or Tx csum enabled, traffic could be dropped and not sent to the wire.
• An issue that caused the firmware to restart upon installing mlnxofed-dpdk-upstream-libs package manually.
• Bad utility paths in rdma-core "dracut" hooks on SLES systems, which used to result in the following errors when running "dracut" with the "--add rdma" option. dracut-install:
  • ERROR: installing ‘/usr/libexec/mlx4-setup.sh’ dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.UdCOSJ/ initramfs /usr/libexec/mlx4-setup.sh dracut-install: ERROR: installing ‘/usr/libexec/rdma-set-sriov-vf’ dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.UdCOSJ/ initramfs /usr/libexec/rdma-set-sriov-vf
• Traffic class value was not updated in DCT when set via sysfs.
• A doorbell loss issue on AMD platforms with Secure Memory Encryption (SME).
• Registering memory using mlx5dv_devx_umem_reg while forking. Without this fix, applications which use fork() or similar syscalls while using a memory registered with umem_reg could hang due to incorrect physical page mapping. This fix requires setting the IBV_FORK_SAFE environment variable.
• When unbinding the device resulted in the following message being printed to the dmesg: "failed to disable DC tracer"
• Content of file /sys/class/net//statistics/ multicast might have been out of date and might have displayed values lower than the real values.
• ERSPAN (Encapsulated Remote SPAN) protocol was available only when turning off Tx checksum offload.
• A udev script issue which caused non-mellanox devices to be renamed.
• Missing representor statistics when using ifconfig.
• Fixed wrong value of skb mark of received packets on representors.
• An issue which caused second port representors to be named as first port representors.

• Extended mlx5 recovery-flow delay on VF driver when PCI interface went down
• ibv_get_device_list returned only accessible devices.
• “rpmbuild” (that includes basic support for building RPM packages) was not installed by the install script on SLES15 SPx systems when trying to rebuild packages.
• AF_XDP was not functional.
• neohost-backend and neohost-sdk packages were not properly removed by the uninstallation procedure and might have required manual removal before re-installing or upgrading MLNX_OFED driver.
• During MLNX_OFED installation, warning messages related to modules iw_cxgb3 and iw_nes might have appeared in the log.
• Command timeouts occurred when the Hypervisor disabled the VF's PCI interface. This fix reduces the device removal time to 2 seconds.
• MLNX_OFED/MLNX_EN installer will no longer automatically remove the spdk package when installing the driver.

Firmware Dependencies:

Problems Fixed:

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

This revision of the System ROM includes the latest revision of Intel microcode.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of Intel microcode: 0x000000E2 (CPUID 506E3). This Intel microcode patch provide mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8696 and CVE-2020-8698. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00381. These issues are not unique to HPE servers.

Known Issues:

None

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 Intel microcode. The Intel microcode patches included in this release are versions 0x000000DC (CPUID 506E3) and 0x0000000DE (CPUID 906E9).

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-0381 and INTEL-SA-00389. The Intel microcode patches included in this release are versions 0x000000DC (CPUID 506E3) and 0x0000000DE (CPUID 906E9). 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.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

None

This product addresses an iSCSI discovery failure with VLAN.

This product addresses an issue where an iSCSI portal is discovered with invalid an VLAN ID.

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 Intel microcode. The Intel microcode patches included in this release are versions 0x00000044 (CPUID 306F2) and 0x00B00003A (CPUID 406F1).

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

None

• TBD
• TBD

• Modified the loop initial values in hpasmcli from 2 to 0.
• Modifications to check the read and write variables to match RBSU in Legacy and UEFI mode
• Updated the hpasmcli check string to correctly report the impitool information.
• Remove the redundant serial embedded and com ports
• Addressed IML message size limitation from 36 to 212 bytes
• Support for hp-health in OS security boot
• Added supporting “quote mark” in SET NAME command
• Enabled to set PXE as boot first 

• Addressed a small amount of memory leak as documented in the Customer Advisory, a00053824en_us
•  NVMe drive information is now available in the CPQSE.

• Added the warning message for users to restart hp-ams service when iLo reset more than twice. This issue is documented in Customer Advisory a00099805en_us.  
• When the server detects the physical network cable is plugged or unplugged, hp-ams will send out a trap to notify the administrator about the physical network status change.

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 Intel microcode. The Intel microcode patches included in this release are versions 0x00000044 (CPUID 306F2) and 0x00B00003A (CPUID 406F1).

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

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:

Firmware Dependencies:

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:

This product addresses an issue where the ixgben driver has high CPU overhead when an SFP+ module is absent.

• Clearing min_rate on all SR-IOV legacy VFs after setting min_rate to at least one of the VFs did not disable QoS min_rate.
• An empty /usr/src/mlnx-ofa_kernel/default is now no longer created.
• An issue where installing packages through a repository failed after generation of metapackages using --add-kernel-support. The failure occurred due to excessive and incorrect Obsolete headers in those metapackages.Enabled installation of mlnx-ofa_kernel package to /bin/python3 instead of / usr/bin/python3 on RHEL 8.x systems.
• All IPoIB offload packets were wrongly counted as rx_csum_complete. These packets are now identified as rx_csum_unnecessary packets.
• mlx5dv_dr_rule_destroy segmentation fault could happen in rare cases with multiple rules on the same matcher with a different number of actions. This could happen after reusing an already deleted rule memory with less actions.
• An issue of moving to SwitchDev mode after configuring DSCP (Differentiated Service Code Point).
• Global traffic class configuration did not take effect on DC QPs (Dynamically Connected Queue Pairs).
• ib_send_bw traffic frequently dropped to zero when RDMA CM was used, because of incorrect min_rnr_timer setting on the responder side. The min_rnr_timer setting is now aligned with the setting in non-RDMA CM cases.
• Traffic did not pass over VFs with VST QinQ feature is enabled.
• When traffic was sent over Geneve VLAN with Tx VLAN offload enabled and TSO (TCP Segmentation Offload) or Tx csum enabled, traffic could be dropped and not sent to the wire.
• An issue that caused the firmware to restart upon installing mlnxofed-dpdk-upstream-libs package manually.
• Bad utility paths in rdma-core "dracut" hooks on SLES systems, which used to result in the following errors when running "dracut" with the "--add rdma" option. dracut-install:
  • ERROR: installing ‘/usr/libexec/mlx4-setup.sh’ dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.UdCOSJ/ initramfs /usr/libexec/mlx4-setup.sh dracut-install: ERROR: installing ‘/usr/libexec/rdma-set-sriov-vf’ dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.UdCOSJ/ initramfs /usr/libexec/rdma-set-sriov-vf
• Traffic class value was not updated in DCT when set via sysfs.
• A doorbell loss issue on AMD platforms with Secure Memory Encryption (SME).
• Registering memory using mlx5dv_devx_umem_reg while forking. Without this fix, applications which use fork() or similar syscalls while using a memory registered with umem_reg could hang due to incorrect physical page mapping. This fix requires setting the IBV_FORK_SAFE environment variable.
• When unbinding the device resulted in the following message being printed to the dmesg: "failed to disable DC tracer"
• Content of file /sys/class/net//statistics/ multicast might have been out of date and might have displayed values lower than the real values.
• ERSPAN (Encapsulated Remote SPAN) protocol was available only when turning off Tx checksum offload.
• A udev script issue which caused non-mellanox devices to be renamed.
• Missing representor statistics when using ifconfig.
• Fixed wrong value of skb mark of received packets on representors.
• An issue which caused second port representors to be named as first port representors.

• Extended mlx5 recovery-flow delay on VF driver when PCI interface went down
• ibv_get_device_list returned only accessible devices.
• “rpmbuild” (that includes basic support for building RPM packages) was not installed by the install script on SLES15 SPx systems when trying to rebuild packages.
• AF_XDP was not functional.
• neohost-backend and neohost-sdk packages were not properly removed by the uninstallation procedure and might have required manual removal before re-installing or upgrading MLNX_OFED driver.
• During MLNX_OFED installation, warning messages related to modules iw_cxgb3 and iw_nes might have appeared in the log.
• Command timeouts occurred when the Hypervisor disabled the VF's PCI interface. This fix reduces the device removal time to 2 seconds.
• MLNX_OFED/MLNX_EN installer will no longer automatically remove the spdk package when installing the driver.

Please reference Customer Advisory a00101958en_us

Firmware Dependencies:

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

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

Firmware Dependencies:

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 50567). 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 50567). 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:

Firmware Dependencies:

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:

Firmware Dependencies:

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:

Fixed the following:

• Purple Screen of Death(PSOD) at random intervals on HPE FlexFabric 20Gb 2-port 650FLB Adapter
• Link down after 1000 times port down and up iterations on switch.
• Detaching is not completing because lpfc_do_work_event can't exit.
• Slab memory use after free causing memory leak.
• Small Computer Sytem Interface(SCSI) command is used after done call.
• Target reset does not report original status

• 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 Toa Firmware Issue" at the following link:

         https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00099050en_us

This revision of the System ROM includes the latest revision of Intel microcode.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of Intel microcode: 0x000000E2 (CPUID 506E3). This Intel microcode patch provide mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8696 and CVE-2020-8698. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00381. These issues are not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

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-0381 and INTEL-SA-00389. The Intel microcode patches included in this release are versions 0x000000DC (CPUID 506E3) and 0x0000000DE (CPUID 906E9). 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.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

• When using OneView, attempts to upgrade firmware from version 1.18 to 1.20 failed.

Note: If the target device was previously updated to firmware version 1.20, it is not necessary to apply firmware update 1.20(C).

VMware: EPK74H3Q Firmware For VMware Operating Systems, https://www.hpe.com/global/swpublishing/MTX-51e52e05d02c4fdc8de04369ac

Windows: EPK74H3Q Firmware for Windows Operating Systems, https://www.hpe.com/global/swpublishing/MTX-17f6773477584f40934ba719f2

Linux: EPK74H3Q Firmware for Linux Operating Systems, https://www.hpe.com/global/swpublishing/MTX-956b407dbe4a42fc97c065e86a

Version EPK74H3Q will be available soon in Service Pack for ProLiant. For more information, refer to HPE Customer Bulletin at the following URL: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00112800en_us. This x64 Smart Component provides firmware for the following drive models: MZPLJ1T6HBJR-000, MZPLJ3T2HBJR-000 and MZPLJ6T4HALA-000

Working version EPK74H3Q resolves the following issue:

• 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.

Firmware Dependencies:

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 50567). 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 50567). 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:

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

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode for Intel Pentium processors which provides mitigations for security vulnerabilities documented as CVE-2020-0543 as well as CVE-2020-0548 and CVE-2020-0549. These security vulnerabilities are documented in Intel Security Advisories INTEL-SA-00320 and INTEL-SA-00329. These issues are not unique to HPE servers. This update does not impact systems using Intel Xeon based processors.

Addressed an issue where the system would become unresponsive with a Red Screen or hang when booting to FreeBSD R12.1 from a USB device when in Legacy Boot Mode. This issue did not impact systems configured for UEFI Boot Mode or when booting from other types of media.

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

None

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 Intel microcode. The Intel microcode patches included in this release are versions 0x00000044 (CPUID 306F2) and 0x00B00003A (CPUID 406F1).

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

None

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

HPE Ethernet 10Gb 2-port BaseT QL41132HLRJ Adapter
HPE Ethernet 10Gb 2-port BaseT QL41132HQRJ OCP3 Adapter

Firmware Dependencies:

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 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 50567). 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:

These drivers have been recompiled with a build setting that allows SUM to identify them correctly for installation on systems they support.

• Memory dumps were not generated during a crash dump in a boot from SAN environment

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 Intel microcode. The Intel microcode patches included in this release are versions 0x00000044 (CPUID 306F2) and 0x00B00003A (CPUID 406F1).

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-0591 and CVE-2020-0592. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00358. 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 platform code advisories and security vulnerabilities documented as CVE-2020-8738, CVE-2020-8740, and CVE-2020-8764. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00390. These issues are not unique to HPE servers.

This version of the System ROM contains an updated UEFI Driver for the SmartArray B140i SATA RAID controller. This update addresses an issue where the system may periodically experience an operating system boot issue such as experiencing a Linux kernel panic on boot.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

None