Bug Fixes in This Version

3928479

Description: Users may encounter an error in "dmesg" when unplugging an emulated PCIe device.

Keyword: DevEmu

Reported in version: 2.7.0

3881941

Description: When working with RShim 2.0.28, PCIe host crash may rarely occur at the beginning of BFB push after the Arm reset.

Keyword: RShim; driver

Reported in version: 2.7.0

3882794

Description: When working with doca_pcc_np context, the return value from the API doca_pcc_get_max_num_threads() is incorrect. The function has an output parameter that indicates the maximum number of threads allowed for a doca_pcc_np context. The correct value that the library expects is 16 instead of the returned 64.

Keyword: PCC; threads

Reported in version: 2.7,0

3840230

Description: Order of cores specified in --core-list is not respected. Cores are picked in ascending order instead.

Keyword: DOCA Bench

Reported in version: 2.7,0

3849701

Description: DOCA Comch tests cannot be launched from BlueField side.

Keyword: DOCA Bench; DOCA Comch

Reported in version: 2.7,0

3857097

Description: DOCA RDMA tests cannot be launched from BlueField side.

Keyword: DOCA Bench; DOCA RDMA

Reported in version: 2.7,0

3857095

Description: Send tasks on DOCA RDMA may fail.

Keyword: DOCA Bench; DOCA RDMA; send

Reported in version: 2.7,0

3859823

Description: Multi-threaded tests using DOCA Comch may hang or emit an infinite amount of log messages. Single-threaded tests are less likely to cause this issue.

Keyword: DOCA Bench; DOCA Comch

Reported in version: 2.7.0

3872654

Description: And issue occurs when submitting tasks with DOCA SHA with the following error. 

[DOCA][ERR][doca_pe.cpp:177][task_submit] Task 0xaaaaf4865bf0: Failed to submit task: task is already submitted

Keyword: DOCA Bench

Reported in version: 2.7,0

3869639

Description: Users cannot use --job-output-buffer-size 0 when using remote output memory (--use-remote-output-buffers).

Keywords: DOCA Bench

Reported in version: 2.7,0

3886315

Description: To reset or shut down the BlueField Arm, it is mandatory to specify the --sync 0 argument with reset level 1 and reset type 3 or 4. For example: 

mlxfwreset -d <device> -l 1 -t 4 --sync 0 r

Keyword: Arm; shutdown

Reported in version: 2.7.0

3957990

Description: Sending a malformed UDP packet with VXLAN configuration causes OVS-DOCA to crash.

Keyword: OVS-DOCA; encap; crash

Reported in version: 2.7.0

3994490

Description: Malformed packets cause OVS to crash when performing encapsulation.

Keyword: Openvswitch

Reported in version: 2.7.0

3949342

Description: NVQual fails due to low line rate.

Keyword: NVQual

Reported in version: 2.7.0

3960883

Description: If working with 2 different NICs with the same app, encryption can occur on the wrong port.

Keyword: PSP gateway

Reported in version: 2.6.0

3546202

Description: After rebooting a BlueField-3 DPU running Rocky Linux 8.6 BFB, the kernel log shows the following error: 

[    3.787135] mlxbf_gige MLNXBF17:00: Error getting PHY irq. Use polling instead

This message indicates that the Ethernet driver will function normally in all aspects, except that PHY polling is enabled.

Keywords: Linux; PHY; kernel

Reported in version: 2.2.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