December 2, 20187 yr Hi there, last night I had my first kernel panic . really don’t have a clue on where to go from there... I am running a hp microserver gen 8 with 16gb and the server has been running fine for more then a year now with Unraid. After te panic I have reset my server and it came up ok, the parity check also went fine. Any idea what could have caused this kernel panic ? tower-syslog-20181202-1040.zip tower-diagnostics-20181202-1232.zip Edited December 2, 20187 yr by DvD
December 2, 20187 yr There is nothing in the syslog to suggest what caused the problem. Unfortunately, the most useful part of the error message has disappeared off the top of the screen. The message "Kernel panic - not syncing: Fatal exception in interrupt" is not very specific. You might think that it suggests a buggy interrupt handler but a Google search shows that it is a very generic error that has been happening on all kinds of hardware with many different kernels for a number of years. I haven't been able to find anything more useful. Did you recently update Unraid? Perhaps the next kernel update will fix it. I'm still running Unraid 6.5.3 on my Gen 8 but I have other servers running 6.6.5. If it happens again you could put the Fix Common Problems plugin into troubleshooting mode and see if it catches anything.
December 2, 20187 yr Author Thnx John_M No I didn't update recently, I am on 6.6.5 for a while now. I will setup splunk and forward the logs ( in case it logs anything). The log attached here is from right after the crash. I don't know either why I didn't see the top part of the error message. This was the view with remote console. Hopefully it was a one time thing...
February 24, 20197 yr I've been getting the exact same error, down to the `RIP` part (`nf_nat_setup_info`). System is the same HP Microserver Gen8, has been working without kernel panics for over a year on versions up to 6.5, until upgrading to 6.6.5 and 6.6.6. This has started happening after updating from 6.5. Downgrading stops the kernel panics completely, so I'm guessing it must be something in the new kernel patches in 6.6.x that address Spectre. I'm attaching the Diagnostic file and will work on using Fix Common Problems for more. lilo-diagnostics-20190224-1157.zip Edited February 24, 20197 yr by adyus Specified system details.
March 2, 20197 yr I had hoped that upgrading to the most recent System ROM for the Microserver Gen8 from HP would have solved this, but unfortunately I got another identical kernel panic last night. Is there anything else I could try, or just wait for 6.6.7 and hope it fixes it by some magic?
Archived
This topic is now archived and is closed to further replies.