Bug/Crash report after trying to reconnect PPPoE connection

webtroter

Hi,

It's the second time now that pfSense crashes when I try to reconnect my pppoe session. I disconnect it because it doesn't work, then I try to connect it again. pfSense becomes unresponsive and eventually I get the crash report on the web page.

See here : https://gitlab.com/-/snippets/2061737/raw/master/snippetfile1.txt

I have the textdump.tar.0 and info.0 available too.

stephenw10

The important part of that is:

db:0:kdb.enter.default>  show pcpu
cpuid        = 3
dynamic pcpu = 0xfffffe0195cd6580
curthread    = 0xfffff8013c354620: pid 43924 "bandwidthd"
curpcb       = 0xfffffe01205d7cc0
fpcurthread  = 0xfffff8013c354620: pid 43924 "bandwidthd"
idlethread   = 0xfffff8000497c620: tid 100006 "idle: cpu3"
curpmap      = 0xfffff80074785138
tssp         = 0xffffffff835a3408
commontssp   = 0xffffffff835a3408
rsp0         = 0xfffffe01205d7cc0
gs32p        = 0xffffffff835aa060
ldt          = 0xffffffff835aa0a0
tss          = 0xffffffff835aa090
tlb gen      = 4265045
db:0:kdb.enter.default>  bt
Tracing pid 43924 tid 100641 td 0xfffff8013c354620
kdb_enter() at kdb_enter+0x3b/frame 0xfffffe01205d6c60
vpanic() at vpanic+0x19b/frame 0xfffffe01205d6cc0
panic() at panic+0x43/frame 0xfffffe01205d6d20
trap_pfault() at trap_pfault/frame 0xfffffe01205d6d70
trap_pfault() at trap_pfault+0x49/frame 0xfffffe01205d6dd0
trap() at trap+0x29d/frame 0xfffffe01205d6ee0
calltrap() at calltrap+0x8/frame 0xfffffe01205d6ee0
--- trap 0xc, rip = 0xffffffff80f9cf86, rsp = 0xfffffe01205d6fb0, rbp = 0xfffffe01205d6fb0 ---
pfi_kif_match() at pfi_kif_match+0x26/frame 0xfffffe01205d6fb0
pf_test_rule() at pf_test_rule+0xe33/frame 0xfffffe01205d7440
pf_test() at pf_test+0x2368/frame 0xfffffe01205d7670
pf_check_out() at pf_check_out+0x1d/frame 0xfffffe01205d7690
pfil_run_hooks() at pfil_run_hooks+0x90/frame 0xfffffe01205d7720
ip_output() at ip_output+0xa53/frame 0xfffffe01205d7850
udp_send() at udp_send+0xa0c/frame 0xfffffe01205d7910
sosend_dgram() at sosend_dgram+0x345/frame 0xfffffe01205d7970
kern_sendit() at kern_sendit+0x1f9/frame 0xfffffe01205d7a20
sendit() at sendit+0x19e/frame 0xfffffe01205d7a70
sys_sendto() at sys_sendto+0x4d/frame 0xfffffe01205d7ac0
amd64_syscall() at amd64_syscall+0xa86/frame 0xfffffe01205d7bf0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe01205d7bf0
--- syscall (133, FreeBSD ELF64, sys_sendto), rip = 0x800de69ea, rsp = 0x7fffffffd218, rbp = 0x7fffffffd260 ---

So I would certainly try disabling bandwidthd and retesting.

Looking at the message buffer there is:

<6>pid 27318 (ntopng), jid 0, uid 0: exited on signal 11 (core dumped)

I would try disabling ntopng too though it quite common to see it fail to start at boot but run fine afterwards.
There are also a load of logs like:

pf_test: kif == NULL, if_xname pppoe0
pf_test: kif == NULL, if_xname pppoe0
pf_test: kif == NULL, if_xname 
pf_test: kif == NULL, if_xname 
pf_test: kif == NULL, if_xname 
pf_test: kif == NULL, if_xname

That could be miniupnpd or maybe Avahi since it looks like you're not running pimd.

Steve

webtroter

@stephenw10
Thank you very much for the hints. I'll take a look!