Crash Report PF2.7.0

starcodesystems

Good Morning..

2.7.0-RELEASE (amd64)
built on Wed Jun 28 03:53:34 UTC 2023
FreeBSD 14.0-CURRENT

stephenw10

Backtrace:

db:0:kdb.enter.default>  bt
Tracing pid 11 tid 100007 td 0xfffffe001ebbe720
kdb_enter() at kdb_enter+0x32/frame 0xfffffe00c56849c0
vpanic() at vpanic+0x183/frame 0xfffffe00c5684a10
panic() at panic+0x43/frame 0xfffffe00c5684a70
trap_fatal() at trap_fatal+0x409/frame 0xfffffe00c5684ad0
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00c5684b30
calltrap() at calltrap+0x8/frame 0xfffffe00c5684b30
--- trap 0xc, rip = 0xffffffff80b05c80, rsp = 0xfffffe00c5684c00, rbp = 0xfffffe00c5684c00 ---
vmxnet3_isc_txd_credits_update() at vmxnet3_isc_txd_credits_update+0x20/frame 0xfffffe00c5684c00
iflib_fast_intr_rxtx() at iflib_fast_intr_rxtx+0xf7/frame 0xfffffe00c5684c60
intr_event_handle() at intr_event_handle+0x123/frame 0xfffffe00c5684cd0
intr_execute_handlers() at intr_execute_handlers+0x4a/frame 0xfffffe00c5684d00
Xapic_isr1() at Xapic_isr1+0xdc/frame 0xfffffe00c5684d00
--- interrupt, rip = 0xffffffff8125b026, rsp = 0xfffffe00c5684dd0, rbp = 0xfffffe00c5684dd0 ---
acpi_cpu_c1() at acpi_cpu_c1+0x6/frame 0xfffffe00c5684dd0
acpi_cpu_idle() at acpi_cpu_idle+0x2fe/frame 0xfffffe00c5684e10
cpu_idle_acpi() at cpu_idle_acpi+0x48/frame 0xfffffe00c5684e30
cpu_idle() at cpu_idle+0x9e/frame 0xfffffe00c5684e50
sched_idletd() at sched_idletd+0x4d1/frame 0xfffffe00c5684ef0
fork_exit() at fork_exit+0x7d/frame 0xfffffe00c5684f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00c5684f30
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---

Panic:

Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address	= 0xfffffe00c6000008
fault code		= supervisor read data, page not present
instruction pointer	= 0x20:0xffffffff80b05c80
stack pointer	        = 0x28:0xfffffe00c5684c00
frame pointer	        = 0x28:0xfffffe00c5684c00
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		= 11 (idle: cpu4)
rdi:             2000 rsi:                0 rdx:                0
rcx:                0  r8:              d40  r9: fffff80006412800
rax: fffffe00c5ffe000 rbx:                0 rbp: fffffe00c5684c00
r10: fffffe001e979d80 r11:                1 r12: fffff80005dc6c00
r13:                0 r14: fffffe00c5ff5000 r15:                0
trap number		= 12
panic: page fault
cpuid = 4
time = 1694606279
KDB: enter: panic

It looks like it panicked after you enabled aes-ni in the message buffer. There are no time-stamps though, was that immediately after that?

Steve

starcodesystems

Hi Steve, Good Morning...

I am going to assume so, as I was in the middle of getting our other sites back up, and VM was quickest solution available.
There are other crash reports I am about to upload...

Thanks for your reply, and I'm like, "where the hell?! Where is he seeing this?? where AES anywhere in here?!"

stephenw10

It's the last thing in the message buffer before the kernel trap:

VMware memory control driver initialized
[fib_algo] inet.0 (bsearch4#32) rebuild_fd_flm: switching algo to radix4_lockless
aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS>
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode

And it's unusual to see the aesni device loaded at that point. It would normally be loaded during bootup if it was already enabled.