From owner-freebsd-net@FreeBSD.ORG Thu Oct 13 18:48:13 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 A8BC3106564A; Thu, 13 Oct 2011 18:48:13 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2-b.corp.bf1.yahoo.com (mrout2-b.corp.bf1.yahoo.com [98.139.253.105]) by mx1.freebsd.org (Postfix) with ESMTP id 6AA678FC0C; Thu, 13 Oct 2011 18:48:12 +0000 (UTC) Received: from [127.0.0.1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout2-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p9DIlnh7009931; Thu, 13 Oct 2011 11:47:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1318531670; bh=aNa/x0Xfiw18RF4OAUgPJyzyXfGv/goT+1DEvEQoqUE=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=XwN7cPguoUDmtrEX6VGzHCVA7KTi1ACkjTMMIBoUjNUtlivLLGKXm9wJjC/QaJO7j zy/q/yrhae+hBkXnZMwn9NNYQ9e0pk+BSzukx/fBW4fJe2TT9rmFjpNQx2IEP4DEjE WJHdNOOBuYcNUmyebGaTpux1osuONn5F8T3jPVvo= From: Sean Bruno To: "pyunyh@gmail.com" In-Reply-To: <20111011224935.GC5661@michelle.cdnetworks.com> References: <1318264942.1236.6.camel@hitfishpass-lx.corp.yahoo.com> <20111010174749.GA1781@michelle.cdnetworks.com> <1318271046.1236.11.camel@hitfishpass-lx.corp.yahoo.com> <20111010190609.GB1781@michelle.cdnetworks.com> <1318278905.1236.18.camel@hitfishpass-lx.corp.yahoo.com> <20111010204456.GD1781@michelle.cdnetworks.com> <5D267A3F22FD854F8F48B3D2B523819385F3669A7D@IRVEXCHCCR01.corp.ad.broadcom.com> <1318356030.2724.11.camel@hitfishpass-lx.corp.yahoo.com> <20111011181219.GB5661@michelle.cdnetworks.com> <1318362745.2724.22.camel@hitfishpass-lx.corp.yahoo.com> <20111011224935.GC5661@michelle.cdnetworks.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 13 Oct 2011 11:47:48 -0700 Message-ID: <1318531668.2658.16.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" , David Christensen , "davidch@freebsd.org" , Pyun YongHyeon 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, 13 Oct 2011 18:48:13 -0000 On Tue, 2011-10-11 at 15:49 -0700, YongHyeon PYUN wrote: > On Tue, Oct 11, 2011 at 12:52:25PM -0700, Sean Bruno wrote: > > > > > > > The Broadcom MFW is configured to load/not load through an NVRAM > > > > > option that is likely not affected by the iDRAC BIOS settings. > > > > > To disable MFW you'd need to run the user diagnostic utility > > > > > (UXDIAG.EXE) with the following command line: > > > > > > > > > > C:\>uxdiag -mfw 0 > > > > > > > > > > To turn it back on run the following: > > > > > > > > > > C:\>uxdiag -mfw 1 > > > > > > > > > > You can find a bootable CD with the user diagnostic here: > > > > > http://www.broadcom.com/support/license.php?file=NXII/Xdiag-5.2.2.iso > > > > > > > > > > Dave > > > > > > > > > > > > > Ah, ok. > > > > > > > > > > > > Pyun: > > > > > > > > Should I do this on a host and validate your changes? > > > > > > > > > > That would be great if you can. Because some part of code is not > > > executed in my patch when firmware is not running. Previously > > > bce(4) executed that code regardless of firmware running state. > > > > > > > Sean > > > > > > > > > > > > > > Ran this on my Dell R410. I can clearly see that the tool is > > "disabling" the MFW bit, and that the dell bios interface to the IPMI > > controller/DRAC is impaired, however ... > > > > The system still thinks that the MFW bit is "ON" and proceeds normally > > in this case. The code still fails to detect that MFW is disabled. > > > > In addition, the IPMI driver attaches to "something" and I can poke at > > it via ipmitool. So, from the driver perspective, the attempt to detect > > MFW enabled doesn't work as the chipset still thinks that its "on". > > > > My patch relied on existing bce(4)'s logic for management firmware > state since public data sheet does not mention anything about that. > Probably David can give us more information. > > > I've commented out the code block that we're trying to work around in > > the yahoo code base for now. > > > > Sean > > As a follow up to this, Yahoo has decided to put the Dell "DRAC" adapter into their machines to work around this issue. So, all of this will go away on our existing systems. Since this technically affects all O/S versions of *nix I'm dropping this message in to close the email thread so others can see that its not a thing that -net@ can fix. Sean