From owner-freebsd-current@FreeBSD.ORG Wed Jul 1 20:17:25 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C084C10656F2; Wed, 1 Jul 2009 20:17:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9A2388FC20; Wed, 1 Jul 2009 20:17:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 2321D46B46; Wed, 1 Jul 2009 16:17:25 -0400 (EDT) Date: Wed, 1 Jul 2009 21:17:25 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jung-uk Kim In-Reply-To: <200907011613.10550.jkim@FreeBSD.org> Message-ID: References: <20090701162108.GA33681@regency.nsu.ru> <200907011613.10550.jkim@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Alexey Dokuchaev , freebsd-current@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 20:17:26 -0000 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... Robert N M Watson Computer Laboratory University of Cambridge