From owner-freebsd-net@FreeBSD.ORG Sun Feb 23 14:59:23 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 394E5F31 for ; Sun, 23 Feb 2014 14:59:23 +0000 (UTC) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2001:470:1f09:14c0::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D536C13B1 for ; Sun, 23 Feb 2014 14:59:22 +0000 (UTC) Received: from [192.168.248.37] ([192.168.248.37]) by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id s1NExHMA081848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sun, 23 Feb 2014 20:59:17 +0600 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <530A0CC4.6060807@norma.perm.ru> Date: Sun, 23 Feb 2014 20:59:16 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: bge0: watchdog timeout Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [192.168.3.10]); Sun, 23 Feb 2014 20:59:17 +0600 (YEKT) X-Spam-Status: No hits=-101.0 bayes=0.5 testhits ALL_TRUSTED=-1, USER_IN_WHITELIST=-100 autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Feb 2014 14:59:23 -0000 Hi. Recently I've upgrade two of my FreeBSD servers from 8.x (8.2-STABLE and 8.3-PRERELEASE). On one server, running with hw.bge.allow_asf: 1 dev.bge.0.msi: 1 I got a bunch of # dmesg -a | grep watch Starting watchdogd. bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting This server has the following chip: bge0@pci0:32:0:0: class=0x020000 card=0x705d103c chip=0x165b14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetXtreme BCM5723 Gigabit Ethernet PCIe' class = network subclass = ethernet Is this known behaviour ? Are there still any issues with bge(4) ? Another one is running some older version of RC1, r259449 - I've checked the svnweb and saw that last update was at r258830, so it must be a combination of ASF + MSI that does this. Is there anything I can do about this, aside from turning off the MSI/ASF stuff ? Thanks. Eugene.