> Hmm, this doesn't convince me yet. Such skews during startup may as well > be triggered by unusual load during runtime (non-RT activity or new RT > components). Did you put your system under adequate non-RT load as well > while measuring the outputs? could you please just remind me how to do this again? OR can i just run the latency test, it has dummy loading in it does it not?
>> Sorry for the pragmatic qualifications here but in the end its the >> stability of the outputs that will determine the behaviour of the >> machine so its not a bad way to assess the software. :) > > A problem isn't solved until it is also understood. You are so right. :( > >>> If the problem persists (or your _really_ want to understand what >>> happens), you could try to put an xntrace_user_freeze(0, 1) before the >>> line which emits that EML warning, turn on the I-pipe tracer, set a >>> large back_trace_points value (a few thousand), enable verbose mode, and >>> grab what /proc/ipipe/trace/frozen reports after the hick-up. See [1] >>> for more howtos. >> Done this before so it should not be a problem. Don't think it is > > In that case, I would even more suggest to collect the data, maybe now > about the fragile startup case. Have got it on my todo list. :) Roland. > >> necessary quite yet as the behaviour at the moment looks good. > > Jan > ------------------------------------------------------------------------- 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
