Am 18.10.2010 16:54, Felix Jirka wrote: > Ok, thanks for your help! > > I'm sorry for sending this issue to the wrong list, I'm quite new to > this and my thought was that is the correct list as the issue was > happening with a vanilla kernel too. > > Just to summarize: > - on real HW with rtai-patch the issue is caused by rtai > - the vanilla kernel used with vmware has some other issues I missed the vanilla part: Can you reproduce under QEMU/KVM? Debugging the guest would be easier then, and it's easier to trace what that hypervisor does. Maybe there is a subtle race in the test code that is exposed by the timing that virtualization implies. > > so the conclusion is that I avoid the use of function tracing for now. > > Regards > > Felix > > PS: what list would have been the right one for this issue? RTAI patch variant -> RTAI mailing list. Official Adeos patch -> Adeos mailing list. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe linux-trace-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|