Date: Tue, 11 Sep 2012 13:35:52 -0400 From: Dominic Blais <dblais@interplex.ca> To: Adrian Chadd <adrian@freebsd.org> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDDBA@WIN2008.Domnt.abi.ca> In-Reply-To: <CAJ-VmomU7kQOHY1j0VE5%2B3jsmD%2Bh5r_ZPDCdqydAaYSCVZrv1A@mail.gmail.com> 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%2B3jsmD%2Bh5r_ZPDCdqydAaYSCVZrv1A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, I'll try the route monitor. Please note that Krzysztof Barcikowski alre= ady did it and got nothing: http://lists.freebsd.org/pipermail/freebsd-net/2012-March/031879.html -- -----Message d'origine----- De=A0: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] De la part de= Adrian Chadd Envoy=E9=A0: 11 septembre 2012 13:30 =C0=A0: Dominic Blais Cc=A0: Gleb Smirnoff; freebsd-net@freebsd.org Objet=A0: Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 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 rou= te... I mean, I would have to run it in a loop endlessly until the bug happ= ens... 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?2DE61B0869B7484997BCA012845482C7EBE62DDDBA>