Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Oct 2011 16:06:18 -0700
From:      Sean Bruno <seanbru@yahoo-inc.com>
To:        David Christensen <davidch@broadcom.com>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, "davidch@freebsd.org" <davidch@freebsd.org>, Pyun YongHyeon <yongari@freebsd.org>
Subject:   RE: bce(4) with IPMI
Message-ID:  <1317683178.15510.25.camel@hitfishpass-lx.corp.yahoo.com>
In-Reply-To: <5D267A3F22FD854F8F48B3D2B523819385F35B4738@IRVEXCHCCR01.corp.ad.broadcom.com>
References:  <1317315666.2777.8.camel@hitfishpass-lx.corp.yahoo.com> <1317323418.2777.14.camel@hitfishpass-lx.corp.yahoo.com> <1317343996.2777.33.camel@hitfishpass-lx.corp.yahoo.com> <1317346748.2777.36.camel@hitfishpass-lx.corp.yahoo.com> <5D267A3F22FD854F8F48B3D2B523819385F35B4738@IRVEXCHCCR01.corp.ad.broadcom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2011-10-03 at 15:30 -0700, David Christensen wrote:
> > > > I should probably say, this is freebsd7.  So I'll peruse the
> > changelogs
> > > > and see if 7 is missing something here.
> > > >
> > > > sean
> > >
> > > commenting this change out seems to be helping quite a bit with my
> > > issue.  I think that this behavior may be wrong in the IPMI shared/nic
> > > case.  Thoughts?
> > >
> > >
> > http://svnweb.freebsd.org/base/head/sys/dev/bce/if_bce.c?r1=210261&r2=210263
> > 
> 
> The main reason bce(4) needs to coordinate with NC-SI/IPMI 
> firmware is to make sure only one software entity manipulates 
> PHY registers.  When bce(4) is loaded it will have priority 
> over firmware (e.g. autoneg, speed, and duplex settings will 
> be set by the host).  If you don't bring up the interface in
> the host the firmware isn't authorized to do so, which sounds
> like your problem.
> 
> Current bce(4) behavior notifies firmware that host driver
> is running when resetting the device in bce_attach().  We
> tell firmware that host driver is still running through
> bce_pulse().  Not sure how to handle the FreeBSD model where
> the driver load doesn't immediately bring the link up.
> 
> Dave 
> 

Hrm, understood.

What are your thoughts on noting that the IPMI f/w is running and
leaving the interface up?  I'm poking around trying to find the right
register bits at initialization to see that this is the case.

What's even more strange is that our freebsd6 instances don't have this
problem.  

Sean




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