From owner-freebsd-net@FreeBSD.ORG Thu Feb 23 18:23:50 2012 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 2C5401065679; Thu, 23 Feb 2012 18:23:50 +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 D4DD68FC0C; Thu, 23 Feb 2012 18:23:48 +0000 (UTC) Received: from [IPv6:::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 q1NINNVE018798; Thu, 23 Feb 2012 10:23:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1330021404; bh=/Zr4Vg75EVt9qV0jEBtbC+fXruciB/5PkWcS3MfIVII=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=MytfW5OXovoXzMwt1k3vvPR7daHlqnezJ8pWqWNyHmQX5gU+qDje5+7Ir6yKa6Rw4 fPX/6/GnhhhADOlwuygS0Ijnh5/r9CcZYuZf68N53xbEIo2kX0LbE3NroPOYV13I98 3GgqA6qrfPTwZOvJYy8PA0uM5uM2IgIV4FXjVYFo= From: Sean Bruno To: "pyunyh@gmail.com" In-Reply-To: <20120223213344.GC13815@michelle.cdnetworks.com> References: <1329958728.78750.6.camel@powernoodle-l7.corp.yahoo.com> <20120223213344.GC13815@michelle.cdnetworks.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 23 Feb 2012 10:23:23 -0800 Message-ID: <1330021403.3443.11.camel@powernoodle-l7.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" Subject: Re: bge(4) failure, Dell 12G hardware, BCM5720C 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, 23 Feb 2012 18:23:50 -0000 > As you see ukphy(4) was attached to bge2 so it may cause various > issues. > Is bge2 ASF/IPMI enabled interface? It seems ASF handling in > bge(4) causes more trouble on recent controllers. Unfortunately > disabling ASF may also trigger other problems like NMI. > I believe bge(4) should always honor ASF/IMPI firmware instead of > relying on hw.bge.allow_asf tunable and have to strictly follow > firmware handshake sequence. Just ignoring ASF/IMPI firmware seems > to confuse firmware. > Unfortunately all these information is undocumented and fixing it > requires real hardware access. ASF/IPMI -- I've tried disabling things, but it just fails miserably. I can at least get the host to a login via serial console and poke at things. Do you want me to rig up a test for you on this box? I suspect I can do something temporarily in the freebsd cluster with this box. Sean