Messages in this thread | | | Subject | Re: Asterisk deadlocks since Kernel 4.1 | From | Stefan Priebe - Profihost AG <> | Date | Tue, 24 Nov 2015 14:35:22 +0100 |
| |
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: >>>> >>>> <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! > > 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 >
| |