The Broadcom NetXtreme II BCM57810 10 Gigabit Ethernet interface sometimes panics and results in interface timeouts

Issue

• The bnx2x driver for NetXtreme II BCM57810 will fail with following access timeout error:

  Jul 28 23:56:41 localhost kernel: bnx2x: [bnx2x_issue_dmae_with_comp:540(enp5s0f0)]DMAE timeout!
  Jul 28 23:56:41 localhost kernel: bnx2x: [bnx2x_write_dmae:586(enp5s0f0)]DMAE returned failure -1
  Jul 28 23:56:41 localhost kernel: bnx2x: [bnx2x_issue_dmae_with_comp:540(enp5s0f0)]DMAE timeout!
  Jul 28 23:56:41 localhost kernel: bnx2x: [bnx2x_write_dmae:586(enp5s0f0)]DMAE returned failure -1
  Jul 28 23:56:41 localhost kernel: bnx2x: [bnx2x_issue_dmae_with_comp:540(enp5s0f0)]DMAE timeout!
  Jul 28 23:56:41 localhost kernel: bnx2x: [bnx2x_write_dmae:586(enp5s0f0)]DMAE returned failure -1
            :
  Jul 29 00:25:23 localhost kernel: bnx2x 0000:05:00.1 enp5s0f1: MDC/MDIO access timeout
  Jul 29 00:25:23 localhost kernel: bnx2x 0000:05:00.1 enp5s0f1: MDC/MDIO access timeout
  Jul 29 00:25:23 localhost kernel: bnx2x 0000:05:00.1 enp5s0f1: Error:  Power fault on Port 0 has been detected and the power to that SFP+ module has been removed to prevent failure of the card. Please remove the SFP+ module and restart the system to clear this error.
  Jul 29 00:25:23 localhost kernel: bnx2x: [bnx2x_timer:5519(enp5s0f0)]MFW seems hanged: drv_pulse (0x397) != mcp_pulse (0x7fff)
  Jul 29 00:25:23 localhost kernel: bnx2x: [bnx2x_hw_stats_update:899(enp5s0f0)]NIG timer max (4294967295)
  Jul 29 00:25:23 localhost kernel: bnx2x: [bnx2x_acquire_hw_lock:1972(enp5s0f0)]lock_status 0xffffffff  resource_bit 0x1
  

• This tend to happen intermittently.

• The below logs keep on generating causing the /var directory fill up quickly

Jul 16 11:49:37 <host> kernel: bnx2x: [bnx2x_timer:5818(eno6)]MFW seems hanged: drv_pulse (0x6e5d) != mcp_pulse (0x2546)
Jul 16 11:49:37 <host> kernel: bnx2x: [bnx2x_timer:5818(eno6)]MFW seems hanged: drv_pulse (0x6e5d) != mcp_pulse (0x2546)
Jul 16 11:49:38 <host> kernel: bnx2x: [bnx2x_timer:5818(eno6)]MFW seems hanged: drv_pulse (0x6e5e) != mcp_pulse (0x2546)
Jul 16 11:49:38 <host> kernel: bnx2x: [bnx2x_timer:5818(eno6)]MFW seems hanged: drv_pulse (0x6e5e) != mcp_pulse (0x2546)
Jul 16 11:49:39 <host> kernel: bnx2x: [bnx2x_timer:5818(eno6)]MFW seems hanged: drv_pulse (0x6e5f) != mcp_pulse (0x2546)
Jul 16 11:49:39 <host> kernel: bnx2x: [bnx2x_timer:5818(eno6)]MFW seems hanged: drv_pulse (0x6e5f) != mcp_pulse (0x2546)
Jul 16 11:49:40 <host> kernel: bnx2x: [bnx2x_timer:5818(eno6)]MFW seems hanged: drv_pulse (0x6e60) != mcp_pulse (0x2546)
Jul 16 11:49:40 <host> kernel: bnx2x: [bnx2x_timer:5818(eno6)]MFW seems hanged: drv_pulse (0x6e60) != mcp_pulse (0x2546)

• What is causing such messages to appear?