Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Feb 2012 10:23:23 -0800
From:      Sean Bruno <seanbru@yahoo-inc.com>
To:        "pyunyh@gmail.com" <pyunyh@gmail.com>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   Re: bge(4) failure, Dell 12G hardware, BCM5720C
Message-ID:  <1330021403.3443.11.camel@powernoodle-l7.corp.yahoo.com>
In-Reply-To: <20120223213344.GC13815@michelle.cdnetworks.com>
References:  <1329958728.78750.6.camel@powernoodle-l7.corp.yahoo.com> <20120223213344.GC13815@michelle.cdnetworks.com>

next in thread | previous in thread | raw e-mail | index | archive | help

> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1330021403.3443.11.camel>