From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Weimer Subject: Re: Asterisk deadlocks since Kernel 4.1 Date: Thu, 19 Nov 2015 14:19:08 +0100 Message-ID: <564DCC4C.1090009@redhat.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: Thomas Gleixner , netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Stefan Priebe - Profihost AG , Hannes Frederic Sowa Return-path: In-Reply-To: <564DC4A5.70104@profihost.ag> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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. 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. Thanks, Florian