From owner-freebsd-current@FreeBSD.ORG Thu May 29 18:04:11 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB442AFF for ; Thu, 29 May 2014 18:04:11 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B430F24A7 for ; Thu, 29 May 2014 18:04:11 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 25F0FB926; Thu, 29 May 2014 14:04:10 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: Memory blackhole in 11. Possibly libc.so.7? Date: Thu, 29 May 2014 12:11:27 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <1401356463384-5916161.post@n5.nabble.com> <201405290908.10274.jhb@freebsd.org> <1401374538677-5916224.post@n5.nabble.com> In-Reply-To: <1401374538677-5916224.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201405291211.27264.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 May 2014 14:04:10 -0400 (EDT) Cc: Beeblebrox X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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, 29 May 2014 18:04:11 -0000 On Thursday, May 29, 2014 10:42:18 am Beeblebrox wrote: > >> Why do you think libc.so.7 has anything to do with this? > > Well, because there are two instances of it running in the lsof dump, with > several possible "child process" candidates. Why would they be hanging > around when practically everything has been killed? Everything that is dynamically pulls in libc.so.7. This includes /bin/sh, etc. However, those mappings are not _wired_ memory. Those would just be active or inactive pages. > Radeon*.ko modules are a very strong possibility, as I knew before I posted. > Unfortunately I cannot kldunload those modules once laded because then tty's > go dark and I must reboot. I send the Radeon developer some of my crash > reports once and a while, so nothing to add there. Have not heard from him > in a while, and I d't want to disturb him unnecessarily. > > And yes, as Alexander points out, zfs is also a possibility. ZFS is almost certainly the cause of the wired memory usage. -- John Baldwin