Thread (8 messages) 8 messages, 5 authors, 2015-02-20

Re: kernel BUG at /build/linux-rt/kernel/locking/rtmutex.c:997!

From: Philipp Tölke <hidden>
Date: 2015-02-18 07:54:39

Hi,

On 17.02.2015 15:13, Sebastian Andrzej Siewior wrote:
quoted
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?
As said in 
<http://thread.gmane.org/gmane.linux.rt.user/12563/focus=12809> I can 
reproduce the issue pretty easy. Using the patch from that thread it 
seems to be fixed.

 > Do you see the same problem with v3.18-RT?

I do feel kind of stupid to ask this: Where would I find 3.18-RT? The 
git only goes to 3.14...

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help