Date: Mon, 17 Dec 2012 21:54:19 +0000 (UTC) From: Rene Ladan <rene@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r40412 - translations/nl_NL.ISO8859-1/books/faq Message-ID: <201212172154.qBHLsJ8n082710@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: rene Date: Mon Dec 17 21:54:18 2012 New Revision: 40412 URL: http://svnweb.freebsd.org/changeset/doc/40412 Log: Merge up to r40411 Modified: translations/nl_NL.ISO8859-1/books/faq/book.xml Modified: translations/nl_NL.ISO8859-1/books/faq/book.xml ============================================================================== --- translations/nl_NL.ISO8859-1/books/faq/book.xml Mon Dec 17 20:42:27 2012 (r40411) +++ translations/nl_NL.ISO8859-1/books/faq/book.xml Mon Dec 17 21:54:18 2012 (r40412) @@ -6,7 +6,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/faq/book.xml - %SRCID% 40403 + %SRCID% 40411 --> <!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN" @@ -2984,37 +2984,6 @@ chip1@pci0:31:5: class=0x040100 c </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: 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> </question> @@ -3071,32 +3040,6 @@ kern.timecounter.hardware: TSC -> i82 </qandaentry> <qandaentry> - <question id="null-null"> - <para>Why did my laptop fail to correctly probe PC - cards?</para> - </question> - - <answer> - <para>This problem is common on laptops that boot more than - one operating system. Some non-BSD operating systems leave - PC card hardware in an inconsistent state. &man.pccardd.8; - will detect the card as - <errorname>"(null)""(null)"</errorname> instead of its - actual model.</para> - - <para>You must remove all power from the PC card slot to fully - reset the hardware. Completely power off the laptop. (Do - not suspend it, do not let it go into standby; the power - needs to be completely off.) Wait a few moments, and reboot. - Your PC card should work now.</para> - - <para>Some laptop hardware lies when it claims to be off. If - the above does not work shut down, remove the battery, wait - a moment, replace the battery, and reboot.</para> - </answer> - </qandaentry> - - <qandaentry> <question id="bootmanager-restore"> <para>Another operating system destroyed my Boot Manager. How do I get it back?</para> @@ -3809,33 +3752,6 @@ kern.timecounter.hardware: TSC -> i82 </qandaentry> <qandaentry> - <question id="multiport-serial-interrupts"> - <para>Why do I get interrupt conflicts with multi-port serial - code?</para> - </question> - - <answer> - <para>When I compile a kernel with multi-port serial code, it - tells me that only the first port is probed and the rest - skipped due to interrupt conflicts. How do I fix - this?</para> - - <para>The problem here is that &os; has code built-in to keep - the kernel from getting trashed due to hardware or software - conflicts. The way to fix this is to leave out the IRQ - settings on all but one port. Here is an example:</para> - - <programlisting># -# Multiport high-speed serial line - 16550 UARTS -# -device sio2 at isa? port 0x2a0 tty irq 5 flags 0x501 vector siointr -device sio3 at isa? port 0x2a8 tty flags 0x501 vector siointr -device sio4 at isa? port 0x2b0 tty flags 0x501 vector siointr -device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting> - </answer> - </qandaentry> - - <qandaentry> <question id="generic-kernel-build-failure"> <para>Why does every kernel I try to build fail to compile, even <filename>GENERIC</filename>?</para>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201212172154.qBHLsJ8n082710>