Skip to main content
NetApp Knowledge Base

E-Series EF300 Controller rebooting continuously due to fatal machine check

Views:
80
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:
7/19/2024, 10:34:24 AM

Applies to

NetApp E-series EF300

Issue

Controller rebooting continuously and is reporting Fatal machine check from console connection
 
 
Starting  [0;1;39mPermi[    6.713486] Kernel panic - not syncing: EKI: Fatal machine check on current CPU
[    6.721650] CPU: 4 PID: 1335 Comm: systemd-user-se Tainted: G   M       O      4.19.0-21-clp-eseries-amd64 #1 Debian 4.19.249-2+clp+39+eseries31
[    6.736112] Hardware name: NetApp, Inc. Falcon/Falcon, BIOS 1.34.0 08/05/2022
[    6.744074] Call Trace:
[    6.746810]  dump_stack+0x66/0x81
[    6.750511]  panic+0xe7/0x23d
[    6.753827]  machine_check_handler.cold.12+0xc/0xc [eki]
[    6.759758]  do_machine_check+0x47f/0x8c0
[    6.764237]  ? machine_check+0x25/0x40
[    6.768422]  machine_check+0x2f/0x40
[    6.772413] RIP: 2b56f8b8:0xf62706
[    6.776204] Code: Bad RIP value.
[    6.779807] RSP: 0a20:00007f572b95cfa0 EFLAGS: 00000004
[    6.779809] Using FPGA to reset processor

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.