Kernel panic

[slykens]

Hello all -

On 24.1.1 this morning I had a kernel panic - this instance runs in a VMware guest, no issues with other guests or the host.

I have been using opnsense in a few places since the great pf exodus months ago and this is the first crash I've had. Maybe it's a one off thing but I figured I'd mention it here in case others see the same

I believe the pertinent logs are below:

Code: [Select]

<45>1 2024-02-15T10:02:09-05:00 108-gateway. syslog-ng 28383 - [meta sequenceId="1"] syslog-ng starting up; version='4.6.0'
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="2"] Fatal trap 12: page fault while in kernel mode
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="3"] cpuid = 2; apic id = 04
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="4"] fault virtual address = 0x28
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="5"] fault code = supervisor read data, page not present
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="6"] instruction pointer = 0x20:0xffffffff80e93473
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="7"] stack pointer         = 0x28:0xfffffe00aa5b8940
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="8"] frame pointer         = 0x28:0xfffffe00aa5b8990
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="9"] code segment = base 0x0, limit 0xfffff, type 0x1b
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="10"] = DPL 0, pres 1, long 1, def32 0, gran 1
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="11"] processor eflags = interrupt enabled, resume, IOPL = 0
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="12"] current process = 64366 (ifconfig)
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="13"] trap number = 12
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="14"] panic: page fault
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="15"] cpuid = 2
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="16"] time = 1708009294
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="17"] KDB: stack backtrace:
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="18"] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00aa5b8700
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="19"] vpanic() at vpanic+0x151/frame 0xfffffe00aa5b8750
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="20"] panic() at panic+0x43/frame 0xfffffe00aa5b87b0
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="21"] trap_fatal() at trap_fatal+0x387/frame 0xfffffe00aa5b8810
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="22"] trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00aa5b8870
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="23"] calltrap() at calltrap+0x8/frame 0xfffffe00aa5b8870
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="24"] --- trap 0xc, rip = 0xffffffff80e93473, rsp = 0xfffffe00aa5b8940, rbp = 0xfffffe00aa5b8990 ---
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="25"] in6_unlink_ifa() at in6_unlink_ifa+0x63/frame 0xfffffe00aa5b8990
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="26"] in6_purgeaddr() at in6_purgeaddr+0x367/frame 0xfffffe00aa5b8ab0
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="27"] in6_purgeifaddr() at in6_purgeifaddr+0x13/frame 0xfffffe00aa5b8ad0
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="28"] in6_control() at in6_control+0x5f7/frame 0xfffffe00aa5b8bc0
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="29"] ifioctl() at ifioctl+0x7bc/frame 0xfffffe00aa5b8cc0
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="30"] kern_ioctl() at kern_ioctl+0x26d/frame 0xfffffe00aa5b8d30
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="31"] sys_ioctl() at sys_ioctl+0x100/frame 0xfffffe00aa5b8e00
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="32"] amd64_syscall() at amd64_syscall+0x10c/frame 0xfffffe00aa5b8f30
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="33"] fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00aa5b8f30
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="34"] --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x75e83cf61ca, rsp = 0x75e807bbc58, rbp = 0x75e807bbcb0 ---
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="35"] KDB: enter: panic
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="36"] Uptime: 7d17h53m56s
<13>1 2024-02-15T10:02:09-05:00 108-gateway. kernel - - [meta sequenceId="37"] ---<<BOOT>>---

[JakaylaLee]

It seems like you're experiencing a kernel panic on an instance running OPNsense in a VMware guest environment. Kernel panics can occur due to various reasons such as hardware issues, driver problems, or software bugs. You can firstly check hardware health by verify the health of your underlying hardware, including the server and storage devices. Ensure that there are no hardware faults or failures that could be causing the kernel panic. Also it would be good to review system logs on the OPNsense instance to gather more information about the kernel panic. Look for any error messages or warnings leading up to the crash.