Date: Wed, 9 Sep 2009 17:07:36 +0200 From: Jacques Fourie <jacques.fourie@gmail.com> To: Steven Hartland <killing@multiplay.co.uk> Cc: stuart cur <nevtic@area51.capnet.state.tx.us>, freebsd-current@freebsd.org Subject: Re: 8.0-B4, Broadcom bge0 not working, HP Proliant DL385, amd64 Message-ID: <be2f52430909090807t7cacb687x788c22bc27214b2d@mail.gmail.com> In-Reply-To: <7147C6D9FE26411197548D67E5025D75@multiplay.co.uk> References: <alpine.BSF.2.00.0909081113220.98111@area51.capnet.state.tx.us> <7147C6D9FE26411197548D67E5025D75@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 8, 2009 at 7:13 PM, Steven Hartland<killing@multiplay.co.uk> wr= ote: > I suspect its the same reason for issues with had with the subjects: > FreeBSD 7.0-RELEASE amd64 on Dell M600 Blade > kern/134658: [bce] bce driver fails on PowerEdge m610 blade. > Quote: "David Christensen" <davidch@broadcom.com> > > I've enquired about this recently but havent seen a response as > yet. > > =A0 Regards > =A0 Steve > >> Sorry, this is the 5709S and I haven't had an opportunity to >> implement this PHY yet. =A0Unfortunately it's more than just a >> change to miidevs since the SerDes is actually an IEEE clause >> 45 compliant device (instead of the more common Clause 22 devices found = in >> 1GbE controllers). =A0The registers are diffrerent so the effort is more >> substantial. =A0No estimate >> yet on when I can get to it. > > ----- Original Message ----- From: "stuart cur" > <nevtic@area51.capnet.state.tx.us> > To: <freebsd-current@freebsd.org> > Sent: Tuesday, September 08, 2009 5:32 PM > Subject: 8.0-B4, Broadcom bge0 not working, HP Proliant DL385, amd64 > > >> In 8.0-B4 for amd64, bge does not recognize that there is an active >> ethernet connection on bge0. =A0Switching the cable to bge1 works correc= tly. >> >> This seems to be the same issue as reported on July 21 by Oyvind Rakvag, >> but I saw no response to that report. >> >> Attached are the dmesg.boot, /var/log/messages, and output of pciconf -l= v >> from the very first boot. >> >> stu > > > >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > This e.mail is private and confidential between Multiplay (UK) Ltd. and t= he > person or entity to whom it is addressed. In the event of misdirection, t= he > recipient is prohibited from using, copying, printing or otherwise > disseminating it or any information contained in it. > In the event of misdirection, illegible or incomplete transmission please > telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > I experienced a similar issue with two 5787M based devices. If I disable gigabit advertisements for auto negotiation everything worked OK. With gigabit advertisements enabled, the auto negotiation got stuck in the next-page-wait state. The problem only occurs on the bge0 device. The bge1 device works with the gigabit advertisements enabled but ifconfig reports that the link is up at 100baseTX while it seems to be 1000baseT. Regards, Jacques
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?be2f52430909090807t7cacb687x788c22bc27214b2d>