Date: Wed, 1 Jul 2009 17:37:05 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: Alexey Dokuchaev <danfe@nsu.ru>, Robert Watson <rwatson@freebsd.org> Subject: Re: Kernel panic with if_sf.ko Message-ID: <200907011737.15525.jkim@FreeBSD.org> In-Reply-To: <alpine.BSF.2.00.0907012116370.27367@fledge.watson.org> References: <20090701162108.GA33681@regency.nsu.ru> <200907011613.10550.jkim@FreeBSD.org> <alpine.BSF.2.00.0907012116370.27367@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907011737.15525.jkim>