RADclock Troubleshooting
If you have some problems, you can probably find a solution here
- Which systems are supported
- I receive an error message when trying to install the radclock package
- I compiled the RADclock software but do not get kernel mode running
- I followed the instructions but the RADclock time is all over the place
Which systems are supported
The RADclock is expected to run any UNIX system. However, a kernel patch is needed to access in-kernel timestamping. The following systems are currently supported.
Do not hesitate to contact us if you need support for a specific system.
| FreeBSD | |||
|---|---|---|---|
| Version | Arch | RADclock version | Feed-Forward kernel version |
| 8.1 | i386 / amd64 | 0.3.3 | 1 |
| 8.0 | i386 / amd64 | 0.3.3 | 1 |
| 7.4 | i386 / amd64 | 0.3.3 | 1 |
| 7.3 | i386 / amd64 | 0.3.3 | 1 |
| 7.2 | i386 / amd64 | 0.3.3 | 1 |
| 7.1 | i386 / amd64 | 0.2.4 | 0 |
| 7.0 | i386 / amd64 | 0.2.4 | 0 |
| 6.3 | i386 | 0.1.0 | 0 |
| 6.1 | i386 | 0.1.0 | 0 |
| 5.3 | i386 | 0.1.0 | 0 |
| Linux | |||
|---|---|---|---|
| Version | Arch | RADclock version | Feed-Forward kernel version |
| 2.6.32 | x86 / x86_64 | 0.3.2 | 1 |
| 2.6.31.14 | x86 / x86_64 | 0.3.2 | 1 |
| 2.6.31 | x86 / x86_64 | 0.3.2 | 0 |
| 2.6.30 | x86 / x86_64 | 0.3.2 | 0 |
| 2.6.29 | x86 / x86_64 | 0.3.2 | 0 |
| 2.6.28 | x86 / x86_64 | 0.3.2 | 0 |
| 2.6.27 | x86 / x86_64 | 0.3.2 | 0 |
| 2.6.26 | x86 / x86_64 | 0.3.2 | 0 |
| 2.6.25 | i386 | 0.1.0 | 0 |
| 2.6.24 | i386 | 0.1.0 | 0 |
| 2.6.20 | i386 | 0.1.0 | 0 |
| 2.6.18 | i386 | 0.1.0 | 0 |
| Mac OSX | ||
|---|---|---|
| Version | Latest RADclock version | Comments |
| 10.5 | 0.2.1 | replay only |
I receive an error message when trying to install the radclock package
The RADclock daemon requires that you have the libpcap, librt and libnl libraries install on your system.
I compiled the RADclock software but do not get kernel mode running
During compilation, your system is tested to see if the kernel has been patched. This is useful for system that don't have kernel support yet but want to test the userland only version of the RADclock. Make sure the kernel you are running is the patched one using:
uname -a
Also, after running the configure script, make sure the RADclock extensions provided by the patched kernel have been detected. The output of the configure script should look like the following.
configure: ---------------------------------------- configure: RADClock version 0.3.3 configure: Found target arch: x86_64 configure: Compiling for linux configure: Detected kernel RADClock extensions: yes configure: Detected kernel access channel: yes configure: get_counter syscall number: 295 configure: get_counter_latency syscall number: 296 configure: ----------------------------------------
I followed the instructions but the RADclock time is all over the place
The RADclock relies on a fairly stable counter. It is likely you have selected the TSC has your hardware counter, while your system is either:
- a SMP/multi-core system with unsynchronised TSC counters
- a system with CPU frequency scaling
- a system with ACPI and APM management
The solution is to choose another hardware counter (HPET for example) and restart the RADclock daemon. See the configuration page for more detais.