From owner-freebsd-current@FreeBSD.ORG Thu Oct 25 13:02:52 2007 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 2531C16A421 for ; Thu, 25 Oct 2007 13:02:52 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id AEC3B13C480 for ; Thu, 25 Oct 2007 13:02:51 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from anb.matik.com.br (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l9PD2hA0037701 for ; Thu, 25 Oct 2007 11:02:43 -0200 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-current@freebsd.org Date: Thu, 25 Oct 2007 11:02:32 -0200 User-Agent: KMail/1.9.7 References: <4712A4A8.7080503@FreeBSD.org> <200710241910.28201.joao@matik.com.br> <200710241904.47701.jkim@FreeBSD.org> In-Reply-To: <200710241904.47701.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710251102.33088.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: panic in 8-CURRENT / BGE hang 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: Thu, 25 Oct 2007 13:02:52 -0000 On Wednesday 24 October 2007 21:04:46 Jung-uk Kim wrote: > For remote server management, there are two major APIs: > > ASF by DMTF: > http://www.dmtf.org/standards/asf/ > > IPMI by Intel: > http://www.intel.com/design/servers/ipmi/ > > The main goal of the two technologies is the same, i.e., out-of-band > server management. =C2=A0Both use Remote Management and Control Protocol > (RMCP) for the network protocol but ASF is implemented on NIC > firmware level while IPMI is implemented on baseboard management > controller (BMC). =C2=A0Now BCM57xx firmware has built-in ASF stack and > the interface can be shared with BMC. =C2=A0If there is a BMC on-board and > network controller is shared, obviously you cannot just reset the > controller, etc. =C2=A0You have to 'tell' the firmware that you are about > to do critical things, such as reset, start, stop, link negotiation, > etc, so that it can communicate with BMC beforehand. =C2=A0If you turn on > hw.bge.allow_asf, it does just that. =C2=A0Unfortunately, it does not work > for all systems in the real world because they are not created equal, > e.g., different spec. revisions, hardware implementations, firmware, > BIOS, etc. =C2=A0Basically some system fails *without* it while some > system fails *with* it. =C2=A0Hence, the tunable was necessary. =C2=A0At = least, > that is how I understand it. thank you, that was great=20 but would really not harm to put something about resumed into the man page =2D-=20 Jo=C3=A3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br