From owner-freebsd-stable@FreeBSD.ORG Tue Apr 21 14:10:49 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A3FE2CA8 for ; Tue, 21 Apr 2015 14:10:49 +0000 (UTC) Received: from mail2.glyndwr.ac.uk (xch2.glyndwr.ac.uk [194.82.118.162]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail2.glyndwr.ac.uk", Issuer "TERENA SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 452121C53 for ; Tue, 21 Apr 2015 14:10:48 +0000 (UTC) Received: from [10.44.1.82] (10.44.1.82) by XCH2.wrexham.local (194.82.118.162) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 21 Apr 2015 15:10:38 +0100 Message-ID: <55365A57.60509@glyndwr.ac.uk> Date: Tue, 21 Apr 2015 15:10:31 +0100 From: Gareth Wyn Roberts User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Alnis Morics , , Chris Ross Subject: Re: 10.1-STABLE bce: Watchdog timeout occurred References: <55361DF6.2080606@gmail.com> In-Reply-To: <55361DF6.2080606@gmail.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.44.1.82] 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 14:10:49 -0000 This may be caused by DMA alignment problems. See https://docs.freebsd.org/cgi/getmsg.cgi?fetch=145859+0+archive/2015/freebsd-stable/20150419.freebsd-stable for a recent thread about the msk driver. The msk maintainer Yonghyeon Pyun has opted for super safe options of 32K alignment! It's a long shot, but you could try increasing BCE_DMA_ALIGN and/or BCE_RX_BUF_ALIGN in the include file if_bcereg.h, say up to 4096, to see whether it makes any difference. - Gareth. On 21/04/2015 10:52, Alnis Morics wrote: > 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 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"