Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > > There where exactly? I can take a look at it. > There's kernel tracing for the scheduler. If you enable it, you also > get > the "scheduler" debugger command. It takes a thread ID and analyzes > the > scheduler tracing information for this thread, printing its min/max > scheduling latencies. For the maximum it also prints the number of > the > tracing entry where that latency was encountered, so you can analyze > what > happened there exactly. > > Feel free to extend the command and the tracing as needed. Also, it will probably be helpful to enable semaphore tracing as well for this. Then just run OSS (or any other audio driver) with a lower latency, and see where it fails :-) Bye, Axel.