Subject: Re: bge0 doesn't like to autodetect gigabit
To: Jonathan Stone <jonathan@DSG.Stanford.EDU>
From: Stephen Borrill <firstname.lastname@example.org>
Date: 09/03/2003 11:03:44
On Tue, 2 Sep 2003, Jonathan Stone wrote:
> In message <r02000100-1026-C3A32494DD2211D79B49000393D5E5DA@[10.0.1.30]>Bryan Vyhmeister writ
> >> I've noticed that IBM servers with onboard Broadcom gigabit ethernet
> >> to have issues when connected to gigabit switches. I've tried Netgear
> What kind of bge? Are these the same onboard 5703 on IBM servers for
> which Matt Thomas(?) added support, or something else again?
5703. dmesg section is:
bge0 at pci3 dev 4 function 0: Broadcom BCM5703X Gigabit Ethernet
bge0: interrupting at irq 7
bge0: ASIC BCM5703 A2, Ethernet address 00:02:55:b7:79:0d
brgphy0 at bge0 phy 1: BCM5703 1000BASE-T media interface, rev. 2
bge1 at pci3 dev 5 function 0: Broadcom BCM5703X Gigabit Ethernet
bge1: interrupting at irq 5
bge1: ASIC BCM5703 A2, Ethernet address 00:02:55:b7:79:0e
brgphy1 at bge1 phy 1: BCM5703 1000BASE-T media interface, rev. 2
> IIRC, that message (and calling bge_tick for link events) is allegedly
> a workaround for a hardware bug/misfeature on the bcm5700 chip: the
> hardware link-state FSM is broken and has to be checked in software.
> The driver should not be taking that path at all for a 5701 or newer.
That's a potential problem then. It definitely is calling it on BCM5703
> It would help to know *exactly* what family and chip is affected
> (e.g., bcm 5703, revision a2). If the driver doesn't give that much
> detail, we can figure it out from the PCI registers.