From owner-freebsd-net@FreeBSD.ORG Thu Mar 7 02:25:00 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EA82ADD2 for ; Thu, 7 Mar 2013 02:25:00 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) by mx1.freebsd.org (Postfix) with ESMTP id 94D46926 for ; Thu, 7 Mar 2013 02:25:00 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id rp2so6899271pbb.20 for ; Wed, 06 Mar 2013 18:24:54 -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=YPZ8COZutJIEvqb0+oF9RXA1P51EFK3FBcE9iwJVvH8=; b=r5pS8R6NfJMjusQLxzlaVWwwEro8drxWKzLr4BR0VE8bEI8nBhPIP/NI1/agAYyp+J V0wm6n/1NuQco0paym2Rnvt6P3sJW3ZMEVzWhLOmn1AeDpbffT0tQZtjfKzHSHTYZfiH LOoOEcPVVmzIsAr3EW5PmOYeSQMHmS2TLlcng8VTJfcjaP00xRSvZyTaE88VXkw97nme lO0uHstQy7XMzUljgvn6/LD/ZZL/wUyRUeAD9T3uo+eBYrbRYWlXTttI+mPzxIKRCqDf LFrlIr1USSYbS+ydvD7ghzOZyPWAFIqa4Wbcjv9W++e7kjQht0lwpUuWQgIkrBaUgzw2 YsZw== X-Received: by 10.68.33.98 with SMTP id q2mr51351215pbi.135.1362623094627; Wed, 06 Mar 2013 18:24:54 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id av14sm243052pac.18.2013.03.06.18.24.51 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Mar 2013 18:24:53 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 07 Mar 2013 11:24:46 +0900 From: YongHyeon PYUN Date: Thu, 7 Mar 2013 11:24:46 +0900 To: "Eugene M. Zheganin" Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Message-ID: <20130307022446.GB3108@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> <20130306062658.GC1483@michelle.cdnetworks.com> <513713C2.1000007@norma.perm.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <513713C2.1000007@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: Thu, 07 Mar 2013 02:25:01 -0000 On Wed, Mar 06, 2013 at 04:00:34PM +0600, Eugene M. Zheganin wrote: > Hi. > Hi. > > On 06.03.2013 12:26, YongHyeon PYUN wrote: > > 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"? > I upgraded one om my routers 2 days ago to 8.3-STABLE, and got today a > freeze. Uptime was less than a day. > I have like dozens of these IBM system x3250, all of them run various > 8.2-STABLE's, that's why I worry that much. I don't know if this is What was previous SVN revision number on that machine? The support for 5718/5719/5720 was merged to stable/8 about 3 months ago. > triggered by some of my actions. These routers run gre/ipsec, dirrerent > routing stuff (quagga, bird), proxies and pf. In 2011/early 2012 I saw > similar watchdog issues on these machines, and I disabled the tso on > them. I don't know whether this is a coincidence or it really helps, but > after that I didn't see these watchdog issues until today. I'm not aware of TSO issue on your controller. pf(4) had TSO issue but I guess it was fixed long time ago. > > I've also discovered that this particular server is running some old > bioses/firmwares including the fact that it misses some NetXtreme > updates available from IBM. Would applying such updates resolve the > situation ? > Updating etherent controller firmware is always good idea. But I'm not sure whether this address the issue. > I am ok with that fact that I cannot run ipmi/sol on these machines, but > it would be nice if this watchdog issue could be somehow resolved. Actually this is the first report after the merge which seems to break bge(4). > Furthermore, I have some spare machines that I can provide full access > to, including ipkvm stuff. Since the machine is only partially freezing, > I cannot even rely on the ichwd and watchdogd to reboot it. Sorry no clue yet. > > pciconf (there's two controllers in this server, I use the first, but > anyway): Thanks for the info. [...]