[Xenomai-git] Philippe Gerum : doc/asciidoc: remove left over
Module: xenomai-3
Branch: master
Commit: 9633e2ddda4255a0b6a9008ae45faaac034e660e
URL:
http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=9633e2ddda4255a0b6a9008ae45faaac034e660e
Author: Philippe Gerum
Date: Sun Sep 28 21:18:28 2014 +0200
doc/asciidoc: remove left over
---
doc/asciidoc/TROUBLESHOOTING.adoc | 650 -
1 file changed, 650 deletions(-)
diff --git a/doc/asciidoc/TROUBLESHOOTING.adoc
b/doc/asciidoc/TROUBLESHOOTING.adoc
deleted file mode 100644
index 9938da8..000
--- a/doc/asciidoc/TROUBLESHOOTING.adoc
+++ /dev/null
@@ -1,650 +0,0 @@
-Troubleshooting guide for Xenomai 3.x
-=
-
-This file is a troubleshooting guide about various known issues
-regarding Xenomai 3.x.
-
-[[kconf]]
-Kernel configuration
-
-
-When configuring the Linux kernel, some options should be avoided.
-
-CONFIG_CPU_FREQ:: This allows the CPU frequency to be modulated with
-workload, but many CPUs change the TSC counting frequency also, which
-makes it useless for accurate timing when the CPU clock can
-change. Also some CPUs can take several milliseconds to ramp up to
-full speed.
-
-CONFIG_CPU_IDLE:: Allows the CPU to enter deep sleep states,
-increasing the time it takes to get out of these sleep states, hence
-the latency of an idle system. Also, on some CPU, entering these deep
-sleep states causes the timers used by Xenomai to stop functioning.
-
-CONFIG_KGDB:: This option can not be enabled with current versions of
-the I-pipe patch.
-
-For x86 specific options see also
-http://www.xenomai.org/index.php/Configuring_x86_kernels[this page].
-
-
-[[kerror]]
-Xenomai or I-pipe error in the kernel log
--
-
-If the Xenomai and I-pipe messages do not appear in the kernel
-log as:
-
---
-I-pipe: head domain Xenomai registered.
-Xenomai: hal/ started.
-Xenomai: scheduling class idle registered.
-Xenomai: scheduling class rt registered.
-Xenomai: real-time nucleus v2.6.1 (Light Years Away) loaded.
-Xenomai: debug mode enabled.
-Xenomai: starting native API services.
-Xenomai: starting POSIX services.
-Xenomai: starting RTDM services.
---
-
-Where is the architecture you use, check the following
-sections, they describe the usual error messages you may encounter.
-
-
-The kernel stops after "Uncompressing Linux... done, booting the kernel."
-~
-
-This means that the kernel crashes before the console is enabled. You
-should enable the +CONFIG_EARLY_PRINTK+ option. For some architectures
-(blackfin, x86, arm), enabling this option also requires passing the
-+earlyprintk+ parameter on the kernel command line. See
-'Documentation/kernel-parameters.txt' for possible values.
-
-For the ARM architecture, you have to enable +CONFIG_DEBUG_KERNEL+ and
-+CONFIG_DEBUG_LL+ in order to be able to enable +CONFIG_EARLY_PRINTK+.
-
-
-The kernel stops with an OOPS
-~
-
-Please make sure that you have followed the <> section. Then, try capturing the oops text (using a
-serial console or netconsole) post the oops to the
-mailto:xeno...@xenomai.org[xenomai mailing list], with the kernel
-configuration you used to compile the failing kernel.
-
-
-The kernel boots but does not print any message
-~~~
-
-Your distribution may be configured to pass the +quiet+ option on the
-kernel command line. In this case, the kernel does not print all the
-log messages, however, they are still available using the +dmesg+
-command.
-
-
-I-pipe: could not find timer for cpu #x
-~~~
-
-See <>.
-
-
-Xenomai: Local APIC absent or disabled!
-~~~
-
-See <>.
-
-[[SMI]]
-Xenomai: SMI-enabled chipset found, but SMI workaround disabled
-~~~
-
-First you should run the latency test under some load and see if
-you experience any pathological latency ("pathological" meaning more
-than, say, 100 micro-seconds). If you do not observe any such latency,
-then this warning is harmless, and if you find it annoying, you may
-disable "SMI detection" in Xenomai's configuration menu. You can skip
-the rest of this section.
-
-If you observe any high latency then you have a problem with SMI, and
-this warning was intended for you. But the Xenomai configuration menu
-allow you to enable two workarounds which may help you. These
-workarounds may be found in the Machine/SMI workaround sub-menu of
-Xenomai configuration menu.
-
-The first workaround which you should try is to disable all SMI
-sources. In order to do this, in the Xenomai configuration menu, select
-the options "Enable SMI workaround" and "Globally disable SMI". This
[Xenomai-git] Philippe Gerum : doc/asciidoc: remove left over
Module: xenomai-3
Branch: next
Commit: 9633e2ddda4255a0b6a9008ae45faaac034e660e
URL:
http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=9633e2ddda4255a0b6a9008ae45faaac034e660e
Author: Philippe Gerum
Date: Sun Sep 28 21:18:28 2014 +0200
doc/asciidoc: remove left over
---
doc/asciidoc/TROUBLESHOOTING.adoc | 650 -
1 file changed, 650 deletions(-)
diff --git a/doc/asciidoc/TROUBLESHOOTING.adoc
b/doc/asciidoc/TROUBLESHOOTING.adoc
deleted file mode 100644
index 9938da8..000
--- a/doc/asciidoc/TROUBLESHOOTING.adoc
+++ /dev/null
@@ -1,650 +0,0 @@
-Troubleshooting guide for Xenomai 3.x
-=
-
-This file is a troubleshooting guide about various known issues
-regarding Xenomai 3.x.
-
-[[kconf]]
-Kernel configuration
-
-
-When configuring the Linux kernel, some options should be avoided.
-
-CONFIG_CPU_FREQ:: This allows the CPU frequency to be modulated with
-workload, but many CPUs change the TSC counting frequency also, which
-makes it useless for accurate timing when the CPU clock can
-change. Also some CPUs can take several milliseconds to ramp up to
-full speed.
-
-CONFIG_CPU_IDLE:: Allows the CPU to enter deep sleep states,
-increasing the time it takes to get out of these sleep states, hence
-the latency of an idle system. Also, on some CPU, entering these deep
-sleep states causes the timers used by Xenomai to stop functioning.
-
-CONFIG_KGDB:: This option can not be enabled with current versions of
-the I-pipe patch.
-
-For x86 specific options see also
-http://www.xenomai.org/index.php/Configuring_x86_kernels[this page].
-
-
-[[kerror]]
-Xenomai or I-pipe error in the kernel log
--
-
-If the Xenomai and I-pipe messages do not appear in the kernel
-log as:
-
---
-I-pipe: head domain Xenomai registered.
-Xenomai: hal/ started.
-Xenomai: scheduling class idle registered.
-Xenomai: scheduling class rt registered.
-Xenomai: real-time nucleus v2.6.1 (Light Years Away) loaded.
-Xenomai: debug mode enabled.
-Xenomai: starting native API services.
-Xenomai: starting POSIX services.
-Xenomai: starting RTDM services.
---
-
-Where is the architecture you use, check the following
-sections, they describe the usual error messages you may encounter.
-
-
-The kernel stops after "Uncompressing Linux... done, booting the kernel."
-~
-
-This means that the kernel crashes before the console is enabled. You
-should enable the +CONFIG_EARLY_PRINTK+ option. For some architectures
-(blackfin, x86, arm), enabling this option also requires passing the
-+earlyprintk+ parameter on the kernel command line. See
-'Documentation/kernel-parameters.txt' for possible values.
-
-For the ARM architecture, you have to enable +CONFIG_DEBUG_KERNEL+ and
-+CONFIG_DEBUG_LL+ in order to be able to enable +CONFIG_EARLY_PRINTK+.
-
-
-The kernel stops with an OOPS
-~
-
-Please make sure that you have followed the <> section. Then, try capturing the oops text (using a
-serial console or netconsole) post the oops to the
-mailto:xeno...@xenomai.org[xenomai mailing list], with the kernel
-configuration you used to compile the failing kernel.
-
-
-The kernel boots but does not print any message
-~~~
-
-Your distribution may be configured to pass the +quiet+ option on the
-kernel command line. In this case, the kernel does not print all the
-log messages, however, they are still available using the +dmesg+
-command.
-
-
-I-pipe: could not find timer for cpu #x
-~~~
-
-See <>.
-
-
-Xenomai: Local APIC absent or disabled!
-~~~
-
-See <>.
-
-[[SMI]]
-Xenomai: SMI-enabled chipset found, but SMI workaround disabled
-~~~
-
-First you should run the latency test under some load and see if
-you experience any pathological latency ("pathological" meaning more
-than, say, 100 micro-seconds). If you do not observe any such latency,
-then this warning is harmless, and if you find it annoying, you may
-disable "SMI detection" in Xenomai's configuration menu. You can skip
-the rest of this section.
-
-If you observe any high latency then you have a problem with SMI, and
-this warning was intended for you. But the Xenomai configuration menu
-allow you to enable two workarounds which may help you. These
-workarounds may be found in the Machine/SMI workaround sub-menu of
-Xenomai configuration menu.
-
-The first workaround which you should try is to disable all SMI
-sources. In order to do this, in the Xenomai configuration menu, select
-the options "Enable SMI workaround" and "Globally disable SMI". This
-o
