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,
--
Philipp Tölke, M.Sc. - Software-Developer - fos4X GmbH - www.fos4x.de
Thalkirchner Str. 210, Geb. 6 - D-81371 München; AG München HRB 189 218
T +49 89 999 542 58 - F +49 89 999 542 01
Managing Directors: Dr. Lars Hoffmann, Dr. Mathias Müller
--
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
