From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bytemark.thekelleys.org.uk (bytemark.thekelleys.org.uk [213.138.109.107]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 95D4521F1DE for ; Fri, 9 Jan 2015 07:36:29 -0800 (PST) Received: from [31.108.134.64] (helo=[192.168.87.210]) by bytemark.thekelleys.org.uk with esmtpa (Exim 4.80) (envelope-from ) id 1Y9bbr-000182-VQ; Fri, 09 Jan 2015 15:36:24 +0000 Message-ID: <54AFF574.10608@thekelleys.org.uk> Date: Fri, 09 Jan 2015 15:36:20 +0000 From: Simon Kelley User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Dave Taht 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> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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 15:36:59 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 A backtrace is the most important starting point. A query log _if_ it's query dependent, but that seems unlikely since it doesn't break when forwarding to IPv4. An easy way to reproduce would be great :-) I can do the same tests here, but it's a bit risky, since my IPv6 is via a sixXS tunnel. If the tunnel goes down, it needs to do DNS queries to bring it back up. Cheers, Simon. On 09/01/15 08:52, Dave Taht wrote: > 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?) > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJUr/VzAAoJEBXN2mrhkTWizvcP/3eCyJEY6kwGSWvh+4QiDulK CMsz1DJYbhYqu1w+oME287Hazd3LcneSZkn/CH05Qo9gLHNIjnQK48OvxaUPLtw5 rereV59vcgSgIVRyeuTJmVeF6Z4uL4kiNsWsNYWT32RNWfZpLQMrww9svrMuNQlN 2LZknand/1XJXVxDdAFOIyx6DIR5NFtRQPtntSr8GFwWMuvyM3PLEfF7Qu4RbrIt pFAirlM+uiuUrGmCf1T5h8h9C7z++T7WXdFyCU6fmH7k6ZnXqYdl5OY0YkHeRhNF UHbcd/Eqr5Onm6F0TZpQKKkKotfyyGoj3HkxBpCn1NrPafexRjUK4Rf4aQkys1ie eLdiSvQafkLDssdPCuNV9+AGKUkZ6zolsf88gG6vxdksrQbVwFw9h25mdbizEw2M KfvFbsJLYZ67U/FJGyW0trBc+t5j8Qv1KZCq4vhdiJfIn2dwOjtTn8IEHSZrbOIt f7zvOKr25rR+fuFsw1PnSOXZwJDlBgKdRB7/1NYg2xrLnzL/luBgpfoOVoJNH1Cf rzpsxZ3ZwzGfFZljokFbbXNWSTDiEgIDEzjLf9ie6+PJtUclhKbcqy35iGRaVRxL tuWVgv24bQv5+FiSmPRCtytIJXhehCCqBeC9wXFOWvzFxILQ3n8THvvOwiRx6n4p lWriAqwv+al2mC9CkthE =9IWM -----END PGP SIGNATURE-----