Jan Kiszka wrote:
> I don't see anything suspicious right now, so please consider capturing
> a trace with the latency as I suggested. That should give a full picture
> of what is happening when latency detects that huge delay.
>
> Jan
To get the tracing to work I had to set CONFIG_IPIPE_TRACE_VMALLOC, as 
my system did not boot when this was not set. I also set 
CONFIG_IPIPE_TRACE_SHIFT to 16. I attached the logfile of a latency session.

This is the log of the cyclictest-session:
bash-3.00# ./cyclictest-Xenomai -q -h
#T: 0 P:80 I:10000 O:   0 C: 100 Min: -5.151 Avg: -0.013 Max:    
6.645        
#T: 1 P:79 I:10000 O:   0 C: 100 Min: -4.334 Avg: 11.177 Max: 
1118.283        
#T: 2 P:78 I:10000 O:   0 C: 100 Min: -6.304 Avg:  3.983 Max:  
399.461        
#T: 3 P:77 I:10000 O:   0 C: 100 Min: -5.296 Avg:  0.005 Max:    
7.245        
#T: 4 P:76 I:10000 O:   0 C: 100 Min: -3.541 Avg:  0.050 Max:    
7.077        
#T: 5 P:75 I:10000 O:   0 C: 100 Min: -5.848 Avg: -0.001 Max:    
6.549        
#T: 6 P:74 I:10000 O:   0 C: 100 Min: -4.431 Avg: -0.004 Max:    
6.620        
#T: 7 P:73 I:10000 O:   0 C: 100 Min: -5.319 Avg: -0.009 Max:    
7.414        
#T: 8 P:72 I:10000 O:   0 C: 100 Min: -4.647 Avg: -0.011 Max:    
7.341        
#T: 9 P:71 I:10000 O:   0 C: 100 Min: -4.598 Avg: -0.009 Max:    
7.101        

Kind regards,
    Johan Borkhuis