Re: bge(4) watchdog timeout

From: Arno J. Klaassen <arno_at_heho.snv.jussieu.fr>
Date: 17 Nov 2004 18:56:13 +0100
"Wilkinson, Alex" <alex.wilkinson_at_dsto.defence.gov.au> writes:

> I get the following errors, however, although it states that there is no
> carrier, there is.
> 
> 	bge0: firmware handshake timed out
> 	bge0: RX CPU self-diagnostics failed!
> 	bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> 	        options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
> 	        inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255
> 	        ether 00:11:0a:40:d2:dd
> 	        media: Ethernet autoselect (none)
> 	        status: no carrier
> 	
> 	Mounting NFS file systems:bge0: watchdog timeout -- resetting
> 
> 
> Here is ifconfig(8) output after fully booted:
> 
> bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
>         inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255
>         ether 00:11:0a:40:d2:dd
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> 
> Seems odd enough, to email the wizards about it.

one of my co-workers had a similar problem (PR 73538).
Leaving out "device apic" from the kernel-config "fixed" the
problem. YMMV

Arno
Received on Wed Nov 17 2004 - 16:56:24 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:22 UTC