On 02/19/2015 07:25 AM, Philipp Tölke wrote: > On 17.02.2015 15:13, Sebastian Andrzej Siewior wrote: >>> I have a simple test that runs two iperf clients in parallel with the >>> ltp network tests and it triggers a deadlock within a few minutes. >>> This is 100% repeatable. I've tried this on different RT kernels and >>> determined that prior to the following commit (which went into 3.10 >>> upstream), the machine doesn't deadlock and seems to run just fine: >>> >>> fb52f40e085ef4074f1335672cd62c1f832af13b rtmutex: Handle deadlock >>> detection smarter >> >> has this been resolved in the meantime? Do you see the same problem with >> v3.18-RT? > > I was not able to reproduce the issue with 3.18.7-rt1 in 24hours. I will > repeat the test to be sure. > > Cheers, I was not able to reproduce the issue either with 3.18.7-rt1. I believe this is mainly attributed to the fact that run-local_timers() in 3.18.7-rt1 no longer calls spin_trylock(&base->lock), removing the condition that could lead to the problem. Thanks, Mak. -- 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
