From owner-freebsd-jail@FreeBSD.ORG Thu Jun 3 14:00:06 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 3E725106566B for ; Thu, 3 Jun 2010 14:00:06 +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 01A398FC1D for ; Thu, 3 Jun 2010 14:00:06 +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 o53E05li083249 for ; Thu, 3 Jun 2010 14:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o53E05Aw083248; Thu, 3 Jun 2010 14:00:05 GMT (envelope-from gnats) Date: Thu, 3 Jun 2010 14:00:05 GMT Message-Id: <201006031400.o53E05Aw083248@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:00:06 -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 15:32:03 +0200 This is a multi-part message in MIME format. ------_=_NextPart_001_01CB0321.2763EF58 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I've obtained some more information. =20 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. =20 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 =20 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. =20 Today I've built a debugging kernel with the options you suggested. I was able to get a backtrace with DDB. =20 You can find the panic here: http://tweakers.net/ext/f/iirS2Omm8Nfmbpb0BLKSRSzY/full.jpg =20 and the backtrace I did here: http://tweakers.net/ext/f/doP5G3aux6tSZdZt6hTtaWTR/full.jpg =20 =20 The backtrace has 2 pf_route calls so that confirms again my hunch. =20 This must be caused by kernel code changes made from 8.0p2 to 8.0p3 8.0p2 did not cause the kernel panic. =20 ------_=_NextPart_001_01CB0321.2763EF58 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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<= /span>

and the backtrace I did = here:

http://tweakers.net/ext/f/doP5G3aux6tSZdZt6hTtaWTR/full.jpg<= /span>

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.

------_=_NextPart_001_01CB0321.2763EF58--