Why is the be2net driver is logging "opcode 36-1 failed:status 68-0"?

Solution Unverified - Updated -

Issue

We are getting the following for each of the be2net interfaces:

Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: be2net version is 10.4r
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: PCIe error reporting enabled
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: adapter not in advanced mode
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: FW config: function_mode=0x2403, function_caps=0xc
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: Max: txqs 1, rxqs 1, rss 0, eqs 16, vfs 0
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: Max: uc-macs 30, mc-macs 64, vlans 8
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: irq 132 for MSI/MSI-X
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: enabled 1 MSI-x vector(s) for NIC
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: created 1 TX queue(s)
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: created 0 RSS queue(s) and 1 default RX queue
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: FW version is 10.2.477.10
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: opcode 36-1 failed:status 68-0
Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: Emulex OneConnect(be3): PF FLEX10 port 0

The error is: Mar 30 09:57:09 rhel7 kernel: be2net 0000:04:00.6: opcode 36-1 failed:status 68-0

Environment

  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content