> What kind of bge? Are these the same onboard 5703 on IBM servers for
> which Matt Thomas(?)  added support, or something else again?

This is what dmesg says:

bge0 at pci0 dev 8 function 0: Broadcom BCM5702X Gigabit Ethernet
bge0: interrupting at irq 9
bge0: ASIC BCM5703 A2, Ethernet address 00:30:48:52:0d:85
brgphy0 at bge0 phy 1: BCM5703 1000BASE-T media interface, rev. 2
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto

> 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.

I have not actually seen this. The bge(4) interface I have seems to work
fine for 100 Mbit ethernet but I cannot get it to go to gigabit. I am
running -current from 08/29 or 08/31/2003 and it does not seem to work.
The lights on the Linksys gigabit switch indicate that it only
negotiated to 100 Mbit.

> >I have experienced the exact same problem except I am using a
Supermicro
> >X5SS8-GM motherboard which has an onboard bge(4) interface. I have
not
> >been able to get it to work with gigabit at all. 
> 
> That's what you would get if the driver is not applying the correct
> PHY/DSP patch for your particular hardware revision. What rev does the
> driver claim, and what are the acutal PCI register values?

Do I use "pcictl /dev/pci0 list" to get the PCI register values? The
dmesg output is above.

> FWIW,I had no problems (once the DSP patches were correct) with
> bcm5700s or 5704s, to Cisco Catalyst or Extreme Summit switches.
> 
> 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.

Let me know what other information you need. Thank you.

Bryan