pfSense has detected a crash report or programming bug

bdiop

Hello,

Our firewall encountered a bug last week. My colleague noticed an internet access outage due to firewall not responding and made a reboot.
After restarting, everything works back again and the following message is displayed in the GUI : "pfSense has detected a crash report or programming bug. Click here for more information."
I downloaded the crash files and uploaded them.

If someone has any idea on this to avoid the same issue in the future.

Thanks.[textdump.tar.1](Invalid file type. Allowed types are: .png, .jpg, .bmp, .txt, .gif, .xls, .gz, .zip, .pcap, .pcapng, .7z, .xml, .jpeg, .diff, .patch, .tgz, .tar, .0, .cap) [textdump.tar.0](Invalid file type. Allowed types are: .png, .jpg, .bmp, .txt, .gif, .xls, .gz, .zip, .pcap, .pcapng, .7z, .xml, .jpeg, .diff, .patch, .tgz, .tar, .0, .cap)
crash_dump.zip

stephenw10

Identical crashes so almost certainly a software issue.

Backtrace:

db:0:kdb.enter.default>  bt
Tracing pid 54720 tid 100695 td 0xfffffe00da57fe40
kdb_enter() at kdb_enter+0x32/frame 0xfffffe0112beb960
vpanic() at vpanic+0x163/frame 0xfffffe0112beba90
panic() at panic+0x43/frame 0xfffffe0112bebaf0
trap_fatal() at trap_fatal+0x40c/frame 0xfffffe0112bebb50
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe0112bebbb0
calltrap() at calltrap+0x8/frame 0xfffffe0112bebbb0
--- trap 0xc, rip = 0xffffffff80f44220, rsp = 0xfffffe0112bebc80, rbp = 0xfffffe0112bebd00 ---
in6_pcbbind() at in6_pcbbind+0x360/frame 0xfffffe0112bebd00
udp6_bind() at udp6_bind+0x13c/frame 0xfffffe0112bebd60
sobind() at sobind+0x32/frame 0xfffffe0112bebd80
kern_bindat() at kern_bindat+0x96/frame 0xfffffe0112bebdc0
sys_bind() at sys_bind+0x9b/frame 0xfffffe0112bebe00
amd64_syscall() at amd64_syscall+0x109/frame 0xfffffe0112bebf30
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe0112bebf30
--- syscall (104, FreeBSD ELF64, bind), rip = 0x82839fcea, rsp = 0x82d9cfaf8, rbp = 0x82d9cfbc0 ---

Panic:

Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address	= 0xb8
fault code		= supervisor read data, page not present
instruction pointer	= 0x20:0xffffffff80f44220
stack pointer	        = 0x28:0xfffffe0112bebc80
frame pointer	        = 0x28:0xfffffe0112bebd00
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		= 54720 (isc-net-0003)
rdi: ffffffff82d62a40 rsi: ffffffff82d62a40 rdx: 0000000000010200
rcx: 0000000000000000  r8: fffff8025bcdb700  r9: 0000000000000000
rax: fffff8000c663540 rbx: fffff8000da57c40 rbp: fffffe0112bebd00
r10: 0000000000000000 r11: fffffe00da580360 r12: fffff8000800cc60
r13: 000000000000ecf6 r14: 000000000000ecf6 r15: fffff8025bcdb700
trap number		= 12
panic: page fault
cpuid = 3
time = 1715038044
KDB: enter: panic

I've seen that a few times with different packages once with Bind which it looks like you're running. In that case we were able to workaround it by unselecting linklocal IPv6 addresses as listening interfaces in Bind. Try that.

Steve

stephenw10

Opened a bug for this: https://redmine.pfsense.org/issues/15503

bdiop

Hello Steve,

Thank you for replying.
In fact, we were listening to IPv4+IPv6 in bind.
I just changed that parameter to listen only on IPv4.

Waiting to see if this happens again.

Thanks a lot.
Birama