From owner-freebsd-net@FreeBSD.ORG Wed Mar 6 06:27:06 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 57F587E3 for ; Wed, 6 Mar 2013 06:27:06 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-f52.google.com (mail-pb0-f52.google.com [209.85.160.52]) by mx1.freebsd.org (Postfix) with ESMTP id F276C368 for ; Wed, 6 Mar 2013 06:27:05 +0000 (UTC) Received: by mail-pb0-f52.google.com with SMTP id ma3so5532032pbc.25 for ; Tue, 05 Mar 2013 22:27:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:date:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=5pksi+SItNBqsH0a7bRloNG3e9weeUdPPTblC0GN32M=; b=v+e2oe/P80/6agI6D3qmtB8ovtJVYCsYHtru50/x/+ft+BCiR/62Yy58bsd8hA7eny X8IQJ+DFnOyEdCTOGhr+PN4sFm01kjqDTTf0uDdU/nbiNsq2PIUWO4jzCBbvw57CkqrZ EwIdr69CBwEq2JZQLRK7ONK9enu75RSPQDf38dALo7pao9LsBIdzvyZVeC4i7v994lvc YeUAkobRSCdH6bwJGK/Mc62gICRu/UWDsg5vVRIv0pUT7f9aqO+VHVa5+yebxoIzwlqN 8bfvpCgrYdDTiDUoKGlalvCXxUhKQLrH1bpTIJWXa3GeKVxnLtSIlkq5LZIEHysIUYRh jsxw== X-Received: by 10.68.138.225 with SMTP id qt1mr42815544pbb.82.1362551225280; Tue, 05 Mar 2013 22:27:05 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id zm1sm29929930pbc.26.2013.03.05.22.27.01 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 05 Mar 2013 22:27:04 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 06 Mar 2013 15:26:58 +0900 From: YongHyeon PYUN Date: Wed, 6 Mar 2013 15:26:58 +0900 To: "Eugene M. Zheganin" Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Message-ID: <20130306062658.GC1483@michelle.cdnetworks.com> References: <201302241106.42477.vegeta@tuxpowered.net> <20130225082042.GB1426@michelle.cdnetworks.com> <512CF97B.8030805@norma.perm.ru> <20130227020123.GA3581@michelle.cdnetworks.com> <512DE968.4020409@quip.cz> <20130228053558.GA1474@michelle.cdnetworks.com> <5136D89D.4000902@norma.perm.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5136D89D.4000902@norma.perm.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Mar 2013 06:27:06 -0000 On Wed, Mar 06, 2013 at 11:48:13AM +0600, Eugene M. Zheganin wrote: > Hi. > > On 28.02.2013 11:35, YongHyeon PYUN wrote: > > The reporter said the machine was Sun Fire X2200 M2 so I guess you > > may see the same issue on both stable/9 and stable/8. Ideally the > > loader tunable hw.bge.allow_asf should not be there and driver > > should take care of it by checking the existence of ASF/IPMI > > firmware. > > > > > Unfortunately, I just had the 'bge0 - watchdog timeout - resetting' on a > recent 8.3-STABLE and a 'Broadcom NetXtreme BCM5722 Gigabit (94309)' > (according to the pciconf -lv) controller. I haven't seen this in a year > or two (I guess), the machine was running 8.2-STABLE. So, in order to > fight this (machine is freezing during these messages) whet should I do > ? Is upgrading to 10.0-CURRENT an option ? hw.bge.allow_asf is 0 already. If you were using latest stable/8, the result would be same on CURRENT. How frequently do you see the watchdog timeouts? Is there way to reproduce it? Would you show me the output of dmesg (bge(4) and brgphy(4) only) and "pciconf -lcbv"?