From: "Philipp Tölke" <philipp.toelke@fos4x.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: kernel BUG at /build/linux-rt/kernel/locking/rtmutex.c:997!
Date: Thu, 19 Feb 2015 15:25:55 +0100 [thread overview]
Message-ID: <54E5F273.9020508@fos4x.de> (raw)
In-Reply-To: <20150217141333.GR26177@linutronix.de>
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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-19 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 11:09 kernel BUG at /build/linux-rt/kernel/locking/rtmutex.c:997! Juerg Haefliger
2014-12-18 13:35 ` Rolf Wojtech
2015-02-17 14:13 ` Sebastian Andrzej Siewior
2015-02-18 7:54 ` Philipp Tölke
2015-02-18 8:32 ` Sebastian Andrzej Siewior
2015-02-19 14:25 ` Philipp Tölke [this message]
2015-02-20 19:25 ` Thavatchai Makphaibulchoke
-- strict thread matches above, loose matches on Subject: below --
2014-12-03 22:39 Thavatchai Makphaibulchoke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E5F273.9020508@fos4x.de \
--to=philipp.toelke@fos4x.de \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).