From owner-freebsd-stable@freebsd.org Mon Nov 21 10:49:05 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4A9DC4CD66 for ; Mon, 21 Nov 2016 10:49:05 +0000 (UTC) (envelope-from kamisouckova@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A0B51263 for ; Mon, 21 Nov 2016 10:49:05 +0000 (UTC) (envelope-from kamisouckova@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id a20so25947526wme.2 for ; Mon, 21 Nov 2016 02:49:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=amUjJ/DO2UnUIN3414P45JHgXdjPizlR+VcuAFR06QQ=; b=tGXYdZNvalzrcXWooAf5vgZKeU2Z5FDN2f3zuSqU24hwnjUmbPgULGaKo2w9pFcfuh o1t6Zth4lZcLeZ2OPGEcGWSQjNh4dxEb73Pf42kBQyHmNk+HPg0I4TlieFJ52w9Dy6Db at4XFBSBGNYiRQsKHybqUzRtLfau70emw4T4rZPVkWg+g1+ZJejijqTss3pabdR62deS dWaLKaPwmwz5PfBlSq2kaPkraR0ED68bdTjiZnKvSVG6JVq5Us9ipjpkM1W1xkdhSJCL fkNHZRkcG2Rhu58Q9C1OJuC5BrWmAnx8AWSKLcXEue/VYfpBR3bbaSgpOUzkWFQQja5q GXQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=amUjJ/DO2UnUIN3414P45JHgXdjPizlR+VcuAFR06QQ=; b=evLwNQQjiEpTpNgs0ueOXle/dLNxKfDJT2vnuHtO+/QJl69JI8MN8K6L+KyEuj5SED Qpo1ODU+AgEYhw08uxfNPzRui2L1ykwplVX2jIhi00W94SYsXLUpI/noy6L7dGsvUo9V hkOLSUXKfoAnrXhlsk3h0fTl4uVNx4P6tyGzgzzaww/Rbk0pgpK0XjNR6dQdgKeOrsws MBAW6nRIQoGWz3sGNnCpJ+udxz5p1pZP3gGRyTYC7PqHM76H1OiYq3GhdakNFJOBjdjD ZiX650IPWch5/4hRT/P3FZTQuJzrDSALil75BHxQkJKHHt7lM4ntv/bVzAs1A6N3vNSz pp9A== X-Gm-Message-State: AKaTC01r3AB/g19UEYZ3s3/ExwFF1ssQiSam8ZC3B0jIFL3WCy2ZKj4ZRygEP1+v2nkv3m1wFmBkjGwIv2JtIQ== X-Received: by 10.28.175.204 with SMTP id y195mr15056562wme.106.1479725343529; Mon, 21 Nov 2016 02:49:03 -0800 (PST) MIME-Version: 1.0 Sender: kamisouckova@gmail.com Received: by 10.194.29.101 with HTTP; Mon, 21 Nov 2016 02:48:42 -0800 (PST) In-Reply-To: References: From: =?UTF-8?B?S2FtaWxhIFNvdcSNa292w6E=?= Date: Mon, 21 Nov 2016 11:48:42 +0100 X-Google-Sender-Auth: 34lQ5I6dIdGYPM_3DuM4miLY37Y Message-ID: Subject: Re: VNET + pf => panic [Was: Panic when tearing down a VNET jail; pf mentioned in stack trace] To: "Bjoern A. Zeeb" Cc: freebsd-stable@freebsd.org, =?UTF-8?B?UmljaGFyZCBLcsOhbG92acSN?= Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 10:49:05 -0000 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