From owner-freebsd-current@FreeBSD.ORG Thu Jun 24 23:03:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 475E316A4CE for ; Thu, 24 Jun 2004 23:03:43 +0000 (GMT) Received: from lakermmtao04.cox.net (lakermmtao04.cox.net [68.230.240.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C662143D2D for ; Thu, 24 Jun 2004 23:03:42 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.localnet.net ([68.11.71.51]) by lakermmtao04.cox.net ESMTP <20040624230308.YWXO29176.lakermmtao04.cox.net@dolphin.localnet.net>; Thu, 24 Jun 2004 19:03:08 -0400 Received: from dolphin.localnet.net (localhost.localnet.net [127.0.0.1]) i5ON36Ag023977; Thu, 24 Jun 2004 18:03:06 -0500 (CDT) (envelope-from conrads@dolphin.localnet.net) Received: (from conrads@localhost) by dolphin.localnet.net (8.12.11/8.12.11/Submit) id i5ON35ql023776; Thu, 24 Jun 2004 18:03:05 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040624193220.GB878@gothmog.gr> Date: Thu, 24 Jun 2004 18:03:05 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Giorgos Keramidas cc: Damian Gerow cc: freebsd-current@freebsd.org Subject: Re: Panic on today's -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2004 23:03:43 -0000 On 24-Jun-2004 Giorgos Keramidas wrote: > On 2004-06-24 14:22, "Conrad J. Sabatier" wrote: >> On 24-Jun-2004 Damian Gerow wrote: >> > See my thread 'ipf 3.4.35 woes' -- I'm using ipf, but not pf, and >> > seeing exactly the same thing. And if I turn off the loading of >> > ipf >> > rulesets on boot, the panic goes away. Reloading them manually >> > afterwards doesn't cause the panic. >> >> Just upgraded the system and tried this. It worked without the >> loading >> of any ipf/ipnat stuff at boot time. Manually loading the rules >> after >> the system was up was fine, just as you said. >> >> I removed pf from my kernel, btw, since I wasn't using it anyway, >> but >> still have ipf (obviously). > > Try applying this minor diff to today's kernel: > > %% > Index: sys/contrib/ipfilter/netinet/fil.c > =================================================================== > RCS file: /home/ncvs/src/sys/contrib/ipfilter/netinet/fil.c,v > retrieving revision 1.38 > diff -u -r1.38 fil.c > --- sys/contrib/ipfilter/netinet/fil.c 21 Jun 2004 22:46:35 > -0000 1.38 > +++ sys/contrib/ipfilter/netinet/fil.c 24 Jun 2004 19:17:33 -0000 > @@ -2155,9 +2155,6 @@ > ip_natsync(ifp); > ip_statesync(ifp); > } > -# if defined(__FreeBSD_version) && (__FreeBSD_version >= 500043) > - IFNET_RUNLOCK(); > -# endif > ip_natsync((struct ifnet *)-1); > # if defined(__FreeBSD_version) && (__FreeBSD_version >= 500043) > IFNET_RUNLOCK(); > %% > Worked. Thanks! -- Conrad J. Sabatier -- "In Unix veritas"