Bug Fixes in This Version

4564535

Description: Under high flow-insertion rates on BlueField-3, pipe resize operations may time out (exceeding 10 seconds). This can cause OVS threads (ovs_rcu) to block, indicating a stall in the hardware offload process.

Keyword: OVS; Pipe Resize; Timeout

Detected in version: 3.1.0

4564538

Description: A pipe resize operation on BlueField-3, often triggered by dynamic flow limits, may fail. This can result in memory allocation errors and severe delays (10+ seconds), leading to a loss of network connectivity, such as BGP peering sessions dropping.

Keyword: Pipe Resize; Flow Limit; Memory Allocation

Detected in version: 3.1.0

4621473

Description: A race condition during flow deletion may cause application instability or incorrect counter values.

Keyword: Flow; delete

Detected in version: 3.1.0

4366800

Description: Creating a packet filtering rule with match criteria on certain unsupported fields (e.g., specific VXLAN-GPE flags) does not return an error as expected.

Keyword: Packet filtering; DOCA Flow

Detected in version: 3.1.0

4627850

Description: The RTC timestamp is not correctly parsed in the doca_telemetry_diag sample.

Keyword: RTC; PTP; DOCA Telemetry

Detected in version: 3.1.0

4548383

Description: The doca_flow_header_ib_bth structure includes fields for which match and action operations are not supported. Supported fields:

• Match and action: opcode, dest_qp

• Match only: AckReq (in flags1)

• Action only: psn 

Keyword: DOCA Flow

Detected in version: 3.1.0

4560966

Description: Enabling the RX Rate flag in the ZTR RTTCC algorithm causes compilation to fail because the private DOCA PCC device header is not included.

Keyword: DOCA PCC; Zero-touch RoCE; round-trip time congestion control

Detected in version: 3.1.0

4223392

Description: CT miss pipe receives configured IP version only.

Keyword: DOCA Flow

Detected in version: 3.1.0

4539156

Description: Fixed an issue on Debian/Ubuntu where DKMS kernel modules post-install scripts did not set autoinstall, causing modules to appear as "added" instead of "installed".

Keyword: DKMS kernel modules, Debian/Ubuntu, post-install scripts

Detected in version: 3.1.0

4548661

Description: Resolved startup warning in MFT caused by missing dimax-init component, which was not included in the EN+RoCE Bundle.

Keyword: MFT

Detected in version: 3.1.0

4578268

Description: Resolved missing kernel symbol dependencies in kmod-* packages by switching to DKMS-based modules in DOCA Host 3.2.0, ensuring proper module load on custom kernels.

Keyword: kmod-* packages, DKMS-based modules

Detected in version: 3.1.0

4648210

Description: Fixed an issue preventing DNF/YUM upgrades of rebuilt mlnx-ofa_kernel-devel packages (via doca-kernel-support) due to version sorting errors. The rebuilt package now appends ".1" and the kernel version to ensure proper RPM comparison and smooth upgrades.

Keyword: mlnx-ofa_kernel-devel package

Detected in version: 3.1.0

4651525

Description: Fixed an issue on ARM64 systems where the write-combining capability might not have been properly detected during driver initialization.
Now, the driver performs an internal check at boot time to correctly determine write-combining support, improving data path efficiency and traffic latency.

Keyword: Firmware, kernel lock

Detected in version: 3.1.0

4642754

Description: Fixed a non-responsive firmware issue that could cause the kernel to lock up for an extended period.

Keyword: Firmware, kernel lock

Detected in version: 3.1.0

4567695 / 4606693

Description: Fixed a rare crash that could occur when a MAD completion queue (CQ) was destroyed while RDMA CM traffic was still active.

Keyword: MAD CQ

Detected in version: 3.0.0

4222720

Description: Fixed an issue where, when running on DPU Arm cores, ptp4l could lose synchronization due to delayed transmit port timestamps, causing the tx_ts_timeout to expire and resulting in the error message: ptp4l[XXXX]: timed out while waiting for tx timestamp.

Keyword: DOCA Firefly Service

Detected in version: 3.1.0

4553499

Description: Fixed an issue where, on devices that do not support BlueFlame, allocation of a new Transport Domain (TD) could fail when attempting to allocate a dedicated UAR.

Keyword: BlueFlame, Transport Domain (TD), UAR

Detected in version: 3.0.0

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

4570205

Description: Fixed a firmware issue where the ZTR_RTTCC algorithm parameters AI and HAI did not support a sufficient range.

Keywords: PCC, ZTR_RTTCC

Detected in version:

32.46.1006

Fixed in Release: 

32.47.1026

4650314

Description: The SBR hot reset error during mlxfwreset level 4 is resolved by skipping configuration of the second (disabled) link via mlxconfig. With only the active link configured, the reset flow completes successfully.

Keywords: mlxfwreset

Detected in version:

32.46.1006

Fixed in Release:

32.47.1026

4629077

Description: Fixed an issue where coalescing regular SX events with SX RTT events under ZTR_RTTCC could keep improper event fields, which could impact congestion control behavior.

Keywords: PCC, ZTR_RTTCC

Detected in version:

32.46.1006

Fixed in Release:

32.47.1026

4683328

Description: Fixed an issue in the ZTR_RTTCC algorithm where probe-abortion handling could behave improperly under high-stress network conditions, ensuring proper congestion control and stable traffic performance.

Keywords: PCC, ZTR_RTTCC

Detected in version:

32.46.1006

Fixed in Release:

32.47.1026

4501554

Description: Fixed an assertion failure that could occur with the E-Switch uplink in specific configurations where the e-switch was disabled and Path Migration was active or GVMIs were using SRQ loopback in SQs. The issue occurred because the firmware attempted to perform cleanup operations when the uplink configuration lacked sufficient capacity.
Now, when the E-Switch is disabled and no actions are available in the uplink STE, the firmware connects to the uplink STE instead of copying it.

Keywords: Path migration, steering

Detected in version:

32.46.1006

Fixed in Release:

32.47.1026

4506854

Description: Added Scaling Factor "read" field. To obtain correct values in mlxlink, MFT version 4.33.0 or later is required.

Keywords: Scaling Factor, mlxlink, MFT

Detected in version:

32.46.1006

Fixed in Release:

32.47.1026

4500365

Description: Fixed the adaptive PCIe gain setting.

Keywords: PCIe gain

Discovered in Version:

32.43.2402

Fixed in Release:

32.47.1026

4571079

Description: Fixed an issue where invoking the resourcedump tool with segment type DPA_PROCESS_LST returned invalid data when the parameter n1 == 1 and no processes existed on the current vhca_id.
The fix adds a proper check, and the resourcedump tool now reports the correct error in this scenario.

Keywords: DPA PROCESS, RESOURCE DUMP

Discovered in Version:

32.45.1020

Fixed in Release:

32.47.1026

4529293

Description: Fixed an issue where, during failover or restart, the SM sending a PortInfo MAD to the HCA firmware triggered reinitialization of port buffers, momentarily halting ingress traffic and causing packet drops.
The firmware now avoids reconfiguring port buffers when the new configuration matches the current one.

Keywords: OpenSM

Discovered in Version:

32.46.1006

Fixed in Release:

32.47.1026

4683346

Description: Fixed an issue where, under the ZTR_RTTCC algorithm, a flow that reached its minimum rate due to heavy congestion would not recover its rate once the congestion cleared.

Keywords: PCC, ZTR_RTTCC

Discovered in Version:

32.46.1006

Fixed in Release:

32.47.1026

4458670

Description: Fixed an issue where writing to nic_interface could set the parent function to DISABLED without propagating the state to its child VFs. The firmware now ensures that children inherit the DISABLED state correctly.

Keywords: VF health

Discovered in Version:

32.45.1020

Fixed in Release:

32.47.1026

4517037

Description: Fixed a rare issue where performing an FLR on a released ICM address from the DPA process could cause the DPA kernel to hang due to a race condition.

Keywords: FLR, ICM address

Discovered in Version:

32.46.1006

Fixed in Release:

32.47.1026

4618972

Description: Fixed an issue that could cause false-positive detection of DEAD_IRISC during DPA destroy_process or destroy_mem operations on highly loaded systems.

Keywords: IRISC

Discovered in Version:

32.43.2402

Fixed in Release:

32.47.1026

4133425

Description: Fixed an issue where PTP was not supported when the port speed was configured to 1G.

Keywords: PTP

Discovered in Version:

32.46.1006

Fixed in Release:

32.47.1026

4500507

Description: Fixed an issue where parallel execution of CREATE_NVME_SQ or CREATE_NVME_SQ_BE objects could lead to a fatal assert (0x8184).

Keywords: NVME, CREATE_NVME_SQ, CREATE_NVME_SQ_BE

Discovered in Version:

32.46.1006

Fixed in Release:

32.47.1026

4501554

Description: Fixed an assertion failure that could occur with the E-Switch uplink in specific configurations where the e-switch was disabled and Path Migration was active or GVMIs were using SRQ loopback in SQs. The issue occurred because the firmware attempted to perform cleanup operations when the uplink configuration lacked sufficient capacity.
Now, when the E-Switch is disabled and no actions are available in the uplink STE, the firmware connects to the uplink STE instead of copying it.

Keywords: Path migration, steering

Discovered in Version: 

24.46.1006

Fixed in Release:

24.47.1026

4529293

Description: Fixed an issue where, during failover or restart, the SM sending a PortInfo MAD to the HCA firmware triggered reinitialization of port buffers, momentarily halting ingress traffic and causing packet drops.
The firmware now avoids reconfiguring port buffers when the new configuration matches the current one.

Keywords: OpenSM

Discovered in Version: 

24.45.1020

Fixed in Release:

24.47.1026

4366117

Description: Configuring a small MTU leads to fragmentation of packets critical for the PXE boot process. As a result, the PXE boot filters mistakenly discard these packets, causing the PXE boot to fail. 

Keywords: PXE boot filters

Discovered in Version: 

24.45.1020

Fixed in Release:

24.47.1026