Date: Mon, 21 Nov 2016 11:48:42 +0100 From: =?UTF-8?B?S2FtaWxhIFNvdcSNa292w6E=?= <kamila@ksp.sk> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-stable@freebsd.org, =?UTF-8?B?UmljaGFyZCBLcsOhbG92acSN?= <ri.kralovic@gmail.com> Subject: Re: VNET + pf => panic [Was: Panic when tearing down a VNET jail; pf mentioned in stack trace] Message-ID: <CAO7yDHqsceBavE2JKuR8XrLiGn8k2pSkOZ=L7vgCj8ZWRem=Cg@mail.gmail.com> In-Reply-To: <B6F1358B-AE79-4DC5-A164-7C284E840CE4@lists.zabbadoz.net> References: <CAO7yDHr=NjsiNGkKNiF0TNthXNeVAuQ-VW8z0G5hTYV10CvMUw@mail.gmail.com> <B6F1358B-AE79-4DC5-A164-7C284E840CE4@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > I might have missed this; which version of FreeBSD are you running? Sorry, I forgot to mention this. 11.0-RELEASE-p3 (both on the host and in jails). Further exposure to crashes revealed that is probably connected to tearing down the jail after all, but with a few seconds delay -- the system is stable when I don't tear down jails. The iocage docs actually mention a problem with this and they have code for "warm restarts" in place, but I have not been able to find out more about this issue. Just wondering, is the -stable mailing list a good place, or should this be moved somewhere else? Here are some more stack traces: Nov 20 17:00:34 oresme kernel: Fatal trap 12: page fault while in kernel mode Nov 20 17:00:34 oresme kernel: cpuid = 6; apic id = 06 Nov 20 17:00:34 oresme kernel: fault virtual address = 0x1800 Nov 20 17:00:34 oresme kernel: fault code = supervisor write data, page not present Nov 20 17:00:34 oresme kernel: instruction pointer = 0x20:0xffffffff8263eaa1 Nov 20 17:00:34 oresme kernel: stack pointer = 0x28:0xfffffe085348b870 Nov 20 17:00:34 oresme kernel: frame pointer = 0x28:0xfffffe085348b8e0 Nov 20 17:00:34 oresme kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Nov 20 17:00:34 oresme kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Nov 20 17:00:34 oresme kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Nov 20 17:00:34 oresme kernel: current process = 473 (pf purge) Nov 20 17:00:34 oresme kernel: trap number = 12 Nov 20 17:00:34 oresme kernel: panic: page fault Nov 20 17:00:34 oresme kernel: cpuid = 6 Nov 20 17:00:34 oresme kernel: KDB: stack backtrace: Nov 20 17:00:34 oresme kernel: #0 0xffffffff80aa8787 at kdb_backtrace+0x67 Nov 20 17:00:34 oresme kernel: #1 0xffffffff80a5d632 at vpanic+0x182 Nov 20 17:00:34 oresme kernel: #2 0xffffffff80a5d4a3 at panic+0x43 Nov 20 17:00:34 oresme kernel: #3 0xffffffff80f3cd51 at trap_fatal+0x351 Nov 20 17:00:34 oresme kernel: #4 0xffffffff80f3cf43 at trap_pfault+0x1e3 Nov 20 17:00:34 oresme kernel: #5 0xffffffff80f3c4ec at trap+0x26c Nov 20 17:00:34 oresme kernel: #6 0xffffffff80f1f521 at calltrap+0x8 Nov 20 17:00:34 oresme kernel: #7 0xffffffff8263e32d at pf_purge_expired_states+0x12d Nov 20 17:00:34 oresme kernel: #8 0xffffffff8263e1bb at pf_purge_thread+0x13b Nov 20 17:00:34 oresme kernel: #9 0xffffffff80a13e85 at fork_exit+0x85 Nov 20 17:00:34 oresme kernel: #10 0xffffffff80f1fa5e at fork_trampoline+0xe Nov 20 17:53:34 oresme kernel: Fatal trap 12: page fault while in kernel mode Nov 20 17:53:34 oresme kernel: cpuid = 1; apic id = 01 Nov 20 17:53:34 oresme kernel: fault virtual address = 0x400 Nov 20 17:53:34 oresme kernel: fault code = supervisor write data, page not present Nov 20 17:53:34 oresme kernel: instruction pointer = 0x20:0xffffffff8263eaa1 Nov 20 17:53:34 oresme kernel: stack pointer = 0x28:0xfffffe0853157870 Nov 20 17:53:34 oresme kernel: frame pointer = 0x28:0xfffffe08531578e0 Nov 20 17:53:34 oresme kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Nov 20 17:53:34 oresme kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Nov 20 17:53:34 oresme kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Nov 20 17:53:34 oresme kernel: current process = 477 (pf purge) Nov 20 17:53:34 oresme kernel: trap number = 12 Nov 20 17:53:34 oresme kernel: panic: page fault Nov 20 17:53:34 oresme kernel: cpuid = 1 Nov 20 17:53:34 oresme kernel: KDB: stack backtrace: Nov 20 17:53:34 oresme kernel: #0 0xffffffff80aa8787 at kdb_backtrace+0x67 Nov 20 17:53:34 oresme kernel: #1 0xffffffff80a5d632 at vpanic+0x182 Nov 20 17:53:34 oresme kernel: #2 0xffffffff80a5d4a3 at panic+0x43 Nov 20 17:53:34 oresme kernel: #3 0xffffffff80f3cd51 at trap_fatal+0x351 Nov 20 17:53:34 oresme kernel: #4 0xffffffff80f3cf43 at trap_pfault+0x1e3 Nov 20 17:53:34 oresme kernel: #5 0xffffffff80f3c4ec at trap+0x26c Nov 20 17:53:34 oresme kernel: #6 0xffffffff80f1f521 at calltrap+0x8 Nov 20 17:53:34 oresme kernel: #7 0xffffffff8263e32d at pf_purge_expired_states+0x12d Nov 20 17:53:34 oresme kernel: #8 0xffffffff8263e1bb at pf_purge_thread+0x13b Nov 20 17:53:34 oresme kernel: #9 0xffffffff80a13e85 at fork_exit+0x85 Nov 20 17:53:34 oresme kernel: #10 0xffffffff80f1fa5e at fork_trampoline+0xe I will try to reproduce this in a VM and look at it (but I am new to all things FreeBSD and rather busy with my studies, so I can't promise anything). Any pointers would be welcome. Thanks! Kamila
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAO7yDHqsceBavE2JKuR8XrLiGn8k2pSkOZ=L7vgCj8ZWRem=Cg>