Enabling MKEY_BY_NAME FW parameter

Hello,

I would like to enable the MKEY_BY_NAME firmware parameter, but so far my attempts have been futile. I set the parameter using the following command:

mlxconfig set MKEY_BY_NAME=1

And then reboot to have the change updated. Unfortunately, after that the NIC does not seem to be able to boot. I see the following messages in the kernel log:

[ 160.955995] mlx5_core 0000:01:00.1: wait_fw_init:321:(pid 142): Waiting for FW initialization, timeout abort in 79s

[ 180.959996] mlx5_core 0000:01:00.1: wait_fw_init:321:(pid 142): Waiting for FW initialization, timeout abort in 59s

[ 200.963998] mlx5_core 0000:01:00.1: wait_fw_init:321:(pid 142): Waiting for FW initialization, timeout abort in 39s

[ 220.967428] mlx5_core 0000:01:00.1: wait_fw_init:321:(pid 142): Waiting for FW initialization, timeout abort in 19s

[ 240.947198] mlx5_core 0000:01:00.1: mlx5_function_setup:1279:(pid 142): Firmware over 120000 MS in pre-initializing state, aborting

[ 240.947351] mlx5_core 0000:01:00.1: init_one:1904:(pid 142): mlx5_load_one failed with error code -16

[ 240.948004] mlx5_core: probe of 0000:01:00.1 failed with error -16

Here is short info about the NIC:

Device #1:


Device Type: BlueField

Part Number: MBF1L516A-CSCA_Ax

Description: BlueField™ SmartNIC 100GbE; Dual Port QSFP28; PCIe Gen4.0 x16; BlueField™ G-Series 16 cores; Crypto enabled; 16GB on-board DDR; FHHL; Single Slot; Tall Bracket

PSID: MT_0000000247

PCI Device Name: 0000:01:00.0

Base GUID: 1c34da030071d8b2

Base MAC: 1c34da71d8b2

Versions: Current Available

FW 18.31.2006 N/A

NVMe 20.1.0005 N/A

PXE 3.6.0404 N/A

UEFI 14.24.0015 N/A

Status: No matching image found

Could you please help me to figure out how to enable the desired configuration option?

Are you seeing these message on the SmartNIC or on the host side? Have you tried to reboot (warm boot) the host one more time? SmartNIC should be running and initialized before driver loading on the host side.

It was in the host side. Do you think Running the same on the SmartNIC side can make a difference?

I will try to do multiple reboots after setting the value, but resetting the value was bringing the NIC back to life upon the next reboot.