Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753605AbbKWM5g (ORCPT ); Mon, 23 Nov 2015 07:57:36 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:57159 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752263AbbKWM5e (ORCPT ); Mon, 23 Nov 2015 07:57:34 -0500 Message-Id: <1448283451.4019628.447573353.3659E447@webmail.messagingengine.com> X-Sasl-Enc: MdDhQ7UxXTZdULnjYcmgA0KEffMean4aUMFxA3XGK4Xm 1448283451 From: Hannes Frederic Sowa To: "Stefan Priebe - Profihost AG" , Florian Weimer Cc: Thomas Gleixner , netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-0a80c2aa In-Reply-To: <56530A42.6030609@profihost.ag> 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> Subject: Re: Asterisk deadlocks since Kernel 4.1 Date: Mon, 23 Nov 2015 13:57:31 +0100 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1388 Lines: 38 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? Thanks, Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/