Remove obsolete question

Noted by:	imp
Approved by:	bcr (mentor, implicit)

en_US.ISO8859-1/books/faq/book.xml

@@ -2224,35 +2224,6 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
 	</answer>
       </qandaentry>
 
-      <qandaentry>
-	<question id="kmem-map-too-small">
-	  <para>My system has more than 1&nbsp;GB of RAM, and I'm
-	    getting panics with <errorname>kmem_map too small</errorname>
-	    messages.  What is wrong?</para>
-	</question>
-
-	<answer>
-	  <para>Normally, &os; determines a number of kernel parameters,
-	    such as the maximum number of files that can be open
-	    concurrently, from the amount of memory installed in the
-	    system.  On systems with one gigabyte of RAM or more, this
-	    <quote>auto sizing</quote> mechanism may choose values that
-	    are too high: while starting up, the kernel allocates
-	    various tables and other structures that fill up most of the
-	    available kernel memory.  Later on, while the system is
-	    running, the kernel has no more space left for dynamic
-	    memory allocations, and panics.</para>
-
-	  <para>Compile your own kernel, and add the
-	    <option>VM_KMEM_SIZE_MAX</option> to your kernel
-	    configuration file, increasing the maximum size to
-	    400&nbsp;MB (<option>options
-	    VM_KMEM_SIZE_MAX=419430400</option>).  400&nbsp;MB appears
-	    to be sufficient for machines with up to 6&nbsp;GB of
-	    memory.</para>
-	</answer>
-      </qandaentry>
-
       <qandaentry>
 	<question id="panic-kmemmap-too-small">
 	  <para>My system does not have 1&nbsp;GB of RAM, and &os; still