DOCA Framework Bug Fixes
|
Ref # |
Issue |
|---|---|
|
4858336 |
Description: A memory leak and potential memory corruption occur within the DOCA Flow library during the lifecycle of Ordered List pipes. |
|
Keyword: IPsec Security Gateway; DOCA Flow |
|
|
Detected in version: 3.2.1 |
|
|
4848219 |
Description: MSI-X interrupts raised from the DPA using the |
|
Keyword: NVMe Emulation; DPA; MSI-X interrupts |
|
|
Detected in version: 3.2.1 |
|
|
4890064 |
Description: A memory leak occurs in the |
|
Keyword: |
|
|
Detected in version: 3.2.1 |
|
|
4810489 |
Description: When the host system is powered off or rebooting, DOCA applications (including |
|
Keyword: DOCA Flow; representor devices; bare metal |
|
|
Detected in version: 3.2.1 |
|
|
4844003 |
Description: The flow mark value is mistakenly discarded when DOCA Flow is operating in default mode. This issue prevents the correct application of mark actions on network flows. |
|
Keyword: DOCA Flow; default mode; mark |
|
|
Detected in version: 3.2.1 |
|
|
4804647 |
Description: |
|
Keyword: DOCA Flow; |
|
|
Detected in version: 3.2.1 |
|
|
4804646 |
Description: |
|
Keyword: DOCA Flow; |
|
|
Detected in version: 3.2.1 |
|
|
4894026 |
Description: When running the DOCA Management Service with its default configuration, the system may unexpectedly lose its connection to the BlueField DPU. |
|
Keyword: DMS; connection loss |
|
|
Detected in version: 3.2.1 |
|
|
4894457 |
Description: When executing a get command on a configuration subtree, the entire command will fail if any single element within that subtree is unsupported on the Arm architecture. |
|
Keyword: Subtree query |
|
|
Detected in version: 3.2.1 |
|
|
4774876 |
Description: The |
|
Keyword: FlexIO; Single Point of Resource Distribution; missing module |
|
|
Detected in version: 3.2.1 |
DOCA-Host and DOCA Drivers Bug Fixes
|
Ref # |
Issue |
|---|---|
|
4878440 / 4834414 |
Description: Fixed an issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig may be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure. |
|
Keyword: Installation |
|
|
Reported in version: 3.2.1 |
|
|
4845289 / 4848666 / 4851349 / 4857860 / NVBug 5825913 |
Description: Fixed an issue where DOCA-Host 3.2 failed to compile on Linux kernel 6.12.60. |
|
Keyword: DOCA-Host compilation |
|
|
Reported in version: 3.2.1 |
|
|
4830937 / 4775049 / 4865514 |
Description: Fixed an issue where the driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs. |
|
Keyword: mlnx-ofa_kernel DKMS package upgrade |
|
|
Reported in version: 3.2.1 |
|
|
4878487 / 4808487 |
Description: Fixed an issue where, under certain circumstances, upgrading the mlnx-ofa_kernel DKMS package could cause a submodule package (e.g., iser or srp) to use a leftover build directory from /var/lib/dkms. |
|
Keyword: mlnx-ofa_kernel DKMS package upgrade |
|
|
Reported in version: 3.2.1 |
|
|
4869510 / 4802194 |
Description: Fixed an overflow issue where the max-rate value was stored in a unsigned 8-bit integer type, causing values above 255 to wrap (e.g., 257 became 1). |
|
Keyword: max-rate value |
|
|
Reported in version: 3.2.1 |
|
|
4868130 / 4426799 |
Description: Fixed an issue where devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations. |
|
Keyword: devlink, fw_reset |
|
|
Reported in version: 3.2.1 |
|
|
4858692 / 4858587 |
Description: Fixed soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow. |
|
Keyword: soft lockup warnings |
|
|
Reported in version: 3.2.1 |
|
|
4789990 / 4778339 / 4776537 |
Description: Added support for MAC forwarding on the uplink representor for multi-host and DPU environments. This allows the uplink representor to explicitly request MAC address forwarding in MPF configurations, where multiple PFs share a single physical port. The implementation includes proper MAC address lifecycle management using the MPFS table, hardware flow rules, and software hash tables, with automatic cleanup when the driver is unloaded or when the eswitch mode is changed. |
|
Keyword: MAC forwarding, uplink representor, MPFS, DPU |
|
|
Reported in version: 3.2.1 |
BSP Bug Fixes
|
Ref # |
Details |
|---|---|
|
5125190 |
Description: On BlueField-3 systems running the DOCA 3.4 Ubuntu 24.04 BFB, |
|
Keywords: APT; Ubuntu; package management |
|
|
Detected in version: 4.15.0 |
|
|
5180884 |
Description: On RHEL 9 and RHEL 10, DOCA Installer may fail to start and report a missing library. |
|
Keywords: DOCA Installer; RHEL; missing library |
|
|
Detected in version: 4.15.0 |
|
|
5172294 |
Description: On JBOF systems, BFB installation may target an NVMe device other than the intended BlueField NVMe. |
|
Keywords: BFB installation; NVMe; JBOF |
|
|
Detected in version: 4.15.0 |
|
|
5172025 |
Description: After installing a RHEL 10.2 BFB, the BlueField-3 DPU may stop at the UEFI menu instead of booting. |
|
Keywords: BFB installation; RHEL; UEFI |
|
|
Detected in version: 4.15.0 |
|
|
4989952 |
Description: On certain BlueField-3 devices upgraded from firmware 4.7.1.4 to 4.13.0, the configured 5200 MT/s DDR speed may not take effect after the first reboot. |
|
Keywords: DDR; firmware upgrade |
|
|
Detected in version: 4.13.0.13932 |
|
|
4986356 |
Description: On BlueField-2 systems running DOCA 3.3 or 3.4, |
|
Keywords: dmidecode; cache information; BlueField-2 |
|
|
Detected in version: DOCA 3.4.0, DOCA 3.3.0 |
|
|
4966842 |
Description: A latent Day 1 bug in the UEFI RTC driver causes the month to be calculated incorrectly (off by one). This results in unexpected date jumps and inaccurate system time reporting. |
|
Keywords: real-time clock; system date |
|
|
Detected in version: 4.15.0 |
|
|
4867794 |
Description: On RHCOS 4.20, |
|
Keywords: RHCOS; release metadata; BFB |
|
|
Detected in version: 4.15.0 |
|
|
4742314 4546931 4822210 |
Description: Running |
|
Keywords: mlxfwreset; ext4; kernel warning |
|
|
Detected in version: 4.15.0 |
|
|
4234285 |
Description: During BlueField boot, the BlueField BIOS/UEFI may fail to acquire a DHCP IP address from the BMC for Redfish communication. This would cause the BIOS to bypass the Redfish step and to ignore any configuration changes in Redfish. |
|
Keywords: DHCP; UEFI; Redfish |
|
|
Detected in version: 4.15.0 |
BMC Bug Fixes
|
Ref # |
Issue Details |
|---|---|
|
5149126 |
Description: During a golden-image BMC firmware update, activation may fail and leave the Redfish task stuck at 0%, preventing subsequent updates. |
|
Reported in version: 26.04 |
|
|
5107116 |
Description: In rare cases, the PLDM firmware update process in NIC mode may fail during the activation phase due to a transient communication error on the device. |
|
Reported in version: 26.04 |
|
|
4966486 |
Description: On BlueField-3 systems, requests to |
|
Reported in version: 26.04 |
|
|
5159819 |
Description: After a watchdog-triggered DPU reset, the reset reason may be missing from the BMC system event log. |
|
Reported in version: 26.04 |
|
|
5071652 |
Description: In rare cases, the CEC/ERoT firmware version reported through Redfish may appear incomplete or contain blank characters. |
|
Reported in version: 26.04 |
|
|
5071052 |
Description: During a DPU OS reboot, the BMC system event log may incorrectly report a P1 link configuration error even when the link is healthy. |
|
Reported in version: 26.04 |
|
|
5044522 |
Description: A timing side channel in HMAC-SHA256-128 integrity verification may allow an adjacent-network attacker to infer authentication data. |
|
Reported in version: 26.04 |
|
|
4833493 |
Description: When the BMC event log is full, rebooting the BMC may cause existing events to be lost. |
|
Reported in version: 26.04 |
BlueField-3 Firmware Bug Fixes
|
Internal Ref.
|
Issue
|
|---|---|
|
4789910 / 4876645 / 4789909 |
Description: Fixed an issue where an FLR on the emulation device could cause corrupted data to be sent to the destination via the emulation device’s backend QP. |
|
Keywords: NVMe and Virtio emulation |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4863794 / 4638676 |
Description: Fixed an issue where, after installing the fw-bundle, the DOCA installer failed to query the BMC/CEC versions, preventing doca-installer --show-running-fw from displaying the BMC/CEC version information. |
|
Keywords: fw-bundle installation, BMC/CEC |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4773334 / 4711949 |
Description: Fixed an issue where, in older versions and under specific configurations, the MEMIC BAR size could be unaligned to 64 bytes. The software now treats the address as aligned down to a 64-byte boundary. |
|
Keywords: MEMIC BAR size |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4796353 / 4785853 |
Description: Fixed an issue where the virtio software controller could encounter an infinite FLR loop if the host shut down during the software live-upgrade procedure in configurations with separate power supplies (i.e., the DPU remains powered when the host is powered off). |
|
Keywords: Virtio, Software Live Upgrade, FLR |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4806969 / 4804664 |
Description: Fixed an issue in the User Debugger “query caps” where it returned only the number of capabilities, not the capability bitmap. |
|
Keywords: User Debugger “query caps” |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4895283 / 4370695 |
Description: Fixed a corner case during warm reboot that could cause some TX lane elastic buffers to lose synchronization during link training. |
|
Keywords: TX lane elastic buffers |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4796352 / 4794198 |
Description: Fixed an issue where, in host-aware mode, the firmware did not block the hotplug FSM transition from HOTPLUG to HOTUNPLUG_PREPARE, which could cause a hotplug device to enter an unexpected state. |
|
Keywords: Hotunplug, Virtio |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4821502 / 4804415 |
Description: Fixed an issue where a host warm reboot with emulated NVMe devices exposed could cause firmware assertion 0x8494, preventing SNAP from operating on the existing emulated NVMe devices. |
|
Keywords: NVMe |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4824535 / 4809134 |
Description: Fixed an issue where the steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD. |
|
Keywords: Steering tables, LLDP |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
|
|
4849832 / 4890248 |
Description: Fixed an issue where internal hardware error 0x07 occurred randomly during device unbind. |
|
Keywords: HW error 0x07 |
|
|
Detected in version: 32.47.1088 |
|
|
Fixed in Release: 32.47.2682 |
BlueField-2 Firmware Bug Fixes
|
Internal Ref. |
Issue |
|---|---|
|
4849832 / 4890248 |
Description: Fixed an issue where internal hardware error 0x07 occurred randomly during device unbind. |
|
Keywords: HW error 0x07 |
|
|
Detected in version: 24.47.1088 |
|
|
Fixed in Release: 24.47.2682 |
Last updated: