Subject: panic: uvm_mapent_alloc: out of static map entries, check MAX_KMAPENT
To: None <tech-kern@netbsd.org>
From: David Brownlee <abs@formula1.com>
List: tech-kern
Date: 07/29/2002 09:17:04
	Just had this on a 1.6_BETA4 machine, reasonably heavily loaded
	webserver with 1GB of RAM, and MAXPROC set to 2048.

	I'm compiling a new kernel with MAX_KMAPENT set to 4096, but is
	it reasonable to have to make this change by hand - could it be
	autosized better?

login: panic: uvm_mapent_alloc: out of static map entries, check MAX_KMAPENT (currently 2138)
Begin traceback...
uvm_mapent_alloc(c157ca00,c05834c0,e5956dcc,c034f315) at
uvm_mapent_alloc+0x7b
uvm_map_clip_end(c157ca00,c0568a00,e3737000,c0335f20) at
uvm_map_clip_end+0x15
uvm_unmap_remove(c157ca00,e3736000,e3737000,e5956e38) at
uvm_unmap_remove+0x123
uvm_unmap(c157ca00,e3736000,e3737000,c1e18000) at uvm_unmap+0x2a
uvm_km_free(c157ca00,e3736000,1000,e3834000) at uvm_km_free+0x31
uvm_km_free_poolpage1(c157ca00,e3736000,e5956edc,c026ebdc) at
uvm_km_free_poolpage1+0x31
mclpool_release(c058e7a0,e3736000,e5956edc,c0258eee) at
mclpool_release+0x18
pool_allocator_free(c058e7a0,e3736000,e5956f10,3) at
pool_allocator_free+0x23
pool_reclaim(c058e7a0,0,0,0) at pool_reclaim+0x1e3
pool_drain(0,0,e5956f8c,c033e90d) at pool_drain+0x5e
uvm_pageout(e5946730) at uvm_pageout+0x10e
End traceback...
syncing disks...


-- 
		David/absolute		abs@formula1.com