DOCA Bug Fixes
|
Ref # |
Issue |
|---|---|
|
3962272 |
Description: |
|
Keyword: Simple forward |
|
|
Reported 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 |
|
|
Reported in version: 2.9.0 |
BSP Bug Fixes
|
Ref # |
Details |
|---|---|
|
4693948 |
Description: When attempting to install the Ubuntu 24.04 (64k kernel) BFB image directly to an EMMC device, the installation may fail with a kernel panic. The system logs indicate an inability to mount the root filesystem, specifically returning the error: |
|
Keywords: VFS; kernel panic; EMMC installation |
|
|
Detected in version: 4.14.0 |
|
|
4923234 |
Description: The |
|
Keywords: Target offload; BFB image |
|
|
Detected in version: 4.14.0 |
|
|
4948318 4945554 |
Description: If a secondary BMC task (such as a log dump) is started after the BMC firmware update has been initiated, but before the installer's monitoring logic has attached to it, the installer may mistakenly track the secondary task. This tracking error causes the installer to misjudge the update's completion, which can cause the subsequent BMC reboot to fail and leave the new firmware in a pending, unactivated state. |
|
Keywords: BFB installer; Redfish API; task monitoring |
|
|
Detected in version: 4.14.0 |
|
|
4863927 |
Description: When attempting to install development packages via |
|
Keywords: gcc; gcc-c++; dnf |
|
|
Detected in version: 4.14.0 |
|
|
4988092 |
Description: Following an out-of-the-box installation and subsequent reboot on Ubuntu 24.04 (64k kernel), the |
|
Keywords: Network Manager; systemd; timeout |
|
|
Detected in version: 4.14.0 |
|
|
4893340 |
Description: A strict 128KB maximum size limit for the |
|
Keywords: BFB installation; file size limit; bf.cfg |
|
|
Detected in version: 4.14.0 |
|
|
4849953 |
Description: The |
|
Keywords: DPA; missing package |
|
|
Detected in version: 4.14.0 |
|
|
4871396 |
Description: The |
|
Keywords: DPA; missing package |
|
|
Detected in version: 4.14.0 |
|
|
4907434 |
Description: When a BMC firmware update requires activation (and is the only component pending), the |
|
Keywords: BMC firmware; pending activation |
|
|
Detected in version: 4.14.0 |
|
|
4907646 |
Description: When using the |
|
Keywords: Automation; interactive prompt |
|
|
Detected in version: 4.14.0 |
|
|
4879150 |
Description: Running the |
|
Keywords: Scalable functions; mlnx-sf; eswitch; mlxdevm |
|
|
Detected in version: 4.14.0 |
|
|
4776492 |
Description: Occasionally, upgrading PLDM BFB from DOCA v3.2.0 to v3.2.1 may lead to an assert 0x7 in dmesg. |
|
Keywords: PLDM |
|
|
Detected in version: 4.14.0 |
|
|
4949639 |
Description: During a BFB installation, the CEC firmware updates successfully, but the completion confirmation message is missing from the RSHIM logs. The log displays "Updating CEC firmware" but omits the final success status before moving on to the next installation step (such as updating certificates). |
|
Keywords: RShim logs; CEC firmware |
|
|
Detected in version: 4.14.0 |
|
|
4836088 |
Description: Executing |
|
Keywords: Secure boot; ASCII conversion; BOOTx_DEVPATH |
|
|
Detected in version: 4.14.0 |
|
|
4839828 |
Description: Host |
|
Keywords: MAC address; tmfifo_net; rshim |
|
|
Detected in version: 4.14.0 |
|
|
4924237 |
Description: The RShim USB device may intermittently disappear from the DPU BMC, causing operations that rely on it to fail with a "Failed to enable BMC rshim" error. |
|
Keywords: RShim USB; out-of-band update |
|
|
Detected in version: 4.14.0 |
|
|
4658222 |
Description: During the DPU boot-up sequence, an intermittent call trace containing the warning |
|
Keywords: Call trace; kernel boot up |
|
|
Detected in version: 4.14.0 |
|
|
4604090 |
Description: If a corrupted or unauthenticated BFB image is transferred from the BMC to the DPU, the system halts the installation process as part of a built-in security mechanism. Once triggered, the recovery path remains locked to prevent potential compromise. |
|
Keywords: Corrupt; BFB |
|
|
Detected in version: 4.14.0 |
|
|
4848119 |
Description: A BlueField-2 UEFI boot-time regression added approximately 20 seconds to system startup. |
|
Keywords: BlueField-2; boot time; UEFI |
|
|
Detected in version: 4.14.0 |
|
|
4904043 |
Description: An intermittent firmware assert error ( |
|
Keywords: PLDM |
|
|
Detected in version: 4.14.0 |
BMC Bug Fixes
|
Ref # |
Issue Details |
|---|---|
|
4944048 |
Description: When upgrading or downgrading between the 25.10-LTSU2 and 26.04 releases, repeated BMC reboots may, in rare cases, cause the |
|
Workaround: Perform a factory reset on the BMC. |
|
|
Keyword: BMC reboot; core dump; factory reset |
|
|
Reported in version: 25.10-LTSU2 |
|
|
4917779 |
Description: Initiating an Arm |
|
Reported in version: 26.01 |
|
|
4948318 4945554 |
Description: If a secondary BMC task (such as a log dump) is started after the BMC firmware update has been initiated, but before the installer's monitoring logic has attached to it, the installer may mistakenly track the secondary task. This tracking error causes the installer to misjudge the update's completion, which can cause the subsequent BMC reboot to fail and leave the new firmware in a pending, unactivated state. |
|
Reported in version: 26.01 |
|
|
4401488 |
Description: The BMC kernel enforces |
|
Reported in version: 26.01 |
|
|
4905017 |
Description: When operating in NIC mode, a host power cycle may intermittently cause the UEFI to fail to retrieve BMC Redfish credentials. This results in a |
|
Reported in version: 26.01 |
|
|
4969243 |
Description: When the |
|
Reported in version: 26.01 |
|
|
4995032 |
Description: Redfish queries via |
|
Reported in version: 26.01 |
|
|
4867786 |
Description: During BFB installation, the Golden ARM image update may intermittently hang and fail via Redfish, logging a |
|
Reported in version: 26.01 |
|
|
4914053 |
Description: The BFB installer defaults to DHCP for the VLAN4040 interface. If no DHCP server is present, the request silently fails after a 300-second timeout, bypassing the static IP fallback and skipping all BMC-related firmware updates. |
|
Reported in version: 26.01 |
|
|
4924426 |
Description: Following a DPU reset, the |
|
Reported in version: 26.01 |
|
|
4987307 |
Description: During BFB installations via Redfish, the task state may change to "Exception" before the specific error message is appended to the HTTP response payload. This results in incomplete error logs on the initial poll following a failure. |
|
Reported in version: 26.01 |
|
|
4980118 |
Description: The |
|
Reported in version: 26.01 |
|
|
4799519 |
Description: Accessing the |
|
Reported in version: 26.01 |
|
|
4932328 |
Description: Excessive Common Platform Error Record (CPER) files in |
|
Reported in version: 26.01 |
|
|
4957197 |
Description: When external monitoring tools or scripts repeatedly query the BMC's Redfish interface using Basic authentication over extended periods, internal session resources fail to release properly. This memory leak eventually causes the BMC to lose network connectivity, even while the DPU management interface remains online. |
|
Reported in version: 26.01 |
|
|
4966472 |
Description: The BMC generates a warning log for PLDM_Sensor_1_100 when the NIC temperature reaches the official 91°C upper non-critical threshold. This is an expected hardware alert for elevated temperatures, not a software defect. |
|
Reported in version: 26.01 |
Last updated: