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

4432078

Description: The PLDM file name uses a different YY/MM tag than the corresponding BFB file name.

Keywords: PLDM; BFB; filename

Detected in version: 3.1.0

4438514

Description: When probing device instance 1, the gpio-mlxbf3 driver may log the following harmless message: mlxbf3_gpio MLNXBF33:01: error -ENXIO: IRQ index 0 not found.

Keywords: Logging

Detected in version: 3.1.0

4546487

Description: In Device Manager, users can still select the “Separated” internal CPU mode even though this mode has been deprecated and is no longer supported.

Keywords: Device Manager; Separated mode; SmartNIC; Embedded mode

Detected in version: 3.1.0

4548563

Description: On BlueField-3 with Ubuntu 24.04, the OP-TEE driver cannot be loaded. Running modprobe optee fails with Operation not supported.

Keywords: OP-TEE; modprobe

Detected in version: 3.1.0

4548705

Description: Oracle Linux 9.4 BFB for BlueField-3 does not include the doca-sosreport package, preventing generation of SOS diagnostic reports.

Keywords: BFB; doca-sosreport; missing package

Detected in version: 3.1.0

4582160

Description: Running dmidecode -t 16 on BlueField-3 may show an incorrect "Number Of Devices" in the physical memory array section. Systems with two memory devices may report only one.

Keywords: SMBIOS; dmidecode; memory devices

Detected in version: 3.1.0

4612418

Description: Configuring hugepages through /etc/default/grub (e.g., default_hugepagesz=1G hugepagesz=1G hugepages=6) does not take effect after reboot.

Keywords: Hugepages; GRUB; boot parameters

Detected in version: 3.1.0

4643161

Description: On some operating systems, the partition UUID may change after the first boot following installation.

Keywords: Maintenance mode; boot failure

Detected in version: 3.1.0

4652620

Description: Real-time CPU frequency monitoring may increase CPU usage by 10–30% on older Linux kernels.

Keywords: CPPC utilization

Detected in version: 3.1.0

4519591

Description: In NIC mode, after Arm reboot, the BMC firmware and CEC versions are intermittently missing in the host query output.

Keywords: Host; firmware

Detected in version: 3.1.0

4550064

Description: When running sos report, several plugins such as kernel, process, and processor may time out during report generation. The timeouts are harmless; reports still generate successfully.

Keywords: Kernel boot failure

Detected in version: 3.1.0

4626552

Description: A firmware update failure may be incorrectly logged as an informational [INFO] message rather than an [ERROR].

Keywords: Firmware update; bfb-install; logging

Detected in version: 3.1.0

4643378

Description: In long-duration AC cycling tests, ipmitool commands may fail due to intermittent I²C device access issues on BlueField-3.

Keywords: I2C; IPMI

Detected in version: 3.1.0

4656521

Description: On BlueField-3 running Debian 13, restarting the openibd driver service on the Arm side may fail if user applications (e.g., reactor_0) are still holding InfiniBand device handles. The service reports Cannot unload the InfiniBand driver stack.

Keywords: Debian; driver restart

Detected in version: 3.1.0

4064373

Description: The DPU BMC LLDP represents the eth0 interface. If a VLAN interface is initiated on top of eth0, the LLDP schema does not function as expected and the transmitted data does not accurately describe the eth0 attribute or the newly created VLAN.

Reported in version: 25.07

4365835

Description: There is a mistake in the message displayed when the BISO secure boot setting is changed through the DPU BMC where the event log shows ScureCurrentBoot instead of SecureBootCurrentBoot.

Reported in version: 25.07

4549368

Description: Power sensors available via ipmitool sensor command are not available when DPU is in kernel lockdown mode.

Reported in version: 25.07

4551450

Description: After BMC factory reset, the ipmitool network interface may fail to connect to the DPU BMC via the RMCP interface.

Reported in version: 25.07

4501157 / 4257750

Description: Fixed a critical issue with a live firmware patch.

Keywords: Live firmware patch

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4377816

Description: Fixed an issue where firmware did not de-assert the PERST of the DSP on pcore1. The fix updates the check to correctly interpret the default GPIO mapping value as 0xFFF (NO_GPIO_FUNCTION) instead of 0xFF (INVALID_READ).

Keywords: mlxconfig

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4286902

Description: Fixed a race condition in DPA process termination during the exception flow, where a failed process could be missed and not reported to the user.

Keywords: DPA

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4420567

Description: Removed an unnecessary and partially incorrect firmware check that blocked valid action list permutations allowed by the PRM. Validation of these permutations remains the responsibility of the software.

Keywords: Header actions

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4498670

Description: Fixed a race condition where destroying two emulation objects with the same VHCA ID could result in one destroy command failing with syndrome 0xF3F880.

Keywords: VirtIO

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4475307

Description: Fixed an issue where PCC DCQCN used incorrect parameter values when link speed was 400Gbps or higher.

Keywords: PCC DCQCN, congestion control.

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4443601

Description: Fixed a firmware issue where PXE failed to boot when both LAG ports were up.

Keywords: PXE, LAG

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4480427

Description: Fixed incorrect calculation of start address and mode for the CQE buffer in DPA CQ, which could cause CQEs to be written to the wrong address when the buffer is not 4K-aligned and spans a second page boundary.

Keywords: CQ, CQE Buffer, DPA

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4388371

Description: Fixed an issue where an uninitialized pport in the SLRG command, when using the SMP interface, caused an assertion failure.

Keywords: SLRG, SMP interface, pport

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4395036

Description: Fixed a race condition between firmware and hardware flows during QP closure.

Keywords: Race condition

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4428580

Description: Fixed a rare issue where triggering mstdump via core_dump in Windows drivers could cause a PCI link down condition.

Keywords: mstdump, windows

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4428580

Description: Fixed an issue with vQoS parameter configuration to improve latency handling for large messages.

Keywords: vQoS, latency

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4436922

Description: DC InfiniBand is not functional in this firmware version.

Keywords: DC, DDP traffic

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

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: 32.45.1020

Fixed in Release: 32.46.1006

4475307

Description: Fixed an issue where PCC DCQCN used incorrect parameter values when link speed was 400Gbps or higher.

Keywords: PCC DCQCN, congestion control.

Detected in version: 32.45.1020

Fixed in Release: 32.46.1006

4486431

Description: Fixed an issue where issuing multiple parallel queries of DPA_THREAD objects with the same object ID could fail.

Keywords: DPA

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

4470053

Description: Fixed an issue with vQoS parameter configuration to improve latency handling for large messages.

Keywords: vQoS, latency

Discovered in Version: 32.45.1020

Fixed in Release: 32.46.1006

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