Date: Sat, 11 Jan 2003 19:45:07 +0900 (JST) From: Hiroki Sato <hrs@eos.ocn.ne.jp> To: phk@FreeBSD.ORG Cc: tlambert2@mindspring.com, current@FreeBSD.ORG Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small... Message-ID: <20030111.194507.130543329.hrs@eos.ocn.ne.jp> In-Reply-To: <2303.1041706799@critter.freebsd.dk> References: <20030105.034940.18284223.hrs@eos.ocn.ne.jp> <2303.1041706799@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
phk@FreeBSD.ORG wrote in <2303.1041706799@critter.freebsd.dk>: phk> I only have 2G ram and that's what I have tested (extensively). If we're phk> still broken for >2G ram, somebody needs to revist this. phk> phk> One thing you can try is reduce the value of the phk> sysctl kern.maxvnodes phk> phk> If you set it to the same value as used for 2G (appros 130000), I phk> think your machine should survive with 3G RAM. Thank you for the clarification. I notice that the panic happens when numvnodes becomes more than about 185000. When kern.maxvnodes=130000 (198799 by default) is specified, the system works fine under heavy loads during this week. Is anyone else suffering from it? If it happens on all of >2GB systems, I think it should be solved (or described in relnotes) before the release. -- | Hiroki SATO <hrs@eos.ocn.ne.jp> 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?20030111.194507.130543329.hrs>