[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170902092707.1e8800bb@mail.com>
Date: Sat, 2 Sep 2017 09:27:07 +0200
From: Mart van de Wege <mvdwege@...l.com> (by way of Mart van de Wege
<mvdwege@...il.com>)
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...el.com>,
Gustavo Padovan <gustavo@...ovan.org>,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rt-users@...r.kernel.org, tglx@...utronix.de,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: Possible BT deadlock due to recursive read locking (Was: Re:
kernel BUG at kernel/locking/rtmutex.c:1059)
On Fri, 1 Sep 2017 10:51:07 +0200
Mart van de Wege <mvdwege@...il.com> wrote:
> On Thu, 31 Aug 2017 16:52:12 +0200
> Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
>
> > On 2017-08-30 23:25:53 [+0200], Mart van de Wege wrote:
> > > Hi,
> > Hi,
> >
> > > The issue persists up to v4.11.12-rt10
> > Does
> > CONFIG_RWLOCK_RT_READER_BIASED=y
> > make it go away?
> >
> Yes, that does make it go away. -rt8 now boots cleanly, and works
> fine. Building -rt10 now to be sure.
>
Confirm that as of 4.11.12-rt11 the deadlock still goes away when
enabling CONFIG_RWLOCK_RT_READER_BIASED
Mart
Powered by blists - more mailing lists