From owner-freebsd-current@FreeBSD.ORG  Wed Jul  1 21:37:25 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 057DD106564A;
	Wed,  1 Jul 2009 21:37:25 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: freebsd-current@FreeBSD.org
Date: Wed, 1 Jul 2009 17:37:05 -0400
User-Agent: KMail/1.6.2
References: <20090701162108.GA33681@regency.nsu.ru>
	<200907011613.10550.jkim@FreeBSD.org>
	<alpine.BSF.2.00.0907012116370.27367@fledge.watson.org>
In-Reply-To: <alpine.BSF.2.00.0907012116370.27367@fledge.watson.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200907011737.15525.jkim@FreeBSD.org>
Cc: Alexey Dokuchaev <danfe@nsu.ru>, Robert Watson <rwatson@freebsd.org>
Subject: Re: Kernel panic with if_sf.ko
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jul 2009 21:37:25 -0000

On Wednesday 01 July 2009 04:17 pm, Robert Watson wrote:
> On Wed, 1 Jul 2009, Jung-uk Kim wrote:
> > On Wednesday 01 July 2009 12:21 pm, Alexey Dokuchaev wrote:
> >> I've started to observe the following rather annoying panic if I
> >> boot with if_sf loaded (via loader.conf) and having sf0
> >> configured via DHCP on recent -CURRENT.  If I comment out driver
> >> from loader.conf and load it manually (via kldload(8)) after
> >> system boots, it loads and gets configured just fine.
> >>
> >> Any clues here?  Attached is relevant dmesg + DDB trace (debug
> >> kernel with WITNESS).  I'm happy to provide any additional
> >> information (that is, ps/show uma/malloc, whatever).
> >
> > Last time I checked, bpf(4) with MAC caused a similar problem
> > when it is destroying bpf descriptor label.  GENERIC includes MAC
> > by default now.  If you don't need MAC, try removing "options
> > MAC" from your kernel configuration.
>
> I was not aware of this problem -- could you provide some more
> details?  Any panic caused by having MAC in the kernel is a bug...

It was about a month ago.  I had funny impression that you and sam 
were working on it cause it started happening when sam added bpf 
detach event handler and MAC was enabled by default.  Any way, I will 
let you know if I can reproduce the problem.

Jung-uk Kim