arp_purge_send_q called from SPL=0
arp_neigh_destroy called from SPL=0
arp_purge_send_q called from SPL=0
arp_free called from SPL=0
arp_purge_send_q called from SPL=0
arp_neigh_destroy called from SPL=0
arp_purge_send_q called from SPL=0
arp_free called from SPL=0
arp_purge_send_q called from SPL=0
arp_neigh_destroy called from SPL=0
arp_purge_send_q called from SPL=0
arp_free called from SPL=0
What does this mean? Is it bad? 2.1.35 is up for a day now, and this is
the only problem. I wouldn't mind, but its cloggin up the screen and the
log files. Each dump occurs with a disk write, but I am assuming
[wrongly?] that this is the write to syslog.
I have a 486 66 with 24 meg ram, NE2000 network card [as a module] ipv6
as a module, and I am not sure if you need anymore info.
Vince
____________
\ /\ /\ / Vince Weaver
\/__\/__\/ weave@eng.umd.edu http://www.glue.umd.edu/~weave
Q: How many Microsoft engineers does it take to change a light bulb?
A: None. Bill Gates will just redefine Darkness(TM) as the new
industry standard.