From owner-freebsd-stable@FreeBSD.ORG Thu Apr 11 05:58:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4851797F for ; Thu, 11 Apr 2013 05:58:23 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2001:470:1f09:14c0::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0179C179 for ; Thu, 11 Apr 2013 05:58:22 +0000 (UTC) Received: from bsdrookie.norma.com. ([IPv6:fd00::726]) by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id r3B5wJEb061710 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 11 Apr 2013 11:58:19 +0600 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <516650FB.2020504@norma.perm.ru> Date: Thu, 11 Apr 2013 11:58:19 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: kern/165903: mbuf leak References: <46D80686C389884BB0C047851038EC456D8BCEBC@AA-EX0.acsi.ca> In-Reply-To: <46D80686C389884BB0C047851038EC456D8BCEBC@AA-EX0.acsi.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [IPv6:fd00::30a]); Thu, 11 Apr 2013 11:58:19 +0600 (YEKT) X-Spam-Status: No hits=-97.8 bayes=0.5 testhits RDNS_NONE=1.274, SPF_SOFTFAIL=0.972,USER_IN_WHITELIST=-100 autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2013 05:58:23 -0000 Hi. On 11.04.2013 01:39, Chris Forgeron wrote: > I do not experience the error if I load up vmware tools and use the vmx3f0 adapter, it's just with em0. > > I have set the mbufs to very high numbers (322144) to buy more time between lockups/crashes. Most often the systems stay functional, they just need a reboot or more mbufs if I add them. Some times they lock up or crash as I ifconfig down/up the adapter or attempt to add more mbufs via sysctl. > > 1) Is anyone else able to reproduce this problem? The PR is still open, which says to me not all of us can be having this problem or there would be more drive to fix. > 2) What do I need to help with to advance this problem? It's not just my systems, as evidenced by the original poster of the PR. > (I'm the author of the PR). I was experiencing this on 9.0 'till some -STABLE, after that the leak was gone on the exactly same configuration. This server is equipped with bce(4) interfaces only, so I don't see any connection with interface driver. I think it's more configuration related. I created this pr in order to investigate why one of my 9.x servers hangs periodically. Since that I tried lots of 9-STABLE snapshots, none of them fixed my problem. Last month I decided to switch to 10.x. The uptime is 37 days so far, none of my 9.x snapshots was able to stand that long. Even if this machine will crash while I write this - this definitely means that 10.x right now is at least equally stable as 9.x is, and can run as smoothly as 9.x does. My advice - use 10.0-CURRENT, 9.0 and all of it's descendant versions are broken beyond repair, imo. Switching to 10.x was a hard decision for me too, I was too scared by the '-CURRENT' karma. Seems like it's not that creepy. Eugene.