Known Issues

127 VF per PF (254 functions)

127

• 127 VF per PF (254 functions)

• 512 PF+VF+SF per PF (1024 functions)

• 127 VF (127 functions)

• 512 PF+VF+SF per PF (512 functions)

4970263 / 4989004

Description: A high-temperature assert may be reported only the first time the chip reaches the thermal threshold.

Workaround: N/A

Keywords: Temperature

Detected in version:

40.49.1014

4893565 / 4532684

Description: Occasional high spikes in operation latency may be observed.

Workaround: N/A

Keywords: Latency

Detected in version:

40.48.1000

5036020 / 5043847 / 5233632

Description: For XDR, DC RDMA Read traffic with fewer than 5 QPs may not reach full performance.

Workaround: N/A

Keywords: DC RDMA Read traffic

Detected in version:

40.49.1014

5234743 / 5145460

Description: Query Port Telemetry v2 (CMD 0x14) reports tag 0x20 (rx_los_mask), which should not be populated.

Workaround: N/A

Keywords: Query Port Telemetry v2

Detected in version:

40.50.1002

5234750

Description: The Plug Voltage sensor does not read the value from the second module.

Workaround: N/A

Keywords: Plug Voltage sensor

Detected in version:

40.50.1002

5230758 / 4553130 / 5231785

Description: For LPO cables, link-up may fail after the port on the peer device is toggled.

Workaround: Toggle the port on the SuperNIC side.

Keywords: LPO cables

Detected in version:

40.50.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.

Workaround: N/A

Keywords: GB300, QoS, GPU, CPU

Detected in version:

40.50.1002

5085252 / 5090080

Description: Following a hot reset, a false Surprise Link Down (SLD) alarm may be reported intermittently on the Downstream Port (DSP) through the Advanced Error Reporting (AER) register. This is a false alarm and has no functional impact on link stability or data integrity.

Workaround: N/A

Keywords: Surprise Link Down (SLD)

Detected in version:

40.49.1014

5133249

Description: A recent update to the default unmapped local port value causes the LED flow to query an invalid port, resulting in a failure of the LED logic.

Workaround: N/A

Keywords: LED indication

Detected in version:

40.49.1014

4901395 / 4919262

Description: When PXE is enabled for both Legacy (FlexBoot) and UEFI drivers, the UEFI driver supports only a single TFTP session after the DHCP handshake.

Workaround: For scenarios that require multiple concurrent TFTP sessions, disable PXE filters via the HCA HII menu.

Keywords: PXE, Filter enabled, UEFI

Detected in version: 40.49.1014

5072222

Description: In DirectNIC and SocketDirect topologies, PCIe TLP Analyzer visibility is limited to the host’s management domain. Traffic passing through an unmanaged host link, such as a DirectNIC connection to a GPU, is not visible to the local tracer.

Workaround: N/A

Keywords: PCIe TLP Analyzer

Detected in version: 40.49.1014

4893639

Description: Direct Memory Access (DMA) protection is not supported in the ipxe.efi driver.

Workaround: N/A

Keywords: DMA

Detected in version: 40.48.1000

4835832

Description: In rare cases, certain module types may experience link-up failures.

Workaround: Configure the requested speed using the following commands:

mlxconfig -d <device> set PHY_RATE_MASK_OVERRIDE_P<port>=1
mlxfwreset -d <device> r -y --no_mst
mlxconfig -d <device> set PHY_RATE_MASK_P<port>=<PTYS.speed_mask> (speed mask is defined in PRM)
mlxfwreset -d <device> r -y --no_mst

Keywords: Cables

Detected in version: 40.48.1000

4594515 / 4622127 / NVbug 5460310

Description: Running perftest with ib_send_bw using a message size of 4KB and 1000 QPs does not reach the expected full line rate.

Workaround: N/A

Keywords: perftest

Detected in version: 40.48.1000

4604969

Description: Probe packets might be dropped at the transmission stage when multiple congestion control flows are active.

Workaround: N/A

Keywords: PCC, RTT, probe

Detected in version: 40.47.1026

4496642

Description: The timestamps (t2, t4) of the received RTT probes are taken from the free-running clock, even when ROCE_CC_RTT_TIMESTAMP_FORMAT is set to 0x02.
The format of all RTT probe timestamps can be found in HCA_CAP.rtt_timestamp_format.

Workaround: N/A

Keywords: RTT RTC timestamp

Detected in version: 40.47.1026

4705241

Description: When Quantum-2 is part of an XDR topology, serving as a leaf switch connected to NDR-based hosts, a bandwidth degradation of approximately 3–7 Gb/s is expected.

Workaround: N/A

Keywords: XDR, NDR, Quantum-2

Detected in version: 40.47.1026

4705948

Description: When using DC as the InfiniBand transport type to perform an ib_read RDMA operation between ConnectX-7 (NDR) and ConnectX-8, a bandwidth degradation of approximately 25% may be observed when using a low number of QPs (1–16). The performance degradation diminishes as the number of QPs increases.

Workaround: N/A

Keywords: DC, ib_read RDMA, NDR, performance

Detected in version: 40.47.1026

4685736

Description: Creating a DPA process that allocates a 128 MB data segment and loads a dynamic library may fail with syndrome 0xdc30ac.

Workaround: Limit the DPA application’s data segment size to 64 MB.

Keywords: DPA

Detected in version: 40.47.1026

4618452

Description: When only a partial number of fiber lanes are connected to a module (i.e., not all supported lanes are populated), the module re-insertion process may experience an extended link-up time of approximately one minute. This occurs because the module requires additional time to detect that only a subset of the lanes is connected.

Workaround: N/A

Keywords: Cables

Detected in version: 40.47.1026

4270913

Description: For DC InfiniBand transport, using SRQs requires distributing QPs across four SRQs. Each QP must be assigned to its own SRQ when there are up to four QPs.

Workaround: If more than four QPs are used, they must be evenly distributed across the four available SRQs.

Keywords: DC InfiniBand transport, SRQ, QPs

Detected in version: 40.47.1026

4665802

Description: Due to a re-burst scheduler limitation, the expected “speed of light” value for single QP RDMA Write on ConnectX-8 devices cannot be calculated. Currently, verification is limited to identifying performance degradations relative to previous firmware versions.

Workaround: N/A

Keywords: Single QP RDMA Write

Detected in version: 40.47.1026

4412310

Description: Split operation (port splitting) on the second port is not supported on the ConnectX-8 SuperNIC model 900-9X81Q-00CN-ST0.

Workaround: N/A

Keywords: Port splitting

Detected in version: 40.45.1020

4394475

Description: The existing congestion control configuration applies globally, rather than on a per-priority basis.

Workaround: Ensure that the configuration values for all priorities are aligned in either mlxconfig ROCE_CC_PRIO_MASK_P$port or sysfs ecn/roce_rp/enable/$port.

Keywords: Congestion control, ROCE_CC_PRIO

Detected in version: 40.45.1020

4240828

Description: Simultaneous access to the same PDDR module info page is not supported.

Workaround: N/A

Keywords: PDDR module

Detected in version: 40.45.1020

4230775

Description: Due to a known issue, telemetry rate must be set to lower than 3 minutes.

Workaround: N/A

Keywords: Telemetry rate

Detected in version: 40.44.0212

4038325 / 
4031430 / 
4038341 / 
4046105

Description: Connecting to systems with NRZ speeds of 1,10, 25, 40, 50, or 100Gb/s is not supported.

Workaround: N/A

Keywords: NRZ, Connectivity

Detected in version: 40.44.0208

4201405

Description: Upgrading to firmware 40.44.0xxx from any previous Engineering Sample version requires power cycling the driver and not just resetting it (using mlxfwreset).  

Workaround: N/A

Keywords: Upgrade, power cycle, reset

Detected in version: 40.44.0208