pfSense 22.05 showing kernel panic on Proxmox after few hours

Snk

Hello good day!
I would like a little help to debug what might be happening inside my proxmox VM.
The host remains stable as a rock, but the pfsense VM after a few hours, ends up crashing and restarting out of nowhere (but the VM uptime remains the same, only the pfsense uptime drops)
I have the debug file generated by pfsense, but so far I haven't been able to get any relevant information.
I've done all Proxmox updates and I'm on the latest pfsense+ version.
My VM is running with 6Gb of ram

Logs: info.0 textdump.tar.0

stephenw10

Backtrace:

db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100081 td 0xfffff800056d2740
kdb_enter() at kdb_enter+0x37/frame 0xfffffe0000578dc0
vpanic() at vpanic+0x194/frame 0xfffffe0000578e10
panic() at panic+0x43/frame 0xfffffe0000578e70
trap_fatal() at trap_fatal+0x38f/frame 0xfffffe0000578ed0
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe0000578f30
calltrap() at calltrap+0x8/frame 0xfffffe0000578f30
--- trap 0xc, rip = 0xffffffff81358580, rsp = 0xfffffe0000579000, rbp = 0xfffffe000057a3c0 ---
Xpage() at Xpage/frame 0xfffffe000057a3c0
virtqueue_notify() at virtqueue_notify+0x8c/frame 0xfffffe000057a3f0
vtnet_start_locked() at vtnet_start_locked+0x345/frame 0xfffffe000057a460
vtnet_start() at vtnet_start+0x41/frame 0xfffffe000057a490
if_transmit() at if_transmit+0x168/frame 0xfffffe000057a4d0
ether_output_frame() at ether_output_frame+0xb4/frame 0xfffffe000057a500
ether_output() at ether_output+0x60e/frame 0xfffffe000057a590
pf_route() at pf_route+0x774/frame 0xfffffe000057a660
pf_test() at pf_test+0x9e8/frame 0xfffffe000057a7e0
pf_check_out() at pf_check_out+0x1d/frame 0xfffffe000057a800
pfil_run_hooks() at pfil_run_hooks+0xa1/frame 0xfffffe000057a8a0
ip_tryforward() at ip_tryforward+0x2b3/frame 0xfffffe000057a920
ip_input() at ip_input+0x415/frame 0xfffffe000057a9d0
netisr_dispatch_src() at netisr_dispatch_src+0xb9/frame 0xfffffe000057aa20
ether_demux() at ether_demux+0x16a/frame 0xfffffe000057aa50
ether_nh_input() at ether_nh_input+0x33b/frame 0xfffffe000057aab0
netisr_dispatch_src() at netisr_dispatch_src+0xb9/frame 0xfffffe000057ab00
ether_input() at ether_input+0x89/frame 0xfffffe000057ab60
vtnet_rxq_eof() at vtnet_rxq_eof+0x6df/frame 0xfffffe000057ac10
vtnet_rx_vq_process() at vtnet_rx_vq_process+0xb7/frame 0xfffffe000057ac50
ithread_loop() at ithread_loop+0x1cb/frame 0xfffffe000057acb0
fork_exit() at fork_exit+0x7e/frame 0xfffffe000057acf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe000057acf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---

Message Buffer:

kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address	= 0x54c
fault code		= supervisor write data, page not present
instruction pointer	= 0x20:0xffffffff81358580
stack pointer	        = 0x28:0xfffffe0032e20020
frame pointer	        = 0x28:0xfffffe0032e21950
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags	= resume, IOPL = 0
current process		= 4515 (sh)
trap number		= 12
panic: page fault
cpuid = 2
time = 1663845550
KDB: enter: panic

Also shows:

<118>ERROR: It was not possible to identify which pfSense kernel is installed

3 panics shown there in different processes.

That error usually indicates an upgrade has not completed as expected. You likely have some parts of 22.01 still present. Though I would not expect that to cause a panic.

Since it's a VM I would first try a clean install and restore your config.

Steve

Snk

@stephenw10 Hi, thanks for the feedback!
If so, would a factory reset and restore from backup be enough?
I believe it is still not possible to install directly from version 22.05, right?

stephenw10

Not to a VM. Not yet. However I tested the upgrade process over the weekend and it completed no problem so I would expect a clean install of 2.6 then upgrade to 22.01 and then 22.05 to work fine.

Steve