Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932306AbbKQT12 (ORCPT ); Tue, 17 Nov 2015 14:27:28 -0500 Received: from mail-ph.de-nserver.de ([85.158.179.214]:51643 "EHLO mail-ph.de-nserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932168AbbKQT10 (ORCPT ); Tue, 17 Nov 2015 14:27:26 -0500 X-Fcrdns: No Subject: Re: Asterisk deadlocks since Kernel 4.1 To: Thomas Gleixner References: <564B3D35.50004@profihost.ag> Cc: netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org From: Stefan Priebe Message-ID: <564B7F9D.5060701@profihost.ag> Date: Tue, 17 Nov 2015 20:27:25 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-User-Auth: Auth by s.priebe@profihost.ag through 185.39.223.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1798 Lines: 53 Am 17.11.2015 um 20:15 schrieb Thomas Gleixner: > On Tue, 17 Nov 2015, Stefan Priebe - Profihost AG wrote: >> 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, 20000000}, >> it_value={0, 140592906050976}}) = 0 >> [pid 6068] read(8, "\1\0\0\0\0\0\0\0", 8) = 8 >> [pid 6068] poll([{fd=9, events=POLLIN}, {fd=8, events=POLLIN|POLLPRI}], >> 2, 1000) = 1 ([{fd=8, revents=POLLIN}]) >> [pid 6068] timerfd_gettime(8, , {it_interval={0, 20000000}, >> it_value={0, 140592906050976}}) = 0 >> [pid 6068] read(8, "\1\0\0\0\0\0\0\0", 8) = 8 >> >> fd 8 is: >> >> lrwx------ 1 root root 64 Nov 17 15:27 /proc/6025/fd/8 -> >> anon_inode:[timerfd] >> >> >> # cat /proc/6025/stack >> [] poll_schedule_timeout+0x49/0x70 >> [] do_sys_poll+0x3d7/0x590 >> [] do_restart_poll+0x3c/0x70 >> [] sys_restart_syscall+0x1f/0x30 >> [] system_call_fastpath+0x12/0x71 >> [] 0xffffffffffffffff >> >> Any ideas how to debug this? > > fd 8 is probably not really interesting. That looks like a interval > timer firing periodically. So it probably waits for fd 9 ... I've now also two gdb backtraces from two crashes: http://pastebin.com/raw.php?i=yih5jNt8 http://pastebin.com/raw.php?i=kGEcvH4T Stefan > > Thanks, > > tglx > -- 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/