Re: Asterisk deadlocks since Kernel 4.1

Hi Herbert, Am 07.12.2015 um 02:20 schrieb Herbert Xu: > On Sun, Dec 06, 2015 at 09:56:34PM +0100, Stefan Priebe wrote: >> Hi Herbert, >> >> i think i found the issue in 4.1 with netlink. Somebody made a >> mistake while backporting or cherry-picking your patch "netlink: Fix >> autobind race

Re: Asterisk deadlocks since Kernel 4.1

> Am 02.12.2015 um 12:40 schrieb Hannes Frederic Sowa > <han...@stressinduktion.org>: > > Hello Stefan, > > Stefan Priebe - Profihost AG <s.pri...@profihost.ag> writes: > > >> here are the results. >> >> It works with 4.1. >> It

Re: Asterisk deadlocks since Kernel 4.1

015 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 - Prof

Re: Asterisk deadlocks since Kernel 4.1

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

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 r

Re: Asterisk deadlocks since Kernel 4.1

Am 19.11.2015 um 10:44 schrieb Florian Weimer: > On 11/18/2015 10:36 PM, Stefan Priebe wrote: > >>> please try to get a backtrace with debugging information. It is likely >>> that this is the make_request/__check_pf functionality in glibc, but it >>> would be nice to get some certainty. >> >>

Re: Asterisk deadlocks since Kernel 4.1

Am 18.11.2015 um 22:22 schrieb Hannes Frederic Sowa: > On Wed, Nov 18, 2015, at 22:20, Stefan Priebe wrote: >> you mean just: >> la /proc/$pid/fd > > ls -l /proc/pid/fd/ > > the numbers in brackets in return from readlink are the inode numbers. > >> and >> >> cat /proc/net/netlink > >

Re: Asterisk deadlocks since Kernel 4.1

fff8800b16cf000 15 4410001 000 20 1542 8800b1168800 15 4294962900 000 20 7978 8800b7088800 15 0 0000 0 0 0 2 0 5 8800b71c9800 16 0 000 20 15 f

Re: Asterisk deadlocks since Kernel 4.1

Am 19.11.2015 um 13:41 schrieb Hannes Frederic Sowa: > On Thu, Nov 19, 2015, at 12:43, Stefan Priebe - Profihost AG wrote: >> >> Am 19.11.2015 um 12:41 schrieb Hannes Frederic Sowa: >>> On Thu, Nov 19, 2015, at 10:56, Stefan Priebe - Profihost AG wrote: >>>>

Re: Asterisk deadlocks since Kernel 4.1

Am 19.11.2015 um 12:41 schrieb Hannes Frederic Sowa: > On Thu, Nov 19, 2015, at 10:56, Stefan Priebe - Profihost AG wrote: >> OK it had a livelock again. It just took more time. >> >> So here is the data: > > Thanks, I couldn't reproduce it so far with simple threa

Asterisk deadlocks since Kernel 4.1

Hello, since Upgrading our Asterisk System from Kernel 3.18.17 to 4.1.13 it deadlocks every few hours (kill -9 is the only thing working). Booting with 3.18 again let it run smooth again. An strace shows asterisk is looping like this: [pid 6068] timerfd_gettime(8, , {it_interval={0, 2000},

slow TCP speed through linux ip forwarding

Hello, i hope somebody has an idea for my problem and may point me to the right direction. Alle servers run kernel 3.18.14. My problem is that i can't archieve more than 20Mbit/s using a single TCP stream and i've no further ideas how to solve it. reduced Network Map Server A | Linux GW