Date: Sat, 04 Jan 2003 12:59:59 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: phk@freebsd.org Cc: Hiroki Sato <hrs@eos.ocn.ne.jp>, wjw@withagen.nl, current@freebsd.org Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small... Message-ID: <3E174B4F.5E183600@mindspring.com> References: <2303.1041706799@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E174B4F.5E183600>