|
Internal Ref. |
Issue |
|---|---|
|
5224865 |
Description: Resolved an issue where, when raising a link with a copper cable, mlxlink incorrectly reported Auto-Negotiation as ON although the link was actually raised with Auto-Negotiation disabled. mlxlink now reports the correct value, FORCE. |
|
Keywords: mlxlink, Auto-negotiation, copper, link |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5344028 |
Description: Resolved an issue where the link failed to come up with a specific LPO (linear pluggable optics) module. Dedicated SI parameters were added for this module. |
|
Keywords: SI parameters, LPO module |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5238449 / NVbug 6642654 |
Description: Resolved an issue where GPUDirect RDMA through ConnectX-8 failed after a warm reboot. |
|
Keywords: GPUDirect RDMA, warm reboot, ConnectX-8 |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5179871 / NVbug 6533702 |
Description: Resolved an issue where NSM GetPortTelemetryCounters incorrectly advertised unsupported counters on Ethernet ports. The supported-counter mask is now corrected, preventing these zero samples from overwriting valid Ethernet telemetry. |
|
Keywords: NSM, GetPortTelemetryCounters, Ethernet, telemetry, supported-counter mask |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5350445 |
Description: Resolved an issue where an active congestion control flow context might be outdated unexpectedly when a large number of congestion control flows are active. |
|
Keywords: PCC |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5227817 / NVbug 6618275 |
Description: Running applications concurrently on both GPU and CPU with different numbers of QPs, for example 1K QPs on the GPU and 1 QP on the CPU, is not supported when using hardware QoS bandwidth sharing. |
|
Keywords: GB300, QoS, GPU, CPU |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5230758 / 4553130 / 5231785 |
Description: For LPO cables, link-up may fail after the port on the peer device is toggled. |
|
Keywords: LPO cables |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5234750 |
Description: The Plug Voltage sensor does not read the value from the second module. |
|
Keywords: Plug Voltage sensor |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5036020 / 5043847 / 5233632 |
Description: For XDR, DC RDMA Read traffic with fewer than 5 QPs may not reach full performance. |
|
Keywords: DC RDMA Read traffic |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in release: 40.51.1002 |
|
|
5313442 / 5194173 / NVbug 6742187 |
Description: Resolved an issue where registering or deregistering very large memory regions (MRs) could intermittently cause the firmware to report "irisc not responding". Commands such as DESTROY_MKEY then timed out, and the device required an AC power cycle to recover. |
|
Keywords: MR, MKey, iRISC, Watchdog |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in release: 40.51.1002 |
|
|
5325274 / 5344239 / NVbug 6874322 |
Description: Resolved an issue where NSM Get Port Address could return an all-zero permanent MAC address and trigger firmware assertion 0x83A6 on mirrored PCIe configurations. Firmware now selects an eligible host that owns the requested port while preserving multihost isolation. |
|
Keywords: NSM, Get Port Address, MAC address, permanent MAC, 0x83A6, mirrored PCIe, multihost, MCTP |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5329814 / 5344856 / NVbug 6887282 |
Description: Resolved an issue where NSM Type 3 Get Inventory Information manufacturing-date queries (command 0x0C, property 0x08) failed. |
|
Keywords: NSM, VPD, serial number, manufacturing date, Get Inventory Information, ISO week |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5295545 / 4477907 / NVbug 6681169 |
Description: Resolved an issue where PCIe error injection via TLV token did not work when NSM was enabled. The fix decouples TLV-based PCIe error injection from NSM, removing the dependency between the two. |
|
Keywords: PCIe error injection, TLV token, NSM, VR-NVL72 |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5160715 / 5156417 |
Description: Resolved an issue where the Physical Monitor (BMX) module on ConnectX-8 did not correctly recover when a PSC entered turtle state. A forced POWER_CYCLE is now triggered after turtle recalibration to restore correct operation. |
|
Keywords: PSC, turtle, POWER_CYCLE, recalibration, Physical Monitor, BMX |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5323929 / NVBug 6536162 |
Description: Resolved a PLDM firmware update failure caused by an insufficient message retry timeout. The timeout has been increased from 1 to 1.5 seconds. |
|
Keywords: PLDM, firmware update, retry timeout |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5313870 |
Description: Resolved a firmware assert (ext_synd 0x00b4) on ConnectX-8 socket direct setups caused by the discovery_notify_en change. |
|
Keywords: MCTP, discovery_notify_en, ext_synd 0x00b4, socket direct, assert, regression |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5243447 |
Description: Resolved an issue where PDDR module info (mlxlink) remained N/A after replacing a transceiver with an incorrect identifier with a valid module. |
|
Keywords: PDDR, mlxlink, module info, optic identifier |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5285582 |
Description: Resolved a link-down issue on PF0/PF1 after a firmware upgrade where 25G/50G speed support was removed, causing ports to become stuck at "Signal Detect" (opcode 1048). |
|
Keywords: Link down, 25G, 50G, Signal Detect, firmware upgrade |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5262916 |
Description: Resolved a firmware issue where deregistering a very large memory region (e.g., 1.7 TB) could exceed the firmware internal watchdog window, causing a false "not responding" error and an OS hang with the message "All CMD slots are stalled, aborting command." |
|
Keywords: Memory region, deregistration, MR, dead iRISC |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5257510 |
Description: Resolved an I2C driver issue where read transactions to MCTP addresses caused non-compliant SCL clock stretching. The timeout is now aligned to the SMBus specification (25 ms). |
|
Keywords: I2C driver, MCTP |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5254803 |
Description: Resolved a firmware assert (ext_synd 0x8d83) triggered when performing a resource dump on NAM_FIFO segment (0x5e) with an index value of 0x21 or greater. |
|
Keywords: NAM_FIFO, firmware assert, ext_synd, resource dump |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5235696 |
Description: Resolved incorrect handling of MACsec confidentiality-offset values during conversion between the software interface and the hardware SADB, which could result in improper packet encryption. |
|
Keywords: MACsec, confidentiality offset, SADB, packet encryption |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5234857 |
Description: Resolved a link-up failure that could occur when connecting a ConnectX-8 NIC equipped with an Innolight module to a TH5 switch in force mode (opcode 36). |
|
Keywords: Link-up failure, Innolight module, TH5 switch in force mode |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5234750 |
Description: The Plug Voltage sensor does not read the value from the second module. |
|
Keywords: Plug Voltage sensor |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5234743 / 5145460 |
Description: Query Port Telemetry v2 (CMD 0x14) reports tag 0x20 (rx_los_mask), which should not be populated. |
|
Keywords: Query Port Telemetry v2 |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5224496 / 4881103 |
Description: Resolved an issue where enabling SR-IOV VFs caused mlx5 driver initialization to fail with error -110 (FW init timeout), because the VFs lacked a functional PCIe BAR. |
|
Keywords: SR-IOV, VF, mlx5, PCIe BAR, FW init timeout |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5219173 / 4628569 |
Description: Resolved a limitation where NSM Get Ethernet Port Telemetry Counters (type 1, cmd 0x0f) did not support multiplane NIC configurations. The restriction is removed and the command is now supported for ConnectX-8 and later NICs in multiplane setups. |
|
Keywords: NSM, Ethernet Port Telemetry, multiplane, cmd 0x0f |
|
|
Detected in version: 40.47.2682 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5198300 / 4490216 |
Description: Resolved a firmware issue where bi-directional traffic could become unbalanced when using DOCA PCC NP, caused by elevated RTT NP TX delay resulting in reduced bandwidth on one side. |
|
Keywords: DOCA PCC, RTT NP TX delay, bi-directional traffic, bandwidth |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5197872 |
Description: Resolved a spurious WARN signal assertion on ConnectX-8 MGX ARC systems immediately after reset. The OVER_TEMP_WARNING GPIO was incorrectly initialized to 1, causing a false thermal warning for approximately 1 second until the first temperature sample was taken. |
|
Keywords: WARN, GPIO, OVER_TEMP_WARNING, MGX ARC, thermal |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5157189 / 4866555 |
Description: Resolved an issue where, when massive flows occurred in parallel with PCC, INIT2RTR could report a false alarm with syndrome 0x7 "dead IRISC." |
|
Keywords: PCC, INIT2RTR, dead irisc |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5130021 |
Description: Resolved a ZTR RTT CC issue where the CNP_VLD_RTT parameter was ignored on the first congestion event, causing the algorithm to misinterpret a large RTT value as congestion and reduce bandwidth. |
|
Keywords: ZTR RTT CC, CNP_VLD_RTT, congestion control, bandwidth |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5093878 / 5138237 |
Description: Resolved a credit leak and resulting TX timeouts that occurred when a DPA application used cross-VHCA, cross-host doorbell messaging via DPA Outbox. |
|
Keywords: DPA, cross-VHCA, TX timeout, credit leak, DPA Outbox |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5089628 / 5128695 / 4964975 / 5073172 / 5298820 / 5110752 / 5176245 |
Description: Resolved an issue where, in a mixed multiplane/non-multiplane ETH port configuration, LAG creation was blocked on multiplane PFs, preventing multiplane traffic and traffic separation between port types. |
|
Keywords: LAG, multiplane, ETH port, PF |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5081175 |
Description: Resolved a ZTR RTT CC issue in topology-aware mode where fabric round-trip times exceeding 200 µs caused false congestion signals and sustained below-line-rate throughput. |
|
Keywords: ZTR RTT CC, topology-aware, fabric RTT, congestion |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5036020 / 5043847 / 5233632 |
Description: For XDR, DC RDMA Read traffic with fewer than 5 QPs may not reach full performance. |
|
Keywords: DC RDMA Read traffic |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5035649 |
Description: When Bus Master Enable (BME) is cleared for a virtio-blk device that uses transaction layer packet (TLP) emulation, host I/O can continue instead of stopping. |
|
Keywords: Function-Level Reset; mkey Invalidation; fio |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.51.1002 |
|
|
5019624 |
Description: Resolved an issue where a PCIe SBR did not reset the MCTP discovery state, causing the device to miss EndpointDiscovery requests and the firmware version to be absent from the Redfish API. |
|
Keywords: PCIe SBR, MCTP, EndpointDiscovery, Redfish |
|
|
Detected in version: 40.50.1002 |
|
|
Fixed in Release: 40.51.1002 |
|
|
4996000 / 4458007 |
Description: Resolved a PLDM Type 6 (RDE) communication failure on ConnectX-8 where the BMC could not allocate an EID for the auxiliary cable in shared IO mode. Resolved by enabling multi-BMC support in socket-direct INIs. |
|
Keywords: PLDM, RDE, BMC, EID, socket-direct |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.51.1002 |
Last updated: