Re: boot problems with bge(4)

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

On 06/03/11 14:18, Christoph Egger wrote:
> Hi,
>
>
> [...]
> bge0 at pci0 dev 20 function 6: Broadcom BCM5785G Gigabit Ethernet
> bge0: interrupting at ioapic1 pin 18, event channel 9
> bge0: unable to find PCIX capability
> bge0: firmware handshake timed out, val = 4b657654
> bge0: firmware handshake timed out, val = 4b657654
> bge0: ASIC unknown BCM5785 (0x5785041), Ethernet address 00:00:1a:1a:d8:ab
> brgphy0 at bge0 phy 1: BCM5785 1000BASE-T media interface, rev. 3
> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FD , auto
> [...]
>
> I have a local patch to attach brgphy on bge(4) rather ukphy(4) ...
>
>
> bge0: firmware handshake timed out, val = 4b657654
> bge0: firmware handshake timed out, val = 4b657654
> bge0: discarding oversize frame (len=-4)
> bge0: discarding oversize frame (len=-4)
> nfs_boot: trying DHCP/BOOTP
> bge0: watchdog timeout -- resetting
> bge0: firmware handshake timed out, val = 4b657654
> bge0: firmware handshake timed out, val = 4b657654
> bge0: discarding oversize frame (len=-4)
> bge0: discarding oversize frame (len=-4)
> nfs_boot: timeout...
> nfs_boot: timeout...
>
>
> The "discarding oversize frame" message comes from if_ethersubr.c

I just figured out in bge_rxeof():

     m->m_pkthdr.len = m->m_len = cur_rx->bge_len - ETHER_CRC_LEN;

cur_rx->bge_len is 0.

Christoph