Watchdog timeouts and dead network on bge - 6.1-RC1
- From: Lars Erik Gullerud <lerik@xxxxxxxxxx>
- Date: Sun, 23 Apr 2006 14:35:24 +0200 (CEST)
We recently upgraded one of our 4.11 servers to 6.1-RC1. The server is a Dell PE2650, dual Xeons, and has two onboard Broadcom BCM5701 cards, using the bge driver.
Some older threads on -net and -current led me to believe that most issues with bge driver in FreeBSD >4 had been sorted. However, after our upgrade, we are seing errors like this:
Apr 22 18:44:01 nebula kernel: bge0: watchdog timeout -- resetting
Apr 22 18:44:01 nebula kernel: bge0: link state changed to DOWN
Apr 22 18:44:03 nebula kernel: bge0: link state changed to UP
...and more importantly - when this happens, the network connection does NOT in fact come back up. Logging into the box locally (or via a different network interface) and manually issuing "ifconfig bge0 down ; ifconfig bge0 up" DOES get the interface going again, however.
We have only seen this on very high network loads - the particular message included above occured while transferring some 120GB of data from a 4.11 NFS-server to this 6.1-RC1 box.
Is this a known issue in bge? If so, is anyone working on it? Can we provide some useful information to whoever this might be?
We have never had any issues with bge in 4.x, but we really need to get this server up to 5.x/6.x at this point in time, any other suggestions on knobs or workarounds that can give us bge stability?
Thanks in advance,
/leg
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Watchdog timeouts and dead network on bge - 6.1-RC1
- From: Oleg Bulyzhin
- Re: Watchdog timeouts and dead network on bge - 6.1-RC1
- From: Robert Watson
- Re: Watchdog timeouts and dead network on bge - 6.1-RC1
- Prev by Date: Re: Automatic VLANS
- Next by Date: Re: Watchdog timeouts and dead network on bge - 6.1-RC1
- Previous by thread: Re: Automatic VLANS
- Next by thread: Re: Watchdog timeouts and dead network on bge - 6.1-RC1
- Index(es):
Relevant Pages
- Re: Upgrade w2k
... will make new server with same SIDs, GUIDs, server names, IP addresses ... This
can cause conflicts on the network... ... Now you take it offline and bring on the network
another clone of this ... take it away from user's network and upgrade it. ...
(microsoft.public.windows.server.general) - Re: Remote Web Workplace not working properly
... How did you get to 2003, an inplace upgrade or swing migration? ... take control
of the server in the room right ... over the internet or from any one desktop within the
network). ... back to the login window. ... (microsoft.public.windows.server.sbs) - Re: domain upgrade question
... as long as you run adprep /forestprep /domainprep and allow for adequate time for changes
to replicate you can install new w2k3 dc's or upgrade w2k dc's. ... It is a Windows 2000
domain with two Exchange 2003 servers ... inetorgfix was never run on this network,
but I read that the mangled ... controller to 2003 or simply install a new 2003 member server
and run ... (microsoft.public.windows.server.active_directory) - Re: Inplace Upgrades, continued...
... upgrade and yet you say you can log in to the old 2k ... >SBS2K3 server
unless I first rejoin the old SBS2K ... network, logoff, switch ... >> When
you say No access to shares describe what you mean. ... (microsoft.public.windows.server.sbs) - ISA in SBS2k Painfully Slow
... I just enabled the ISA Server on an SBS2K server this past weekend. ... upgrade
also involved reconfiguring the network. ... (microsoft.public.backoffice.smallbiz2000)