CPU ERROR are observed in System Event Logs of Fujitsu iRMC after triggering NMI and post reboot NIC's failed to get detected.

Solution In Progress - Updated -

Issue

  • CPU ERROR are observed in System Event Logs of Fujitsu iRMC after triggering NMI and post reboot NIC's failed to get detected.
  • The snippet from System Event logs from iRMC.
2019-06-21 15:54:13  | Info         | 0D000C     | No   | iRMC                 | Reboot after a CPU error
2019-06-21 15:54:52  | Critical     | 0C0004     | No   | CPU1                 | 'CPU1': CPU internal error (IERR)
2019-06-21 15:54:52  | Critical     | 0C0004     | No   | CPU2                 | 'CPU2': CPU internal error (IERR)
  • The snippet of NIC getting failed to detect.
kernel: i40e: probe of 0000:3d:00.0 failed with error -54
kernel: i40e: probe of 0000:3d:00.1 failed with error -15
kernel: i40e: probe of 0000:3d:00.0 failed with error -54
kernel: i40e: probe of 0000:3d:00.1 failed with error -15
kernel: i40e 0000:3d:00.0: The driver for the device stopped because the device firmware failed to init. Try updating your NVM image.

Environment

  • RHEL 7.5 and above.
  • The NIC model as below.
3d:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 for 10GbE SFP+ [8086:37d3] (rev 09)
    Subsystem: Fujitsu Technology Solutions Device [1734:1230]
3d:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 for 10GbE SFP+ [8086:37d3] (rev 09)
    Subsystem: Fujitsu Technology Solutions Device [1734:1230]
  • i40e kernel driver.
  • Firmware version : nvm 3.33 0x800010ef

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