From owner-freebsd-current Sat Jan 4 13: 1:20 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D49637B401; Sat, 4 Jan 2003 13:01:19 -0800 (PST) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECA4043E4A; Sat, 4 Jan 2003 13:01:18 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0130.cvx40-bradley.dialup.earthlink.net ([216.244.42.130] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18UvPx-0005z7-00; Sat, 04 Jan 2003 13:01:18 -0800 Message-ID: <3E174B4F.5E183600@mindspring.com> Date: Sat, 04 Jan 2003 12:59:59 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: phk@freebsd.org Cc: Hiroki Sato , wjw@withagen.nl, current@freebsd.org Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small... References: <2303.1041706799@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a421fad4f9745fe1549aa2578693c231b893caf27dac41a8fd350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG phk@freebsd.org wrote: > In message <20030105.034940.18284223.hrs@eos.ocn.ne.jp>, Hiroki Sato writes: > > I also had "kmem_malloc(4096): kmem_map too small: 275378176 total allocated" > > several times on -current as of Jan 4th. My -current box has 3GB memory, > > but when the memory size is explicitly specified as 2GB via MAXMEM option, > > the panic disappears (but I don't know why...). > > Now that's different from the previous poster. > > The problem in this case is that some of the system constants are sized > based on the amount of RAM and appearantly we do this wrong for large > RAM configurations. > > I only have 2G ram and that's what I have tested (extensively). If we're > still broken for >2G ram, somebody needs to revist this. > > One thing you can try is reduce the value of the > sysctl kern.maxvnodes > > If you set it to the same value as used for 2G (appros 130000), I > think your machine should survive with 3G RAM. You can also increase the maximum number of open files, which will cause the number to be scaled larger. You can do this in the boot loader (e.g. loader.rc). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message