System crash report

[senseivita]

I got a system crash and I was just about to send it to the Redmine thingy, got an account and everything, but that sort of seems for people who know what they're doing. System's working fine though. Most likely a hiccup but what do I know. :)

pfSense 2.4.4-RELEASE-p2 (amd64)
info.0
textdump.tar.0

[jimp]

It crashed in a network memory operation.

db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100026 td 0xfffff80004e1f620
m_tag_delete_chain() at m_tag_delete_chain+0x83/frame 0xfffffe01735bf8d0
mb_dtor_pack() at mb_dtor_pack+0x11/frame 0xfffffe01735bf8e0
uma_zfree_arg() at uma_zfree_arg+0x42/frame 0xfffffe01735bf940
mb_free_ext() at mb_free_ext+0xfe/frame 0xfffffe01735bf970
m_freem() at m_freem+0x48/frame 0xfffffe01735bf990
vmxnet3_stop() at vmxnet3_stop+0x273/frame 0xfffffe01735bf9e0
vmxnet3_init_locked() at vmxnet3_init_locked+0x2c/frame 0xfffffe01735bfa50
softclock_call_cc() at softclock_call_cc+0x13a/frame 0xfffffe01735bfb00
softclock() at softclock+0x79/frame 0xfffffe01735bfb20
intr_event_execute_handlers() at intr_event_execute_handlers+0xe9/frame 0xfffffe01735bfb60
ithread_loop() at ithread_loop+0xe7/frame 0xfffffe01735bfbb0
fork_exit() at fork_exit+0x83/frame 0xfffffe01735bfbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe01735bfbf0

vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0
vmx0: watchdog timeout on queue 0


Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 06
fault virtual address	= 0x0
fault code		= supervisor read data, page not present
instruction pointer	= 0x20:0xffffffff80d0eee3
stack pointer	        = 0x28:0xfffffe01735bf8c0
frame pointer	        = 0x28:0xfffffe01735bf8d0
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 12 (swi4: clock (0))

It's not normal to see those kinds of NIC timeouts in a VM either.

I'd make sure your ESX or VMWare install is completely current first, and upgrade the VM hardware compatibility as far as possible. Also make sure the selected OS version matches what you have installed. The exact text will vary depending on your ESX/VMware version but it should be set to FreeBSD 11.x 64-bit.