Bug Fixes in This Version

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 flexio_dev_msix_send() function fail to reach the host system.

Keyword: NVMe Emulation; DPA; MSI-X interrupts

Detected in version: 3.2.1

4890064

Description: A memory leak occurs in the ovs-doca environment when repeatedly attaching and detaching e-switch (ESW) ports. The leak is specifically associated with the doca-flow hash pipe implementation.

Keyword: ovs-doca; memory leak; hash pipe

Detected in version: 3.2.1

4810489

Description: When the host system is powered off or rebooting, DOCA applications (including DOCA_FLOW) fail to discover network representor devices (e.g., PFs and SFs).

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: DOCA_FLOW does not support matching the ICMPv6 Identifier field within ICMPv6 Echo Request and Echo Reply packets.

Keyword: DOCA Flow; RTE_FLOW; ICMPv6 identifier

Detected in version: 3.2.1

4804646

Description: DOCA_FLOW does not support masked matching of the VXLAN RSVD1 (Reserved 1) field.

Keyword: DOCA Flow; RTE_FLOW; VXLAN RSVD1

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 dpa-resource-mgmt tool fails to run on systems defaulting to Python 3.12, displaying the error ModuleNotFoundError: No module named 'pkg_resources'.

Keyword: FlexIO; Single Point of Resource Distribution; missing module

Detected in version: 3.2.1

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

4693948

Description: When attempting to install the Ubuntu 24.04 (64k kernel) BFB image directly to an EMMC device, the installation may fail with a kernel panic. The system logs indicate an inability to mount the root filesystem, specifically returning the error: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0).

Keywords: VFS; kernel panic; EMMC installation

Detected in version: 4.14.0

4923234

Description: The libdoca-sdk-sta-dev package is missing from the BFB and DOCA base images for Ubuntu 24.04. This package is required for target offload functionality.

Keywords: Target offload; BFB image

Detected in version: 4.14.0

4948318

4945554

Description: If a secondary BMC task (such as a log dump) is started after the BMC firmware update has been initiated, but before the installer's monitoring logic has attached to it, the installer may mistakenly track the secondary task. This tracking error causes the installer to misjudge the update's completion, which can cause the subsequent BMC reboot to fail and leave the new firmware in a pending, unactivated state.

Keywords: BFB installer; Redfish API; task monitoring

Detected in version: 4.14.0

4863927

Description: When attempting to install development packages via dnf on Rocky Linux 9.2, users may encounter a package repository inconsistency. This version mismatch results in a dependency resolution failure, preventing the installation of the packages.

Keywords: gcc; gcc-c++; dnf

Detected in version: 4.14.0

4988092

Description: Following an out-of-the-box installation and subsequent reboot on Ubuntu 24.04 (64k kernel), the NetworkManager-wait-online.service fails to start. The system logs indicate that the service times out while waiting for network connectivity, causing the service state to be marked as failed (status=1/FAILURE).

Keywords: Network Manager; systemd; timeout

Detected in version: 4.14.0

4893340

Description: A strict 128KB maximum size limit for the bf.cfg configuration file caused deployment failures in environments requiring more extensive configurations, such as those that pass large Ignition configuration payloads via the Data Processing Framework (DPF).

Keywords: BFB installation; file size limit; bf.cfg

Detected in version: 4.14.0

4849953

Description: The dpa-ps and dpa-statistics diagnostic tools are missing from the BlueField-3 BFB image for Oracle Linux 8.

Keywords: DPA; missing package

Detected in version: 4.14.0

4871396

Description: The dpa-ps and dpa-statistics diagnostic tools are missing from the BlueField-3 BFB image for Oracle Linux 9.

Keywords: DPA; missing package

Detected in version: 4.14.0

4907434

Description: When a BMC firmware update requires activation (and is the only component pending), the doca-installer tool incorrectly advises the user to perform a Level 3 firmware reset (mlxfwreset -l 3). Executing this recommended reset will not activate the pending BMC firmware. This is a messaging error in the tool's final status summary.

Keywords: BMC firmware; pending activation

Detected in version: 4.14.0

4907646

Description: When using the doca-installer --compare command with the --psid flag to target specific devices, the tool correctly identifies and skips unsupported BlueField-2 devices but still incorrectly halts to ask, "Continue with the available devices?". This unexpected interactive prompt interrupts automated scripts that rely on the tool executing without manual intervention.

Keywords: Automation; interactive prompt

Detected in version: 4.14.0

4879150

Description: Running the mlnx-sf utility with the -e or --enable-eswitch flag causes the command to fail, returning an Unknown option "eswitch" error. This occurs because the eswitch configuration action is no longer supported by the underlying mlxdevm and devlink utilities.

Keywords: Scalable functions; mlnx-sf; eswitch; mlxdevm

Detected in version: 4.14.0

4776492

Description: Occasionally, upgrading PLDM BFB from DOCA v3.2.0 to v3.2.1 may lead to an assert 0x7 in dmesg.

Keywords: PLDM

Detected in version: 4.14.0

4949639

Description: During a BFB installation, the CEC firmware updates successfully, but the completion confirmation message is missing from the RSHIM logs. The log displays "Updating CEC firmware" but omits the final success status before moving on to the next installation step (such as updating certificates).

Keywords: RShim logs; CEC firmware

Detected in version: 4.14.0

4836088

Description: Executing bfcfg -d produces corrupt output and displays incorrect boot options. This occurs due to a parsing error when the tool attempts to convert the BOOTx_DEVPATH variables from their binary configuration format back into ASCII text.

Keywords: Secure boot; ASCII conversion; BOOTx_DEVPATH

Detected in version: 4.14.0

4839828

Description: Host tmfifo_net interfaces may intermittently acquire random MAC addresses instead of the expected 00:1a:ca:ff:ff:XX pattern. This can cause failures in environments that enforce strict MAC address validation.

Keywords: MAC address; tmfifo_net; rshim

Detected in version: 4.14.0

4924237

Description: The RShim USB device may intermittently disappear from the DPU BMC, causing operations that rely on it to fail with a "Failed to enable BMC rshim" error.

Keywords: RShim USB; out-of-band update

Detected in version: 4.14.0

4658222

Description: During the DPU boot-up sequence, an intermittent call trace containing the warning WARN_ON(!host->claimed) may appear in the system logs.

Keywords: Call trace; kernel boot up

Detected in version: 4.14.0

4604090

Description: If a corrupted or unauthenticated BFB image is transferred from the BMC to the DPU, the system halts the installation process as part of a built-in security mechanism. Once triggered, the recovery path remains locked to prevent potential compromise.

Keywords: Corrupt; BFB

Detected in version: 4.14.0

4848119

Description: A BlueField-2 UEFI boot-time regression added approximately 20 seconds to system startup.

Keywords: BlueField-2; boot time; UEFI

Detected in version: 4.14.0

4904043

Description: An intermittent firmware assert error (synd 0x7: irisc not responding) may appear in system logs (dmesg) following a PLDM firmware upgrade while the device is in NIC mode.

Keywords: PLDM

Detected in version: 4.14.0

4944048

Description: When upgrading or downgrading between the 25.10-LTSU2 and 26.04 releases, repeated BMC reboots may, in rare cases, cause the profile-manager service to fail due to a malformed JSON file. This failure triggers a core dump of the service, populates core dump logs, and causes the golden-image service to become unresponsive.

Workaround: Perform a factory reset on the BMC.

Keyword: BMC reboot; core dump; factory reset

Reported in version: 25.10-LTSU2

4917779

Description: Initiating an Arm GracefulReset can cause the BMC's Redfish UpdateService to incorrectly report its state as UnavailableOffline.

Reported in version: 26.01

4948318

4945554

Description: If a secondary BMC task (such as a log dump) is started after the BMC firmware update has been initiated, but before the installer's monitoring logic has attached to it, the installer may mistakenly track the secondary task. This tracking error causes the installer to misjudge the update's completion, which can cause the subsequent BMC reboot to fail and leave the new firmware in a pending, unactivated state.

Reported in version: 26.01

4401488

Description: The BMC kernel enforces CONFIG_STATIC_USERMODEHELPER, which routes all usermode helper calls to /sbin/usermode-helper. Because this executable does not exist on the system, these calls fail and may cause undefined system behavior.

Reported in version: 26.01

4905017

Description: When operating in NIC mode, a host power cycle may intermittently cause the UEFI to fail to retrieve BMC Redfish credentials. This results in a DPU-BMC RF credentials not found error and introduces a timeout delay during the boot sequence.

Reported in version: 26.01

 4969243

Description: When the ENABLE_BMC_WAIT flag is active on BlueField-3 DPUs, the BMC SEL may intermittently fail to record the complete UEFI boot progress following a host power cycle. This is a cosmetic issue and does not affect the functionality of the DPU.

Reported in version: 26.01

4995032

Description: Redfish queries via OobUpdate --show_all_version intermittently returned empty strings for IPMB-backed properties (such as BOARD and BSP).

Reported in version: 26.01

 4867786

Description: During BFB installation, the Golden ARM image update may intermittently hang and fail via Redfish, logging a golden_image_arm firmware update timed out error.

Reported in version: 26.01

 4914053

Description: The BFB installer defaults to DHCP for the VLAN4040 interface. If no DHCP server is present, the request silently fails after a 300-second timeout, bypassing the static IP fallback and skipping all BMC-related firmware updates.

Reported in version: 26.01

4924426

Description: Following a DPU reset, the BaseMAC, BaseGUID, and Description fields may incorrectly return as empty within the redfish/v1/Systems/Bluefield/Oem/Nvidia schema response.

Reported in version: 26.01

 4987307

Description: During BFB installations via Redfish, the task state may change to "Exception" before the specific error message is appended to the HTTP response payload. This results in incomplete error logs on the initial poll following a failure.

Reported in version: 26.01

 4980118

Description: The set_emu_params.sh script attempts to load the mlxbf_ptm (DPU Power Telemetry) driver, leading to continuous module load failures and log spam because mlxbf_ptm is a non-upstreamed debug driver that is unsupported on several operating systems.

Reported in version: 26.01

 4799519

Description: Accessing the /redfish/v1/Managers/Bluefield_BMC Redfish endpoint may time out, accompanied by repeated ipmb-host timeout errors in the console and significant delays (multiple minutes) when opening the UEFI "System Configuration" page.

Reported in version: 26.01

4932328

Description: Excessive Common Platform Error Record (CPER) files in /var/cper can exhaust the BMC root partition space. This crashes the entity-manager service and causes IPMI commands like ipmitool sdr to fail.

Reported in version: 26.01

4957197

Description: When external monitoring tools or scripts repeatedly query the BMC's Redfish interface using Basic authentication over extended periods, internal session resources fail to release properly. This memory leak eventually causes the BMC to lose network connectivity, even while the DPU management interface remains online.

Reported in version: 26.01

4966472

Description: The BMC generates a warning log for PLDM_Sensor_1_100 when the NIC temperature reaches the official 91°C upper non-critical threshold. This is an expected hardware alert for elevated temperatures, not a software defect.

Reported in version: 26.01

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

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