Known Issues

Workaround: Remove PK key and initiate UEFI/ATF firmware upgrade again.

To remove the PK key, use the UEFI menu to navigate to Device Manager → Secure Boot Configuration → Custom Secure Boot Options → PK Options → Delete Signature.

Workaround: To perform yum update with either openEuler 22.03 SP3 and openEuler 20.03 SP1, follow these procedures depending on the use case:

1. To update DOCA only, disable ALL repos:

   Copy

   Copied!

               
   
               
   dnf --disablerepo='*' --enablerepo='kubernetes,doca' -y update
           

2. To update OS components, exclude rdma-core using one of the following options:

   • Option 1 – disable rdma-core from dnf.conf using excludepkgs=rdma-core*oe2203sp3*
   • Option 2 – disable rdma-core from openEuler.repo file under OS and everything using exlude=rdma-core*

   • Option 3 – run

     Copy

     Copied!

                 
     
                 
     yum update -x rdma-core
             

4129715

4021752

4021748

Description: In all RDMA samples, if an error occurs in any of the following functions:

• Exporting RDMA/MMAP/Sync event
• Connecting RDMA
• Writing or reading the descriptors

An error is printed but the sample resumes and might:

1. Fail later, or be in busy-wait state indefinitely; and/or
2. Result in access to an unknown address, causing an address sanitizer violation.

Workaround for 1: Either:

• Follow the error logs to verify no errors occurred in the relevant function. And if it did, stop the sample.
• Fix the issue locally.

Workaround for 2: The mentioned address sanitizer violation shall be ignored in case of an error in a relevant function.

Workaround: Wait 2 more minutes before rebooting the host. Before proceeding with host OS reboot, it is recommended to query the operational state of the BlueField Arm cores from the BlueField BMC to verify that shutdown state has been reached. Run the following command:

            

            
ipmitool -C 17 -I lanplus -H <bmc_ip> -U root -P <password> raw 0x32 0xA3
        

Expected output is "06".

Description: During BFB installation in NIC mode on BlueField-3, too much information is added into RShim log which fills it, causing the Linux installation progress log to not appear in the RShim log.

            

            
echo "DISPLAY_LEVEL 2" > /dev/rshim0/misc
cat /dev/rshim0/misc
        

Workaround: Monitor the BlueField-3 Arm's UART console to check whether BFB installation has completed or not for NIC mode.

            

            
[13:58:39] INFO: Installation finished
...
[14:01:53] INFO: Rebooting...
        

Description: When enabling the PCI_SWITCH_EMULATION_ENABLE NVconfig, the mlx devices, and potentially the RShim devices disappear. Also, looking at the kernel logs using dmesg shows the following messages:

            

            
pci 0000:29:00.0: BAR 0: no space for [mem size 0x0200 0000 64bit pref]
pci 0000:29:00.0: BAR 2: no space for [mem size 0x0080 0000 64bit pref]
...
        

3831230

3743879

Workaround: Set PCIE_HAS_VFIO=0 and PCIE_HAS_UIO=0 in /etc/rshim.conf and restart the RShim driver. Then re-run the mlxfwreset command.

If host Linux kernel lockdown is enabled, then manually unbind the RShim driver before mlxfwreset and bind it back after mlxfwreset:

            

            
echo "DROP_MODE 1" > /dev/rshim0/misc
mlxfwreset <arguments>
echo "DROP_MODE 0" > /dev/rshim0/misc
        

N/A

3666160

Description: After rebooting a BlueField-3 DPU running Rocky Linux 8.6 BFB, the kernel log shows the following error:

            

            
[    3.787135] mlxbf_gige MLNXBF17:00: Error getting PHY irq. Use polling instead
        

This message indicates that the Ethernet driver will function normally in all aspects, except that PHY polling is enabled.

3566042

3546474

Workaround: Before downgrading the firmware:

1. Run:

   Copy

   Copied!

               
   
               
   echo 0 > /sys/bus/platform/drivers/mlxbf-bootctl/large_icm
           

2. Reboot Arm.

When trying to perform a PXE installation when UEFI Secure Boot is enabled, the following error messages may be observed:

            

            
error: shim_lock protocol not found.
error: you need to load the kernel first.
        

Workaround: Use ib_core module parameter netns_mode=0. For example:

            

            
echo "options ib_core netns_mode=0" >> /etc/modprobe.d/mlnx-bf.conf
        

Description: In Rocky and CentOS 8.2 inbox-kernel BFBs, RegEx requires the following extra huge page configuration for it to function properly:

            

            
sudo hugeadm --pool-pages-min DEFAULT:2048M
sudo systemctl start mlx-regex.service
systemctl status mlx-regex.service
        

If these commands have executed successfully you should see active (running) in the last line of the output.

4404719

Description: Splitting a DPU into 4 ports conflicts with the shared_rq feature.

Workaround:

1. Disable shared RQ by setting ALLOW_SHARED_RQ="no" in /etc/mellanox/mlnx-bf.conf.

2. Restart the driver with the command: /etc/init.d/openibd restart.

Keyword: PCI information

Reported in version: 3.0.0

4273881

Description: PCI information is missing on RedHat p host.

Workaround: Matching an interface name with its PCI address requires running: ll /sys/class/net/ | grep <interface name>

Keyword: PCI information

Reported in version: 3.0.0

4155701

Description: When offloading xfrm states to hardware, the offloading device is linked to the skb's secpath. If an skb is freed or deferred, an unregister netdevice operation may hang because the netdevice is still being reference-counted.

Workaround: Remove the netdevice from the xfrm states when the netdevice is unregistered.

Keyword: IPSec Crypto Offload

Reported in version: 2.10.0

Workaround: If this capability is not disabled by default on your adapter cards (pxe_boot_filter_en=1/TRUE in the bios HII), take the following actions:

1. Reduce the TFTP block size to a value that prevents packet fragmentation.
2. Manually disable the PXE filter.

Description: The I²C clock fall time is lower than the 12ns minimum defined in the I2C-bus specification.

For further information, refer to the I²C-bus Specification, Version 7.0, October 2021, https://www.i2c-bus.org/.

Workaround: Before downgrading the firmware, perform:

• echo 0 > /sys/bus/platform/drivers/mlxbf-bootctl/large_icm
• Arm reboot

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.

Workaround: If this capability is not disabled by default on your adapter cards (pxe_boot_filter_en=1/TRUE in the bios HII), take the following actions:

1. Reduce the TFTP block size to a value that prevents packet fragmentation.

2. Manually disable the PXE filter.

Keywords: PXE boot filters

Detected in version: 24.45.1016

3754913

Description: PHYless Reset is currently not supported.

Workaround: N/A

Keywords: PHYless Reset

Discovered in Version: 24.40.1000

3525865

Description: Unexpected system behavior might be observed if the driver is loaded while reset is in progress.

Workaround: N/A

Keywords: Sync 1 reset, firmware reset

Discovered in Version: 24.39.2048

-

Description: When tx_port_ts is set to "true", due to a compensation mechanism in the Tx timestamp available in some hardware Rx timestamp errors, a symmetrical error and no clock offset occur when using the timestamps to synchronize the device clock.

This might also cause an error while using timestamps for delay measurements (e,g., delay measurements reported by a PTP daemon) and even negative delay measurements in some cases.

Workaround: N/A

Keywords: PTP path delay

Discovered in Version: 24.38.1002

2878841

Description: The firmware rollback fails for the signature retransmit flow if the QPN field is configured in the mkey (as it only allows the given QP to use this Mkey) as the firmware rollback flow relies on an internal QP that uses the mkey.

Workaround: N/A

Keywords: Signature retransmit flow

Discovered in Version: 24.37.1300

3329109

Description: MFS1S50-H003E cable supports only HDR rate when used as a split cable.

Workaround: N/A

Keywords: HDR, split cable, MFS1S50-H003E

Discovered in Version: 24.37.1300

3267506

Description: CRC is included in the traffic byte counters as a port byte counter.

Workaround: N/A

Keywords: Counters, CRC

Discovered in Version: 24.35.2000

3141072

Description: The "max_shaper_rate" configuration query via QEEC mlxreg returns a value translated to hardware granularity.

Workaround: N/A

Keywords: RX Rate-Limiter, Multi-host

Discovered in Version: 24.34.1002

2870970

Description: GTP encapsulation (flex parser profile 3) is limited to the NIC domain.

Encapsulating in the FDB domain will render a 0-size length in GTP header.

Workaround: N/A

Keywords: GTP encapsulation

Discovered in Version: 24.34.1002

2870213

Description: Servers do not recover after configuring PCI_SWITCH_EMULATION_NUM_PORT to 32 followed by power cycle.

Workaround: N/A

Keywords: VirtIO-net; power cycle

Discovered in Version: 24.33.1048

2855592

Description: When working with 3rd party device (e.g., Paragon) in 25GbE speed, the 25GbE speed must be configured in force mode.

Workaround: N/A

Keywords: Force mode, 3rd party devices, 25GbE

Discovered in Version: 24.33.1048

2850003

Description: Occasionally, when rising a logical link, the link recovery counter is increase by 1.

Workaround: N/A

Keywords: Link recovery counter

Discovered in Version: 24.33.1048

2616755

Description: Forward action for IPoIB is not supported on RX RDMA Flow Table.

Workaround: N/A

Keywords: Steering, IPoIB

Discovered in Version: 24.33.1048