> Strangely, the kernel sends SIGXCPU (due to real-time CPU usage reaching the soft RLIMIT_RTTIME) in a write() call. The setrlimit(2) man page says that blocking calls reset the RTTIME count.
Ok, thanks for the investigation - perhaps that write call is not considered a blocking call, or not so on RT kernels, or it gets stuck in the for (;;) loop around the write call in pa_fdsem_post - might be worth checking the result from that write call to see what goes wrong?
> Strangely, the kernel sends SIGXCPU (due to real-time CPU usage reaching the soft RLIMIT_RTTIME) in a write() call. The setrlimit(2) man page says that blocking calls reset the RTTIME count.
Ok, thanks for the investigation - perhaps that write call is not considered a blocking call, or not so on RT kernels, or it gets stuck in the for (;;) loop around the write call in pa_fdsem_post - might be worth checking the result from that write call to see what goes wrong?
Happy bug hunting :-)