From owner-freebsd-net@FreeBSD.ORG Thu Sep 9 19:30:13 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 ABF4816A4CE for ; Thu, 9 Sep 2004 19:30:13 +0000 (GMT) Received: from gw.Awfulhak.org (awfulhak.demon.co.uk [80.177.173.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 010DC43D5C for ; Thu, 9 Sep 2004 19:30:13 +0000 (GMT) (envelope-from brian@Awfulhak.org) Received: from dev.lan.Awfulhak.org (brian@dev.lan.Awfulhak.org [172.16.0.5]) by gw.Awfulhak.org (8.12.11/8.12.11) with SMTP id i89JTvFR042943; Thu, 9 Sep 2004 20:29:57 +0100 (BST) (envelope-from brian@Awfulhak.org) Date: Thu, 9 Sep 2004 20:29:55 +0100 From: Brian Somers To: Hannes Mehnert Message-ID: <20040909202955.438a4327@dev.lan.Awfulhak.org> In-Reply-To: <20040714185248.GC70193@mehnert.org> References: <200406091423.31355.durian@boogie.com> <200407121532.18503.durian@boogie.com> <20040714185248.GC70193@mehnert.org> X-Mailer: Sylpheed-Claws 0.9.12a (GTK+ 1.2.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on gw.lan.Awfulhak.org 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 19:30:13 -0000 On Wed, 14 Jul 2004 20:52:48 +0200, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > 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. This explains all of the mis-aligned mbuf frees that turn up and panic the system. In fact, I can't really explain *why* dtom() actually works, but that's the content of my other posting.... -- Brian Don't _EVER_ lose your sense of humour !