On Aug 9, 2012, at 3:25 AM, Claudio Scordino <claudio@xxxxxxxxxxxxxxx> wrote: > > > PI_STRESS: > > Finally, the pi_stress (priority-inheritance code paths for POSIX mutexes) sometimes fails with preempt_rt on the SCHED_FIFO policy (this behavior did not occurred without preempt_rt, even if it is still possible): > > $ pi_stress --duration 100 --groups=2 > Starting PI Stress Test > Number of thread groups: 2 > Duration of test run: 100 seconds > Number of inversions per group: unlimited > Test threads using scheduler policy: SCHED_FIFO > Admin thread priority: 4 > 2 groups of 3 threads will be created > High thread priority: 3 > Med thread priority: 2 > Low thread priority: 1 > Current Inversions: 2531 > ERROR: WATCHDOG triggered: group 0 is deadlocked! > ERROR: reporter stopping due to watchdog event > Stopping test > Terminated This possibly related to the test implementation. In the past there were similar issues in LTP, where a supervisor thread is polling for a signal our completion of another thread that never arrives because the supervisor thread is hogging the CPU (FIFO thread ) and either the other threads never run, or the signal is not being delivered. In RT it is correct behavior that a CPU-bound thread should preempt other threads and signals. IIRC there are several ways to correct this, by also raising the prio of softirqd, or by fixing the implementation of the test. If you could provide a link to the test source, this would be helpful. First and foremost however, do follow Carsten's recommendation about setting the prio appropriately high. Thanks Sven-- 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
