kernel: arpresolve: can't allocate llinfo for 65.59.233.102

[Adrian Chadd]

On 11 September 2012 09:01, Dominic Blais <dblais at 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