Date: Tue, 21 Apr 2015 12:52:54 +0300 From: Alnis Morics <alnis.morics@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: 10.1-STABLE bce: Watchdog timeout occurred Message-ID: <55361DF6.2080606@gmail.com> In-Reply-To: <A1E984E1-B551-4CB6-A343-4E73FB58C35E@distal.com> References: <A1E984E1-B551-4CB6-A343-4E73FB58C35E@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/21/2015 06:17 AM, Chris Ross wrote: > I got a new [to me] system recently, a Dell PE 1950. It has two bce parts on the motherboard that identify as: > > bce#: <QLogic NetXtreme II BCM5708 1000Base-T (B2)> > > The OS I installed and kernel I'm running are from a download of a 10.1 STABLE ISO, r281235, April 7, 2015. > > I had gone on to check out a newer stable from subversion, and build a custom kernel, but when I booted that one I got a bce0 that didn't seem to work, and kept emitting: > > bce0: /usr/src/sys/dev/bce/if_bce.c(7869): Watchdog timeout occurred, resetting! > bce0: link state changed to DOWN > bce0: link state changed to UP > > So, I fell back. But I've since noticed that even the original kernel seems to do this after booting. I'm not yet running any notable amount of traffic through the system, but intend to make it an edge router, so certainly will be. > > Is there any sort of issue noted in the bce driver in recent days/weeks/months? Are other folks seeing this diagnostic/error? > > I'll do a little more testing and see if I'm seeing it more or less often, but I know that in at least some cases the interface has flapped like this after boot for long enough that I was unable to get connected remotely, and resorted to a console login to reboot. > > - Chris > There are "Watchdog timeout" errors with some msk NICs. Both msk and bce are dependent on MII bus code (see /usr/src/sys/amd64/conf/GENERIC) -Alnis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55361DF6.2080606>