Date: Mon, 27 Feb 2017 14:08:13 +0200 From: Ross <basarevych@gmail.com> To: freebsd-pf@freebsd.org Subject: sonewconn: pru_attach() failed and kernel panic in PF Message-ID: <CANmv3=xB0Kce4ZQ4GYBE0cNpam0jzGPX7dSYSVBPiT-sryCyHA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hello One of my machines panics almost every day. It is always like this: first there is a number of messages about "sonewconn: pcb 0xfffff80085478740: pru_attach() failed" at the same time and then panic. Here's an example: ... many lines of sonewconn ... Feb 27 13:41:43 core kernel: sonewconn: pcb 0xfffff8008575bcb0: pru_attach() failed Feb 27 13:41:43 core kernel: Feb 27 13:41:43 core kernel: Feb 27 13:41:43 core kernel: Fatal trap 12: page fault while in kernel mode Feb 27 13:41:43 core kernel: cpuid = 5; apic id = 0a Feb 27 13:41:43 core kernel: fault virtual address = 0x0 Feb 27 13:41:43 core kernel: fault code = supervisor write data, page not present Feb 27 13:41:43 core kernel: instruction pointer = 0x20:0xffffffff80e45383 Feb 27 13:41:43 core kernel: stack pointer = 0x28:0xfffffe00d7dd7f80 Feb 27 13:41:43 core kernel: frame pointer = 0x28:0xfffffe00d7dd7fe0 Feb 27 13:41:43 core kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Feb 27 13:41:43 core kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Feb 27 13:41:43 core kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Feb 27 13:41:43 core kernel: current process = 0 (em0 taskq) Feb 27 13:41:43 core kernel: trap number = 12 Feb 27 13:41:43 core kernel: panic: page fault Feb 27 13:41:43 core kernel: cpuid = 5 Feb 27 13:41:43 core kernel: KDB: stack backtrace: Feb 27 13:41:43 core kernel: #0 0xffffffff80b312c7 at kdb_backtrace+0x67 Feb 27 13:41:43 core kernel: #1 0xffffffff80ae5c92 at vpanic+0x182 Feb 27 13:41:43 core kernel: #2 0xffffffff80ae5b03 at panic+0x43 Feb 27 13:41:43 core kernel: #3 0xffffffff80fd6d51 at trap_fatal+0x351 Feb 27 13:41:43 core kernel: #4 0xffffffff80fd6f43 at trap_pfault+0x1e3 Feb 27 13:41:43 core kernel: #5 0xffffffff80fd64ec at trap+0x26c Feb 27 13:41:43 core kernel: #6 0xffffffff80fb9d61 at calltrap+0x8 Feb 27 13:41:43 core kernel: #7 0xffffffff80e4185e at uma_zfree_arg+0x4fe Feb 27 13:41:43 core kernel: #8 0xffffffff82442165 at pf_get_translation+0x2c5 Feb 27 13:41:43 core kernel: #9 0xffffffff824369d3 at pf_test_rule+0x2b3 Feb 27 13:41:43 core kernel: #10 0xffffffff82433e23 at pf_test+0x1a23 Feb 27 13:41:43 core kernel: #11 0xffffffff8244596d at pf_check_in+0x1d Feb 27 13:41:43 core kernel: #12 0xffffffff80c1e983 at pfil_run_hooks+0x83 Feb 27 13:41:43 core kernel: #13 0xffffffff80c82d7b at ip_input+0x3bb Feb 27 13:41:43 core kernel: #14 0xffffffff80c1d905 at netisr_dispatch_src+0xa5 Feb 27 13:41:43 core kernel: #15 0xffffffff80c0636a at ether_demux+0x12a Feb 27 13:41:43 core kernel: #16 0xffffffff80c06fc2 at ether_nh_input+0x322 Feb 27 13:41:43 core kernel: #17 0xffffffff80c1d905 at netisr_dispatch_src+0xa5 What should I do to fix it? PS This is FreeBSD 11.0-RELEASE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANmv3=xB0Kce4ZQ4GYBE0cNpam0jzGPX7dSYSVBPiT-sryCyHA>