On 02/18/2014 04:39 PM, Yogi A. Patel wrote:
Hi -
I have patched Scientific Linux 6.5 (Linux kernel v 2.6.32.20) with
2.6.32 is very old.
1. I don't quite understand everything being printed out here, however I
know that not having overruns is great - but I also know that the worst
case latencies are not acceptable.
In the example you show, the worst case latency is 11µs, is this what
you do not find acceptable? If this is indeed what you find
unacceptable, I am afraid there is little we can do.
2. I read that the SMI-enabled chipsets can cause latency issues. I
added "xeno_hal.smi=1" to the kernel boot arguments, however I got an
error saying "SMI workaroudn failed" when I rebooted into the kernel. I
believe I have a BIOS that can't change the bit for the SMI. Not sure
what else to do here.
SMI cause problems when they cause latencies above, say 80us. A latency
of 10us is something normal.
3. I'm not sure if the following two lines are causing the error
(primarily because I don't know what they mean):
clock_gettime failed for clock id 42
XNVDSO_FEAT_HOST_REALTIME not available
No, they simply mean that you are using a too old kernel.
--
Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
