Reported Driver Events

Linux Kernel Upstream Release Notes v6.5

The driver records events in the system log of the Windows server event system which can be used to identify, diagnose, and predict sources of system problems.

To see the log of events, open System Event Viewer as follows:

  • Right click on My Computer, click Manage, and then click Event Viewer.

OR

  1. Click Start → Run and enter "eventvwr.exe".

  2. In Event Viewer, select the system log.

The following events are recorded:

  • Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> has been successfully initialized and enabled.

  • Failed to initialize Mellanox ConnectX EN 10Gbit Ethernet Adapter.

  • Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> has been successfully initialized and enabled. The port's network address is <MAC Address>

  • The Mellanox ConnectX EN 10Gbit Ethernet was reset.

  • Failed to reset the Mellanox ConnectX EN 10Gbit Ethernet NIC. Try disabling then re-enabling the "Mellanox Ethernet Bus Driver" device via the Windows device manager.

  • Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> has been successfully stopped.

  • Failed to initialize the Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> because it uses old firmware version (<old firmware version>). You need to burn firmware version <new firmware version> or higher, and to restart your computer.

  • Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> device detected that the link connected to port <Y> is up, and has initiated normal operation.

  • Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> device detected that the link connected to port <Y> is down. This can occur if the physical link is disconnected or damaged, or if the other end-port is down.

  • Mismatch in the configurations between the two ports may affect the performance. When Using MSI-X, both ports should use the same RSS mode. To fix the problem, configure the RSS mode of both ports to be the same in the driver GUI.

  • Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> device failed to create enough MSI-X vectors. The Network interface will not use MSI-X interrupts. This may affects the performance. To fix the problem, configure the number of MSI-X vectors in the registry to be at least <Y>

  • <Device>: <Execution of | Post> FW command failed. op <x>, status <y>, errno <n>, token <m>, in_modifier <k>, op_modifier <l>, in_param <j>.

  • <Device>: SR-IOV was successfully enabled. Running in master mode.

  • Port type registry value for device <device name> could not be modified to value (PortType = <n>). Previous value will be set.

  • <Device>: Virtual Function (VF) #<VF ID> issued an invalid or out-of-sequence device-command (channel=<n>, fragment=<m>, cmd=<k>, status=<l>) - command blocked.

© Copyright 2023, NVIDIA. Last updated on May 23, 2023.