From owner-freebsd-ppc@freebsd.org Tue May 3 03:24:13 2016 Return-Path: Delivered-To: freebsd-ppc@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 8087CB2BAB6 for ; Tue, 3 May 2016 03:24:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FB8E1CE4 for ; Tue, 3 May 2016 03:24:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ig0-x232.google.com with SMTP id u10so103994077igr.1 for ; Mon, 02 May 2016 20:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=pQBnEn1LQpkBztPlW/MyUBfUvX8drJ9PVvfgvpJPoxI=; b=wPNER6xrHaijGyTPbcJeCN9zjrpIJYRinTA5aa25ms9tVXRvSt6Hbfe29FDTfbJiRE 234RK0k0bwBiY7uPATN2oAJe21SZ7NqhmZkBC2YEhod+1+GGSYeiAOuVtC890ErkWcIg yXew21eF7OBSwofQPNBlmsxWXSBZn112Twk/czIK9F7G7DY73py8hhQ/J7JAosbYxT1A XfGcqM50xCw37YqBHtfAPEKzcKRYzGdTW2hmgfCexw7p9Ui36GWvtMMc0MskLV8j7a2N mn3d41yKNTM9MDdXgCWMME4IsGnVQTY/sv+JsONJxfahwYhv2j5hVxBlsTeoro4avUep kK/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=pQBnEn1LQpkBztPlW/MyUBfUvX8drJ9PVvfgvpJPoxI=; b=BYGSp3LGJhuYu9iSD2AizfBqU4YZEawsV0TK5yEE94N/1KGWvoVy5k3ZBSefdf16DI EbfDikK61l2nP4eIkKVwcj3OV7kAtypizlYMftkIgbjgb3JB2cBPyw79ybZALcOardUK PxxRxP96i+4lLaWhqK5mFq3olnhPBPlHYVKIywL4jmyQfxNamGS3pNMwzPJ5uMdG2WFY HEDSumm4ES6pnoN7GW9HfolC8H+7ddbu3IdkaFespmLR2zw3YBp20sCP/5ZwnP4lHuJO /WKOBr6Rh933jbK+8J81NdGuMyQScRwLBTqHuxMjPJt/ZCrLYcgcG5AF8fRah2NyuuTI rQoQ== X-Gm-Message-State: AOPr4FXgyENEv7nddXvMsVqMLsCLMwnYjx22z3+tPhRTKpGqxsB+M5SA2yicECYBlZhRJBfB2fzf6CQfgTGN9A== MIME-Version: 1.0 X-Received: by 10.50.32.102 with SMTP id h6mr23676945igi.16.1462245852205; Mon, 02 May 2016 20:24:12 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.75.68 with HTTP; Mon, 2 May 2016 20:24:12 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <5727F71E.20101@FreeBSD.org> References: <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> Date: Mon, 2 May 2016 21:24:12 -0600 X-Google-Sender-Auth: l5icnEmHYaEw9yRZzPTHdihg5Jo Message-ID: Subject: Re: wired memory leak at r298785 From: Warner Losh To: Steve Wills Cc: FreeBSD PowerPC ML , FreeBSD Current , Scott Long Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 03:24:13 -0000 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. Warner