On 2017-01-27 14:04:35 [+0000], Koehrer Mathias (ETAS/ESW5) wrote: > Hi Sebastian, Hi Mathias, > In all the successful loops the lines in the trace look like the lines in the successful (2nd) example below. > In the error case there is an additional sched_waking and sched_wakeup in the trace. > Also there is always "prev_state=S" within the forked process. > In the error case, there is "prev_state=T|K". That T|K is probably some kind of debug state the program remains until the debugger puts it back on track. I think the interesting part ist figure out what decided to send this signal or put the program into stop-state. Usually a breakpoint, invalid opcode, … causes this kind of action but my understanding is that you use none of those. > Thanks > > Best regards > > Mathias Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
