From owner-freebsd-stable@FreeBSD.ORG Wed Oct 25 17:31:28 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 3FC3A16A4B3 for ; Wed, 25 Oct 2006 17:31:28 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.200.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C2C43D5E for ; Wed, 25 Oct 2006 17:31:27 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (sccrmhc12) with ESMTP id <20061025173116012002fo83e>; Wed, 25 Oct 2006 17:31:26 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id B2E441FA037; Wed, 25 Oct 2006 10:31:15 -0700 (PDT) Date: Wed, 25 Oct 2006 10:31:15 -0700 From: Jeremy Chadwick To: Stefan Bethke Message-ID: <20061025173115.GA97447@icarus.home.lan> Mail-Followup-To: Stefan Bethke , FreeBSD Stable References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: FreeBSD Stable Subject: Re: panic: kmem_map too small 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: Wed, 25 Oct 2006 17:31:28 -0000 On Wed, Oct 25, 2006 at 07:17:26PM +0200, Stefan Bethke wrote: > We're consistely getting this panic even under smallish loads. I've > experimented with various values for VM_KMEM_SIZE_MAX (384, 512, 768 > and 1024 MB), but the boxes are still panicking after even short > periods (a few hours) just doing a buildworld, a few ports compiles, > or even when logging out of the console(?). > > Would logging vm.zone every few minutes help detecting a kernel > memory leak? > > I'm at a complete loss as to the actual cause of these. The ACPI > errors precede the panic below by only a few seconds, so I'd guess > they're a symptom, not a cause. We've tried with ACPI disabled in > the BIOS, but we also got these panics, so we re-enabled it. > > The hardware is a Tyan GT20 (2865) with a single-core Opteron, two > gigs of RAM and two or three SATA disks. > > Any ideas? Try tuning memory parameters via loader.conf: $ cat /boot/loader.conf # Increase maximum allocatable memory on a process to 768MB. # We don't choose 2GB (our amount of RAM) since that would # exhaust all memory, and result in a kernel panic. Maximum # stack size is still set to 128MB. One can view these # settings using limits(1). # kern.maxdsiz="805306368" kern.dfldsiz="805306368" kern.maxssiz="134217728" Adjusting kern.maxfiles and kern.maxfilesperproc might also help. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |