kernel: arpresolve: can't allocate llinfo for 65.59.233.102
Gleb Smirnoff
glebius at FreeBSD.org
Tue Sep 11 19:58:39 UTC 2012
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 at freebsd.org> wrote:
V> > On 11 September 2012 09:01, Dominic Blais <dblais at 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.
More information about the freebsd-net
mailing list