diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml
index 7bc6aa879b..b19828c0e7 100644
--- a/en_US.ISO8859-1/books/faq/book.xml
+++ b/en_US.ISO8859-1/books/faq/book.xml
@@ -2898,37 +2898,6 @@ chip1@pci0:31:5:        class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02
 	</answer>
       </qandaentry>
 
-      <qandaentry>
-	<question id="calcru-negative-runtime">
-	  <para>Why are <errorname>calcru: negative runtime</errorname>
-	    or <errorname>calcru: runtime went backwards</errorname>
-	    messages pounding the console?</para>
-	</question>
-
-	<answer>
-	  <para>There is a known problem when enabling &intel; Enhanced
-	    SpeedStep from the BIOS: it causes the kernel to start printing
-	    <errorname>calcru</errorname> messages like this:</para>
-
-	  <screen>calcru: runtime went backwards from 6 usec to 3 usec for pid 37 (pagezero)
-calcru: runtime went backwards from 6 usec to 3 usec for pid 36 (vmdaemon)
-calcru: runtime went backwards from 170 usec to 138 usec for pid 35 (pagedaemon)
-calcru: runtime went backwards from 553 usec to 291 usec for pid 15 (swi6: task queue)
-calcru: runtime went backwards from 15521 usec to 10366 usec for pid 2 (g_event)
-calcru: runtime went backwards from 25 usec to 12 usec for pid 11 (swi1: net)
-calcru: runtime went backwards from 4417 usec to 3960 usec for pid 1 (init)
-calcru: runtime went backwards from 2084385 usec to 1793542 usec for pid 1 (init)
-calcru: runtime went backwards from 408 usec to 204 usec for pid 0 (swapper)</screen>
-
-	  <para>It is because &intel; SpeedStep (EIST) is incompatible
-	    with some motherboards.</para>
-
-	  <para>Workaround: Disable the EIST feature in the BIOS.  You
-	    can still achieve ACPI-based processor frequency throttling
-	    by using &man.powerd.8;.</para>
-	</answer>
-      </qandaentry>
-
       <qandaentry>
 	<question id="computer-clock-skew">
 	  <para>Why does the clock on my computer keep incorrect time?</para>