From owner-freebsd-current@FreeBSD.ORG Thu May 29 14:42:20 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4345BAB9 for ; Thu, 29 May 2014 14:42:20 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 25ECF21BA for ; Thu, 29 May 2014 14:42:19 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Wq1X8-00026N-MK for freebsd-current@freebsd.org; Thu, 29 May 2014 07:42:18 -0700 Date: Thu, 29 May 2014 07:42:18 -0700 (PDT) From: Beeblebrox To: freebsd-current@freebsd.org Message-ID: <1401374538677-5916224.post@n5.nabble.com> In-Reply-To: <201405290908.10274.jhb@freebsd.org> References: <1401356463384-5916161.post@n5.nabble.com> <201405290908.10274.jhb@freebsd.org> Subject: Re: Memory blackhole in 11. Possibly libc.so.7? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 14:42:20 -0000 >> 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? 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. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Memory-blackhole-in-11-Possibly-libc-so-7-tp5916161p5916224.html Sent from the freebsd-current mailing list archive at Nabble.com.