Commit d04a78fb authored by Gilles Chanteperdrix's avatar Gilles Chanteperdrix

doc: regenerate

parent c5da78a1

Too many changes to show.

To preserve performance only 1000 of 1000+ files are displayed.
Installing Xenomai 2.6.4
Installing Xenomai 2.6.5
-------------------------------------------------------------------------------
......
......@@ -62,6 +62,8 @@ Table of Contents
6.4. Any Xenomai service fails with code -38 (ENOSYS)
6.5. My application reserves a lot of memory
-------------------------------------------------------------------------------
This file is a troubleshooting guide about various known issues regarding
Xenomai.
......@@ -73,6 +75,8 @@ For questions, corrections and improvements, write to the mailing list:
1. Kernel configuration
-----------------------
When configuring the Linux kernel, some options should be avoided.
CONFIG_CPU_FREQ
......@@ -96,6 +100,8 @@ For x86 specific options see also this page:
2. 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.
......@@ -111,7 +117,9 @@ Xenomai: starting RTDM services.
Where <arch> is the architecture you use, check the following sections, they
describe the usual error messages you may encounter.
2.1. 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,
......@@ -122,27 +130,35 @@ 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.
2.2. Kernel stops with an OOPS
------------------------------
Please make sure that you have followed the "Kernel configuration" section.
Then, try capturing the oops text (using a serial console or netconsole) post
the oops to the xenomai mailing list: "xenomai@xenomai.org", with the kernel
configuration you used to compile the failing kernel.
2.3. 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.
2.4. Xenomai: compiled for TSC, but CPU has no TSC
--------------------------------------------------
You selected a CPU which as a TSC ("Pentium classic", and above), but the CPU
on which you run the kernel has no TSC. This issue was resolved in the I-pipe
core for Linux 3.4, but for prior versions, you need to select a CPU without a
TSC when configuring the kernel, and recompile the kernel.
2.5. Xenomai has detected a CPU frequency of 0
----------------------------------------------
This happens when running in emulators. In such a case, Xenomai can not run as
it needs to know the clock frequency.
......@@ -151,15 +167,21 @@ This may also happen when using I-pipe core patch for Linux 3.2, compiled for a
CPU with a TSC, but running on a CPU without a TSC, as in the "Xenomai:
compiled for TSC case.
2.6. I-pipe: could not find timer for cpu #x
--------------------------------------------
See code -19.
2.7. Xenomai: Local APIC absent or disabled!
--------------------------------------------
See code -19.
2.8. 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
......@@ -210,14 +232,18 @@ when running the latency test again, your peripheral is working properly and
you still observe high latencies, then you are out of luck, the peripheral you
want is likely to be the cause of such latencies.
2.9. Xenomai: system init failed, code -19
------------------------------------------
The most probable reason is that Xenomai could not find a timer.
Check that you have not enabled one of the options in the "Kernel
configuration" section.
2.9.1. On x86
-------------
You will most likely also see the following message:
......@@ -238,7 +264,9 @@ support is available. There are two options for fixing this issue:
You may want to look at the file Documentation/kernel-parameters.txt from
the Linux source tree, for more information about this parameter.
2.9.2. On AMD x86_64
--------------------
You will most likely also see the following message:
......@@ -253,7 +281,9 @@ located in the Advanced BIOS Features→ menu (AMD C1E Support).
Disabling AMD K8 Cool&Quiet option in a BIOS does not solve the
problem.
2.9.3. On ARM
-------------
If you see the following message:
......@@ -264,7 +294,9 @@ configuration, but the processor on which you are running the kernel has no
support for VFP. In that case, you have to recompile the kernel with
CONFIG_XENO_HW_FPU disabled.
2.9.4. On other supported platforms
-----------------------------------
As on x86, on other platforms where Xenomai shares the timer with Linux, the
timer is only used if it was not shut down by Linux. So you should check the
......@@ -278,7 +310,9 @@ post a message to the xenomai mailing list: "xenomai@xenomai.org", sending:
issue
* the complete kernel boot log.
2.9.5. On a new I-pipe port
---------------------------
You will most likely also see the following message:
......@@ -292,7 +326,9 @@ with the ipipe_timer member of the struct clock_event_device structure.
For an example on the ARM platform see this page:
"http://www.xenomai.org/index.php/I-pipe-core:ArmPorting#The_general_case".
2.10. Xenomai: system init failed, code -22
-------------------------------------------
On the ppc64 platform, check whether CONFIG_PPC_64K_PAGES is defined in your
kernel configuration. If so, then you likely need to raise all Xenomai
......@@ -304,11 +340,15 @@ assumption that PAGE_SIZE = 4k.
3. Problems when running the latency test
-----------------------------------------
The first test to run to see if Xenomai is running correctly on your platform
is the latency test. The following sections describe the usual reasons for this
test not to run correctly.