From owner-freebsd-current@FreeBSD.ORG Thu Jun 24 19:04:56 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 0F12C16A4CE for ; Thu, 24 Jun 2004 19:04:56 +0000 (GMT) Received: from northwindcom.dyndns.org (135-203-237-24.gci.net [24.237.203.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id C044643D58 for ; Thu, 24 Jun 2004 19:04:55 +0000 (GMT) (envelope-from akbeech@northwindcom.dyndns.org) Received: from localhost.dyndns.org (localhost.dyndns.org [127.0.0.1]) by northwindcom.dyndns.org (Postfix) with ESMTP id 4DBAD26FA; Thu, 24 Jun 2004 11:04:23 -0800 (AKDT) From: Beecher Rintoul Organization: NorthWind Communications To: freebsd-current@freebsd.org Date: Thu, 24 Jun 2004 11:04:21 -0800 User-Agent: KMail/1.6.2 References: <200406232148.07916.akbeech@northwindcom.dyndns.org> <20040624142347.GD28051@afflictions.org> In-Reply-To: <20040624142347.GD28051@afflictions.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406241104.22202.akbeech@northwindcom.dyndns.org> cc: Damian Gerow Subject: Re: Panic on today's -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: akbeech@northwindcom.dyndns.org 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 19:04:56 -0000 On Thursday 24 June 2004 06:23 am, Damian Gerow wrote: > Thus spake Conrad J. Sabatier (conrads@cox.net) [24/06/04 10:18]: > : On 24-Jun-2004 Beecher Rintoul wrote: > : > Hi, > : > > : > I'm getting a panic on today's -current kernel. I don't have a serial > : > cable so > : > I couldn't save the message, but it panics after loading lo0. > : > : Same here. Just after, or during, the configuration of lo0. > : > : On a normal boot, the next thing to appear just after lo0 is: > : > : filter sync'd > : starting dhclient > : > : Perhaps it has something to do with ipf and/or pf? I have both > : configured into my kernel. > > 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. Thanks, that did the trick. I much prefer having the kernel in sync with the userland. I would switch firewalls, but I have a ruleset that works and I don't like the idea of re-writing a new set. I still would like to figure out what the "This: not found" message is all about. I'm getting bombarded by mail from cron trying to save-entropy. Beech --------------------------------------------------------------------------------------- Beech Rintoul - System Administrator - akbeech@northwindcom.dyndns.org /"\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ ---------------------------------------------------------------------------------------