Bug Fixes in This Version

4220089

Description: Using dpdkvhostuser interface with OVS-DOCA causes it to crash.

Keyword: OVS

Detected in version: 2.9.0

4155959

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

Detected in version: 2.4.0

4268399

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

Keyword: CQEs; polling; mbuf overwrite

Detected in version: 2.9.0

4224295

Description: Traffic between non-hostnetwork workloads stops after 5 minutes due to the DPU VTEP MAC address aging out in OVS.

Keyword: OVS; aging; VTEP MAC

Detected in version: 2.9.0

4200690

Description: The fTPM trusted application is signed for testing proposes only (i.e., not securely) with a development key.

Keyword: fTPM over OP-TEE

Detected in version: 2.9.1

3962272

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

Detected in version: 2.9.0

4130438

Description: Firefly is not compliant with "SyncE to 1pps Class B/C Transient response" while using NVIDIA® ConnectX®-7 FHHL adapter card.

Keyword: Firefly

Detected in version: 2.9.0

4019161

Description: Increased the default TX queue length in IPoIB to enhance qdisc queueing and reduce CPU spikes.

Keyword: TX queue; qdisc; CPU

Detected in version: 2.10

4181675

Description: Fixed incorrect SA switching when multiple active TX SAs are created on a SC, caused by failing to respect the SA configured by encoding_sa.

Keyword: TX SAs

Detected in version: 2.10

4037307

Description: Fixed the receive queue cache size calculation to account for the host page size.

Keyword: Memory allocation

Detected in version: 2.10

4125071

Description: The --defltprio flag has been deprecated and removed from the mlnx_qos tool.

Keyword: mlnx_qos tool

Detected in version: 2.10

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

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

4087432

Description: Increased the RX lossless buffer size to delay the transmission of Pause/PFC frames during NIC congestion.

Keywords: RX lossless buffer size

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

4184904 / 4183908

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

Keywords: VDPA, feature cap, GUEST_TSO4, GUEST_TSO6

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

4184910

Description: Fixed an issue where enabling PCC NP and setting the link type to one port as IB and the other as Ethernet could cause an assert to appear in dmesg with ext_synd 0x8309.

Keywords: PCC NP, port type

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

4206142

Description: Fixed an issue related to the warning assert 0x8a88, which occurred due to a non-harmful read of the mkey during CREATE_XRQ with RNDV type.

Keywords: Warning assert 0x8a88

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

4073037

Description: An incorrect GPIO identification led to a false assumption of an overcurrent event. Fixing the GPIO definition resolved the issue.

Keywords: GPIO identification

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

4220460

Description: The default-enabled MSB in pkg_id has been removed from the strap. pkg_id now supports values from 0 to 3.

Keywords: NC-SI package ID

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

3672595

Description: When using multiple links on the same PCORE, if one link goes down (e.g., due to a disconnected cable), the PCIe tree below the active link is only partially visible, with only the outer switch USP being enumerated.

Keywords: PCIe Tree

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

3920614

Description: When a QP attached to XRQ is moved to an error state via the 2ERR command, the firmware waits for requests in the device to complete before sending a new event. The software must wait for this event before proceeding with the new QP, preventing conflicting requests between the new and old QPs.

Keywords: NVMe-oF Target Offload

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

3956166

Description: Fixed an issue in the ZTR_RTTCC algorithm when using SOURCE_QP (ROCE_CC_SHAPER_COALESCE in mlxconfig) in LAG mode, which caused low bandwidth in many-to-one traffic scenarios.

Keywords: LAG, PCC, ZTR_RTTCC

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

4258064

Description: When "Support separate priority configuration for RTT packets for DOCA PCC" is enabled and a QP is created after DOCA PCC starts, a fwassert will appear in dmesg, along with basic debug output, when the QP is destroyed. In addition to the fwassert, the allocated steering rules for the QP are not deallocated, leading to a resource leak.

Keywords: DOCA PCC

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

4265811

Description: Fixed an issue that caused HCA initialization to fail due to a random memory violation.

Keywords: HCA initialization

Discovered in Version:

32.43.2402

Fixed in Release:

32.44.1036

3661179

Description: Added a new mechanism for allocations and deallocations flows to enhance parallelism.

Keywords: Allocations, deallocations flows

Discovered in Version:

32.39.2048

Fixed in Release:

32.44.1036

4178900

Description: The following nvconfig settings for the Communication DPU (BF3-COM-DPU) are now set by default:

• INTERNAL_CPU_MODEL=1

• LAG_RESOURCE_ALLOCATION=1

• NUM_OF_PF=0

• CQE_COMPRESSION=1

• NUM_OF_VFS=0

• HAIRPIN_DATA_BUFFER_LOCK=1

• MEMIC_SIZE_LIMIT=0

• PCI_WR_ORDERING=1

Keywords: Communication DPU (BF3-COM-DPU), default nvconfig settings

Discovered in Version:

32.42.1000

Fixed in Release:

32.44.1036

3837255

Description: Fixed an issue with the Arm shutdown from the host OS process that resulted in the "-E- Failed to send Register MRSI" message.

Keywords: Host OS; reboot; error

Discovered in Version:

32.42.1000

Fixed in Release:

32.44.1036

4206142

Description: Fixed an issue related to the warning assert 0x8a88, which occurred due to a non-harmful read of the mkey during CREATE_XRQ with RNDV type.

Keywords: Warning assert 0x8a88

Discovered in Version:

24.43.2402

Fixed in Release:

24.44.1036

4154495

Description: Fixed rare issue that caused traffic to halt and prevented recovery when the emulation doorbell malfunctioned.

Keywords: Doorbell

Discovered in Version:

24.43.2402

Fixed in Release:

24.44.1036