From owner-freebsd-stable@FreeBSD.ORG Thu Apr 11 00:08:19 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 9DEE84EC for ; Thu, 11 Apr 2013 00:08:19 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:17]) by mx1.freebsd.org (Postfix) with ESMTP id 83AA32BA for ; Thu, 11 Apr 2013 00:08:19 +0000 (UTC) Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta10.emeryville.ca.mail.comcast.net with comcast id NQ4W1l0070lTkoCAAQ8KJl; Thu, 11 Apr 2013 00:08:19 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta04.emeryville.ca.mail.comcast.net with comcast id NQ8J1l00G1t3BNj8QQ8Jh5; Thu, 11 Apr 2013 00:08:19 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8777D73A33; Wed, 10 Apr 2013 17:08:18 -0700 (PDT) Date: Wed, 10 Apr 2013 17:08:18 -0700 From: Jeremy Chadwick To: Chris Forgeron Subject: Re: kern/165903: mbuf leak Message-ID: <20130411000818.GA38803@icarus.home.lan> References: <46D80686C389884BB0C047851038EC456D8BCEBC@AA-EX0.acsi.ca> <20130410235347.GA38492@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130410235347.GA38492@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1365638899; bh=dD/cKkrr0vWaOVfcYuwTBWWwsQYTDuEC2z/4cCTDnIM=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=lFZ71dzeWCjbDQsb1EkaSoN3J/hzIrojtk26eIMUdyaSXxbC9e4mEyI0UkhPT91Uc NfHnIIZIAlyrCzQ53uhttLapUW1SuibOsbCHIcMN+rQl0Rn7Ug1k6kYrsdI71yUZUq PpDC6IsRkvKG5+vlxjPov7K8Owm4zjfoDyzbGleb4Oh2zyxX/zQDVDPzLx48QnI+Ng qpyzqa6p3Fr2DXHiUPf7WKZkb/6008Qi/c3TZ2eidLsiPiHfz89eY8HHPqjlfV+y4z 0enDfeVwuRrnZCs5sTiHwyIrV44avykYgoG6bMsWbFpmVM/n98YMvejxSpU7hoDwpM 1+rg+83IUYLuA== Cc: "freebsd-stable@freebsd.org" 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 00:08:19 -0000 On Wed, Apr 10, 2013 at 04:53:47PM -0700, Jeremy Chadwick wrote: > On Wed, Apr 10, 2013 at 07:39:31PM +0000, Chris Forgeron wrote: > > I've updated the PR on this via bug track email (hopefully, it bounced my first email) , but I thought I should bring it to the attention of the list as it's still happening, and the original PR was from March 2012. > > > > The PR is here: http://www.freebsd.org/cgi/query-pr.cgi?pr=165903&cat= > > > > I am experiencing the same mbuf leak on fresh 9.1-RELEASE machines (AMD64). Most of my machines are ESXi 5.1 VM's running the e1000 (em0) NIC. This VM is stock, just one freebsd-update done, nothing custom. > > > > I have also experienced this condition on an older 9.0-STABLE from Jul 1st 2012. I did not notice it much before that date, but I can't tell for sure. I have a few machines on that build that I still use, so confirmation was easy. > > > > 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. > > 1. This PR does not contain output from "dmesg" nor "pciconf -lvbc", nor > does your Email. Output from this matters. > > 2. Please try 9.1-STABLE and see if there is an improvement; there have > been a huge number of changes/fixes to em(4) between 9.1-RELEASE and > now. You can try this: > > https://pub.allbsd.org/FreeBSD-snapshots/amd64-amd64/9.1-RELENG_9-r249290-JPSNAP/ Other output that would be useful on a machine where the current mbuf count is actively very high: * vmstat -z * netstat -Q * netstat -n -x It would also be beneficial to provide any sysctl.conf and loader.conf adjustments you do. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |