From owner-freebsd-net@FreeBSD.ORG Wed Mar 13 01:58:07 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 A2A3BC08 for ; Wed, 13 Mar 2013 01:58:07 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-f51.google.com (mail-pb0-f51.google.com [209.85.160.51]) by mx1.freebsd.org (Postfix) with ESMTP id 770958C2 for ; Wed, 13 Mar 2013 01:58:07 +0000 (UTC) Received: by mail-pb0-f51.google.com with SMTP id un15so470631pbc.24 for ; Tue, 12 Mar 2013 18:58:01 -0700 (PDT) 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=CZuvzbXbskLafvGOtKnjX2wKg3IPLXLMvsroM1+S0VY=; b=ia3ThWGJKehX0rJ2IhhpO4b/4LVQWQVj251qFRBkj4S2Iz8Kmh5oi2cTyzDwKjMzAX sGZ7eIcQOBIL2kobZSIJlq7pQrCDm9qQ9g0F3k+LTpzgTBskvPOH8WhVOeSHdZLjRJ7S bIuEc+HAXIGiH8mtsNpz0sO+F9Pncae/2Dx98ltqbP1Hfte1fdfChyyAa5Q42O/Zjwer p7icj697OLSIlyTcyZ+ykHC5AVFIwODdOGpSQtq6IgcejXlELCzuIJTh19mV1/2bBc+D 0GkkehRXtu1W1HXcZeP6Z8oMQso0+53ckGseBQs2hcKNaiT4ioRpwP9muZP66CjaIwmU kOBA== X-Received: by 10.68.75.72 with SMTP id a8mr41486379pbw.143.1363139880726; Tue, 12 Mar 2013 18:58:00 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id z1sm4577102pbw.19.2013.03.12.18.57.57 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 12 Mar 2013 18:57:59 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 13 Mar 2013 10:57:53 +0900 From: YongHyeon PYUN Date: Wed, 13 Mar 2013 10:57:53 +0900 To: "Eugene M. Zheganin" Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Message-ID: <20130313015753.GD3062@michelle.cdnetworks.com> References: <512DE968.4020409@quip.cz> <20130228053558.GA1474@michelle.cdnetworks.com> <5136D89D.4000902@norma.perm.ru> <20130306062658.GC1483@michelle.cdnetworks.com> <513713C2.1000007@norma.perm.ru> <20130307022446.GB3108@michelle.cdnetworks.com> <513820E2.806@norma.perm.ru> <20130307062335.GB1478@michelle.cdnetworks.com> <51383E3B.5030007@norma.perm.ru> <20130307081548.GD1478@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130307081548.GD1478@michelle.cdnetworks.com> 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, 13 Mar 2013 01:58:07 -0000 On Thu, Mar 07, 2013 at 05:15:48PM +0900, YongHyeon PYUN wrote: > On Thu, Mar 07, 2013 at 01:14:03PM +0600, Eugene M. Zheganin wrote: > > Hi. > > > > On 07.03.2013 12:23, YongHyeon PYUN wrote: > > > On Thu, Mar 07, 2013 at 11:08:50AM +0600, Eugene M. Zheganin wrote: > > >> It was definitely older than "months". It was running something similar > > >> to "FreeBSD 8.2-STABLE #0: Mon Sep 19 08:10:00 YEKST 2011", this is the > > >> uname from a neighbor machine. > > >> > > >> I have, as I said, identical servers running FreeBSD. Here are some of > > >> the unames that I don't see timeouts on: > > >> > > >> 8.3-STABLE #2: Wed Aug 29 13:00:02 YEKT 2012 (up 187 days) > > >> 8.3-PRERELEASE #1: Thu Mar 29 16:14:11 MSK 2012 (up 15 days, previous > > >> uptime around 180 days) > > > These servers do not have 5718/5719/5720 changes. > > > > > >> 8.2-STABLE #0: Wed Dec 14 16:56:11 YEKT 2011 (up 99 days) > > > This server has the bge(4) change but it didn't trigger watchdog > > > timeouts. Does this server use the same controller? If yes, the > > > issue didn't come from bge(4) change. > > > > > How's that ? It's running even older version than previous two. I guess > > you misread the year. > > Oops, you're right. If your controller supports ASF/IPMI access please apply r248226 to stable/8 and let me know whether that makes any difference. I believe ignoring ASF/IPMI firmware is not good idea since the ASF/IPMI firmware will run regardless of hw.bge.allow_asf loader tunable configuration. You may have to set hw.bge.allow_asf=1 since it's off by default on stable/8.