From owner-freebsd-stable@FreeBSD.ORG Tue Apr 21 09:52:59 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A87AFA01 for ; Tue, 21 Apr 2015 09:52:59 +0000 (UTC) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D0691F01 for ; Tue, 21 Apr 2015 09:52:59 +0000 (UTC) Received: by lbbzk7 with SMTP id zk7so151463222lbb.0 for ; Tue, 21 Apr 2015 02:52:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rSGOlt3ZalUwrC5Q7BJx28QWMG9GrjAY5KLw6GghyqM=; b=xNzsvzQhfu6hmrWZWb0FLdwjVhpm3WB/QoBbAMMWAXEMnC/0jygLOX07jl9++gt7ng 1iEjXmTKRw7SEfAiEEqueIgE6UU33eQdZc/kCGI4JujdBB0MzDQawMn8o19IxVgPCqX9 PrR4VV9ZP5zr9yKHHoTjLPEfp5/YXJep+Z0h0EYdkCIRbXw1AnEu0FvhCnKd3Lg0k5ke N6U4BuLuaLbqsW3YDD3RIu/cDCyjylv83o7/EPl7PyRndjIsC7OD7QmL4Suun0J4juTr 7Qqj/3SFWgf5hrH+qxWXZziYB9UVGiJQ/2nanMOl2IVrOjcjn2aEySq0yQYHCWyHO5zR I98w== X-Received: by 10.152.204.40 with SMTP id kv8mr19157385lac.113.1429609977059; Tue, 21 Apr 2015 02:52:57 -0700 (PDT) Received: from [192.168.2.192] ([78.84.244.14]) by mx.google.com with ESMTPSA id c5sm277396lac.15.2015.04.21.02.52.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Apr 2015 02:52:56 -0700 (PDT) Message-ID: <55361DF6.2080606@gmail.com> Date: Tue, 21 Apr 2015 12:52:54 +0300 From: Alnis Morics User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 10.1-STABLE bce: Watchdog timeout occurred References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2015 09:52:59 -0000 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#: > > 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