Messages

@Borys - your log looks the same as mine did. Do what I did a couple posts up and I would imagine you will be good to go. Check the kernel version now that you've updated and then

Code Select Expand

pkg install -f syslog-ng

Just reporting back... after 3 days of uptime, we are still running stable. Looks like all is good and thank you so much for your help. Updating the kernel and reinstalling syslog fixed everything. Interestingly enough, my ram use also seems to have gone down. Same amount of services and interfaces (I didn't change anything else) but I'm now only using half the memory that I was before. Wonder if that all had something to do with it. Anyways, all seems good now. Thank you!

@newsense - I updated the kernel to
"stable/24.7-n267981-8375762712f" and rebooted. Then reinstalled syslog and restarted the service. So far the log shows that Syslog-ng has started and that's when the page fault was occurring. Thank you everyone for the help and I will report back. Fingers crossed!

@meyergru - it is installed on ZFS and ran stable for months like that with no problems. Appreciate the input. I was just thinking maybe SSD issue because it seems to be syslog that's messing everything up. No kernel panic for 2 days now after stopping the syslog service.

@dedi - thanks for that info. Looks like my best bet is to export my config and grab the latest version from the website and do a fresh install. Thanks

I haven't had a chance to read through the rest of your log dumps but I went back through several days of mine and found out that the page fault happens right when syslog-ng seems to reload? I'm not sure about some of that stuff so I don't know if there is something wrong with syslog-ng or if it is supposed to reload regularly. After playing with my ram configurations, I came to the conclusion that it's not a ram problem. I don't have an extra SSD to test that it is a drive problem.

Have you noticed what comes right before the page fault?

I traced mine back to starting on the evening of Dec. 31st after my 2 year old "accidentally" hit the power button since I stupidly leave the router sitting out in the living room LOL! Ever since then, every time syslog-ng seems to reload, I have a problem. I have disabled the syslog service and despite now having no logging, I have yet to have another page fault and kernel panic

Edit to add: my next step is to try a fresh install. I just haven't had the time to do so yet

Hey, I'm running:
OPNsense 24.7.11_2-amd64
FreeBSD 14.1-RELEASE-p6
OpenSSL 3.0.15

on a Dell Optiplex 3080 i5 CPU with 8gb ram.

Getting random Kernel panic and the box restarts every 8-24 hours. I originally had been playing around with ram so I changed the ram configuration a few times and the only difference is I seem to get 24-ish hours between reboots now instead of 4-6. Before the Kernel panics, I had increased the ram and it ran stable for 14 days and then out of nowhere started to have this problem. Hopefully this log dump comes through ok as I currently don't have a desktop PC to work from so these were taken from an SSH app on an iPhone. I don't know how the formatting will look. Thank you for any help possible!

Btw: the ram is currently back to the same configuration that had run stable for months

Code Select Expand

<11>1 2025-01-02T04:02:00-05:00 OPNsense.lan configctl 62410 - [meta sequenceId="1"] error in configd communication  Traceback (most recent call last):   File "/usr/local/sbin/configctl", line 65, in exec_config_cmd     line = sock.recv(65536).decode()            ^^^^^^^^^^^^^^^^ TimeoutError: timed out
<45>1 2025-01-02T04:08:35-05:00 OPNsense.lan syslog-ng 34164 - [meta sequenceId="1"] syslog-ng starting up; version='4.8.1'
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="2"] Fatal trap 12: page fault while in kernel mode
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="3"] cpuid = 0; apic id = 00
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="4"] fault virtual address    = 0xaca52425
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="5"] fault code               = supervisor read data, page not present
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="6"] instruction pointer      = 0x20:0xffffffff8109fa60
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="7"] stack pointer            = 0x28:0xffffffff82e1d750
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="8"] frame pointer            = 0x28:0xffffffff82e1d750
: <13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="9"] code segment             = base 0x0, limit 0xfffff, type 0x1b
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="10"]                         = DPL 0, pres 1, long 1, def32 0, gran 1
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="11"] processor eflags        = interrupt enabled, resume, IOPL = 0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="12"] current process         = 0 (re0 taskq)
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="13"] rdi: 00000000aca52425 rsi: ffffffff82e1d7f8 rdx: 0000000000000028
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="14"] rcx: 00000000000568f1  r8: 0000000000000026  r9: 00000000c02d0426
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="15"] rax: 0000000000000000 rbx: fffff80001f43740 rbp: ffffffff82e1d750
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="16"] r10: 00000000e6b08a34 r11: 0000000081463854 r12: ffffffff82e1d7f8
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="17"] r13: 00000000aca52425 r14: fffff80001e00500 r15: fffffe00dc59c000
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="18"] trap number             = 12
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="19"] panic: page fault

<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="20"] cpuid = 0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="21"] time = 1735808760
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="22"] KDB: stack backtrace:
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="23"] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff82e1d440
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="24"] vpanic() at vpanic+0x131/frame 0xffffffff82e1d570
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="25"] panic() at panic+0x43/frame 0xffffffff82e1d5d0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="26"] trap_fatal() at trap_fatal+0x40b/frame 0xffffffff82e1d630
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="27"] trap_pfault() at trap_pfault+0x46/frame 0xffffffff82e1d680
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="28"] calltrap() at calltrap+0x8/frame 0xffffffff82e1d680
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="29"] --- trap 0xc, rip = 0xffffffff8109fa60, rsp = 0xffffffff82e1d750, rbp = 0xffffffff82e1d750 ---
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="30"] memcmp() at memcmp+0x110/frame 0xffffffff82e1d750

<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="31"] pf_find_state() at pf_find_state+0xc0/frame 0xffffffff82e1d7a0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="32"] pf_test_state_tcp() at pf_test_state_tcp+0x1c4/frame 0xffffffff82e1d910
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="33"] pf_test6() at pf_test6+0x13ce/frame 0xffffffff82e1dac0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="34"] pf_check6_in() at pf_check6_in+0x5e/frame 0xffffffff82e1daf0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="35"] pfil_mbuf_in() at pfil_mbuf_in+0x38/frame 0xffffffff82e1db20
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="36"] ip6_input() at ip6_input+0x607/frame 0xffffffff82e1dc00
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="37"] netisr_dispatch_src() at netisr_dispatch_src+0x9e/frame 0xffffffff82e1dc50
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="38"] ether_demux() at ether_demux+0x149/frame 0xffffffff82e1dc80
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="39"] ether_nh_input() at ether_nh_input+0x36a/frame 0xffffffff82e1dce0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="40"] netisr_dispatch_src() at netisr_dispatch_src+0x9e/frame 0xffffffff82e1dd30

<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="41"] ether_input() at ether_input+0x56/frame 0xffffffff82e1dd80
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="42"] re_rxeof() at re_rxeof+0x344/frame 0xffffffff82e1de00
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="43"] re_int_task() at re_int_task+0xbd/frame 0xffffffff82e1de40
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="44"] taskqueue_run_locked() at taskqueue_run_locked+0x182/frame 0xffffffff82e1dec0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="45"] taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xffffffff82e1def0
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="46"] fork_exit() at fork_exit+0x7f/frame 0xffffffff82e1df30
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="47"] fork_trampoline() at fork_trampoline+0xe/frame 0xffffffff82e1df30
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="48"] --- trap 0x7ae80af6, rip = 0xfed9d7f271182d56, rsp = 0x82612ed2a3d8c8d7, rbp = 0xc102a8878f76d1ca ---
<13>1 2025-01-02T04:08:35-05:00 OPNsense.lan kernel - - [meta sequenceId="49"] KDB: enter: panic