linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Juerg Haefliger <juergh@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: kernel BUG at /build/linux-rt/kernel/locking/rtmutex.c:997!
Date: Tue, 17 Feb 2015 15:13:33 +0100	[thread overview]
Message-ID: <20150217141333.GR26177@linutronix.de> (raw)
In-Reply-To: <CADLDEKuPf3UNf-CB_xpmjcmQxQA_drFkXzBMQYUF_7K0dM7V3w@mail.gmail.com>

* Juerg Haefliger | 2014-12-02 12:09:47 [+0100]:

>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?

Sebastian

  parent reply	other threads:[~2015-02-17 14:13 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 [this message]
2015-02-18  7:54   ` Philipp Tölke
2015-02-18  8:32     ` Sebastian Andrzej Siewior
2015-02-19 14:25   ` Philipp Tölke
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=20150217141333.GR26177@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=juergh@gmail.com \
    --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).