os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove Question 5.19

Browse source 
Reviewed by:	trhodes, danger, remko
Approved by:	gabor (mentor)
This commit is contained in:
Gabor Pali 2008-06-14 10:27:43 +00:00
parent 100ecdb205
commit ff68033ea1
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=32242
1 changed files with 0 additions and 41 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -3434,47 +3434,6 @@ quit</programlisting>
</answer>
</qandaentry>
<qandaentry>
<question id="calcru-negative">
<para>Why does my machine print
<errorname>calcru: negative time...</errorname>?</para>
</question>
<answer>
<para>This can be caused by various hardware or software
ailments relating to interrupts. It may be due to bugs but can
also happen by nature of certain devices. Running TCP/IP over
the parallel port using a large MTU is one good way to provoke
this problem. Graphics accelerators can also get you here, in
which case you should check the interrupt setting of the card
first.</para>
<para>A side effect of this problem are dying processes with the
message <errorname>SIGXCPU exceeded cpu time limit</errorname>.</para>
<para>If the problem cannot be fixed otherwise the solution
is to set this sysctl variable:</para>
<screen>&prompt.root; <userinput>sysctl -w kern.timecounter.method=1</userinput></screen>
<note>
<para>The <option>-w</option> option of &man.sysctl.8; is
deprecated and silently ignored in &os; 4.4-RELEASE and all
newer versions. You can safely ommit it when setting options
with <command>sysctl</command> as shown above.</para>
</note>
<para>This means a performance impact, but considering the cause
of this problem, you probably will not notice. If the problem
persists, keep the sysctl set to one and set the
<literal>NTIMECOUNTER</literal> option in your kernel to
increasingly large values. If by the time you have reached
<literal>NTIMECOUNTER=20</literal> the problem is not solved,
interrupts are too hosed on your machine for reliable
time keeping.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="pnp-not-found">
<para>Why is my PnP card no longer found (or found as