Networking DOCA SDK Documentation

Bug Fixes in This Version


DOCA Bug Fixes

Ref #

Issue

4328216

Description: Fixed an issue in OVS-DOCA where using connection tracking can cause an invalid packet to reach software and for the connection to not close.

Keyword: Openswitch, OVS-DOCA

Detected in version: 2.9.2

4268325

Description: Consumer context may get suspended before it has fully initialized.

Keyword: Consumer, context

Detected in version: 2.9.2

4316503

Description: rte_eth_dev_start() performs unnecessary recreation of mlx5 control flow rules, resulting in increased delay of rte_eth_dev_start().

Keyword: Simple forward, mlx5

Detected in version: 2.9.2

4310521

Description: When counters are preallocated for use with Flow Template API through rte_flow_configure(), CPU usage on a core which runs a service thread (spawned by mlx5 PMD) might reach 100% even when no flow rules are being created/destroyed.

Keyword: CPU utilization, counters, Flow Template

Detected in version: 2.9.2

4270617

Description: The RX queue may exhaust its mbuf pool, leading to incorrect CQE polling that mistakenly accesses application-owned mbufs, potentially causing crashes.

Keyword: CPU utilization, counters, Flow Template

Detected in version: 2.9.2

4260450

Description: Fixed an issue where enabling SFLOW with OVN causes OVS to crash.

Keyword: SFLOW

Detected in version: 2.9.2

4249302

Description: Fixed an issue where using dpdkvhostuser interface with OVS-DOCA causes it to crash.

Keyword: OVS-DOCA, dpdkvhostuser

Detected in version: 2.9.2

4213469

Description: Fixed an issue where openvswitch service gets disabled (masked) after DOCA installation. 

Keyword: openvswitch, installation

Detected in version: 2.9.2

4192818

Description: With uplinks in the br-sfc bridge, IPv6 traffic in uplink-to-uplink direction results in OVS crash resulting in complete traffic drop.

Keyword: OVS restart, traffic drop

Detected in version: 2.9.2


BSP Bug Fixes

Ref #

Details

5125190

Description: On BlueField-3 systems running the DOCA 3.4 Ubuntu 24.04 BFB, apt update may fail, preventing packages from being updated or installed.

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, dmidecode may reverse the reported sizes of the L1 data and instruction caches.

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, /etc/mlnx-release may show a release name and date that do not match the installed BFB.

Keywords: RHCOS; release metadata; BFB

Detected in version: 4.15.0

4742314

4546931

4822210

Description: Running mlxfwreset on BlueField-3 with Ubuntu 24.04 may trigger an ext4 journal warning call trace (ext4_journal_check_start+0xc8/0x120); no functional impact observed, safe to ignore.

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 /redfish/v1/Managers/Bluefield_BMC may take several minutes and return an internal error or timeout. Other Redfish resources may remain responsive, and the UEFI System Configuration page may also load slowly.

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

4186805

Description: Fixed an issue in the default DPU configuration that prevented the DPU from hiding the PF device by default after a firmware upgrade. Additionally, CQE_COMPRESSION=1 and NUM_OF_VFS=0 were not set as expected.

Keywords: BF3-COM-DPU default nvconfig settings

Discovered in Version:

32.42.1000

Fixed in Release:

32.43.2566

4219027

Description: Fixed an issue where the BlueField-3 device, which uses two GPIOs for pkg_id calculation, had the MSB incorrectly set to zero.

Keywords: NC-SI

Discovered in Version:

32.42.1000

Fixed in Release:

32.43.2566

4271933

Description: Fixed an issue that could cause the DESTROY_MKEY command to take an unusually long time to execute, with the host driver showing a "No done completion" for the command.

Keywords: Mkey

Discovered in Version:

32.42.1000

Fixed in Release:

32.43.2566

4271933

Description: Fixed the issue where HCA initialization could fail due to occasional random memory violations.

Keywords: HCA initialization

Discovered in Version:

32.42.1000

Fixed in Release:

32.43.2566

4189104

Description: Fixed the issue where the vDPA feature bits GUEST_TSO4 and GUEST_TSO6 were unexpectedly set by default, leading to traffic interruption.

Keywords: vDPA

Discovered in Version:

32.42.1000

Fixed in Release:

32.43.2566

BlueField-2 Firmware Bug Fixes

This version does not include Bug Fixes.

Last updated: