From owner-freebsd-net@FreeBSD.ORG Tue Mar 19 06:03:40 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 AC4BC50A for ; Tue, 19 Mar 2013 06:03:40 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by mx1.freebsd.org (Postfix) with ESMTP id 4F67E3D9 for ; Tue, 19 Mar 2013 06:03:40 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id u10so52743pdi.9 for ; Mon, 18 Mar 2013 23:03:33 -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=/EZ5euU0SEjm6o5WLwPezg+Hz2lh/eD7lfagsl79634=; b=R1XCnL9NddET/ex7Zx8a5bepTE3GAckbCymJ26Trn1tLhG9qqFG89TV3LBKkgbCGb6 5zlRgf90IQKoTUMYqHE/KhUcrwKDVH6qEd37AQq3qFG7V4Ss/u5B+EQvA2xmowFV2uK0 0ji1ofX7hMUHXs1ELBc37GJWYEeHH6Y7fhkolmw6VxcuPAfuOWfwjMeICHbJW0oO8NDz nWtXtrpiSB0/WsgKy2QbOXDyyDjkkdOeD072fV9e3odeixt5/Cu6hrlu9EhXBCymGQzk SWpW3i6rmTu31NFCegAze83qcB+uuQ4nQdWZWK1hvynSeDoePxeh7JBiJ07l//v17iDQ qPcQ== X-Received: by 10.66.152.129 with SMTP id uy1mr1527380pab.36.1363673013923; Mon, 18 Mar 2013 23:03:33 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id fh1sm11210740pac.1.2013.03.18.23.03.30 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 18 Mar 2013 23:03:32 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 19 Mar 2013 15:03:27 +0900 From: YongHyeon PYUN Date: Tue, 19 Mar 2013 15:03:27 +0900 To: "Eugene M. Zheganin" Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Message-ID: <20130319060327.GC1437@michelle.cdnetworks.com> References: <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> <20130313015753.GD3062@michelle.cdnetworks.com> <514171D1.50807@norma.perm.ru> <20130314072946.GA1519@michelle.cdnetworks.com> <51469BE4.6070502@norma.perm.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51469BE4.6070502@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: Tue, 19 Mar 2013 06:03:40 -0000 On Mon, Mar 18, 2013 at 10:45:24AM +0600, Eugene M. Zheganin wrote: > Hi. > > On 14.03.2013 13:29, YongHyeon PYUN wrote: > > >I thought you were using stable/8 but it seems you have slightly > >older stable/8. The bge(4) code difference between CURRENT and > >stable9/stable8 is very minor. > Nah, I really am running recent 8/stable. My mistake was to try to apply > the whole code of the if_bge.c to 8/stable. > > >I've attached diff against stable/8 which will address ASF/IPMI > >issue but I'm not sure whether it helps watchdog timeout or not. > >I have plan to MFC the change but I need time for settlement before > >the MFC. > Thanks a lot. Now the 'watchdog timeout' behaviour stopped, the driver > reports nothing on the console, but the freezes, unfortunately - didn't > stop. The machine is freezing at random periods of time, usually 1-2 > days, it partially stops answering to network (network services running > on this machine close the connection, and other weird stuff happens), it > partially responds on the console (I can type but I cannot login) and so I have no idea how this change can freeze your box. It would be even better to know whether the issue was triggered by bge(4) changes. I think you can use bge(4)/brgphy(4) of 8.3-RELEASE on your stable/8. Copy required files from 8.3-RELEASE to stable/8 and rebuild your kernel. For instance, Copy /usr/src/sys/dev/bge/if_bge.c from 8.3-RELEASE to /usr/src/sys/dev/bge on stable/8 Copy /usr/src/sys/dev/bge/if_bgereg.h from 8.3-RELEASE to /usr/src/sys/dev/bge on stable/8 Copy /usr/src/sys/dev/mii/brgphy.c from 8.3-RELEASE to /usr/src/sys/dev/mii on stable/8 Copy /usr/src/sys/dev/mii/brgphyreg.g from 8.3-RELEASE to /usr/src/sys/dev/mii on stable/8 And rebuild your kernel. > on. The asf feature has no influence on this - I tried to enable it, > this happens anyway. > > Should I try upgrade to 9 or 10, do they have more improvements in bge(4) ? No, there is no bge(4) functional differences between stable/8 and stable/9.