Kernel panics after update to 2.2.5 [Solved]
After upgrading to 2.2.5 I'm getting kernel panics stating:```
Fatal trap12: page fault while in kernel mode
cupid = 3; apic id = 01
fault virtual address = 0xa40c050150
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80cf0b96
stack pointer = 0x28:0xfffffe00651ad610
frame pointer = 0x28:0xfffffe00651as6a0
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor flags = interrupt enabled, resume, IOPL = 0
current process = 47463 (unbound)
I've been searching the web and haven't turned up anything of much use yet. The search continues. I haven't found any triggers for the the error yet. It's happen a few times in 12 hours. If someone out there knows more then I do that would be extremely helpful. If there are any logs I should post please let me know. I've been looking though them and haven't seen much though.
dennypage last edited by
Thanks for the replay but I'm going to need more then that. Should it be off or on. Does it cause problems, if so what kind. Thank you
I also finally got a crash report. I have submitted it. The first two octets should be 104.8 It was submitted a few minutes before I making this post.
He's asking if you have it enabled. There is a crash that a small minority see when AES-NI is enabled, but don't have enough to go on (if you do have it enabled) to determine whether or not that's the cause. That didn't change from earlier 2.2.x versions, so the upgrade didn't change it, but
could be coincidentally encountering it afterwards.
There aren't any crash reports from IPs starting with those two octets. There is one at about the time you mentioned from an IPv6 IP, but that system was 2.2.4, doesn't seem likely to be yours geographically in comparison to your v4 IP, and the crash doesn't match that snippet.
Without seeing the bt output, there's no telling what it might be. You save anything beyond the snippet in the first post?
I just has the hard drive on this system crash with no SMART warning(s) beforehand. I'm going to assume that these crashes were caused by this. I bought a new drive and I'll see how it goes.
Thank you all for your help.