From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 28 17:01:59 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDFE316A4CE for ; Wed, 28 Apr 2004 17:01:59 -0700 (PDT) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFA2343D41 for ; Wed, 28 Apr 2004 17:01:59 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (fad986123a8e9afe9ac506b34088370b@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i3T01wOH004029; Wed, 28 Apr 2004 17:01:59 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CCFCC5220D; Wed, 28 Apr 2004 17:01:58 -0700 (PDT) Date: Wed, 28 Apr 2004 17:01:58 -0700 From: Kris Kennaway To: John Uhlig Message-ID: <20040429000158.GA61693@xor.obsecurity.org> References: <409024D6.7090800@parc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <409024D6.7090800@parc.com> User-Agent: Mutt/1.4.2.1i cc: sunsa@parc.com cc: hackers@freebsd.org Subject: Re: kmem_malloc crashes running FreeBSD 5.2.1-RELEASE-p5 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2004 00:02:00 -0000 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 28, 2004 at 02:40:38PM -0700, John Uhlig wrote: > Hi. >=20 > We are running FreeBSD 5.2.1-RELEASE-p5 with a fairly generic kernel on a > Dell PowerEdge 2650 with 1/2TB of disk RAID arrays. It recently crashed at > about 3AM while running the daily /etc/periodic/security/100.chksetuid=20 > script. >=20 > I am able to crash this system at will (takes about 5-10 minutes by=20 > running the > security scripts in a loop and using gtar to copy files to the server at= =20 > the same > time. I have included output from one core dump below. The other core dum= ps > I have so far are almost exactly the same e.g. "Error accessing memory=20 > address > 0xf8b7983c" is the same in all core dumps so far. >=20 > On the web, freebsd mailing lists and bug lists, I have seen existing=20 > thread about > "kmem_malloc and kmem_map too small" problems - but no evidence of a fix > or patch. We experienced the same problem running 4.9 but were able to=20 > fix it > by setting the MAXMEM option in our kernel conf file to a value 1GB less= =20 > than > actual physical memory size. This does not help with 5.2.1-RELEASE-p5. >=20 > My group is under pressure to bring 3 of these servers on-line for our us= er > community by the end of the month and would greatly appreciate any help > in resolving this problem. See PR 53416. You just need to tune your kernel resource allocation to deal with the large amount of memory your system has. Kris --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAkEX2Wry0BWjoQKURAoRYAJ47tYUJTpJXREpY5t8TZphwK7MgvACfVKOM +iH0o1aIlPsTFMkshfW3Z2k= =+b00 -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI--