Date: Wed, 04 Oct 2006 12:01:26 +0200 From: Philippe Pegon <Philippe.Pegon@crc.u-strasbg.fr> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable@freebsd.org Subject: Re: Watchdog Timeout - bge devices Message-ID: <45238676.1040506@crc.u-strasbg.fr> In-Reply-To: <20061004051857.GA58194@icarus.home.lan> References: <9F7B653A50CF3D45A92C05401046239B0E0C27@rwsrv06.rw2.riverwillow.net.au> <20061004051857.GA58194@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On this subject, does somebody know why there is no pending issues listed at http://www.freebsd.org/releases/6.2R/todo.html ? -- Philippe Pegon Jeremy Chadwick wrote: > On Wed, Oct 04, 2006 at 02:34:16PM +1000, John Marshall wrote: >> $ dmesg | grep bge >> bge0: <Broadcom BCM5705K Gigabit Ethernet, ASIC rev. 0x3003> mem >> 0xe8200000-0xe820ffff irq 17 at device 4.0 on pci4 >> miibus1: <MII bus> on bge0 >> bge0: Ethernet address: 00:0b:cd:e7:51:ba >> bge0: watchdog timeout -- resetting >> bge0: link state changed to DOWN >> bge0: link state changed to UP > > As far as SCHED_ULE goes, if you have issues with it, use SCHED_4BSD. > 4BSD is still the default, and definitely works. I've run into too > many issues (in the past; maybe some have since been dealt with) > with ULE, so I stick purely with 4BSD. > > Now, about watchdog timeouts in general -- there's a pending issue > which is still under investigation. Please see this thread: > > http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028792.html > > Yes, it's long, but it does pertain to bge (despite the subject > stating em). After you read it all, or most of it, you should > probably partake in the convo there.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45238676.1040506>