Bug Fixes in This Version

4044057

4035446

Description: The shared mirror pool resource is created with static memory, so it consumed too much memory.

Keyword: DOCA Flow; memory

Reported in version: 2.8.0

3988904

Description: Failure to create a control entry with shared endecap action.

Keyword: DOCA Flow

Reported in version: 2.8.0

3989851

Description: A DOCA Flow pipe has multiple actions. When the action idx is not 0 and it has a shared endecap action, a crash occurs when attempting to create an entry.

Keyword: DOCA Flow

Reported in version: 2.8.0

4098122

Description: NVQual does not correctly handle cases where mixed prefix to the PCIe of 0000 and any other option existed.

Keyword: NVQual; PCIe

Reported in version: 2.8.0

4096870

Description: Probing a bond interface while SFs are configured does not work.

Keyword: SF; LAG

Reported in version: 2.8.0

3885930

Description: When installing DOCA-Host on a system using NVMe storage (typically local NVMe disk), and the script doca-kernel-support is used to rebuild and install kernel modules, unloading the mlx5 drivers is only possible after also unmounting the NVMe storage, which would typically necessitate a reboot.

Keyword: NVMe; doca-kernel-support; DOCA for host

Reported in version: 2.7.0

3886674

Description: Installing doca-all and other DOCA metapackages does not install the mlnx-nvme driver.

Keyword: NVMe; DOCA profile

Reported in version: 2.7.0

4037010

Description: When calling *_is_equal_pci_addr() with a PCIe address of BDF format (i.e., without the domain component), then the assumed domain is "0000" (e.g., if the input PCI address is 03:00.0), then it is treated as if the input is 0000:03:00.0.

Keyword: PCIe; address

Reported in version: 2.6.0

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