From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: Asterisk deadlocks since Kernel 4.1 To: Hannes Frederic Sowa , Florian Weimer References: <564B3D35.50004@profihost.ag> <564B7F9D.5060701@profihost.ag> <564CDE2F.8000201@profihost.ag> <564CEB0C.40006@redhat.com> <564CEF5D.3080005@profihost.ag> <564D9A17.6080305@redhat.com> <564D9B21.302@profihost.ag> <564D9CE6.2090104@profihost.ag> <1447933294.1974772.444210441.67F1AC5E@webmail.messagingengine.com> <564DB5F5.9060208@profihost.ag> <1447936902.1986892.444251921.3928A049@webmail.messagingengine.com> <564DC4A5.70104@profihost.ag> <564DCC4C.1090009@redhat.com> <564E2852.8000200@profihost.ag> <56530A42.6030609@profihost.ag> <1448283451.4019628.447573353.3659E447@webmail.messagingengine.com> Cc: Thomas Gleixner , netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org From: Stefan Priebe - Profihost AG Message-ID: <5654679A.3010109@profihost.ag> Date: Tue, 24 Nov 2015 14:35:22 +0100 MIME-Version: 1.0 In-Reply-To: <1448283451.4019628.447573353.3659E447@webmail.messagingengine.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: Am 23.11.2015 um 13:57 schrieb Hannes Frederic Sowa: > On Mon, Nov 23, 2015, at 13:44, Stefan Priebe - Profihost AG wrote: >> Am 19.11.2015 um 20:51 schrieb Stefan Priebe: >>> >>> Am 19.11.2015 um 14:19 schrieb Florian Weimer: >>>> On 11/19/2015 01:46 PM, Stefan Priebe - Profihost AG wrote: >>>> >>>>> I can try Kernel 4.4-rc1 next week. Or something else? >>>> >>>> I found this bug report which indicates that 4.1.10 works: >>>> >>>> >>>> >>>> But in your original report, you said that 4.1.13 is broken. >>> >>> That's correct i'm running 4.1.13. >>> >>>> This backtrace: >>>> >>>> >>>> >>>> shows a lot of waiting on quite different netlink sockets. So if this >>>> is due to a race in Asterisk, it must have happened several times in a >>>> row. >> >> Kernel 4.4-rc2 works fine. How can we grab / get an idea which is >> causing the isse in 4.1? It's an LTE kernel so it should be fixed! > > Thanks for testing. I was not able to reproduce it at all, with as much > parallelism and threads as possible on any kernel. Could you try to do a > git bisect? OK i'll start digging around with major versions first to have a working and a non working version. I'll try 4.3 and 4.2 first to get an idea where it got fixed. Sadly i can't bisect from 4.1.13 to 4.X so i have to verify first it also happens with 4.1. OK? Stefan > > Thanks, > Hannes >