Kernel panic after upgrade

Started by tamer, February 01, 2019, 09:51:22 PM

Previous topic - Next topic
After updating to 19.1, rebooting will cause kernel panic:


Fatal trap 12: page fault while in kenl mode
cpuid = 0; apic id = 00
fault virtual address    = 0xd5
fault code               = supervisor read data, page not present
instruction pointer      = 0x20:0xffffffff80f3c7b0
stack pointer            = 0x20:0xffffffff8259e6b0
frame pointer            = 0x20:0xffffffff8259e7a0
code segment             = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres1, long 1, def32 0, gran 1
processor eflags         = interrupt enabled, resume, IOPL = 0
current process          = 0 ()
[ thread pid 0 tid 0 ]
Stopped at        vm_map_lookup+0x70:      cmpb     $0,0xd5(%rbx)


running bt:

Tracing pid 0 tid 0 td 0xffffffff8202d260
vm_map_lookup() at vm_map_lookup+0x70/frame 0xffffffff8259e7a0
vm_fault_hold() at vm_faulthold+0x66/frame 0xffffffff8259e8e0
vm_fault() at vm_faul+0x75/frame 0xffffffff8259ea920
trap_pfault() at trap_pfault+0x14c/frame 0xffffffff8259e980
trap() at trap+0x2c7/frame0xffffffff8259ea90
calltrap() at calltrap+0x8/frame 0xffffffff8259ea90
--- trap 0xc, rip = 0xffffffff80bc0896, rsp = 0xffffffff8259eb60, rbp = 0xffffffff8259eb70 ---
mi_startup() at mi_startup+0xc6/frame 0xffffffff8259eb70
btext() at btext+0x2c


I'm running in ESXi 6.7, this issue wasn't tested on 6.5 though. Other upgrades do not cause panic (tested 18.1->18.7).

Let me know if there is anything in particular I need to check. I have downgraded to 18.7.10_4 (using a snapshot) for now.

Edit: I forgot to mention that using kernel.old after upgrade boots without issue.

Dell r415 also kernel panics and reboots after tying to upgrade it to 19.1

Managed to get into it's idrac and boot the old kernel.
>:(

Adding HP 290 G1 sff to the list of kernel panics after upgrade....
kernel.old working...

Also seeing this w/ Intel i3-8100 (Gigabyte B360M DS3H mobo).


Have the same issue here on Hyper-V 9.0 after updating via GUI.

I wanted to start a fresh installation - kernel panic!
on Dell PowerEdge R340!
No workaround helps! does anyone have a tip or any other help?

I'm running this on my Dell Poweredge R210.  Have you all made sure that your Bios and firmware are up to date?  I made sure mine where all up to date before I built the box, as I just put this together last week and seems to be running well. 

Quote from: cguilford on February 06, 2019, 01:40:04 PM
I'm running this on my Dell Poweredge R210.  Have you all made sure that your Bios and firmware are up to date?  I made sure mine where all up to date before I built the box, as I just put this together last week and seems to be running well.

bios is up2date!
it's frustrating! I'm not the only one with the kernel panic!
even under vmware there are these problems! that's a joke!

Same problem, also i3 8100 and MSI board. Downgrade now until this is fixed.

What happens when you set:

hw.ibrs_disable=1
vm.pmap.pti=0

February 08, 2019, 03:08:16 AM #10 Last Edit: February 08, 2019, 03:13:16 AM by bunchofreeds
This error is the same as what I and others have experienced in this thread

https://forum.opnsense.org/index.php?topic=11403.0

Hopefully there is a solution soon.

Edit: My particular error message is the same (Verbatim) as what Shremdog and velvet have posted.

After entering
hw.ibrs_disable = 1
vm.pmap.pti = 0
Download successful.
What you need to change so as not to constantly enter these commands.

Would putting them under System -> Settings -> Tunables work?

February 08, 2019, 03:56:10 PM #13 Last Edit: February 08, 2019, 04:23:35 PM by RNHurt
I just upgraded my Acer Aspire AMD machine from 18.7.10 --> 19.1.1 and it threw a kernel panic.  I was able to get back up and running by choosing the old kernel at the boot menu but I don't feel like this is a good solution.

Here's a screenshot of my panic:
Later...
Richard

Quote from: lattera on February 07, 2019, 07:27:52 PM
What happens when you set:

hw.ibrs_disable=1
vm.pmap.pti=0

Doesn't setting those bypass/disable Spectre and Meltdown mitigations?