From owner-freebsd-net@FreeBSD.ORG  Tue Sep 11 19:58:39 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 18CD8106564A;
	Tue, 11 Sep 2012 19:58:39 +0000 (UTC)
	(envelope-from glebius@FreeBSD.org)
Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117])
	by mx1.freebsd.org (Postfix) with ESMTP id 7BC6B8FC14;
	Tue, 11 Sep 2012 19:58:38 +0000 (UTC)
Received: from cell.glebius.int.ru (localhost [127.0.0.1])
	by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q8BJwbTf080035;
	Tue, 11 Sep 2012 23:58:37 +0400 (MSK)
	(envelope-from glebius@FreeBSD.org)
Received: (from glebius@localhost)
	by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q8BJwavb080034;
	Tue, 11 Sep 2012 23:58:36 +0400 (MSK)
	(envelope-from glebius@FreeBSD.org)
X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to
	glebius@FreeBSD.org using -f
Date: Tue, 11 Sep 2012 23:58:36 +0400
From: Gleb Smirnoff <glebius@FreeBSD.org>
To: Vijay Singh <vijju.singh@gmail.com>
Message-ID: <20120911195836.GQ44854@FreeBSD.org>
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>
	<CAJ-VmomU7kQOHY1j0VE5+3jsmD+h5r_ZPDCdqydAaYSCVZrv1A@mail.gmail.com>
	<CALCNsJSo1PEPrB9tQ7H+A9NLOaKtCQkEh70Yhs4wtNhcOcpBRQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <CALCNsJSo1PEPrB9tQ7H+A9NLOaKtCQkEh70Yhs4wtNhcOcpBRQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "freebsd-net@freebsd.org" <freebsd-net@FreeBSD.org>,
	Adrian Chadd <adrian@FreeBSD.org>, Dominic Blais <dblais@interplex.ca>
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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 19:58:39 -0000

On Tue, Sep 11, 2012 at 10:35:25AM -0700, Vijay Singh wrote:
V> On Tue, Sep 11, 2012 at 10:29 AM, Adrian Chadd <adrian@freebsd.org> wrote:
V> > On 11 September 2012 09:01, Dominic Blais <dblais@interplex.ca> wrote:
V> >> 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...
V> >
V> > The route monitor is a good idea. It should tell us whether it's from
V> > some tool/program/network event sending a routing table update, or
V> > whether it's just plain memory corruption.
V> 
V> Could this be http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331

Why do you suspect this one?

-- 
Totus tuus, Glebius.