From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 8BCA021F5E7 for ; Fri, 9 Jan 2015 00:52:15 -0800 (PST) Received: by mail-oi0-f45.google.com with SMTP id x69so11071416oia.4 for ; Fri, 09 Jan 2015 00:52:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=95svytX0b61LLtXxfp6CR9sMUEqF3Zj3euy7J/zN34U=; b=wkMzVoAARme+9A6wVbhG8VWlDqWnfRfzf73S68sA9MpMoqR6bZsvLSqIkGrMmg8+yv pWJPPzd0aF0coHG+Uw6ws7HNXICnZDf+F+Ex8fo+7kbsUn0IzAQvR/YvtFczgTHFCtm3 qPrse/RaFc+ClD5KVbWmxdg2kG4hUDw6XJSqDWmm5K9XbwkCpKyJi2lb2yvcMADL875H 4aOLWzfpGRTl52KzvFT87SGm0KmQk/6+hDQ+jW1WxOoCxjs6oOaQu9lJMY9g5ndpceIq jWqLVrDMFV9QkYNIBkD6nB5xycBftQyiQ3w78SOqR1mFhzetK/R+Z0QAtECe1phbr3Jc hDfw== MIME-Version: 1.0 X-Received: by 10.60.52.72 with SMTP id r8mr8527633oeo.75.1420793534050; Fri, 09 Jan 2015 00:52:14 -0800 (PST) Received: by 10.202.51.66 with HTTP; Fri, 9 Jan 2015 00:52:13 -0800 (PST) In-Reply-To: References: <535EACCB.7090104@thekelleys.org.uk> <20140428232459.GA55372@redoubt.spodhuis.org> <535FA793.8020502@thekelleys.org.uk> <542E6C43.9030002@mit.edu> <54AEB183.7050000@thekelleys.org.uk> <54AEC775.7070101@thekelleys.org.uk> Date: Fri, 9 Jan 2015 00:52:13 -0800 Message-ID: From: Dave Taht To: Simon Kelley Content-Type: text/plain; charset=UTF-8 Cc: dnsmasq-discuss , "cerowrt-devel@lists.bufferbloat.net" , Anders Kaseorg Subject: Re: [Cerowrt-devel] Problems with DNSsec on Comcast, with Cero 3.10.38-1/DNSmasq 4-26-2014 X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2015 08:52:43 -0000 I was able to lock up this version of dnsmasq twice: 100% cpu usage. No syscalls were visible from strace during the lockup. Lockups occurred once on nearly at boot, and the second time, after a few hours of casual usage, with only ipv6 upstreams, on cero-3.10.50-1. furthermore, the only thing that kills it is a kill -9. I will build a non-stripped version in the morning... (and I do note that I was testing two things - one ipv6 upstreams only, and two, dnssec. Prior to this version I was using both ipv4 and ipv6 upstreams, no issues, had dnssec on also, usually no issues) Other suggestions for debugging the causes of a lockup requested (log all queries?)