On Wed, Nov 18, 2015, at 21:23, Stefan Priebe wrote: > > Am 17.11.2015 um 20:43 schrieb Thomas Gleixner: > > On Tue, 17 Nov 2015, Stefan Priebe wrote: > >> I've now also two gdb backtraces from two crashes: > >> http://pastebin.com/raw.php?i=yih5jNt8 > >> > >> http://pastebin.com/raw.php?i=kGEcvH4T > > > > They don't tell me anything as I have no idea of the inner workings of > > asterisk. You might be better of to talk to the asterisk folks to help > > you track down what that thing is waiting for, so we can actually look > > at a well defined area. > > The asterisk guys told me it's a livelock asterisk is waiting for > getaddrinfo / recvmsg. > > Thread 2 (Thread 0x7fbe989c6700 (LWP 12890)): > #0 0x00007fbeb9eb487d in recvmsg () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007fbeb9ed4fcc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > #2 0x00007fbeb9ed544a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > #3 0x00007fbeb9e92007 in getaddrinfo () from > /lib/x86_64-linux-gnu/libc.so.6 Florian Weimer recently patched glibc to detect filedescriptors which have been reused incorrectly in the glibc name resolving routines: <https://sourceware.org/ml/libc-alpha/2015-10/msg00865.html> Could you determine the type of filedescriptor in /proc/pid/fd and /proc/net/netlink by matching inodes? Thanks, Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
