From owner-freebsd-net@FreeBSD.ORG Tue Sep 11 17:35:27 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 305AB106566C; Tue, 11 Sep 2012 17:35:27 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 888008FC18; Tue, 11 Sep 2012 17:35:26 +0000 (UTC) Received: by eeke52 with SMTP id e52so706136eek.13 for ; Tue, 11 Sep 2012 10:35:25 -0700 (PDT) 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=UUWM2lZP8B90sbE7zXxerUGJlHl00iA9xFS8gTw2ELA=; b=ohjYH7vGHfRmKUZ4Y47jJrSbvbH+kBZZz1aKGucoOkpm93PALTg2kql9wHgBqy6Zh4 KwvJ/H/8YI2ihjG5jCth3gbt9TJH2xLQvoNc+oq3EHUwPW1OSyTYwprr0XQdDPdvz8Ew OQHPLYCfjiPHA+bPBK//9AKc5DkUaI2Ot6P8ipNzEUEqiNkcIkEwZGlrQ5+6smtwXUnw H7qbokWfLT9IMwXl9A/0BEH2tDpivsFyS1d95NvN+8lsuoVzr9oGd5roU4TePEq9Oala mz+pGdOOxhhgNwDZMYKdkriOhl/Lp1MOKXrq2cQC9MsxOvk2C7mSajcw1E1Xkib97owr yiPg== MIME-Version: 1.0 Received: by 10.14.224.4 with SMTP id w4mr27072461eep.21.1347384925699; Tue, 11 Sep 2012 10:35:25 -0700 (PDT) Received: by 10.14.219.134 with HTTP; Tue, 11 Sep 2012 10:35:25 -0700 (PDT) In-Reply-To: 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:35:25 -0700 Message-ID: From: Vijay Singh To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-net@freebsd.org" , Dominic Blais 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:35:27 -0000 On Tue, Sep 11, 2012 at 10:29 AM, Adrian Chadd wrote: > 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. Could this be http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331