Date: Fri, 3 Nov 2006 16:34:08 +0000 From: Greg Eden <greg@warprecords.com> To: freebsd-stable@freebsd.org Subject: Re: Watchdog Timeout - bge device - 6.2-PRERELEASE Message-ID: <AB18640D-B516-4FAB-B21B-C92F72820FB4@warprecords.com> In-Reply-To: <9F7B653A50CF3D45A92C05401046239B0E0CBD@rwsrv06.rw2.riverwillow.net.au> References: <9F7B653A50CF3D45A92C05401046239B0E0CBD@rwsrv06.rw2.riverwillow.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 Nov 2006, at 23:50, John Marshall wrote: > bge0: watchdog timeout -- resetting > bge0: link state changed to DOWN > bge0: link state changed to UP I'm seeing similar behaviour on a HP DL360g4 running 6.1-RELEASE and a GENERIC kernel. It had similar problems with 5.4. I have 2 other similar machines running 6.1, which don't record these errors, however they never see any sustained throughput whereas this machine does. bge0: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2100> mem 0xfde70000-0xfde7ffff irq 25 at device 2.0 on pci2 IRQ is not shared vmstat -i interrupt total rate irq1: atkbd0 1668 0 irq6: fdc0 87 0 irq14: ata0 46 0 irq16: uhci0 49865767 5 irq24: ciss0 6645080 0 irq25: bge0 336582162 34 irq26: bge1 313542372 32 irq48: mpt0 49865839 5 cpu0: timer 2055753320 210 Total 2812256341 287 > Scott Long said > Is it causing stuck connections or other messy problems? Also, is it > any worse than 6.1? Fortunately all it seems to be doing is bothering my log files. I'm taking an interest as I have two important production machines using the bge driver both about to be upgraded from 5.3R to 6.1R. I've just grepped the logs on those machines and they both have a sprinkling of timeouts (5 over 18 months on one quite heavily trafficked webserver, the other which continously serves http downloads is clean apart from 1 24hour period when it was having 200GB of files uploaded to it). My concern is that upgrading to 6.1 or 6.2 and then enabling device polling is going to make the issue worse. I'm happy to supply more info. best. greg.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AB18640D-B516-4FAB-B21B-C92F72820FB4>