From owner-freebsd-current@freebsd.org Tue May 3 06:03:04 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E2F5B2B737; Tue, 3 May 2016 06:03:04 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EEA881EC9; Tue, 3 May 2016 06:03:03 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [0.0.0.0] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id u4362oK1093461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 3 May 2016 06:02:56 GMT (envelope-from swills@FreeBSD.org) Subject: Re: wired memory leak at r298785 To: Warner Losh References: <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> Cc: FreeBSD PowerPC ML , FreeBSD Current , Scott Long From: Steve Wills Message-ID: <57283F05.80305@FreeBSD.org> Date: Tue, 3 May 2016 02:02:45 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Tue, 03 May 2016 06:02:58 +0000 (UTC) X-Spam-Status: No, score=2.8 required=4.5 tests=HELO_MISC_IP, RCVD_ILLEGAL_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 03 May 2016 06:03:04 -0000 On 05/ 2/16 11:24 PM, Warner Losh wrote: > > > On Mon, May 2, 2016 at 6:55 PM, Steve Wills > wrote: > > Hi, > > On 05/ 2/16 09:32 AM, Steve Wills wrote: > > Hi, > > > > Just did my monthly update and r298785 seems to be leaking wired > memory > > rather rapidly. My system has 8gb of RAM and the amount of wired > memory > > just goes up and up continuously. It takes about 12 hours before it > > exhausts all the RAM and sort of locks up (though shutdown still > works). > > > > I also made one other change to the system at the same time as > updating, > > which was to add another disk and configure it using ZFS. Perhaps this > > is a ZFS on PowerPC64 issue? My amd64 box running the same rev of > > CURRENT doesn't have the issue. > > > > I've rebooted the box and started repeatedly logging the output of > vmstat -m. It seems to show CAM CCB using a lot of memory and growing > rather rapidly. For example, here's a few lines of diff output: > > - CAM CCB 91418 182836K - 187149 2048 > + CAM CCB 447070 894140K - 900292 2048 > > from two samples that are 60 minutes apart. > > The box is isn't terribly busy, it's just running the monitoring daemons > running (snmpd, collectd), whatever web requests are hitting it (very > few if any), this logging process, and my shell, etc. > > Could this be related to recent changes in CURRENT? > > Copying Scott and Warner in case they have comments on this since I'm > told they have been active in this area recently. > > > I've been looking into it. I'm not sure what's up since I don't see it > in production. I'll give it a bump in priority though. > Thanks! I did notice that killing bsnmpd drastically slowed the rate of growth, but didn't completely eliminate it. Steve