From owner-freebsd-current@FreeBSD.ORG Thu Jun 24 14:24:21 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 09A9E16A4CE for ; Thu, 24 Jun 2004 14:24:21 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3627543D45 for ; Thu, 24 Jun 2004 14:24:20 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pandora.afflictions.org (Postfix) with ESMTP id B050178C7C for ; Thu, 24 Jun 2004 10:25:11 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 0D784170C3; Thu, 24 Jun 2004 10:23:48 -0400 (EDT) Date: Thu, 24 Jun 2004 10:23:48 -0400 From: Damian Gerow To: freebsd-current@freebsd.org Message-ID: <20040624142347.GD28051@afflictions.org> Mail-Followup-To: freebsd-current@freebsd.org References: <200406232148.07916.akbeech@northwindcom.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 5.2-CURRENT on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.6i Subject: Re: Panic on today's -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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 14:24:21 -0000 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.