From: Roosen Henri <Henri.Roosen@ginzinger.com>
To: "bigeasy@linutronix.de" <bigeasy@linutronix.de>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: inconsistent lock state on v4.14.20-rt17
Date: Wed, 21 Mar 2018 08:31:31 +0000 [thread overview]
Message-ID: <1521621090.2390.1.camel@ginzinger.com> (raw)
In-Reply-To: <20180317210358.3h66haslmgqcwojs@linutronix.de>
Henri Roosen | Entwicklung Software
GINZINGER ELECTRONIC SYSTEMS GMBH
Tel.: +43 7723 5422 161
Mail: henri.roosen@ginzinger.com
Web: www.ginzinger.com
On Sat, 2018-03-17 at 22:03 +0100, bigeasy@linutronix.de wrote:
> On 2018-03-16 11:30:09 [+0100], To Roosen Henri wrote:
> > On 2018-03-14 20:55:24 [+0100], To Roosen Henri wrote:
> > > This survived 6 days. It was challenging to cancel hackbench
> > > because it
> > > was running via ssh in a screen session and I was loosing my
> > > network
> > > connection due to inactivity…
> >
> > okay. It may have survived but it managed to trigger this. Trying
> > to
> > make sense to this…
>
> So after I traced it down I figured out that you need
> 6b0ef92fee2a ("rtmutex: Make rt_mutex_futex_unlock() safe for irq-
> off callsites")
> https://git.kernel.org/tip/6b0ef92fee2a
>
Sorry for not being able to reply earlier, I was on a short holiday.
Thanks for figuring out the fix! I noticed you released v4.14.28-rt23
which includes the patch. I will give that version a test on our
systems.
As the inconsistent lock state issue was introduced only in v4.14, this
will not be the issue we've seen on v4.9. However, that might have been
fixed along the way to v4.14... I will keep you posted on the outcome.
> > > > Thanks,
> > > > Henri
>
> Sebastian
Thanks,
Henri
________________________________________
Ginzinger electronic systems GmbH
Gewerbegebiet Pirath 16
4952 Weng im Innkreis
www.ginzinger.com
Firmenbuchnummer: FN 364958d
Firmenbuchgericht: Ried im Innkreis
UID-Nr.: ATU66521089
prev parent reply other threads:[~2018-03-21 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 15:27 inconsistent lock state on v4.14.20-rt17 Roosen Henri
2018-03-06 18:21 ` Sebastian Andrzej Siewior
[not found] ` <1520411200.1744.11.camel@ginzinger.com>
2018-03-08 15:57 ` bigeasy
2018-03-08 17:38 ` Roosen Henri
2018-03-08 18:00 ` bigeasy
2018-03-09 9:47 ` Roosen Henri
2018-03-14 19:55 ` bigeasy
2018-03-16 10:30 ` bigeasy
2018-03-17 21:03 ` bigeasy
2018-03-21 8:31 ` Roosen Henri [this message]
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=1521621090.2390.1.camel@ginzinger.com \
--to=henri.roosen@ginzinger.com \
--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).