Crash Report 10-29

amarcino

I had a crash report today around noon version 2.5.2-RELEASE.

Who should I send the reports to?

stephenw10

You can post the backtrace and panic string here if you would like us to review it.

If you have support you can open a ticket and send the complete report for review.

Is this the first time you've seen it?

Steve

amarcino

@stephenw10 Yes first time I had seen one.

amarcino

@stephenw10

Here are the crash alert files.textdump.tar.0 info.0

stephenw10

Ok. The important bits of that are:

db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100007 td 0xfffff80004241000
kdb_enter() at kdb_enter+0x37/frame 0xfffffe00252aaa30
vt_kbdevent() at vt_kbdevent+0x16a/frame 0xfffffe00252aaa90
kbdmux_intr() at kbdmux_intr+0x3f/frame 0xfffffe00252aaab0
kbdmux_kbd_intr() at kbdmux_kbd_intr+0x1d/frame 0xfffffe00252aaad0
taskqueue_run_locked() at taskqueue_run_locked+0x144/frame 0xfffffe00252aab30
taskqueue_run() at taskqueue_run+0x72/frame 0xfffffe00252aab50
ithread_loop() at ithread_loop+0x23c/frame 0xfffffe00252aabb0
fork_exit() at fork_exit+0x7e/frame 0xfffffe00252aabf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00252aabf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---

That's not a crash I'm familiar with.

But in the message buffer, just before it crashed is:
[zone: pf frag entries] PF frag entries limit reached

You should never see that and it has been known to cause crashes. You can increase the frags limit in Sys > Adv > Firewall&NAT but it's usually a symptom of something on your system producing far too much fragmentation. Mismatched MTU somewhere?

Most of the msg buffer, and I imagine your system log, is filled with:

<6>arp: 192.168.1.20 moved from 74:ac:b9:01:e3:24 to 74:ac:b9:01:ce:e2 on igb1
<6>arp: 192.168.1.20 moved from 74:ac:b9:01:ce:e2 to 74:ac:b9:01:e3:24 on igb1

If those are NICs in a LAG or some other known cause you might want to just stop logging it to make your logs more useful:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/logs-arp-moved.html

Steve

amarcino

@stephenw10

Yes those to NICs are in a lag configuration, have been for several years at least.

I will try your suggestions and see what I can find.