pfSense has detected a crash report or programming bug

cgarrett

I have no idea why it detected a crash as i have not seen any issues. the only thing I did was update the OpenVPN package and today. a couple of months ago i upgraded it from 2.6.0-release to 2.7.0.
I have uploaded the crash dump info.

Crash report begins. Anonymous machine information:
PfSense Crash Dump.txt

stephenw10

Backtrace:

db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100039 td 0xfffffe0011f73720
kdb_enter() at kdb_enter+0x32/frame 0xfffffe0083e27a30
vpanic() at vpanic+0x183/frame 0xfffffe0083e27a80
panic() at panic+0x43/frame 0xfffffe0083e27ae0
trap_fatal() at trap_fatal+0x409/frame 0xfffffe0083e27b40
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe0083e27ba0
calltrap() at calltrap+0x8/frame 0xfffffe0083e27ba0
--- trap 0xc, rip = 0xffffffff80d8d26e, rsp = 0xfffffe0083e27c70, rbp = 0xfffffe0083e27ce0 ---
m_copydata() at m_copydata+0xfe/frame 0xfffffe0083e27ce0
ip_forward() at ip_forward+0x30f/frame 0xfffffe0083e27d90
ip_input() at ip_input+0x686/frame 0xfffffe0083e27df0
swi_net() at swi_net+0x138/frame 0xfffffe0083e27e60
ithread_loop() at ithread_loop+0x257/frame 0xfffffe0083e27ef0
fork_exit() at fork_exit+0x7d/frame 0xfffffe0083e27f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0083e27f30
--- trap 0xa1d1b1c0, rip = 0xcdb5dcb5dca5dda4, rsp = 0x5ca14da04db05cb, rbp = 0xf3e4e2e5e3f4e2f5 ---

Panic:

Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 06
fault virtual address	= 0x18
fault code		= supervisor read data, page not present
instruction pointer	= 0x20:0xffffffff80d8d26e
stack pointer	        = 0x28:0xfffffe0083e27c70
frame pointer	        = 0x28:0xfffffe0083e27ce0
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 (swi1: netisr 2)
rdi: fffff80032265760 rsi: fffff800320d200e rdx: 9e0c0000f6010121
rcx:               1d  r8: 2fc48a6f00040406  r9: c0ea55a5902fc48a
rax: fffff80032265760 rbx:               1d rbp: fffffe0083e27ce0
r10: ffffffffffea00a8 r11: fffff801a9dbff60 r12:               1d
r13:                0 r14: fffff8003226577d r15:               83
trap number		= 12
panic: page fault
cpuid = 3
time = 1698147368
KDB: enter: panic

However the message buffer is full of these:

<6>arp: 192.168.0.192 moved from 10:60:4b:6d:0e:c5 to f6:2f:56:cb:12:5a on re0
<6>arp: 192.168.0.192 moved from f6:2f:56:cb:12:5a to 10:60:4b:6d:0e:c5 on re0
<6>arp: 192.168.0.192 moved from 10:60:4b:6d:0e:c5 to f6:2f:56:cb:12:5a on re0
<6>arp: 192.168.0.192 moved from f6:2f:56:cb:12:5a to 10:60:4b:6d:0e:c5 on re0

Consider disabling logging ARP movements:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/logs-arp-moved.html

But more importantly:

<6>re0: watchdog timeout
<6>re0: link state changed to DOWN
<6>re0.6: link state changed to DOWN
<6>re0: link state changed to UP
<6>re0.6: link state changed to UP
<6>re0: watchdog timeout
<6>re0: link state changed to DOWN
<6>re0.6: link state changed to DOWN
<6>re0: link state changed to UP
<6>re0.6: link state changed to UP

You should switch to the alternative Realtek driver and see it that prevents it. Or, better, use a different NIC type there.

Steve

cgarrett

@stephenw10 how would i get a different Realtek driver for it?

stephenw10

At the command line run:

pkg-static install realtek-re-kmod

Then:

echo 'if_re_load="YES"' >> /boot/loader.conf.local
echo 'if_re_name="/boot/modules/if_re.ko"' >> /boot/loader.conf.local

Then reboot and check the boot logs show the 1.98 driver:

    re0: <Realtek PCIe GbE Family Controller> port 0x1000-0x10ff mem 0xf7a00000-0xf7a00fff,0xf7900000-0xf7903fff irq 16 at device 0.0 on pci1
    re0: Using Memory Mapping!
    re0: Using 1 MSI-X message
    re0: ASPM disabled
    re0: version:1.98.00
    re0: Ethernet address: 00:0d:b9:38:30:10

Steve