From owner-freebsd-stable@FreeBSD.ORG Thu May 25 20:56:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 504F216C3B6 for ; Thu, 25 May 2006 20:56:23 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AB3243E48 for ; Thu, 25 May 2006 20:54:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 21B8C1A4EE7; Thu, 25 May 2006 13:54:15 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9B05E51716; Thu, 25 May 2006 16:54:14 -0400 (EDT) Date: Thu, 25 May 2006 16:54:14 -0400 From: Kris Kennaway To: "Arno J. Klaassen" Message-ID: <20060525205414.GC30137@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uh9ZiVrAOUUm9fzH" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: kmem leak in tmpmfs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 20:56:29 -0000 --uh9ZiVrAOUUm9fzH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote: > Hello, >=20 > I get a very easy to reproduce panic on 6.1-STABLE : >=20 > /etc/periodic/weekly/310.locate panics with >=20 > panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated It looks like you are using a malloc-backed md and you do not have enough RAM to handle the size. Perhaps tmpmfs does not use swap backing, as it is supposed to? Kris --uh9ZiVrAOUUm9fzH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdhl1Wry0BWjoQKURAoidAKCmFCfxU1zyI9eWevyyvMeGnpsQhgCeKdJw ppcYcFoDPfwqRPAvFrv+cxI= =tmsg -----END PGP SIGNATURE----- --uh9ZiVrAOUUm9fzH--