From owner-freebsd-net@FreeBSD.ORG Thu Sep 29 19:01:17 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C21F11065670 for ; Thu, 29 Sep 2011 19:01:17 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id 7CEDC8FC0A for ; Thu, 29 Sep 2011 19:01:17 +0000 (UTC) Received: from [127.0.0.1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p8TJ0q6K020428; Thu, 29 Sep 2011 12:00:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1317322852; bh=w3LgCm4wMP7/pGJlTp6toZiV//o4cuDmYTU92ge7H7w=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=Gg46KjqCYbWAE0hVAhaNAEtphtanKAOPq2RzjbeRkDghSugGBfHw/IBFYtAb811LH RzbKDa0SXsD3uQ1FMzmVLLJit9jexmrsisZDG8Vg38tB44WhHqmqyJRt3tSV5e0bg3 yjjB28bfKX1SOOsYnawWafDqKASjk+UcskSg6zPY= From: Sean Bruno To: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: <4E84B882.7040400@quip.cz> References: <1317315666.2777.8.camel@hitfishpass-lx.corp.yahoo.com> <4E84B882.7040400@quip.cz> Content-Type: text/plain; charset="UTF-8" Date: Thu, 29 Sep 2011 12:00:51 -0700 Message-ID: <1317322851.2777.12.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" Subject: Re: bce(4) with IPMI X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2011 19:01:17 -0000 On Thu, 2011-09-29 at 11:27 -0700, Miroslav Lachman wrote: > Sean Bruno wrote: > > We've been getting reports of odd behavior on our Dell R410 machines > > when trying to use IPMI. The servers have two NIC's that we have > > assigned as the IPMI interface(bce0) and production interface(bce1) > > respectively. > > > > Since we don't actually configure bce0 in FreeBSD, we've found that the > > IPMI interface deactivated when bce(4) loads. I assume that the driver > > is not initializing the interface correctly in this case and the default > > case is to turn the interface off. Does it make sense to completely > > turn off the interface when there is an active link on the port, but no > > configuration assigned? > > I had similar problem few years ago with bge interface. There is > following loader tunable option for it: > > hw.bge.allow_asf > Allow the ASF feature for cooperating with IPMI. Can cause sys- > tem lockup problems on a small number of systems. Disabled by > default. > > Is it possible that something similar is needed for bce too? > > Miroslav Lachman Maybe. But from the changelogs of bce(4), it looks like the deactivation of the interface when not configured is pretty much intentional. Sean