From ff68033ea16f5310d78ae01f0ec8f262cd0fbbf9 Mon Sep 17 00:00:00 2001 From: Gabor Pali Date: Sat, 14 Jun 2008 10:27:43 +0000 Subject: [PATCH] Remove Question 5.19 Reviewed by: trhodes, danger, remko Approved by: gabor (mentor) --- en_US.ISO8859-1/books/faq/book.sgml | 41 ----------------------------- 1 file changed, 41 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 5066232280..b2569fb2ad 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -3434,47 +3434,6 @@ quit - - - Why does my machine print - calcru: negative time...? - - - - 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. - - A side effect of this problem are dying processes with the - message SIGXCPU exceeded cpu time limit. - - If the problem cannot be fixed otherwise the solution - is to set this sysctl variable: - - &prompt.root; sysctl -w kern.timecounter.method=1 - - - The 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 sysctl as shown above. - - - 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 - NTIMECOUNTER option in your kernel to - increasingly large values. If by the time you have reached - NTIMECOUNTER=20 the problem is not solved, - interrupts are too hosed on your machine for reliable - time keeping. - - - Why is my PnP card no longer found (or found as