Date: Tue, 11 Sep 2012 10:29:46 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Dominic Blais <dblais@interplex.ca> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Message-ID: <CAJ-VmomU7kQOHY1j0VE5%2B3jsmD%2Bh5r_ZPDCdqydAaYSCVZrv1A@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 September 2012 09:01, Dominic Blais <dblais@interplex.ca> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomU7kQOHY1j0VE5%2B3jsmD%2Bh5r_ZPDCdqydAaYSCVZrv1A>