From owner-freebsd-stable@FreeBSD.ORG Sat May 4 12:07:21 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1F98277 for ; Sat, 4 May 2013 12:07:21 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by mx1.freebsd.org (Postfix) with ESMTP id B00C416D5 for ; Sat, 4 May 2013 12:07:20 +0000 (UTC) Received: by mail-ee0-f44.google.com with SMTP id t10so1146442eei.31 for ; Sat, 04 May 2013 05:07:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=jI8f/SCM1CXJjJg95yv9WDssUO4oDTdKhniQPO76Hv0=; b=goCTgAvm3V0zT8OZ+vaPKaDWqbFCCBGOb//XDoADNUVxcppVZezAdKH6r//k3yP2GI lcmQnOK0mpDnqJK9Xh079MXmUkEPhdpo7mkc2DmDUueBLz/ql1okkbJrsMUy2EksBWJr nRQJRlv4TksGjGbuEMXvUbTq+Nv3xdIECD0SYoD05ApkGM030sJh8Fb42pWfwqPHrBlS 4zpAe5dC3Gpis0A79A9sW9cv58J3juL8w7iPpfbbHQtFeNk3X/ooWEhgL7+EDFamJ0ga QwLay6T/4ug693s04aRhJ8rtllgWtzooSrtfoLPD1cDL0V6rIJQe/5MrOg1+YRrmj8I1 gQkQ== X-Received: by 10.15.32.71 with SMTP id z47mr29843093eeu.3.1367669234465; Sat, 04 May 2013 05:07:14 -0700 (PDT) Received: from localhost ([178.150.115.244]) by mx.google.com with ESMTPSA id n7sm21475496eeo.0.2013.05.04.05.07.12 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sat, 04 May 2013 05:07:13 -0700 (PDT) Sender: Mikolaj Golub Date: Sat, 4 May 2013 15:07:11 +0300 From: Mikolaj Golub To: KIRIYAMA Kazuhiko Subject: Re: Vimage Jail kernel crashed Message-ID: <20130504120710.GB70992@gmail.com> References: <201305040552.r445qNB3023430@pis.elm.toba-cmt.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201305040552.r445qNB3023430@pis.elm.toba-cmt.ac.jp> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 May 2013 12:07:21 -0000 On Sat, May 04, 2013 at 02:52:23PM +0900, KIRIYAMA Kazuhiko wrote: > May 4 11:19:46 xxxxxx kernel: Fatal trap 12: page fault while in kernel mode > May 4 11:19:46 xxxxxx kernel: cpuid = 2; apic id = 02 > May 4 11:19:46 xxxxxx kernel: fault virtual address = 0x7818c3798 > May 4 11:19:46 xxxxxx kernel: fault code = supervisor write data, page not present > May 4 11:19:46 xxxxxx kernel: instruction pointer = 0x20:0xffffffff8162c19e > May 4 11:19:46 xxxxxx kernel: stack pointer = 0x28:0xffffff8121b22860 > May 4 11:19:46 xxxxxx kernel: frame pointer = 0x28:0xffffff8121b22870 > May 4 11:19:46 xxxxxx kernel: code segment = base 0x0, limit 0xfffff, type 0x1b > May 4 11:19:46 xxxxxx kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 > May 4 11:19:46 xxxxxx kernel: processor eflags = interrupt enabled, resume, IOPL = 0 > May 4 11:19:46 xxxxxx kernel: current process = 15360 (ifconfig) > May 4 11:19:46 xxxxxx kernel: trap number = 12 > May 4 11:19:46 xxxxxx kernel: panic: page fault > May 4 11:19:46 xxxxxx kernel: cpuid = 2 > May 4 11:19:46 xxxxxx kernel: KDB: stack backtrace: > May 4 11:19:46 xxxxxx kernel: #0 0xffffffff80923446 at kdb_backtrace+0x66 > May 4 11:19:46 xxxxxx kernel: #1 0xffffffff808ed0be at panic+0x1ce > May 4 11:19:46 xxxxxx kernel: #2 0xffffffff80c7e330 at trap_fatal+0x290 > May 4 11:19:46 xxxxxx kernel: #3 0xffffffff80c7e668 at trap_pfault+0x1e8 > May 4 11:19:46 xxxxxx kernel: #4 0xffffffff80c7ec6e at trap+0x3be > May 4 11:19:46 xxxxxx kernel: #5 0xffffffff80c682ef at calltrap+0x8 > May 4 11:19:46 xxxxxx kernel: #6 0xffffffff8162c76d at pfi_change_group_event+0x4d > May 4 11:19:46 xxxxxx kernel: #7 0xffffffff809a0d3b at if_delgroup+0x38b > May 4 11:19:46 xxxxxx kernel: #8 0xffffffff809a7846 at if_clone_destroyif+0x136 > May 4 11:19:46 xxxxxx kernel: #9 0xffffffff809a831a at if_clone_destroy+0x17a > May 4 11:19:46 xxxxxx kernel: #10 0xffffffff809a5892 at ifioctl+0x482 > May 4 11:19:46 xxxxxx kernel: #11 0xffffffff80934ef6 at kern_ioctl+0x106 > May 4 11:19:46 xxxxxx kernel: #12 0xffffffff8093513d at sys_ioctl+0xfd > May 4 11:19:46 xxxxxx kernel: #13 0xffffffff80c7dc10 at amd64_syscall+0x540 > May 4 11:19:46 xxxxxx kernel: #14 0xffffffff80c685d7 at Xfast_syscall+0xf7 It looks like it crashed when referring vnet that had already been destroyed, in pfi_change_group_event hook. > Is there any suggestions? VIMAGE+pf support is fragile. If it works for someone it is rather by accident. I expect replacing pf with ipfw_nat or natd will give better results. If you still prefer pf, you may try destroying epair interface before destroying vnet, e.g. using prestop rc.d/jail hooks instead of poststop, if it is possible. -- Mikolaj Golub