Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1725509
| From | Mart van de Wege <mvdwege@mail.com> (by way of Mart van de Wege <mvdwege@gmail.com>) |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Possible BT deadlock due to recursive read locking (Was: Re: kernel BUG at kernel/locking/rtmutex.c:1059) |
| Date | 2017-09-02 16:00 +0200 |
| Message-ID | <ulh7Q-3Ed-9@gated-at.bofh.it> (permalink) |
| References | <ukz6O-6TE-23@gated-at.bofh.it> <ukz6O-6TE-25@gated-at.bofh.it> <ukPXY-1xv-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 1 Sep 2017 10:51:07 +0200 Mart van de Wege <mvdwege@gmail.com> wrote: > On Thu, 31 Aug 2017 16:52:12 +0200 > Sebastian Andrzej Siewior <bigeasy@linutronix.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
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Possible BT deadlock due to recursive read locking (Was: Re: kernel BUG at kernel/locking/rtmutex.c:1059) Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2017-08-31 17:00 +0200
Re: Possible BT deadlock due to recursive read locking (Was: Re: kernel BUG at kernel/locking/rtmutex.c:1059) Mart van de Wege <mvdwege@gmail.com> - 2017-09-01 11:00 +0200
Re: Possible BT deadlock due to recursive read locking (Was: Re: kernel BUG at kernel/locking/rtmutex.c:1059) Mart van de Wege <mvdwege@mail.com> (by way of Mart van de Wege <mvdwege@gmail.com>) - 2017-09-02 16:00 +0200
csiph-web