Date: Thu, 29 May 2014 07:42:18 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-current@freebsd.org Subject: Re: Memory blackhole in 11. Possibly libc.so.7? 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>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1401374538677-5916224.post>