From owner-freebsd-jail@FreeBSD.ORG Thu Jun 3 14:30:04 2010 Return-Path: Delivered-To: freebsd-jail@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CA0C1065670 for ; Thu, 3 Jun 2010 14:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (unknown [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0393A8FC0A for ; Thu, 3 Jun 2010 14:30:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o53EU3bN009012 for ; Thu, 3 Jun 2010 14:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o53EU3c5009007; Thu, 3 Jun 2010 14:30:03 GMT (envelope-from gnats) Date: Thu, 3 Jun 2010 14:30:03 GMT Message-Id: <201006031430.o53EU3c5009007@freefall.freebsd.org> To: freebsd-jail@FreeBSD.org From: Cc: Subject: Re: kern/147162: [jail] [panic] Page Fault / Kernel panic when jail starts on boot X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom.DEWAELE@abvv.be List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2010 14:30:04 -0000 The following reply was made to PR kern/147162; it has been noted by GNATS. From: To: , Cc: Subject: Re: kern/147162: [jail] [panic] Page Fault / Kernel panic when jail starts on boot Date: Thu, 3 Jun 2010 16:26:25 +0200 I've obtained some more information. I had a hunch this was caused by a PF rule. I disabled PF and the jails did not cause a panic. Then I disabled the suspicious rule and again no panic. Re-enabled the rule -> panic. This is the rule that is either directly or indirectly involved in the kernel panic: pass out quick route-to (lagg0 10.200.0.1) from 10.200.0.0/24 to ! 10.200.0.0/24 I have this rule because my jails are on another vlan so they need to use another interface for outgoing packets. The problem must be linked to this rerouting. Today I've built a debugging kernel with the options you suggested. I was able to get a backtrace with DDB. You can find the panic here: http://tweakers.net/ext/f/iirS2Omm8Nfmbpb0BLKSRSzY/full.jpg and the backtrace I did here: http://tweakers.net/ext/f/doP5G3aux6tSZdZt6hTtaWTR/full.jpg The backtrace has 2 pf_route calls so that confirms again my hunch. This must be caused by kernel code changes made from 8.0p2 to 8.0p3 8.0p2 did not cause the kernel panic.