From owner-freebsd-current@FreeBSD.ORG Thu May 29 13:57:29 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 EA11B42B; Thu, 29 May 2014 13:57:29 +0000 (UTC) Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 969C52C97; Thu, 29 May 2014 13:57:29 +0000 (UTC) Received: by mail-qg0-f44.google.com with SMTP id i50so1031823qgf.31 for ; Thu, 29 May 2014 06:57:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type; bh=5dvVBP5nXgKDo/zmXi0dEzZfYUgAFMtcLvG3x1aO88s=; b=x7sMPkcMaKgwVdJZwQTmffnzjOAyUcn8xycea2do0ZKRj/CsvK8BqTHaeAMaD3+PNw BYh3AXD3pCpf50y59ga8UnVIQtKumdQWSVk+fR7Dhq87SmkOBJ7kOpBjtBmgDZS92ZPf cU8EtVs2tttcTROXSYUvn1ai4NscguZV9LYejexPgSmeTVndSUMvZWvktIO9DEi4Brl+ LfgNg3AWi5S9kyhCpxkFdbT+KAw7jwnggfp3Q0fbd5jADd7bdCmT72C0kjaTsY9heUkB tDCPty5R8bS1wu2/co6buPIab7KzbfuTXOgwUttgNqL+gjIuQQt+J75FeHWpad8QF4RI Xi+Q== X-Received: by 10.224.167.70 with SMTP id p6mr10127040qay.48.1401371848796; Thu, 29 May 2014 06:57:28 -0700 (PDT) Received: from kan ([2601:6:6780:750:226:18ff:fe00:232e]) by mx.google.com with ESMTPSA id m13sm1104041qab.19.2014.05.29.06.57.27 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Thu, 29 May 2014 06:57:27 -0700 (PDT) Date: Thu, 29 May 2014 09:57:22 -0400 From: Alexander Kabaev To: John Baldwin Subject: Re: Memory blackhole in 11. Possibly libc.so.7? Message-ID: <20140529095722.1765ce36@kan> In-Reply-To: <201405290908.10274.jhb@freebsd.org> References: <1401356463384-5916161.post@n5.nabble.com> <201405290908.10274.jhb@freebsd.org> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/m_bq8cJkdRCt329x3m1Pg62"; protocol="application/pgp-signature" Cc: freebsd-current@freebsd.org, 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 13:57:30 -0000 --Sig_/m_bq8cJkdRCt329x3m1Pg62 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 29 May 2014 09:08:10 -0400 John Baldwin wrote: > On Thursday, May 29, 2014 5:41:03 am Beeblebrox wrote: > > uname: FreeBSD 11.0-CURRENT #0 r266393M: Sun May 18 13:04:00 2014 > > amd64 I'm also loading the Radeon_kms modules > >=20 > >=20 > > I don't know if the lsof dump in single user mode will be of any > > help, but it seems like lib/libc.so.7 has something to do with it: >=20 >=20 > Why do you think libc.so.7 has anything to do with this? wired > memory is usually only allocated in the kernel, so if anything you > are looking at some sort of memory leak in a driver (maybe the radeon > driver?) >=20 > --=20 > John Baldwin Aren't ZFS buffers accounted as kernel wired memory?=20 -- Alexander Kabaev --Sig_/m_bq8cJkdRCt329x3m1Pg62 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iD8DBQFThzzGQ6z1jMm+XZYRAl+VAKDrpe09bFaY1eVKWFka2dmhxj6T3QCgvWjP eM2UZ6zdyfwsQT01nuy3ReE= =d2dL -----END PGP SIGNATURE----- --Sig_/m_bq8cJkdRCt329x3m1Pg62--