Date: Tue, 4 Nov 2008 06:58:59 -0500 From: "John Fitzgerald" <jjfitzgerald@gmail.com> To: freebsd-bugs@freebsd.org Subject: Re: bce watchdog timeout occurred, resetting Message-ID: <5e49673f0811040358k4272c1fck1ed0c32bafad21d5@mail.gmail.com> In-Reply-To: <5e49673f0811031156n5e44795bo55b7df11b75e7bf8@mail.gmail.com> References: <5e49673f0811031156n5e44795bo55b7df11b75e7bf8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 3, 2008 at 2:56 PM, John Fitzgerald <jjfitzgerald@gmail.com> wrote: > Hi there, > > I have a pretty busy firewall / gateway that's running two Broadcom > NetXtreme II cards on full-duplex GigE ports. The internal interface > is autoselect (negotiate) and the external is hard-coded GigE. Every > so often the hard-coded interface dies and the system logs (like > today) show this: > > Nov 3 14:39:20 myserver kernel: bce0: > /usr/src/sys/dev/bce/if_bce.c(5002): Watchdog timeout occurred, > resetting! > Nov 3 14:39:20 myserver kernel: bce0: link state changed to DOWN > Nov 3 14:39:23 myserver kernel: bce0: link state changed to UP > > Searching around, the only thing I can spot is this, from the bce man page: > > bce%d: Watchdog timeout occurred, resetting! The device has stopped > responding to the network, there is a problem with the cable > connection, or a driver logic problem has occurred. > > I'm afraid it's the driver logic problem, but I don't know where to go > from here. Any ideas? I'm using 6.2-RELEASE. > > Thanks, > > JJ > Anybody know / care?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5e49673f0811040358k4272c1fck1ed0c32bafad21d5>