Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Nov 2004 16:57:42 -0500
From:      John Baldwin <jhb@FreeBSD.org>
To:        "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au>
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: bge(4) watchdog timeout
Message-ID:  <200411191657.42735.jhb@FreeBSD.org>
In-Reply-To: <20041118053724.GS66822@squash.dsto.defence.gov.au>
References:  <20041116021421.GK56252@squash.dsto.defence.gov.au> <wpoehwcqbm.fsf@heho.snv.jussieu.fr> <20041118053724.GS66822@squash.dsto.defence.gov.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 18 November 2004 12:37 am, Wilkinson, Alex wrote:
> Well, if I do that I will be using the old AT-PIC.
> Which as far as I am aware is old and crusty ;-\
>
> Is this correct john ?

It will still work ok.  The only major downside is that PCI devices will 
probably have to share IRQ lines whereas they usually don't with APICs.

>  -aW
>
> 	0n Wed, Nov 17, 2004 at 06:56:13PM +0100, Arno J. Klaassen wrote:
>
> 	"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

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org



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