8.0-B4, Broadcom bge0 not working, HP Proliant DL385, amd64
jacques.fourie at gmail.com
Wed Sep 9 15:36:21 UTC 2009
On Tue, Sep 8, 2009 at 7:13 PM, Steven Hartland<killing at multiplay.co.uk> wrote:
> 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 at broadcom.com>
> I've enquired about this recently but havent seen a response as
>> Sorry, this is the 5709S and I haven't had an opportunity to
>> implement this PHY yet. Unfortunately 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). The registers are diffrerent so the effort is more
>> substantial. No estimate
>> yet on when I can get to it.
> ----- Original Message ----- From: "stuart cur"
> <nevtic at area51.capnet.state.tx.us>
> To: <freebsd-current at 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. Switching the cable to bge1 works correctly.
>> 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 -lv
>> from the very first boot.
>> freebsd-current at freebsd.org mailing list
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> This e.mail is private and confidential between Multiplay (UK) Ltd. and the
> person or entity to whom it is addressed. In the event of misdirection, the
> 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 at multiplay.co.uk.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at 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.
More information about the freebsd-current