Date: Tue, 20 Mar 2012 08:58:39 -0700 From: YongHyeon PYUN <pyunyh@gmail.com> To: Sean Bruno <seanbru@yahoo-inc.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: bge(4) failure, Dell 12G hardware, BCM5720C Message-ID: <20120320155839.GA11016@michelle.cdnetworks.com> In-Reply-To: <1332192431.7409.6.camel@powernoodle-l7.corp.yahoo.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120320155839.GA11016>