|
Internal Ref. |
Issue |
|---|---|
|
4980585 / NVBug 6084453 |
Description: Fixed an issue where NSM Get-Port-Network-Addresses returned an invalid format on B200/B300 HMC. It now follows the documented non-compact format. |
|
Keywords: NSM Get-Port-Network-Addresses |
|
|
Detected in version: 28.48.1000 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4971034 / 4967948 |
Description: Fixed an issue that could prevent the adapter’s PCIe link from re-establishing after the host resumed from a deep power-down state. This fix improves the reliability of suspend/resume cycles. |
|
Keywords: PCIe (Standby / L2-L3 link recovery) |
|
|
Detected in version: 28.48.1000 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4885134 / 4875169 / 4885137 / 4892844 |
Description: Fixed PCIe link training failures on GB200 by correcting the equalization sequence logic. |
|
Keywords: PCIe |
|
|
Detected in version: 28.48.1000 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4964566 / 4957757 |
Description: Fixed a DEAD IRISC assert that could occur during TLV NV_DATA flash access by suspending the watchdog while waiting for flash IPC (until timeout), preventing the assert on TLV access. |
|
Keywords: DEAD IRISC assert |
|
|
Detected in version: 28.48.1000 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4657767 / 4658776 / 4874764 / 4874765 |
Description: Fixed an issue where repeatedly writing NVCONFIG TLVs could cause excessive NV_DATA partition swaps during garbage collection. This rapid cycling could accelerate flash wear (end-of-life at 100,000 erases) and potentially render the device inoperable. Firmware now avoids unnecessary physical writes by returning OK when the requested configuration already exists in flash, and increases the maximum supported NV_DATA partition swaps from 100,000 to 200,000. |
|
Keywords: NVCONFIG TLVs |
|
|
Detected in version: 28.48.1000 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4871267 / 4871254 |
Description: Fixed an issue where ICM_RES_HW_DMFS_ENCAP_H_FW was allocated per GVMI, preventing some RTTs from using it. |
|
Keywords: GVMI, RTT |
|
|
Detected in version: 28.48.1000 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4774394 / 4890471 / 4890472 / 4890473 |
Description: Fixed an issue where vDPA doorbell resources were not released, which could cause failures when running other functionality after a vDPA FLR. Doorbell resources are now properly unlocked. |
|
Keywords: vDPA |
|
|
Detected in version: 28.48.1000 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4789601 / 4850200 / NVBug 5736447 |
Description: Fixed an issue where RDMA traffic could stall in large-scale deployments for certain source IP and UDP source-port combinations when DOCA PCC was active and no congestion-control algorithm was configured in algorithm slot 0. |
|
Keywords: RDMA, DOCA PCC, Congestion Control Algorithm |
|
|
Detected in version: 28.48.1000 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4796182 |
Description: Fixed an issue where the live migration target did not receive a port state change event on the resume VHCA command. The target now generates this event so software that depends on port state is notified of any changes. |
|
Keywords: Live migration |
|
|
Detected in version: 28.47.1026 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4873608 / 4921307 |
Description: Fixed an issue where a precopy image was processed during the stop-copy phase, causing prolonged downtime due to a software limitation. The handling was slow because the handler performed a linear search for data; this was improved by replacing it with a faster search approach enabled via compile-time preprocessing. |
|
Keywords: Live Migration Downtime |
|
|
Detected in version: 28.47.1026 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4683339 / 4780301 / 4895260 |
Description: Fixed an issue where QPs established before loading DOCA PCC could exhibit inconsistent algorithm-selected behavior between ports in LAG mode after DOCA PCC is loaded. |
|
Keywords: Congestion Control, DOCA PCC |
|
|
Detected in version: 28.47.1026 |
|
|
Fixed in Release: 28.49.1014 |
|
|
4867969 / 4868140 |
Description: Fixed an issue where, on ConnectX-7 Multi-ASIC systems, initializing the maximum number of VFs concurrently with large MSI-X allocations could hit ICMC resource limits; note that the 320 KB allocation remains mandatory on affected devices. |
|
Keywords: ICMC memory allocation |
|
|
Detected in version: 28.47.1026 |
|
|
Fixed in Release: 28.49.1014 |
Last updated: