[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56530A42.6030609@profihost.ag>
Date: Mon, 23 Nov 2015 13:44:50 +0100
From: Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>
To: Florian Weimer <fweimer@...hat.com>,
Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, netdev@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Asterisk deadlocks since Kernel 4.1
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:
>>
>> <https://issues.asterisk.org/jira/browse/ASTERISK-25251>
>>
>> But in your original report, you said that 4.1.13 is broken.
>
> That's correct i'm running 4.1.13.
>
>> This backtrace:
>>
>> <https://issues.asterisk.org/jira/secure/attachment/52702/bt.txt>
>>
>> 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!
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists