[Bug 268246] crash and panic using pfsync on 13.1-RELEASE

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 13 Dec 2022 15:54:21 UTC

--- Comment #7 from jjasen@gmail.com ---
We seem to have two different crashdumps relating to pfsync. 

I posted the ones where pfsyncintr seems to be involved, but the ones overnight
look different:

Fatal trap 12: page fault while in kernel mode
cpuid = 6; apic id = 0c
fault virtual address   = 0x388
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff826ed5e4
stack pointer           = 0x28:0xfffffe017cbb1d40
frame pointer           = 0x28:0xfffffe017cbb1da0
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 (swi4: clock (0))
trap number             = 12
panic: page fault
cpuid = 6
time = 1670920384
KDB: stack backtrace:
#0 0xffffffff80c694a5 at kdb_backtrace+0x65
#1 0xffffffff80c1bb5f at vpanic+0x17f
#2 0xffffffff80c1b9d3 at panic+0x43
#3 0xffffffff810afdf5 at trap_fatal+0x385
#4 0xffffffff810afe4f at trap_pfault+0x4f
#5 0xffffffff810875b8 at calltrap+0x8
#6 0xffffffff80c3884d at softclock_call_cc+0x13d
#7 0xffffffff80c38cd9 at softclock+0x79
#8 0xffffffff80bdbcfa at ithread_loop+0x25a
#9 0xffffffff80bd8a9e at fork_exit+0x7e
#10 0xffffffff8108862e at fork_trampoline+0xe
Uptime: 16h46m12s
Dumping 8003 out of 130983 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

0xffffffff80c1b91e in doadump (textdump=<optimized out>) at
414     /usr/src/sys/kern/kern_shutdown.c: No such file or directory.

(kgdb) bt
#0  0xffffffff80c1b91e in doadump (textdump=<optimized out>) at
#1  0xffffffff80c1b75c in kern_reboot (howto=260) at
#2  0xffffffff80c1bbce in kproc_shutdown (arg=0x0, howto=<optimized out>) at
#3  0xffffffff80c1b9d3 in vpanic (fmt=0xffffffff811b4fb9 "%s", ap=0x100) at
#4  0xffffffff810afdf5 in trap_fatal (frame=0xfffffe017cbb1c80,
eva=18446741881073900480) at /usr/src/sys/amd64/amd64/trap.c:944
#5  0xffffffff810afe4f in trap_pfault (frame=0xfffffe017cbb1c80,
usermode=false, signo=<optimized out>, ucode=<optimized out>)
    at /usr/src/sys/amd64/amd64/trap.c:763
#6  <signal handler called>
#7  0xffffffff826ed5e4 in pfsync_defer_tmo () from /boot/kernel/pfsync.ko
#8  0xffffffff80c3884d in softclock_call_cc (c=0xfffff80d088882a0,
cc=0xfffffe017cf393a0, direct=0) at /usr/src/sys/kern/kern_timeout.c:717
#9  0xffffffff80c38cd9 in softclock (arg=0xffffffff81cadc00 <cc_cpu>) at
#10 0xffffffff80bdbcfa in atomic_fcmpset_long (dst=0xfffff80104968858,
src=18446741881077601184, expect=<optimized out>)
    at /usr/src/sys/amd64/include/atomic.h:225
#11 intr_event_execute_handlers (ie=0xfffff80104968800, p=<optimized out>) at
#12 ithread_execute_handlers (ie=<optimized out>, p=<optimized out>) at
#13 ithread_loop (arg=0xfffff80104895b00) at /usr/src/sys/kern/kern_intr.c:1269
#14 0xffffffff80bd8a9e in fork_exit (callout=0xffffffff80bdbaa0
<ithread_loop+64>, arg=0xfffff80104895b00, frame=0xfffffe017cbb1f40)
    at /usr/src/sys/kern/kern_fork.c:1085
#15 <signal handler called>
#16 0xffffffff80ba970f in mi_startup () at /usr/src/sys/kern/init_main.c:329
Backtrace stopped: Cannot access memory at address 0x8

You are receiving this mail because:
You are the assignee for the bug.