Troubleshooting

Adapter is no longer identified by the operating system after firmware upgrade

Happens due to burning the wrong firmware on the adapter, firmware corruption or adapter's hardware failure.

Power cycle the server. If the issue persists, extract the adapter and contact Support

Server is booting in loop/not completing boot after performing adapter firmware upgrade

Happens due to burning the wrong firmware on the adapter, firmware corruption or adapter's hardware failure.

Extract the adapter and contact Support

Enabling hardware access after configuring new secure host key, fails

The new configuration of the secure host key was not loaded by the driver

Restart the driver before enabling the hardware access again

mstflint tools fail on PCI device with the following errors:

• Operation not permitted

• Failed to identify device

• Failed to detect device ID

• Unknown device

• No such device

• Failed to open device

Tools PCI semaphore might be locked due to unexpected process shutdown.

Run the following command:

# mcra -c <mst_pci_device>

*Supported on mstflint-4.4.0 and newer versions.

Unable to install the tool package on ESXi platform and the following message is printed on the screen:

Got no data from process

Insufficient privileges

1. Copy the tool's package to /tmp/vmware and continue with the installation. If the issue persists, reboot the ESX server and try again

2. Use full file path of the tool's package

Note: an additional reboot will be required after completing the installation

Unable to install kernel-mft in Linux due to compilation error that contains the following message:

'error: conflicting types for 'compat_sigset_t''

CONFIG_COMPAT might not be enabled in the kernel configuration.

Set the CONFIG_COMPAT to “y” in the kernel .config file, and rebuild the kernel.

The following message is printed on the screen when performing firmware update:

An update is needed for the flash layout.

The operation is not failsafe and terminating the process is not allowed.

A flash alignment operation is required.

Approve the alignment, avoid process interrupt.

Firmware update fails with the following message:

-E- Burning FS4 image failed: Bad parameter

Note: This is a rare scenario.

Firmware compatibility issue.

Re-run the burn command with --no_fw_ctrl flag.

The following message is printed on the screen when performing firmware update:

Shifting between different image partition sizes requires a current image to be re-programmed on the flash.

Once the operation is done, reload FW and run the command again

Note: This is a rare scenario.

Firmware compatibility issue.

Re-load firmware and re-run the burn command.

The following message is printed on the screen when trying to query/burn a Connect-IB device:

-E- Cannot open Device: 41:00.0. B14 Operation not permitted MFE_CMDIF_GO_BIT_BUSY

Using an outdated firmware version with the Connect-IB adapter.

1. Unload MLNX_OFED driver: /etc/init.d/openibd stop.

2. Add “-ocr” option to the 'mstflint' command.

For example:

mstflint -d 41:00.0 -ocr q

The following message is reported on screen when trying to remove the expansion ROM using the 'drom' option:

-E- Remove ROM failed: The device FW contains common FW/ROM Product Version - The ROM cannot be removed separately.B9

Updating only the EXP_ROM (FlexBoot) for recent firmware images which requires adding the 'allow_rom_change' option.

Allow “-allow_rom_change” option to the “mstflint” command.

For example:

mstflint -d <mst_device> - allow_rom_change drom

Generating a firmware image file on Windows fails and the following message is printed on screen:

-E- File: C:/Users/Administrator/ ps.ini, Line: 1 - Invalid syntax

-E- Image generation failed: child process exited abnormally

Using a firmware configuration file (.ini) which was generated by PowerShell text redirection:

mstflint -d <mst_device> dc > <fw_conf_file>.ini

Generate the firmware configuration file (.ini) using CMD edit and continue with generating the firmware image file.

Burning command fails and the following message is printed on screen:

-E- Can not open 06:00.0: Can not obtain Flash semaphore (63). You can run "mstflint -clear_semaphore

- d <device>" to force semaphore unlock. See help for details.

Semaphore can be locked for any of the following reasons:

• Another process is burning the firmware at the same time

• Failure in the firmware boot

• Burning process was force- fully killed

• In a Multi-Host environment, another Host is cur- rently burning the firmware

If no other process is taking place at the same time run the following command: mstflint -d <device> -- clear_semaphore

OR

Reboot the machine.

Burning tool fails with the following message:

–E– Unsupported binary version (2.0) please update to latest mstflint package.

The binary version is incompatible with the burning tool.

Update mstflint to the latest package.

Burning tool fails with an error mentioning Firmware time stamping e.g

-E- Burning FS3 image failed: Stamped FW version missmatch: 12.16.0212 differs from 12.16.0230

The device was set with a timestamp for a different firmware version than the one being burnt or the image is stamped with an older timestamp

Either set a newer timestamp on the image than there is on the device, or reset the timestamp completely. mstflint -d <device> ts reset mstflint -i <image> ts reset

Burning the image on Controlled FW (default update method: fw_ctrl in 'mstflint -d <device> query full' output), fails with:

-E- Burning FS3 image failed: The Digest in the signature is wrong.

The image was changed without calculating the new digest on it with 'mstflint -i <img.bin> sign'.

Run 'mstflint -i <img.bin> sign', and retry.