Date: Thu, 9 Sep 2004 14:58:52 -0600 From: Mike Durian <durian@boogie.com> To: Hannes Mehnert <hannes@mehnert.org> Cc: freebsd-net@freebsd.org Subject: Re: Racoon breakage with recent kernel - what NOT to do Message-ID: <200409091458.53088.durian@boogie.com> In-Reply-To: <20040909200142.GD1128@mehnert.org> References: <200406091423.31355.durian@boogie.com> <20040909202955.438a4327@dev.lan.Awfulhak.org> <20040909200142.GD1128@mehnert.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <hannes@mehnert.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409091458.53088.durian>