https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290177
Bug ID: 290177
Summary: PF - panicking after upgrade to 15.0-STABLE
Product: Base System
Version: 15.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: [email protected]
Reporter: [email protected]
It’s definitely triggered by network packets. The behaviour looks ugly -
reminiscent of the “packet fights” seen during the wild TCP/IP stack testing
days of the previous century.
I’ve been running stable/15 on this host for over a month; it was recently
upgraded to 15.0-STABLE (equivalent of BETA1). For this month, stable/15 was
run almost without any issues, but this evening I was summoned to the remote
console by a continuous series of panics. Booting the machine without PF
resolved the issue.
There were not many changes to pf.conf recently. I had reworked "rdr pass"
rules on this machine to overcome the deficiency of PF from the early stable/15
stage, but it was fixed later in stable/15 AFAIK, so now I can probably remove
additional "pass", but this redirected traffic doesn't seem to trigger the
panic.
Below is the record. Unfortunately, I have no opportunity to collect cores
there; it can change later this week.
Fatal trap 12: page fault while in kernel mode
cpuid = 13; apic id = 0d
fault virtual address = 0x5dc
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff83551f78
stack pointer = 0x28:0xfffffe005bc609d0
frame pointer = 0x28:0xfffffe005bc60a60
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 13)
rdi: 0000000000000000 rsi: fffffe005bc60b40 rdx: fffff8038b1ada80
rcx: 0000000000000000 r8: 0000000000000000 r9: fffffe005bc60ca8
rax: 0000000000000000 rbx: 0000000000000002 rbp: fffffe005bc60a60
r10: 0000000000000001 r11: fffff8038b1adab8 r12: fffff80883954900
r13: fffff8038b1ada80 r14: fffff80005bca000 r15: fffff80883954900
trap number = 12
panic: page fault
cpuid = 13
time = 1760299905
KDB: stack backtrace:
#0 0xffffffff80ba353d at kdb_backtrace+0x5d
#1 0xffffffff80b57466 at vpanic+0x136
#2 0xffffffff80b57323 at panic+0x43
#3 0xffffffff81059436 at trap_pfault+0x3c6
#4 0xffffffff81030608 at calltrap+0x8
#5 0xffffffff83549cc1 at pf_test+0xb51
#6 0xffffffff83565423 at pf_check_in+0x33
#7 0xffffffff80ca1478 at pfil_mbuf_in+0x38
#8 0xffffffff80d1d629 at ip_input+0x349
#9 0xffffffff80c9ecb8 at swi_net+0x128
#10 0xffffffff80b11569 at ithread_loop+0x239
#11 0xffffffff80b0db3b at fork_exit+0x7b
#12 0xffffffff8103162e at fork_trampoline+0xe
Uptime: 24s
--
You are receiving this mail because:
You are the assignee for the bug.
