Skip site navigation (1)Skip section navigation (2)
Date:      17 Nov 2004 18:56:13 +0100
From:      "Arno J. Klaassen" <arno@heho.snv.jussieu.fr>
To:        "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au>
Cc:        freebsd-current@freebsd.org
Subject:   Re: bge(4) watchdog timeout
Message-ID:  <wpoehwcqbm.fsf@heho.snv.jussieu.fr>
In-Reply-To: <20041116021421.GK56252@squash.dsto.defence.gov.au>
References:  <20041116021421.GK56252@squash.dsto.defence.gov.au>

next in thread | previous in thread | raw e-mail | index | archive | help
"Wilkinson, Alex" <alex.wilkinson@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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wpoehwcqbm.fsf>