From owner-freebsd-stable@FreeBSD.ORG Wed Feb 29 20:41:33 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 237A1106566B for ; Wed, 29 Feb 2012 20:41:33 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id B17CF8FC17 for ; Wed, 29 Feb 2012 20:41:32 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id q1TKfU1m061524; Wed, 29 Feb 2012 21:41:31 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id q1TKfUK9061523; Wed, 29 Feb 2012 21:41:30 +0100 (CET) (envelope-from marius) Date: Wed, 29 Feb 2012 21:41:30 +0100 From: Marius Strobl To: "Garrett R. Groesbeck" Message-ID: <20120229204130.GA61509@alchemy.franken.de> References: <000001ccf4d6$66513b00$32f3b100$@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001ccf4d6$66513b00$32f3b100$@gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.0-RELEASE - Trouble Booting on SPARC64 - kmem_suballoc error 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, 29 Feb 2012 20:41:33 -0000 On Sun, Feb 26, 2012 at 05:31:35PM -0500, Garrett R. Groesbeck wrote: > Hello, > > I hope you are well. I've been working on a Sun Blade 2000 with FreeBSD 9.0 > (sparc64) installed. > > There's trouble with /boot/loader.conf when you try to boot the install disc > (and even after the install when I try to boot up): > > panic: kmem_suballoc: bad status return of 3 > > So when it gives me the chance to enter a boot command, I enter the > following: > > OK set hw.physmem=1048576000 > That apparently is a bug in the MI part of the VM triggered by the highly fragment physical memory of b1k and b2k with 2 GB of RAM. You can work around it by setting the vm.kmem_size_scale tunable to 2 without sacrificing physical memory. The latter meanwhile is also the default set by the MD part, awaiting further clues from alc@. Marius