Jan Kiszka wrote:
> Karl Reichert wrote:
> >> I can't look into this soon, but it has high priority for time I will 
> >> have test equipment in reach again!
> >>
> > Thanks Jan! Keep informed the list then, please ;)
> > Would really like to know why this happens, although it's not so
> critical to my project.
> 
> /me would really like to understand this as well. Assuming your driver
> is rt_e1000 and that already the first sync frame shows abnormal
> latencies, could you try this patch with the I-pipe tracer enabled [1]?
> Use "echo 16000 > /proc/ipipe/trace/backtrace_points", "echo 1 >
> /proc/ipipe/trace/verbose", and grab the result from
> /proc/ipipe/trace/frozen.
> 
> Thanks in advance,
> Jan
> 
> 
> [1] http://www.xenomai.org/index.php/I-pipe:Tracer
It's written there:
'To enable tracing support, go the the "Kernel hacking" section of the kernel 
configuration and switch on "I-pipe debugging" and then "I-pipe tracing".'

I do not find this point in my 2.6.20 kernel. There is 'Latency tracing', is 
this what they mean?
If so, I have to recompile my kernel and it can take some time till you get my 
results, cause I'm busy at the moment. But I will give you the results, for 
sure.

Karl
-- 
von Karl Reichert

Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to