From owner-freebsd-net@FreeBSD.ORG Thu Sep 9 20:59:01 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9559F16A4CE for ; Thu, 9 Sep 2004 20:59:01 +0000 (GMT) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65B7B43D55 for ; Thu, 9 Sep 2004 20:59:01 +0000 (GMT) (envelope-from durian@boogie.com) Received: from cpe-66-87-52-132.co.sprintbbd.net ([66.87.52.132] helo=mailhost.boogie.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1C5W0P-0003yR-00; Thu, 09 Sep 2004 13:58:57 -0700 Received: from man.boogie.com (man.boogie.com [192.168.1.3]) by mailhost.boogie.com (8.13.1/8.13.1) with ESMTP id i89Kwr77092151; Thu, 9 Sep 2004 14:58:53 -0600 (MDT) (envelope-from durian@boogie.com) From: Mike Durian To: Hannes Mehnert Date: Thu, 9 Sep 2004 14:58:52 -0600 User-Agent: KMail/1.7 References: <200406091423.31355.durian@boogie.com> <20040909202955.438a4327@dev.lan.Awfulhak.org> <20040909200142.GD1128@mehnert.org> In-Reply-To: <20040909200142.GD1128@mehnert.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409091458.53088.durian@boogie.com> cc: Brian Somers cc: freebsd-net@freebsd.org Subject: Re: Racoon breakage with recent kernel - what NOT to do X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Sep 2004 20:59:01 -0000 On Thursday 09 September 2004 02:01 pm, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > On Thu, Sep 09, 2004 at 08:29:55PM +0100, Brian Somers wrote: > > On Wed, 14 Jul 2004 20:52:48 +0200, Hannes Mehnert wrote: > > > On Mon, Jul 12, 2004 at 03:32:18PM -0600, Mike Durian wrote: > > > > This is just a follow-up to say the problem still exists in a > > > > -current system I built from source yesterday (7/11/04). Does anyone > > > > know what's going on? > > > > > > > > And to clarify, the URL listed above does show the same problem I'm > > > > seeing. > > > > > > A workaround is setting MSIZE to 320 in your kernel config: > > > options MSIZE=320 > > > > Well, I applied this tweak to my kernel config file (some time ago!) and > > it fixed the racoon issue.... **BUT** doing this badly breaks dtom() - > > all sorts of issues turn up when a data pointer can't be turned back into > > its owning mbuf pointer. > > I'm currently using MSIZE=512 and get no panic. I agree. I too received kernel panics when I used MSIZE=320. After changing it to MSIZE=512 my panics disappeared and racoon started to work. Maybe this MSIZE change should become the default. mike