Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Jun 2004 14:03:55 +0000
From:      Jens Rehsack <rehsack@liwing.de>
To:        Damian Gerow <dgerow@afflictions.org>
Cc:        current@freebsd.org
Subject:   Re: ipf 3.4.35 woes
Message-ID:  <40DADF4B.5020601@liwing.de>
In-Reply-To: <20040623155702.GD52737@afflictions.org>
References:  <20040623020801.GA156@afflictions.org> <20040623155702.GD52737@afflictions.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <gallatin@cs.duke.edu> - 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40DADF4B.5020601>