[1521] in linux-net channel archive
Re: Strange ARP messages on 1.3.46
daemon@ATHENA.MIT.EDU (A.N.Kuznetsov)
Fri Dec 15 07:23:25 1995
To: linux-net@vger.rutgers.edu
Date: Thu, 14 Dec 1995 16:02:57 +0300 (MSK)
Cc: clameter@fuller.edu
Reply-To: kuznet@ms2.inr.ac.ru
From: inr-linux-net@ms2.inr.ac.ru (A.N.Kuznetsov)
> From: clameter@fuller.EDU (Christoph Lameter)
>
> Here is a part of my kernel log:
>
> Dec 13 15:23:10 hur kernel: registered device ppp3
> Dec 13 16:03:07 hur kernel: arp_cache_bind: 0f1b01ce backlogged
> Dec 13 16:03:07 hur kernel: arp_find: 0f1b01ce backlogged
> Dec 13 16:03:07 hur kernel: arp_run_bh: 0f1b01ce reinstalled
> Dec 13 16:03:07 hur kernel: arp_run_bh: entry 0f1b01ce was born dead
> Dec 13 16:30:18 hur kernel: rt_cache: route to 0901a8c0 was born dead
> Dec 13 19:45:33 hur kernel: registered device ppp4
>
If they occur each 5-10 sec, please send me full syslog and your system setup.
If they are rare (as in your syslog example) just ignore them,
and if they are too annoying, set
#define RT_CACHE_DEBUG 0
in <net/route.h>.
I set it to 1 in order to get reports about cache efficiency.
Backlogged/reinstalled are just debugging messages,
"was born dead" means that cache entry was created, which
will be used only once and really slows down rather than speeds up
routing/arping. Real cache efficiency is full number of transferred packets
divided by number of "was born dead" messages.
It is almost infinity, is not it? 8)
Alexey Kuznetsov
