From owner-freebsd-net@FreeBSD.ORG Mon Mar 19 23:58:46 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 130CF106566C; Mon, 19 Mar 2012 23:58:46 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id CBB318FC17; Mon, 19 Mar 2012 23:58:45 +0000 (UTC) Received: by dald2 with SMTP id d2so11493718dal.13 for ; Mon, 19 Mar 2012 16:58:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=MLCrfjpdYNxNqX4pIQiT/qdetCpXkTpRHzcN9nbyBxM=; b=FstdDY4WeeFxWmJogYJJJzCOvpKrp/QPCgwsm4Raj2yrX71eyXYUopRHGtPL1oRnkX 7QATSV50yTihosYYnlcZn3twxBpd+pArmyop2Iv2OtfUgs+pTXBxMMNUv1MBzYtgEDBv LTYAL4n0MZZs3yiT3ImaqRf+xT5vbubakMXPn/1YmpNnxzlkQdthJ/zpP6jctKz9mlZS D7LPkGtUh6XrF8ON+9SBLQ133BRUO/1eGYtnm9O9TzNsFmiFFNJ99F80lllMFEBPsVSR EKWczvA7b6I4UmEKbAi1pDlVkpDX18FEERK2GrwCd/Riw0OAFZsmC+ZgiwGofAX4GQuw lAhg== Received: by 10.68.135.100 with SMTP id pr4mr25823009pbb.79.1332201525279; Mon, 19 Mar 2012 16:58:45 -0700 (PDT) Received: from pyunyh@gmail.com ([114.111.62.249]) by mx.google.com with ESMTPS id b4sm12361821pbc.7.2012.03.19.16.58.42 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Mar 2012 16:58:44 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 20 Mar 2012 08:58:39 -0700 From: YongHyeon PYUN Date: Tue, 20 Mar 2012 08:58:39 -0700 To: Sean Bruno Message-ID: <20120320155839.GA11016@michelle.cdnetworks.com> References: <1329958728.78750.6.camel@powernoodle-l7.corp.yahoo.com> <20120223213344.GC13815@michelle.cdnetworks.com> <1330021403.3443.11.camel@powernoodle-l7.corp.yahoo.com> <20120224180653.GA18456@michelle.cdnetworks.com> <1332192431.7409.6.camel@powernoodle-l7.corp.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1332192431.7409.6.camel@powernoodle-l7.corp.yahoo.com> User-Agent: Mutt/1.4.2.3i 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 Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2012 23:58:46 -0000 On Mon, Mar 19, 2012 at 02:27:11PM -0700, Sean Bruno wrote: > On Fri, 2012-02-24 at 10:06 -0800, YongHyeon PYUN wrote: > > On Thu, Feb 23, 2012 at 10:23:23AM -0800, Sean Bruno wrote: > > > > > > > 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. > > > > > > > Hmm, I still have to understand what is correct handshake sequence > > for ASF/IPMI firmware. This handshake may be related with suspend/ > > resume as well as WOL. I'll let you know when I have experimental > > patch. > > > > > Sean > > > > > Hrm, looking at the BCM57XX programming guide, I see that there's a > section on ASF. Is that what you're looking for or is there a different > bit of information you are trying to find? > Yes the public data sheet mentions ASF specific registers. However what we want to know is communication interface between ASF/IPM firmware and driver. This would be done via several undocumented mailbox registers for each events(driver up/down, WOL configuration, suspend and resume etc). bge(4) does not care about registers that make ASF work. > Sean > > ref. http://www.broadcom.com/collateral/pg/57XX-PG105-R.pdf >