From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 17:29:47 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D432B106564A; Tue, 11 Sep 2012 17:29:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7CDF08FC1B; Tue, 11 Sep 2012 17:29:46 +0000 (UTC) Received: by obbun3 with SMTP id un3so1507479obb.13 for ; Tue, 11 Sep 2012 10:29:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ubCVJP+h1joc3Zby+rn+qM6UCyrQU0DMMXXBtIvXEys=; b=bEmLe/9Xat9OFR5UijTaM5w842s9XM/+xteshDqYxkT5kqulPcbB91+DdpNMuOoD1+ PsBoKMt14KTBcAOYo7fkoQ9sb1Nwc9wbN4ICuR5QtZYHccqbmbCr5+nRcwgr/va94Cnx 8AfebB2rfchlQ5F+/ROn0ARdc8jBqoJQK2WL1SYUCYX8kprAqni5bllXHwbMjFAmLm++ z+g5GVgHy9CLDd/H+5/wb9hrVeUT57V0CGrW7fjvNRUkJEvb+Un3Go9Cra0bw2GCYIvA bjC8NWHM5ab2Khon/jMWsf5c5jUgcZJBKOsBCkTMcn2VQuaUcZZMwY9MeQFoLUtf/l6B PCRw== MIME-Version: 1.0 Received: by 10.182.43.40 with SMTP id t8mr19315307obl.93.1347384586301; Tue, 11 Sep 2012 10:29:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.76.8.98 with HTTP; Tue, 11 Sep 2012 10:29:46 -0700 (PDT) In-Reply-To: <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> Date: Tue, 11 Sep 2012 10:29:46 -0700 X-Google-Sender-Auth: Yx4NDsHiaqEOuz768YR3E3cXozw Message-ID: From: Adrian Chadd To: Dominic Blais Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-net@freebsd.org" Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 17:29:47 -0000 On 11 September 2012 09:01, Dominic Blais wrote: > I could do something about the route monitor but not the fstat | grep route... I mean, I would have to run it in a loop endlessly until the bug happens... Even with it, it's not even sure I would catch it... The route monitor is a good idea. It should tell us whether it's from some tool/program/network event sending a routing table update, or whether it's just plain memory corruption. adrian