From owner-freebsd-current@FreeBSD.ORG Thu Aug 20 18:23:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 597AD1065672 for ; Thu, 20 Aug 2009 18:23:16 +0000 (UTC) (envelope-from bofh@terranova.net) Received: from tog.net (tog.net [216.89.226.5]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0668FC66 for ; Thu, 20 Aug 2009 18:23:15 +0000 (UTC) Received: from [192.168.5.143] (host-216-89-228-162.wlb.terranova.net [216.89.228.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tog.net (Postfix) with ESMTPSA id 2021F82AE; Thu, 20 Aug 2009 14:07:51 -0400 (EDT) Message-ID: <4A8D90EB.8090602@terranova.net> Date: Thu, 20 Aug 2009 14:07:39 -0400 From: Travis Mikalson Organization: TerraNovaNet Internet Services User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4A66CFFC.30601@doghouserepair.com> <11167f520907220200m5dd456dfs2ad53d4b579b851b@mail.gmail.com> <4A66D587.9060001@haruhiism.net> <11167f520907220326m430709efv7aa6c779f9511b78@mail.gmail.com> <20090722211600.GC1184@weongyo.local> <4A679223.10604@doghouserepair.com> <20090812214932.GH55129@michelle.cdnetworks.com> <4A84D245.5050703@doghouserepair.com> <20090814175649.GB1311@michelle.cdnetworks.com> In-Reply-To: <20090814175649.GB1311@michelle.cdnetworks.com> X-Enigmail-Version: 0.95.7 OpenPGP: url=http://www.terranova.net/pgp/bofh Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, Ryan Rogers Subject: Re: nfe problem on 8.0-BETA2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2009 18:23:16 -0000 Pyun YongHyeon wrote: > On Thu, Aug 13, 2009 at 07:56:05PM -0700, Ryan Rogers wrote: >> Pyun YongHyeon wrote: >>> On Wed, Jul 22, 2009 at 03:26:43PM -0700, Ryan Rogers wrote: >>>> Weongyo Jeong wrote: >>>>> On Wed, Jul 22, 2009 at 05:26:07AM -0500, Sam Fourman Jr. wrote: >>>>>>> svn co svn://svn.freebsd.org/base/head >>>>>>> svn merge -c -193289 >>>>>>> >>>>>>> Thereafter, in the root of the repo: >>>>>>> svn up >>>>>>> svn merge >>>>>> Confirmed, running the above set of commands fixed my 88E1116 nfe >>>>>> problem >>>>>> everything works as it should now. thanks guys for the help. >>>>>> >>>>>> Sam Fourman Jr. >>>>>> >>>>>> ps. svn was WAY faster than csup, I think I am going to use svn all >>>>>> the time now. >>>>> I know that yongari@ knows what the problem is and the solution but he >>>>> could not access the internet right now due to relocation to USA. >>>>> >>>>> It looks he is busy with looking for house and etc... >>>>> >>>>> regards, >>>>> Weongyo Jeong >>>>> >>>>> >>>>> >>>> Well, the good news is that r193289 was the only thing keeping my nics >>> >from working. I was able to update to current as of today and revert >>>> that patch, and everything is working nicely now. So I'll just keep my >>>> eye on the commit logs and patch that up by hand whenever I need to >>>> update until yongari is able to get situated. >>>> >>> Would you try attached patch and let me know how it goes on your >>> box? >> The patch works great, thanks! > > Thanks for testing. > Unfortunately the change requires more testing on various > controllers. 88E1116 PHY is commonly found on Yukon Ultra or newer > Yukon controllers as well as NVIDIA controllers. Since we are in > 8.0-BETA stage changing common PHY code at this time looks > dangerous. Before I start a bug report, I'm curious, do you think it is possible for this issue to also affect the general stability in operation of the nfe driver? I mean if nfe comes up and works fine for many days and then suddenly stops passing traffic? In both 8.0 and 7.2-STABLE some time after the beginning of June, two separate systems with two different nfe NICs started showing exactly the same issue. The 7.2-STABLE system was built from June 16th source and has a Marvell 88E1116. The 8.0-BETA2 system has a Marvell 88E1111 and is built from Aug 13th source. Both systems did not ever have this issue with code from before June (7.2-RELEASE included). Both will stop passing traffic across their nfe0 NIC randomly and require an ifconfig nfe0 down; ifconfig nfe0 up to continue. In the meantime before the interface is reset, ping says sendto no buffer space available and named starts spitting out a lot of "error sending response: not enough free resources" from the DNS queries it was in the middle of responding to.