• Applied fixes to net-snmp open source code for CVE-2018-18065, CVE-2018-18066, CVE-2015-5621

iLO Driver

• Fixed driver unload function to allow controller to function properly on reload and when Quickboot is enabled

• Applied fixes to net-snmp open source code for CVE-2018-18065, CVE-2018-18066, CVE-2015-5621

iLO Driver

• Fixed driver unload function to allow controller to function properly on reload and when Quickboot is enabled

• Temperature sensors logic inside gSEP model and SES database
• When an IOM is pulled the surviving IOM reports false critical temperatures

Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.

• Temperature sensors logic inside gSEP model and SES database
• When an IOM is pulled the surviving IOM reports false critical temperatures

Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.

• Removed the support for Blade Servers.

The following issues have been fixed in version 4.9-4.0.8.1:

• openibd did not load automatically after reboot on certain Linux Operating Systems.

• openibd did not load automatically after reboot on certain Linux Operating Systems.

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

• ConnectX-6 supported up to 100GbE speed link only.

• Live unload of the driver was not supported. Doing so may cause a PSOD if the max_vfs parameter was set.

• The maximum number of established active RDMA connections (QPs) was 5000.

• Setting ETS value to 0 caused WQE timeout.

• ConnectX-6 supported up to 100GbE speed link only.

• Live unload of the driver was not supported. Doing so may cause a PSOD if the max_vfs parameter was set.

• The maximum number of established active RDMA connections (QPs) was 5000.

• Setting ETS value to 0 caused WQE timeout.

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

• To support scalability, function representor channels were limited to 4.However in scenarios when SF (Scalable Function) was not used, certain use cases required representors to support a large number of channels.Hence, representor channel limit to 4 was applicable only when a PCI device, such as Scalable Function support, was enabled.
• Matching on ipv4_ihl (internet header length) was supported only for outer headers. 
• When using one counter for both pop/push VLAN actions, the counter value was incorrect. Hence, Spliting the counter for pop_vlan_action_counter and push_vlan_action_counter.
• Incorrect L3 decapsulation occured when the original inner frame was small and was padded to comply with minimum frame size of 64-bytes.
• dapl and libmlx4 were needed by libdat2 and libdpdk. In order to remove or update dapl and libmlx4, their dependencies had to be removed.
• In fork situation, if parent/children processes happen to have samevirtual address, then the doorbell mechanism did not work well and may led to errors in application behavior.
• An override of log_max_qp by other devices occured if the devices share the same mlx5_core module.
• A synchronization issue where closing and opening channels (which might happen on configuration changes such as changing number of channels) may caused null pointer dereference in function mlx5e_select_queue.
• Enabling tx-udp_tnl-csum-segmentation had no affect on the driver. 
• Old udevd versions could get stuck renaming network devices, leaving interfaces named eth* instead of enp*. 
• Flows with t commit action with ct state -trk were not be offloaded (i.e., table=0,ct_state=-trk,ip actions=ct(commit,table=1)).
• Connection tracking over VF LAG with tunnel encapsulation/decapsulation was not supported and caused traffic drop.
• OFED compilation failed when stack size was limited to 1024.
• Setting rate/burst values higher than 2,147,483,648 were rejected.
• Offloaded remote mirroring flows on tunnel device caused forwarded traffic to VF to not be decapsulated.
• Trying to set VPort match mode on VF (cat/sys/class/net/enp8s0f2/compat/devlink/vport_match_mode), leads to kernel crash.
• OVS flows were not being offloaded over socket-direct devices.
• When VXLAN was configured and illegal route was added, the system crashed with call trace.
• If any traffic was sent before the netdev went up for the first time, a division by zero caused by a modulo operation occured in ndo_select_queue, leading to a kernel panic.
• After restarting driver, the x86 host might be in grace period and might not recover on its own. As part of the fix, 5 FW_fatal recoveries are allowed within the 20-minute grace period. As a result, the grace period in the devlink health show command will appear as 0 for FW_fatal reporter.

• To support scalability, function representor channels were limited to 4.However in scenarios when SF (Scalable Function) was not used, certain use cases required representors to support a large number of channels.Hence, representor channel limit to 4 was applicable only when a PCI device, such as Scalable Function support, was enabled.
• Matching on ipv4_ihl (internet header length) was supported only for outer headers. 
• When using one counter for both pop/push VLAN actions, the counter value was incorrect. Hence, Spliting the counter for pop_vlan_action_counter and push_vlan_action_counter.
• Incorrect L3 decapsulation occured when the original inner frame was small and was padded to comply with minimum frame size of 64-bytes.
• dapl and libmlx4 were needed by libdat2 and libdpdk. In order to remove or update dapl and libmlx4, their dependencies had to be removed.
• In fork situation, if parent/children processes happen to have samevirtual address, then the doorbell mechanism did not work well and may led to errors in application behavior.
• An override of log_max_qp by other devices occured if the devices share the same mlx5_core module.
• A synchronization issue where closing and opening channels (which might happen on configuration changes such as changing number of channels) may caused null pointer dereference in function mlx5e_select_queue.
• Enabling tx-udp_tnl-csum-segmentation had no affect on the driver. 
• Old udevd versions could get stuck renaming network devices, leaving interfaces named eth* instead of enp*. 
• Flows with t commit action with ct state -trk were not be offloaded (i.e., table=0,ct_state=-trk,ip actions=ct(commit,table=1)).
• Connection tracking over VF LAG with tunnel encapsulation/decapsulation was not supported and caused traffic drop.
• OFED compilation failed when stack size was limited to 1024.
• Setting rate/burst values higher than 2,147,483,648 were rejected.
• Offloaded remote mirroring flows on tunnel device caused forwarded traffic to VF to not be decapsulated.
• Trying to set VPort match mode on VF (cat/sys/class/net/enp8s0f2/compat/devlink/vport_match_mode), leads to kernel crash.
• OVS flows were not being offloaded over socket-direct devices.
• When VXLAN was configured and illegal route was added, the system crashed with call trace.
• If any traffic was sent before the netdev went up for the first time, a division by zero caused by a modulo operation occured in ndo_select_queue, leading to a kernel panic.
• After restarting driver, the x86 host might be in grace period and might not recover on its own. As part of the fix, 5 FW_fatal recoveries are allowed within the 20-minute grace period. As a result, the grace period in the devlink health show command will appear as 0 for FW_fatal reporter.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

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-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

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

• To support scalability, function representor channels were limited to 4.However in scenarios when SF (Scalable Function) was not used, certain use cases required representors to support a large number of channels.Hence, representor channel limit to 4 was applicable only when a PCI device, such as Scalable Function support, was enabled.
• Matching on ipv4_ihl (internet header length) was supported only for outer headers. 
• When using one counter for both pop/push VLAN actions, the counter value was incorrect. Hence, Spliting the counter for pop_vlan_action_counter and push_vlan_action_counter.
• Incorrect L3 decapsulation occured when the original inner frame was small and was padded to comply with minimum frame size of 64-bytes.
• dapl and libmlx4 were needed by libdat2 and libdpdk. In order to remove or update dapl and libmlx4, their dependencies had to be removed.
• In fork situation, if parent/children processes happen to have samevirtual address, then the doorbell mechanism did not work well and may led to errors in application behavior.
• An override of log_max_qp by other devices occured if the devices share the same mlx5_core module.
• A synchronization issue where closing and opening channels (which might happen on configuration changes such as changing number of channels) may caused null pointer dereference in function mlx5e_select_queue.
• Enabling tx-udp_tnl-csum-segmentation had no affect on the driver. 
• Old udevd versions could get stuck renaming network devices, leaving interfaces named eth* instead of enp*. 
• Flows with t commit action with ct state -trk were not be offloaded (i.e., table=0,ct_state=-trk,ip actions=ct(commit,table=1)).
• Connection tracking over VF LAG with tunnel encapsulation/decapsulation was not supported and caused traffic drop.
• OFED compilation failed when stack size was limited to 1024.
• Setting rate/burst values higher than 2,147,483,648 were rejected.
• Offloaded remote mirroring flows on tunnel device caused forwarded traffic to VF to not be decapsulated.
• Trying to set VPort match mode on VF (cat/sys/class/net/enp8s0f2/compat/devlink/vport_match_mode), leads to kernel crash.
• OVS flows were not being offloaded over socket-direct devices.
• When VXLAN was configured and illegal route was added, the system crashed with call trace.
• If any traffic was sent before the netdev went up for the first time, a division by zero caused by a modulo operation occured in ndo_select_queue, leading to a kernel panic.
• After restarting driver, the x86 host might be in grace period and might not recover on its own. As part of the fix, 5 FW_fatal recoveries are allowed within the 20-minute grace period. As a result, the grace period in the devlink health show command will appear as 0 for FW_fatal reporter.

• To support scalability, function representor channels were limited to 4.However in scenarios when SF (Scalable Function) was not used, certain use cases required representors to support a large number of channels.Hence, representor channel limit to 4 was applicable only when a PCI device, such as Scalable Function support, was enabled.
• Matching on ipv4_ihl (internet header length) was supported only for outer headers. 
• When using one counter for both pop/push VLAN actions, the counter value was incorrect. Hence, Spliting the counter for pop_vlan_action_counter and push_vlan_action_counter.
• Incorrect L3 decapsulation occured when the original inner frame was small and was padded to comply with minimum frame size of 64-bytes.
• dapl and libmlx4 were needed by libdat2 and libdpdk. In order to remove or update dapl and libmlx4, their dependencies had to be removed.
• In fork situation, if parent/children processes happen to have samevirtual address, then the doorbell mechanism did not work well and may led to errors in application behavior.
• An override of log_max_qp by other devices occured if the devices share the same mlx5_core module.
• A synchronization issue where closing and opening channels (which might happen on configuration changes such as changing number of channels) may caused null pointer dereference in function mlx5e_select_queue.
• Enabling tx-udp_tnl-csum-segmentation had no affect on the driver. 
• Old udevd versions could get stuck renaming network devices, leaving interfaces named eth* instead of enp*. 
• Flows with t commit action with ct state -trk were not be offloaded (i.e., table=0,ct_state=-trk,ip actions=ct(commit,table=1)).
• Connection tracking over VF LAG with tunnel encapsulation/decapsulation was not supported and caused traffic drop.
• OFED compilation failed when stack size was limited to 1024.
• Setting rate/burst values higher than 2,147,483,648 were rejected.
• Offloaded remote mirroring flows on tunnel device caused forwarded traffic to VF to not be decapsulated.
• Trying to set VPort match mode on VF (cat/sys/class/net/enp8s0f2/compat/devlink/vport_match_mode), leads to kernel crash.
• OVS flows were not being offloaded over socket-direct devices.
• When VXLAN was configured and illegal route was added, the system crashed with call trace.
• If any traffic was sent before the netdev went up for the first time, a division by zero caused by a modulo operation occured in ndo_select_queue, leading to a kernel panic.
• After restarting driver, the x86 host might be in grace period and might not recover on its own. As part of the fix, 5 FW_fatal recoveries are allowed within the 20-minute grace period. As a result, the grace period in the devlink health show command will appear as 0 for FW_fatal reporter.

• Applied fixes to net-snmp open source code for CVE-2018-18065, CVE-2018-18066, CVE-2015-5621

iLO Driver

• Fixed driver unload function to allow controller to function properly on reload.

• Applied fixes to net-snmp open source code for CVE-2018-18065, CVE-2018-18066, CVE-2015-5621

iLO Driver

• Fixed driver unload function to allow controller to function properly on reload.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

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-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

• QXCR1001795387: [SV-HPE War]jquery-1.11.3 is vulnerable, upgrade jquery-3.6.0
   

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5056:

• Fixed an issue that resulted in reading from invalid I/O address on handover from UEFI boot to OS boot, when a port was configured as InfiniBand on a VPI adapter device.

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5056:

• Fixed an issue that resulted in reading from invalid I/O address on handover from UEFI boot to OS boot, when a port was configured as InfiniBand on a VPI adapter device.

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000019 (CPUID 306F4) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes microcode mitigations for security vulnerability CVE-2021-0127. These issues are not unique to HPE servers.

Known Issues:

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-24512. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x000000EA (CPUID 506E3 and CPUID 906E9). These issues are not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel sighting CVE-2020-24512. This security vulnerability is documented in Intel Security Advisory INTEL-SA-00463. The Intel microcode patches included in this release are version 0x000000EA (CPUID 506E3) and 0x000000EA (CPUID 906E9). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8670 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Please reference Customer Advisory a00095304en_us.

Please reference Customer Advisory SIK5264.

• To support scalability, function representor channels were limited to 4.However in scenarios when SF (Scalable Function) was not used, certain use cases required representors to support a large number of channels.Hence, representor channel limit to 4 was applicable only when a PCI device, such as Scalable Function support, was enabled.
• Matching on ipv4_ihl (internet header length) was supported only for outer headers. 
• When using one counter for both pop/push VLAN actions, the counter value was incorrect. Hence, Spliting the counter for pop_vlan_action_counter and push_vlan_action_counter.
• Incorrect L3 decapsulation occured when the original inner frame was small and was padded to comply with minimum frame size of 64-bytes.
• dapl and libmlx4 were needed by libdat2 and libdpdk. In order to remove or update dapl and libmlx4, their dependencies had to be removed.
• In fork situation, if parent/children processes happen to have samevirtual address, then the doorbell mechanism did not work well and may led to errors in application behavior.
• An override of log_max_qp by other devices occured if the devices share the same mlx5_core module.
• A synchronization issue where closing and opening channels (which might happen on configuration changes such as changing number of channels) may caused null pointer dereference in function mlx5e_select_queue.
• Enabling tx-udp_tnl-csum-segmentation had no affect on the driver. 
• Old udevd versions could get stuck renaming network devices, leaving interfaces named eth* instead of enp*. 
• Flows with t commit action with ct state -trk were not be offloaded (i.e., table=0,ct_state=-trk,ip actions=ct(commit,table=1)).
• Connection tracking over VF LAG with tunnel encapsulation/decapsulation was not supported and caused traffic drop.
• OFED compilation failed when stack size was limited to 1024.
• Setting rate/burst values higher than 2,147,483,648 were rejected.
• Offloaded remote mirroring flows on tunnel device caused forwarded traffic to VF to not be decapsulated.
• Trying to set VPort match mode on VF (cat/sys/class/net/enp8s0f2/compat/devlink/vport_match_mode), leads to kernel crash.
• OVS flows were not being offloaded over socket-direct devices.
• When VXLAN was configured and illegal route was added, the system crashed with call trace.
• If any traffic was sent before the netdev went up for the first time, a division by zero caused by a modulo operation occured in ndo_select_queue, leading to a kernel panic.
• After restarting driver, the x86 host might be in grace period and might not recover on its own. As part of the fix, 5 FW_fatal recoveries are allowed within the 20-minute grace period. As a result, the grace period in the devlink health show command will appear as 0 for FW_fatal reporter.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

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-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

• Drive status all shows failed on SL4540 Gen8 H220 [LSI] ILO4 due to  incorrect SCSI command tags.
• Addressed issue where hp-ams may fail to start when U.3 NVMe devices are installed in the system
• The HPE Synergy 6810C 25/50Gb Ethernet Adapter not displaying information in hp-ams is now resolved

• Drive status all shows failed on SL4540 Gen8 H220 [LSI] ILO4 due to  incorrect SCSI command tags.
• Addressed issue where hp-ams may fail to start when U.3 NVMe devices are installed in the system
• The HPE Synergy 6810C 25/50Gb Ethernet Adapter not displaying information in hp-ams is now resolved

• FW Transfer Fix
• Drive Failure Fix
• Power Loss Protection
• FW Download Fix
• Reset Fix
• Shutdown fix
• PCIe Improvement
• Random Write Improvement

• TBD

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

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes microcode mitigations for security vulnerability CVE-2021-0127. These issues are not unique to HPE servers.

Known Issues:

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-24512. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x000000EA (CPUID 506E3 and CPUID 906E9). These issues are not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel sighting CVE-2020-24512. This security vulnerability is documented in Intel Security Advisory INTEL-SA-00463. The Intel microcode patches included in this release are version 0x000000EA (CPUID 506E3) and 0x000000EA (CPUID 906E9). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8670 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes microcode mitigations for security vulnerability CVE-2021-0127. These issues are not unique to HPE servers.

Known Issues:

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-24512. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x000000EA (CPUID 506E3 and CPUID 906E9). These issues are not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel sighting CVE-2020-24512. This security vulnerability is documented in Intel Security Advisory INTEL-SA-00463. The Intel microcode patches included in this release are version 0x000000EA (CPUID 506E3) and 0x000000EA (CPUID 906E9). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8670 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for an Intel sighting where the system may experience a machine check after updating to the latest System ROM which contained a fix for an Intel TSX (Transactional Synchronizations Extensions) sightings. The previous microcode was first introduced in the v2.62 System ROM. This issue only impacts systems configured with Intel Xeon® D-1500 processors. This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

• FW Transfer Fix
• Drive Failure Fix
• Power Loss Protection
• FW Download Fix
• Reset Fix
• Shutdown fix
• PCIe Improvement
• Random Write Improvement

The following issues have been fixed in MFT version 4.17.

• Inconsistent flashing of the firmware while using the Intelligent Platform Management Bus/Bridge service.
• Occasional disconnections when the connected port was being activated.
• Flag "--json" did not work with features that required a user confirmation. 
• mlxconfig query for the BOOT_INTERRUPT_DIS TLV showed a wrong value in the "current value" field.
• mst version returned an incorrect string: "mst, MFT_VERSION_STR built on TOOLS_BUILD_TIME + Git SHA Hash: TOOLS_GIT_SHA".
• MFT tools did not support using combined short flags without a separation between them.
• Performing a driver restart while burning the firmware resulted in firmware burning failure and occasionally device was not accessible.
• MVPD read errors occurred from the mlxfwmanager during fast reboot.

• Fixed a compatibility issue with VMware Update Manager as it wouldn't accept a bundle with metadata xml with old versioning scheme. The metadata xml now contains the new versioning scheme.

• Fixed a compatibility issue with VMware Update Manager as it wouldn't accept a bundle with metadata xml with old versioning scheme. The metadata xml now contains the new versioning scheme.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000019 (CPUID 306F4) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000019 (CPUID 306F4) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

• Due to a SLES 15 kernel setting, hfi1_eprom cannot work while the HFI driver is loaded. The tool and driver are mutually exclusive.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes Intel Platform Update 2021.2. It provides mitigations for security vulnerabilities documented as INTEL-SA-00561 for below CVEs: CVE-2021-0092, CVE-2021-0144, CVE-2021-0099, CVE-2021-0103, CVE-2021-0107, CVE-2021-0111, CVE-2021-0114, CVE-2021-0115, CVE-2021-0116, CVE-2021-0117, CVE-2021-0118, CVE-2021-0125, CVE-2021-0124.

These issues are not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel technical sighting referred to as MD Clear. The Intel microcode patches included in this release are version 0x00000046 (CPUID 306F2) and 0x0B00003E (CPUID 406F1). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-12360 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

• To support scalability, function representor channels were limited to 4.However in scenarios when SF (Scalable Function) was not used, certain use cases required representors to support a large number of channels.Hence, representor channel limit to 4 was applicable only when a PCI device, such as Scalable Function support, was enabled.
• Matching on ipv4_ihl (internet header length) was supported only for outer headers. 
• When using one counter for both pop/push VLAN actions, the counter value was incorrect. Hence, Spliting the counter for pop_vlan_action_counter and push_vlan_action_counter.
• Incorrect L3 decapsulation occured when the original inner frame was small and was padded to comply with minimum frame size of 64-bytes.
• dapl and libmlx4 were needed by libdat2 and libdpdk. In order to remove or update dapl and libmlx4, their dependencies had to be removed.
• In fork situation, if parent/children processes happen to have samevirtual address, then the doorbell mechanism did not work well and may led to errors in application behavior.
• An override of log_max_qp by other devices occured if the devices share the same mlx5_core module.
• A synchronization issue where closing and opening channels (which might happen on configuration changes such as changing number of channels) may caused null pointer dereference in function mlx5e_select_queue.
• Enabling tx-udp_tnl-csum-segmentation had no affect on the driver. 
• Old udevd versions could get stuck renaming network devices, leaving interfaces named eth* instead of enp*. 
• Flows with t commit action with ct state -trk were not be offloaded (i.e., table=0,ct_state=-trk,ip actions=ct(commit,table=1)).
• Connection tracking over VF LAG with tunnel encapsulation/decapsulation was not supported and caused traffic drop.
• OFED compilation failed when stack size was limited to 1024.
• Setting rate/burst values higher than 2,147,483,648 were rejected.
• Offloaded remote mirroring flows on tunnel device caused forwarded traffic to VF to not be decapsulated.
• Trying to set VPort match mode on VF (cat/sys/class/net/enp8s0f2/compat/devlink/vport_match_mode), leads to kernel crash.
• OVS flows were not being offloaded over socket-direct devices.
• When VXLAN was configured and illegal route was added, the system crashed with call trace.
• If any traffic was sent before the netdev went up for the first time, a division by zero caused by a modulo operation occured in ndo_select_queue, leading to a kernel panic.
• After restarting driver, the x86 host might be in grace period and might not recover on its own. As part of the fix, 5 FW_fatal recoveries are allowed within the 20-minute grace period. As a result, the grace period in the devlink health show command will appear as 0 for FW_fatal reporter.

• To support scalability, function representor channels were limited to 4.However in scenarios when SF (Scalable Function) was not used, certain use cases required representors to support a large number of channels.Hence, representor channel limit to 4 was applicable only when a PCI device, such as Scalable Function support, was enabled.
• Matching on ipv4_ihl (internet header length) was supported only for outer headers. 
• When using one counter for both pop/push VLAN actions, the counter value was incorrect. Hence, Spliting the counter for pop_vlan_action_counter and push_vlan_action_counter.
• Incorrect L3 decapsulation occured when the original inner frame was small and was padded to comply with minimum frame size of 64-bytes.
• dapl and libmlx4 were needed by libdat2 and libdpdk. In order to remove or update dapl and libmlx4, their dependencies had to be removed.
• In fork situation, if parent/children processes happen to have samevirtual address, then the doorbell mechanism did not work well and may led to errors in application behavior.
• An override of log_max_qp by other devices occured if the devices share the same mlx5_core module.
• A synchronization issue where closing and opening channels (which might happen on configuration changes such as changing number of channels) may caused null pointer dereference in function mlx5e_select_queue.
• Enabling tx-udp_tnl-csum-segmentation had no affect on the driver. 
• Old udevd versions could get stuck renaming network devices, leaving interfaces named eth* instead of enp*. 
• Flows with t commit action with ct state -trk were not be offloaded (i.e., table=0,ct_state=-trk,ip actions=ct(commit,table=1)).
• Connection tracking over VF LAG with tunnel encapsulation/decapsulation was not supported and caused traffic drop.
• OFED compilation failed when stack size was limited to 1024.
• Setting rate/burst values higher than 2,147,483,648 were rejected.
• Offloaded remote mirroring flows on tunnel device caused forwarded traffic to VF to not be decapsulated.
• Trying to set VPort match mode on VF (cat/sys/class/net/enp8s0f2/compat/devlink/vport_match_mode), leads to kernel crash.
• OVS flows were not being offloaded over socket-direct devices.
• When VXLAN was configured and illegal route was added, the system crashed with call trace.
• If any traffic was sent before the netdev went up for the first time, a division by zero caused by a modulo operation occured in ndo_select_queue, leading to a kernel panic.
• After restarting driver, the x86 host might be in grace period and might not recover on its own. As part of the fix, 5 FW_fatal recoveries are allowed within the 20-minute grace period. As a result, the grace period in the devlink health show command will appear as 0 for FW_fatal reporter.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes microcode mitigations for security vulnerability CVE-2021-0127. These issues are not unique to HPE servers.

Known Issues:

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-24512. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-464. The Intel microcode patches included in this release are version 0x000000EA (CPUID 506E3 and CPUID 906E9). These issues are not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for the Intel sighting CVE-2020-24512. This security vulnerability is documented in Intel Security Advisory INTEL-SA-00463. The Intel microcode patches included in this release are version 0x000000EA (CPUID 506E3) and 0x000000EA (CPUID 906E9). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for BIOS advisories and security vulnerabilities documented as CVE-2020-8670 and CVE-2020-12357. These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00463. These issues are not unique to HPE servers.

Known Issues:

• TBD

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