panic: kmem_malloc

Bosko Milekic bmilekic at
Thu Jul 10 11:54:02 PDT 2003

Sorry for the top-reply...

But for now the only advice I have is that you tune the boot-time
kern.vm.kmem.size tunable.  Don't set it too high, but you can try about
250,000 for your configuration.  The constant we have that caps the size
is getting too small and we're at least going to have to bump that up


On Thu, Jul 10, 2003 at 07:45:46PM +0200, Lukas Ertl wrote:
> Hi,
> we are currently stress-testing two 5.1 machines. Each of the machines
> have a 2.6GHz P4 and 512 MB RAM. The machines are running zebra, ospfd and
> nscd. We bomb the machines with many DNS requests (up to 50k/s),
> transmitted over Gigabit Ethernet.
> Unfortunately, both machines panic soon after starting the tests, and both
> go down with "kmem_malloc(4096): kmem_map too small" and says the current
> process is "4 (g_down)". I'd love to present a coredump and a backtrace,
> but somehow it just doesn't dump, it rather panics again with
> "ata_dmasetup: transfer active".
> Well, if I get this right, it means that the kernel VM is exhausted. Is
> there anything I can do apart from using more RAM?
> regards,
> le
> -- 
> Lukas Ertl                             eMail: l.ertl at
> UNIX-Systemadministrator               Tel.:  (+43 1) 4277-14073
> Zentraler Informatikdienst (ZID)       Fax.:  (+43 1) 4277-9140
> der Universit?t Wien         
> _______________________________________________
> freebsd-current at mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at"

Bosko Milekic  *  bmilekic at  *  bmilekic at
TECHNOkRATIS Consulting Services  *

More information about the freebsd-current mailing list