Ok, I'll try the route monitor. Please note that Krzysztof Barcikowski already did it and got nothing:
http://lists.freebsd.org/pipermail/freebsd-net/2012-March/031879.html -- -----Message d'origine----- De : adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] De la part de Adrian Chadd Envoyé : 11 septembre 2012 13:30 À : Dominic Blais Cc : Gleb Smirnoff; freebsd-net@freebsd.org Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 On 11 September 2012 09:01, Dominic Blais <dbl...@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 _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
