From 163083d41ad468b412de6311f46334461db90a22 Mon Sep 17 00:00:00 2001 From: Ceri Davies Date: Mon, 8 Nov 2004 19:22:25 +0000 Subject: [PATCH] Update an FAQ that was never really 2.0 specific to reflect reality. --- en_US.ISO8859-1/books/faq/book.sgml | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index cfaed52e42..cf163ef9c3 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -3667,32 +3667,27 @@ quit - Why does FreeBSD 2.0 panic with + Why does FreeBSD panic with kmem_map too small!? - - The message may also be - mb_map too small! - - The panic indicates that the system ran out of virtual memory for network buffers (specifically, mbuf clusters). You can increase the amount of VM available for mbuf clusters by adding: - options "NMBCLUSTERS=n" + options NMBCLUSTERS=n to your kernel config file, where n is a number in the range 512-4096, depending on the number of concurrent TCP - connections you need to support. I would recommend trying + connections you need to support. We recommend trying 2048 - this should get rid of the panic completely. You can monitor the number of mbuf clusters allocated/in use on the system with netstat -m (see &man.netstat.1;). The default value for NMBCLUSTERS is - 512 + MAXUSERS * 16. + 1024 + MAXUSERS * 64.