Return the question about "calcru" error messages. It is heavily based

on koitsu@'s wiki page and the mailing list archives.

Reviewed by:  trhodes, danger
Approved by:  gabor
This commit is contained in:
Gabor Pali 2008-06-21 08:36:19 +00:00
parent 67b6e2d1ea
commit ebb3804718
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=32381

View file

@ -3702,6 +3702,37 @@ chip1@pci0:31:5: class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02
</answer>
</qandaentry>
<qandaentry>
<question>
<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 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>