This section includes history of bug fixes of 3 major releases back. For older releases history, please refer to the relevant firmware versions Release Notes.
|
Internal Ref. |
Issue |
|---|---|
|
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. |
|
Keywords: LED indication |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4835832 |
Description: In rare cases, certain module types may experience link-up failures. |
|
Keywords: Cables |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4893565 / 4532684 |
Description: Occasional high spikes in operation latency may be observed. |
|
Keywords: Latency |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
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. |
|
Keywords: PCIe TLP Analyzer |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4038325 /
|
Description: Connecting to systems with NRZ speeds of 1,10, 25, 40, 50, or 100Gb/s is not supported. |
|
Keywords: NRZ, Connectivity |
|
|
Detected in version: 40.44.0208 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5085054 / 5103944 |
Description: Resolved an issue where resetting the ID list register released only the domain counters. |
|
Keywords: Counters |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4918704 / 5246587 |
Description: Resolved an issue where the NoSnoop enable bit was incorrectly exposed as 0 in the PCIe configuration space. |
|
Keywords: NoSnoop enable |
|
|
Detected in version: 40.47.2682 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5063565 |
Description: Resolved an issue where PCIe TX error counters could report negative values on Gen6 links. |
|
Keywords: PCIe TX |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5083504 / NVbug 6078783 |
Description: Resolved an issue where firmware internal errors could occur due to FW_INTERNAL_USAGE partition data corruption. The firmware now recovers by erasing the corrupted partition. |
|
Keywords: Firmware internal errors |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4032807 |
Description: Resolved an issue where ConnectX-8 x16 Gen6 links could drop with malformed TLP and completion-timeout errors during sustained high-bandwidth bidirectional PCIe traffic. |
|
Keywords: TLP, link drop, PCIe |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5000069 |
Description: Fixed an issue where repeatedly creating and destroying virtual machines with ConnectX-8 virtual functions could cause a hypervisor panic. |
|
Keywords: VM, VF |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5159911 / NVbug 6427609 |
Description: Fixed an issue where a full NIC flap could occur due to a failed I2C expander read transaction. A retry mechanism was added for failed expander read transactions. |
|
Keywords: NIC flap |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4988895 |
Description: Added 25G support in the INI configuration. |
|
Keywords: Cable speed |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4994872 |
Description: Fixed link-up issues by correcting marker lane and virtual lane calculations across split configurations, centralizing Ethernet interleave detection logic, passing FEC mode into PLU Ethernet configuration, and improving debug logs for marker mapping. |
|
Keywords: Link-up, FEC |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5028793 |
Description: Resolved issues in the TLP-SACK handling flow, including PSN calculation, SACK packet handling, and capability enablement for ConnectX-8 and later devices. |
|
Keywords: TLP-SACK handling flow |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5232646 |
Description: Resolved an issue where PLDM update from the auxiliary card side could fail on devices in multi-host configurations. |
|
Keywords: PLDM |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5073671 |
Description: Resolved an issue where a firmware assert could be raised due to a GPIO expander write timeout. |
|
Keywords: GPIO |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5130705 / 5131942 / NVbug 6376684 |
Description: Resolved an issue that could cause CoRIM FLM test failures during SBIOS and SMA validation on MGX Vera platform/system configurations. |
|
Keywords: CoRIM |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5139055 / 5072582 / NVbug 6427860 |
Description: Resolved an issue where firmware did not validate all port health threshold slots. Firmware now rejects unsupported threshold values instead of silently accepting them. |
|
Keywords: Firmware threshold |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5173627 |
Description: Resolved an issue where critical messages could be dropped due to queue overflow. |
|
Keywords: Queue overflow |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5041711 |
Description: Resolved an issue where, after toggling a port, the peer could incorrectly remain in the PHY-up state. |
|
Keywords: Port toggle |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4971613 / 4852107 |
Description: Resolved an issue where, after setting FORCE on a specific speed and rebooting, mlxlink could incorrectly show all default speeds as enabled instead of showing only the forced speed. |
|
Keywords: mlxlink |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4936278 |
Description: Added support for 10G and 25G using limited LLU request messages via the disable_b2b flag, with clause49_en enabled and the numerator/denominator configured to a 1:1 ratio. |
|
Keywords: LLU, 10G/25G speed |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5042147 / 5041441 |
Description: Updated the Best Known Values (BKV) to version 1.1, improving the overall stability and robustness of the link-training reset flow during boot-up. |
|
Keywords: BKV |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5012336 / NVbug 6140150 |
Description: Resolved a potential issue that could result in lower-than-expected bidirectional RDMA bandwidth in PCIe switch topologies. |
|
Keywords: RDMA bandwidth |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4851684 |
Description: Resolved an issue where RDMA workloads using null memory regions with MKEY_BY_NAME enabled could experience up to a 30% throughput drop. The internal null/dump-fill key was incorrectly routed through the slower signature datapath. Workloads not using MKEY_BY_NAME or null memory regions were unaffected. |
|
Keywords: RDMA |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4851684 |
Description: Resolved an issue where, under high-stress LRO traffic, an internal FIFO could enter a hardware deadlock state, preventing the NIC from receiving additional traffic.
|
|
Keywords: LRO traffic |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5174504 / 5140787 |
Description: Resolved an issue where intensive parallel QP INIT2RTR / DESTROY operations could incur high operation latency and reduce connection establishment rates when PCC was enabled. |
|
Keywords: PCC, INIT2RTR, DOCA PCC |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5044357 |
Description: Resolved an issue where a RISC could become stuck in a fw_memcpy loop called by the multi-ASIC I2C mailbox function. This could occur if firmware read invalid parameters from I2C HW fields. Parameter validation was added before calling fw_memcpy, along with an error indication when the parameters are invalid. |
|
Keywords: RISC |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5166648 |
Description: Resolved an issue involving an uninitialized stack read and an inverted EtherType check in the RX parser. |
|
Keywords: RX parser |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4937640 |
Description: Resolved an issue where a PPCC mlxreg read operation could succeed when executed on a PF that is not the port owner, which could have security implications. |
|
Keywords: PCC, PPCC |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5161601 |
Description: Resolved an issue where multiplane emulation mode conditioning used the raw num_pfs value before invalid values were reduced during FMT initialization.
|
|
Keywords: PF, FMT initialization |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4670019 |
Description: Resolved an issue where GPIO expander write operations could take more than 200 ms. |
|
Keywords: GPIO expander |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5154717 / 5152076 / 5154806 / NVbug 6422398 |
Description: Resolved an issue where, when a transceiver module held its I2C management bus line stuck (SDA or SCL), the firmware detected the stuck bus and reset the module. After the reset, the module remained in low-power mode and its datapath was not re-established, preventing the link from coming up. On a shared module, all associated ports could drop simultaneously. |
|
Keywords: Cables |
|
|
Detected in version: 40.45.3034 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4923806 / 4867111 / 4927875 |
Description: Resolved an issue that could cause RoCE communication failures between specific NIC pairs after repeated queue pair (QP) create/destroy cycles. In the affected cases, traffic could enter a bad state and fail with transport retry counter exceeded errors. This fix prevents the NIC from entering that condition. |
|
Keywords: RDMA; connection failure |
|
|
Detected in version: 40.46.3036 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5155445 |
Description: Resolved an issue with SyncE frequency adjustment overflow when using a third-party secondary vendor. |
|
Keywords: SyncE frequency |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5125089 |
Description: Resolved an issue where an incorrect Flex Parser configuration could trigger an assert. A syndrome was added to notify HWS when an invalid configuration is provided. |
|
Keywords: Flex Parser configuration |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5093695 |
Description: Resolved an issue where using mlxconfig to configure all modules with the 0xff module split value could reset the modules to the default configuration. |
|
Keywords: mlxconfig |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5090639 |
Description: Resolved an issue in single-domain mode where an FLR on a GVMI did not clear the per-domain usage bits in |
|
Keywords: PCIe Link Latency Arch counters |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5089348 |
Description: Resolved an issue where the MFT database was not updated to configure profile 12 for the Flex Parser. |
|
Keywords: MFT, Flex Parser |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4950259 |
Description: Unblocked 4-port, single‑LAG configurations by updating the INI setting nv_config.global.power_cap.max_num_port=4, and fixed the Queue Affinity error seen in LAG mode. |
|
Keywords: LAG, Queue Affinity |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5077326 / 4902171 |
Description: Resolved an issue where a slow module response to the NCSI GetModuleSerialData command could incorrectly trigger a dead IRISC watchdog assert. The firmware now handles this waiting state correctly, so slow module responses no longer cause a false watchdog hang indication. |
|
Keywords: NCSI |
|
|
Detected in version: 40.44.1036 |
|
|
Fixed in Release: 40.50.1002 |
|
|
5025688 |
Description: Resolved an incorrect INI settings on one downstream link of CX8_Rithmax_CX8aas_BP_4P. All DSLs now operate in Gen6. |
|
Keywords: INI settings |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4412310 |
Description: Split operation (port splitting) on the second port is not supported on the ConnectX-8 SuperNIC model 900-9X81Q-00CN-ST0. |
|
Keywords: Port splitting |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.50.1002 |
|
|
4947006 / 4980956 / 4982511 |
Description: Resolved two rare race conditions in the PCC steering extension when the feature is enabled through path migration, empty RTT, or a custom header.
|
|
Keywords: PCC steering extension |
|
|
Detected in version: 40.49.1014 |
|
|
Fixed in Release: 40.50.1002 |
|
Internal Ref. |
Issue |
|---|---|
|
4903859 / 4888221 / 4917766 / 4924468 / 4924833 |
Description: Resolved an issue with corrupted flash entries:
|
|
Keywords: Flash entries |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4869576 |
Description: Fixed the rate limiter for XDR clusters. |
|
Keywords: Rate limiter |
|
|
Detected in version: 40.44.1036 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4976460 |
Description: Fixed an issue that caused low performance when the link was not saturated in many-to-one traffic scenarios by optimizing the plane load balancer. |
|
Keywords: Performance |
|
|
Detected in version: 40.46.3048 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4812446 / 4917369 |
Description: Fixed an issue where CREATE_PARSE_GRAPH_NODE incorrectly applied validation intended for WA mode, in which Validation is now mode-specific: normal-mode rules are applied on ConnectX-8 and newer adapters, while WA-mode rules are applied on older adapters. |
|
Keywords: Parse graph node |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4812446 |
Description: Fixed an issue where firmware did not enforce the adapter limit for the number of flow match samples per parse graph node across the device. As a result, creation could succeed even when the total exceeded the hardware-supported limit. Firmware now enforces this limit before allocating samples. Creating a parse graph node that would exceed the maximum number of hardware flow match samples now fails with a “no resources” error. |
|
Keywords: Parse graph node |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4864823 / 4858750 |
Description: Fixed an issue where, when Flex Parser overwrite native arc was enabled, destroying or closing a parse graph node on a native protocol arc did not restore the native protocol parser. As a result, the native parser remained unavailable on the device until a reset or another recovery action was performed. Native protocol parsing is now restored as expected when the parse graph node is closed or destroyed. Native parsers are disabled only while the Flex Parser graph owns the arc. |
|
Keywords: Flex Parser |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
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: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4928056 / 4999011 / 4999400 |
Description: Fixed a corner-case race condition triggered by DSP resets, causing the link to hang. |
|
Keywords: DSP reset |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.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: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4835832 |
Description: In rare cases, certain module types may experience link-up failures. |
|
Keywords: Cables |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4859294 |
Description: Fixed an issue where, after toggling all ports, one port could become stuck in the Receiver Detect state. |
|
Keywords: Port toggling |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.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: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4983638 / NVBug 6090735 |
Description: Fixed an issue where NSM did not function reliably in multihost configurations when a DMA physical function (PF) was present. |
|
Keywords: NSM, multihost configurations, DMA physical function (PF) |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.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: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4860860 |
Description: Fixed an issue where queue pairs (QPs) created during a PCC process transition could miss congestion-control (CC) information, preventing them from being fully managed. |
|
Keywords: DOCA, PCC, QP, Congestion Control |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4774410 / 4773595 |
Description: Fixed an issue where the LAG layer steering table had only one strict-SQ entry, causing strict no-port-select traffic to be routed to a single default port. With LOAD_BALANCE_MODE_P1=3, this could lead to link flapping because LACP packets were transmitted only from that default port. The fix expands the LAG layer steering table and adds additional strict-port entries to distribute strict traffic correctly. |
|
Keywords: Link Flapping |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.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: 40.48.1000 |
|
|
Fixed in Release: 40.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: 40.47.1026 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4859742 / 4847702 |
Description: Fixed an issue during hitless upgrade where, after the SACK generation/handler fence, firmware could mark the old port configuration ID as invalid. If SACK causes were still active, a race could cause SACK ISRs to stop unexpectedly. The fix is to always return BUSY while handover is active. |
|
Keywords: Hitless upgrade |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4873533 / 4947034 |
Description: Fixed an issue where, when using multiplane ZTRCC congestion control with multiple flows, the RTT timeout counter in the PPCC register could increase even when the network was not congested. |
|
Keywords: Congestion control, multiplane, SPCX CC, RTT, PPCC |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4876790 / 4822829 |
Description: Fixed an issue where a firmware race between packet receive and QP cleanup could move a QP to error when reopening the same QP and sending the same MSN. This could occur when interrupting traffic (e.g., Ctrl+C) and running many iterations until the same QP/MSN combination is reused. |
|
Keywords: Firmware race |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4905774 |
Description: Fixed an issue where the FMT Static PF verifier did not account for the Tools PF when verifying the DMA PF. |
|
Keywords: FMT Static PF verifier |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.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: 40.45.1020 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4843342 / 4970550 |
Description: Fixed an issue where one-to-one RoCE traffic using a single QP might not achieve line rate on some platforms when using the default ROCE_CC_COMPATIBILITY_MODE setting in mlxconfig. |
|
Keywords: Congestion control, PCC, ROCE_CC_COMPATIBILITY_MODE |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4892822 / 4638811 |
Description: Fixed an issue where, in some configurations with ConnectX-8 connected to an MP3 switch, the link might fail to come up on the switch side after toggling ports. In these cases, ConnectX-8 reported opcode 14, indicating detected remote faults and that the partner was not bringing the link up. |
|
Keywords: Link down, opcode 14, AC/DC cycles |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4783261 / 4658799 |
Description: Fixed an issue where ACS errors could occur due to a race condition when performing LDE/SBR while MCTP traffic to the device was active. |
|
Keywords: ACS, MCTP |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4881141 / 4882127 / 4882128 |
Description: Fixed a potential routing error when IOVAs assigned to the NIC overlap with the PCIe address space. In certain configurations, an IOVA could fall into an “unclaimed address” range, within a PCIe switch’s Upstream Port (USP) window but outside any Downstream Port (DSP) aperture.
|
|
Keywords: ACS Unclaimed Request Redirect, IOVA |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.49.1014 |
|
|
4952219 / NVBug 6026050 |
Description: Fixed an issue where partially enabling ACS enhanced capability could cause unexpected driver and system behavior. ACS enhanced capability remains disabled and will not be enabled. |
|
Keywords: ACS |
|
|
Detected in version: 40.48.1000 |
|
|
Fixed in Release: 40.49.1014 |
|
Internal Ref. |
Issue |
|---|---|
|
4823907 / NVbug 5742181 |
Description: Fixed an issue where, in certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting nan. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses). Note: On legacy firmware, additional configuration steps may still be required, as detailed below. If you cannot update the firmware immediately, you can restore device detection using one of the following options:
|
|
Keywords: ConnectX-8 PCIe, GPU, PERST# assertion |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4786813 |
Description: Fixed an issue where the DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR. |
|
Keywords: DPA kernel, FLR |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4804664 / 4806969 |
Description: Fixed an issue in the User Debugger “query caps” where it returned only the number of capabilities, not the capability bitmap. |
|
Keywords: User Debugger “query caps” |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4813862 / 4146077 |
Description: Fixed an issue where CR dumps could time out when accessing xpl_top addresses across all three pcores. |
|
Keywords: CR dump |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4833440 |
Description: Fixed an issue where the Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig. |
|
Keywords: Virtio and NVMe emulation, mlxconfig |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4756451 |
Description: Fixed an issue where the PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only. |
|
Keywords: PHY LED |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4768546 |
Description: Fixed an issue where, on multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port. |
|
Keywords: PF FLR |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4705918 |
Description: Fixed an issue where PTP could converge to an incorrect time/offset and report an inaccurate path delay. |
|
Keywords: PTP |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4657792 / NVbug 5567725 |
Description: Fixed an issue where, in Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner. |
|
Keywords: Flit Mode |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4484662 |
Description: Fixed an issue where mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT. |
|
Keywords: mlxlink |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4621747 / 4792742 / 4794290 / NVbug 5502241 |
Description: Fixed an issue where parallel accesses to the MCIA register could return incorrect data. In some hosts running |
|
Keywords: MCIA register |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4686284 / NVbug 5607036 |
Description: Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: |
|
Keywords: IB extended port telemetry counters, NSM |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4758174 / NVbug 5698200 |
Description: Fixed a rare attestation certificate signature formatting issue by removing an unnecessary leading zero byte in the “r” or “s” value. |
|
Keywords: Attestation certificate signature format |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4532684 / 4635872 / 4794865 / 4794866 / 4794867 / NVbug 5385446 |
Description: Fixed an issue by improving the ADP-RETX algorithm to avoid re-arming without performing a retransmission. |
|
Keywords: ADP-RETX algorithm |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4542516 / 4554220 |
Description: Fixed an issue where, in certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed. |
|
Keywords: RDMA READ bidirectional traffic |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4554763 / 4808657 |
Description: Fixed an issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling |
|
Keywords: Zero Touch Tuning, mlxconfig |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4608214 |
Description: Fixed an issue where probe packets might not be sent under heavy traffic. |
|
Keywords: PCC, ZTR_RTTCC, probe |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4450570 / 4780432 / 4780433 |
Description: Fixed an issue where the root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned. |
|
Keywords: MCTP-over-PCI, BDF, MCTP messages |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4809134 / 4824635 |
Description: Fixed an issue where the steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD. |
|
Keywords: Steering tables, LLDP |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
|
4797308 / NVbug 5706024 |
Description: Fixed an issue where an intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0. |
|
Keywords: intX message |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.48.1000 |
|
Internal Ref. |
Issue |
|---|---|
|
4608544 |
Description: Fixed an issue where, in rare live migration scenarios, a delayed doorbell triggered a false timeout alarm. |
|
Keywords: Live migration, doorbell, timeout alarm |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1088 |
|
|
4648642 |
Description: Fixed a rare issue in which destroying PCC NP configuration objects could result in assert 0x8175 being logged in dmesg. |
|
Keywords: Assert 0x8175, PCC NP |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.47.1088 |
|
|
4655971 |
Description: Fixed the PCIe counters to correctly report event values in nanoseconds. |
|
Keywords: DOCA Telemetry Diagnostics |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.47.1088 |
|
|
4690503 |
Description: Fixed an issue where creating a DPA process that uses 128 MB of data caused the dynamic library to fail with syndrome 0xdc30ac. The BSS section of the DPA application is now limited to 64 MB. |
|
Keywords: DPA process, BSS |
|
|
Detected in version: 40.47.1026 |
|
|
Fixed in Release: 40.47.1088 |
|
Internal Ref. |
Issue |
|---|---|
|
4884739 |
Description: Resolved an issue where link failures could occasionally occur at PAM4 speeds over optical interfaces in rare cases. |
|
Keywords: PAM4 speeds, optical interfaces |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4570205 |
Description: Fixed a firmware issue where the ZTR_RTTCC algorithm parameters AI and HAI did not support a sufficient range. |
|
Keywords: PCC, ZTR_RTTCC |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4629077 |
Description: Fixed an issue where coalescing regular SX events with SX RTT events under ZTR_RTTCC could keep improper event fields, which could impact congestion control behavior. |
|
Keywords: PCC, ZTR_RTTCC |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4683328 |
Description: Fixed an issue in the ZTR_RTTCC algorithm where probe-abortion handling could behave improperly under high-stress network conditions, ensuring proper congestion control and stable traffic performance. |
|
Keywords: PCC, ZTR_RTTCC |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4501554 |
Description: Fixed an assertion failure that could occur with the E-Switch uplink in specific configurations where the e-switch was disabled and Path Migration was active or GVMIs were using SRQ loopback in SQs. The issue occurred because the firmware attempted to perform cleanup operations when the uplink configuration lacked sufficient capacity.
|
|
Keywords: Path migration, steering |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4506854 |
Description: Added Scaling Factor "read" field. To obtain correct values in mlxlink, MFT version 4.33.0 or later is required. |
|
Keywords: Scaling Factor, mlxlink, MFT |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4468319 |
Description: Fixed an issue where the ConnectX-8 downstream port failed to send a NACK when rejecting an L1 entry request from the upstream port. |
|
Keywords: NACK, downstream port |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4550782 |
Description: Fixed an issue on GB200 systems with two symmetrical ConnectX-8 SuperNICs, which caused DPN numbering differences on the HCA upstream port. Legacy drivers accessed with dpn=0,0,0, which could result in attempts to access the wrong DPN node in socket-direct systems.
|
|
Keywords: DPN numbering |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4571079 |
Description: Fixed an issue where invoking the resourcedump tool with segment type DPA_PROCESS_LST returned invalid data when the parameter n1 == 1 and no processes existed on the current vhca_id.
|
|
Keywords: DPA PROCESS, RESOURCE DUMP |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4529293 |
Description: Fixed an issue where, during failover or restart, the SM sending a PortInfo MAD to the HCA firmware triggered reinitialization of port buffers, momentarily halting ingress traffic and causing packet drops.
|
|
Keywords: OpenSM |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4641215 |
Description: Fixed a rare issue where MFRL operations could fail due to a timeout. |
|
Keywords: MFRL |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4683346 |
Description: Fixed an issue where, under the ZTR_RTTCC algorithm, a flow that reached its minimum rate due to heavy congestion would not recover its rate once the congestion cleared. |
|
Keywords: PCC, ZTR_RTTCC |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4575692 |
Description: Fixed an issue where a missing interrupt from the module IO (Expander) could prevent the module from being raised. |
|
Keywords: Module IO (Expander) |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4620765 |
Description: Fixed an issue where reading debug registers could cause link BER (Bit Error Rate) degradation over time. |
|
Keywords: BER |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4658434 |
Description: Fixed an issue where ports connected via 4 or 8 lanes and configured for 200G_2x (using only 2 lanes) would fail to link when using a mix of new firmware (with “Non Tx-Squelch” support) and older firmware versions. Note: Please make sure on both sides, switch (local device) and Ssitch/NIC (peer device) you:
|
|
Keywords: Port speed |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4401684 |
Description: Fixed an issue in Arch diagnostic data counters where the pcie_link_outbound_data_bytes counter was incorrectly returning only zero values. |
|
Keywords: Arch diagnostic data counters |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4575696 |
Description: Fixed an issue where multiple long-running process registers could cause aborted access and timeouts, the internal state is now properly handled. |
|
Keywords: ibdiagnet2 |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4583940 |
Description: Fixed an issue where enabling the CCMAD custom header on one PCC probe slot caused other slots to malfunction when multiple slots were configured. Note: If using firmware versions older than the 40.47.10xx GA release, disable the CCMAD custom header when multiple probe slots are enabled. |
|
Keywords: PCC CCMAD custom header |
|
|
Detected in version: 40.46.1006 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4208960 |
Description: A packet may be parsed incorrectly, if a driver uses the |
|
Keywords: PARSE GRAPH NODE, Flex Parser |
|
|
Detected in version: 40.44.0208 |
|
|
Fixed in Release: 40.47.1026 |
|
|
4610740 |
Description: Fixed a firmware issue where a CQE error with vendor_syndrome RDE_MAL_WQE (0xd6) could cause traffic disruption on the affected QP. |
|
Keywords: RDMA, transport |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.47.1026 |
|
Internal Ref. |
Issue |
|---|---|
|
4603774 |
Description: Fixed an issue where the adapter card could drop NC-SI over MCTP commands when padding bytes were present after the NC-SI checksum. |
|
Keywords: NC-SI
|
|
|
Discovered in Version: 40.46.1006 |
|
|
Fixed in Release: 40.46.3048 |
|
Internal Ref. |
Issue |
|---|---|
|
4286902 |
Description: Fixed a race condition in DPA process termination during the exception flow, where a failed process could be missed and not reported to the user. |
|
Keywords: DPA |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4401109 |
Description: Fixed an issue where RTTs on IFA1 were not sent when IFA1 and IFA2 were configured in cumulative slots. |
|
Keywords: PCC, multi probe, IFA |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4486431 |
Description: Fixed an issue where issuing multiple parallel queries of DPA_THREAD objects with the same object ID could fail. |
|
Keywords: DPA |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4443601 |
Description: Fixed a firmware issue where PXE failed to boot when both LAG ports were up. |
|
Keywords: PXE, LAG |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4475307 |
Description: Fixed an issue where PCC DCQCN used incorrect parameter values when link speed was 400Gbps or higher. |
|
Keywords: PCC DCQCN, congestion control. |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4480427 |
Description: Fixed incorrect calculation of start address and mode for the CQE buffer in DPA CQ, which could cause CQEs to be written to the wrong address when the buffer is not 4K-aligned and spans a second page boundary. |
|
Keywords: CQ, CQE Buffer, DPA |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4402022 |
Description: Fixed an issue where Wake-on-LAN (WoL) may not function correctly on certain multihost configurations. |
|
Keywords: Wake-on-LAN (WoL) |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4445479 |
Description: Added a fixed estimated power value for Hvdd in the INI configuration. |
|
Keywords: Hvdd |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4426779 |
Description: Updated the handling of the PLDM Type-5 'Activate Firmware' command to ensure the update flow does not fail when 'self-contained activation' is requested. Although the 'Self Contained Activation Is Not Supported' completion code will still be returned, the component will now be successfully marked as pending. |
|
Keywords: PLDM |
|
|
Detected in version: 40.44.1036 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4318063 |
Description: When running the PTP4L application, the path delay displays inconsistent values after each fwreset and rerun, resulting in a non-constant PPS offset that fails to meet Class B/C requirements. |
|
Keywords: PTP
|
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4163634 |
Description: When connecting a Quantum-3 switch system (with a port split into 8 ports) to a ConnectX-8 single port SuperNIC, the link will not be established. |
|
Workaround: Configure the Quantum-3 switch system port to be split into 2 or 4 ports, or set the ConnectX-8 to operate in multiplane mode. |
|
|
Keywords: Port split, Quantum-3
Detected in version: 40.44.0212 |
|
|
Fixed in Release: 40.46.1006 |
|
|
4366117 |
Description: Configuring a small MTU leads to fragmentation of packets critical for the PXE boot process. As a result, the PXE boot filters mistakenly discard these packets, causing the PXE boot to fail. |
|
Keywords: PXE boot filters |
|
|
Detected in version: 40.45.1020 |
|
|
Fixed in Release: 40.46.1006 |
Last updated: