From owner-freebsd-current@FreeBSD.ORG Thu Jun 24 14:31:04 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 B591916A537 for ; Thu, 24 Jun 2004 14:31:03 +0000 (GMT) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5774443D49 for ; Thu, 24 Jun 2004 14:31:02 +0000 (GMT) (envelope-from rehsack@liwing.de) Received: (qmail 82504 invoked from network); 24 Jun 2004 14:03:55 -0000 Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164]) (envelope-sender ) by mail.liwing.de (qmail-ldap-1.03) with SMTP for ; 24 Jun 2004 14:03:55 -0000 Message-ID: <40DADF4B.5020601@liwing.de> Date: Thu, 24 Jun 2004 14:03:55 +0000 From: Jens Rehsack User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040517 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: Damian Gerow References: <20040623020801.GA156@afflictions.org> <20040623155702.GD52737@afflictions.org> In-Reply-To: <20040623155702.GD52737@afflictions.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: darrenr@freebsd.org cc: current@freebsd.org Subject: Re: ipf 3.4.35 woes 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:31:05 -0000 Damian Gerow wrote: > Thus spake Damian Gerow (dgerow@afflictions.org) [22/06/04 22:10]: > : The upgrade to ipf 3.4.35 is causing me grief. And yes, my kernel and > : userland are in sync: > > As someone pointed out to me, this is before the pf import -- these sources > are from the eve of the ipf import, just after the two fixes were committed. > > I can completely and totally reproduce this on every reboot, but for the > life of me, I can't reproduce it manually. It /appears/ to be either a > problem with bringing up lo0, or a problem bringing up fxp0 with dhclient. > Or something that might happen between those two steps, I'm not sure. I didn't to try to reproduce it manually but I tried to get a dumb. Not a chance today, I try again tomorrow respecting the hint from Andrew Gallatin - but for now I can report following: Compiling not an own kernel but the GENERIC brings following during initialization of lo0: panic: lock (sleep mutex) ifnet not locked @ /usr/src/sys/contrib/ipfilter/netinet/fil.c:2163 Maybe it helps a little. Best regards, Jens