need assistance with a pfsense crash report

sylvain613

i keep getting this crash dump every day it reboots my pfsense im not sure what by the logs what the issue is if someone could point me in the right direction.

thanks

textdump.tar.0

stephenw10

Relevant parts there are:

db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100064 td 0xfffff80004802620
kdb_enter() at kdb_enter+0x3b/frame 0xfffffe00b7cf4720
vpanic() at vpanic+0x19b/frame 0xfffffe00b7cf4780
panic() at panic+0x43/frame 0xfffffe00b7cf47e0
propagate_priority() at propagate_priority+0x291/frame 0xfffffe00b7cf4810
turnstile_wait() at turnstile_wait+0x31c/frame 0xfffffe00b7cf4860
__rw_rlock_hard() at __rw_rlock_hard+0x281/frame 0xfffffe00b7cf48f0
rip_input() at rip_input+0x2bb/frame 0xfffffe00b7cf4960
igmp_input() at igmp_input+0x131/frame 0xfffffe00b7cf4a20
ip_input() at ip_input+0x131/frame 0xfffffe00b7cf4ab0
swi_net() at swi_net+0x143/frame 0xfffffe00b7cf4b20
intr_event_execute_handlers() at intr_event_execute_handlers+0xe9/frame 0xfffffe00b7cf4b60
ithread_loop() at ithread_loop+0xe7/frame 0xfffffe00b7cf4bb0
fork_exit() at fork_exit+0x83/frame 0xfffffe00b7cf4bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00b7cf4bf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
db:0:kdb.enter.default>  ps

Sleeping thread (tid 100345, pid 50777) owns a non-sleepable lock
KDB: stack backtrace of thread 100345:
sched_switch() at sched_switch+0x64a/frame 0xfffffe00da8b8530
mi_switch() at mi_switch+0xeb/frame 0xfffffe00da8b8560
sleepq_wait() at sleepq_wait+0x2c/frame 0xfffffe00da8b8590
_sx_xlock_hard() at _sx_xlock_hard+0x2fe/frame 0xfffffe00da8b8640
bxe_ioctl() at bxe_ioctl+0x7a/frame 0xfffffe00da8b8680
if_delmulti() at if_delmulti+0x114/frame 0xfffffe00da8b86c0
vlan_setmulti() at vlan_setmulti+0x43/frame 0xfffffe00da8b8700
vlan_ioctl() at vlan_ioctl+0x8c/frame 0xfffffe00da8b8780
inp_setmoptions() at inp_setmoptions+0x177e/frame 0xfffffe00da8b8950
ip_ctloutput() at ip_ctloutput+0x11b/frame 0xfffffe00da8b89a0
rip_ctloutput() at rip_ctloutput+0x133/frame 0xfffffe00da8b89d0
sosetopt() at sosetopt+0xb1/frame 0xfffffe00da8b8a30
kern_setsockopt() at kern_setsockopt+0xc8/frame 0xfffffe00da8b8aa0
sys_setsockopt() at sys_setsockopt+0x24/frame 0xfffffe00da8b8ac0
amd64_syscall() at amd64_syscall+0xa86/frame 0xfffffe00da8b8bf0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00da8b8bf0
--- syscall (105, FreeBSD ELF64, sys_setsockopt), rip = 0x80092ea8a, rsp = 0x7fffffffea38, rbp = 0x7fffffffea80 ---
panic: sleeping thread
cpuid = 6
KDB: enter: panic

Also quite a few things shown in the message buffer:

bxe0: link_vars phy_flags : 1
bxe0: NIC Link is Up, 2500 Mbps full duplex, Flow control: ON - receive & transmit

Is that running the custom driver/firmware to link at 2.5Gbps?

calcru: runtime went backwards from 301 usec to 298 usec for pid 29085 (sleep)
calcru: runtime went backwards from 1212 usec to 1200 usec for pid 64379 (getty)
calcru: runtime went backwards from 1157 usec to 1145 usec for pid 63990 (getty)
calcru: runtime went backwards from 294 usec to 291 usec for pid 98020 (minicron)

Implies a virtualisation issue or occasionally some problem with CPU frequency control.

bxe1: ERROR: resource (0x8) not in use (status 0x0 bit 0x100)
bxe1: ERROR: Can't unload in closed or error state recover_state 0x1 state = 0x0

I haven't seen a non-sleepable lock panic for a long time. Looks like it's in the bxe driver.

Steve

Edit: This looks like it is the modified driver: QLogic NetXtreme II BCM57810 10GbE [BELL BYPASS] (B0)

stephenw10

@stephenw10 said in need assistance with a pfsense crash report:

Sleeping thread (tid 100345, pid 50777) owns a non-sleepable lock

Actually that process is igmpproxy:

Tracing command igmpproxy pid 50777 tid 100345 td 0xfffff80073cfd620
sched_switch() at sched_switch+0x64a/frame 0xfffffe00da8b8530
mi_switch() at mi_switch+0xeb/frame 0xfffffe00da8b8560
sleepq_wait() at sleepq_wait+0x2c/frame 0xfffffe00da8b8590
_sx_xlock_hard() at _sx_xlock_hard+0x2fe/frame 0xfffffe00da8b8640
bxe_ioctl() at bxe_ioctl+0x7a/frame 0xfffffe00da8b8680
if_delmulti() at if_delmulti+0x114/frame 0xfffffe00da8b86c0
vlan_setmulti() at vlan_setmulti+0x43/frame 0xfffffe00da8b8700
vlan_ioctl() at vlan_ioctl+0x8c/frame 0xfffffe00da8b8780
inp_setmoptions() at inp_setmoptions+0x177e/frame 0xfffffe00da8b8950
ip_ctloutput() at ip_ctloutput+0x11b/frame 0xfffffe00da8b89a0
rip_ctloutput() at rip_ctloutput+0x133/frame 0xfffffe00da8b89d0
sosetopt() at sosetopt+0xb1/frame 0xfffffe00da8b8a30
kern_setsockopt() at kern_setsockopt+0xc8/frame 0xfffffe00da8b8aa0
sys_setsockopt() at sys_setsockopt+0x24/frame 0xfffffe00da8b8ac0
amd64_syscall() at amd64_syscall+0xa86/frame 0xfffffe00da8b8bf0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00da8b8bf0
--- syscall (105, FreeBSD ELF64, sys_setsockopt), rip = 0x80092ea8a, rsp = 0x7fffffffea38, rbp = 0x7fffffffea80 ---

Can you disable that as a test?

sylvain613

@stephenw10 said in need assistance with a pfsense crash report:

thank you so much for the reply @stephenw10 bxe1 is a spf port that i dont use i do however use the bxe0 port for ftth bell the drivers are modified to be able to link at 2.5gb nodia gpon.

you want me to disable igmp proxy service? and see if the issue is resolved?

stephenw10

Yes, that's the first thing I would try.

See if subsequent crashes are similar.

Steve

sylvain613

This post is deleted!

sylvain613

@stephenw10
I have disabled the service and here is my igmpproxy.conf file setup is for IPTV with bell if this helps

##------------------------------------------------------
## Enable Quickleave mode (Sends Leave instantly)
##------------------------------------------------------
quickleave
phyint bxe0.36 upstream
altnet 10.2.0.0/16

phyint ix0 downstream

phyint pppoe0 disabled
phyint ix1 disabled

stephenw10

I can't imagine that being a specific issue. Basic config.
If you are able to disable the service as a test though I would do that.

Otherwise I would be comparing other crashes with that to see if they are all the same.

Steve