kernel: arpresolve: can't allocate llinfo for 65.59.233.102

[Dominic Blais]

Hi!

Here's what I got seconds prior/while it happened this morning:

got message of size 24 on Wed Sep 12 00:15:49 2012
RTM_IFANNOUNCE: interface arrival/departure: len 24, if# 37, what: arrival

got message of size 168 on Wed Sep 12 00:15:49 2012
RTM_IFINFO: iface status change: len 168, if# 37, link: unknown, flags:<PTP,NOARP,SIMPLEX,MULTICAST>

got message of size 184 on Wed Sep 12 00:15:49 2012
RTM_DELETE: Delete Route: len 184, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,STATIC>
locks:  inits:
sockaddrs: <DST,GATEWAY,NETMASK>
 default default default               ### <- This looks normal, I usually see it when customers connect to
					          ###    pppoe from MPD.

got message of size 100 on Wed Sep 12 00:15:49 2012
RTM_DELADDR: address being removed from iface: len 100, metric 0, flags:
sockaddrs: <NETMASK,IFP,IFA,BRD>
 default ng30 default default

got message of size 184 on Wed Sep 12 00:15:49 2012
RTM_DELETE: Delete Route: len 184, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,STATIC>
locks:  inits:
sockaddrs: <DST,GATEWAY,NETMASK>
 default default default

got message of size 108 on Wed Sep 12 00:15:49 2012
RTM_DELADDR: address being removed from iface: len 108, metric 0, flags:
sockaddrs: <NETMASK,IFP,IFA,BRD>
 255.255.255.255 ng30 default default

got message of size 116 on Wed Sep 12 00:15:49 2012
RTM_NEWADDR: address being added to iface: len 116, metric 0, flags:
sockaddrs: <NETMASK,IFP,IFA,BRD>
 255.255.255.255 ng30 10.0.0.1 192.168.50.29

got message of size 224 on Wed Sep 12 00:15:49 2012
RTM_ADD: Add Route: len 224, pid: 0, seq 0, errno 0, flags:<UP,HOST>
locks:  inits:
sockaddrs: <DST,GATEWAY>
 192.168.50.29

got message of size 88 on Wed Sep 12 00:15:49 2012
RTM_NEWMADDR: new multicast group membership on iface: len 88,
sockaddrs: <IFP,IFA>
 ng30 224.0.0.1

got message of size 148 on Wed Sep 12 00:15:49 2012
RTM_NEWADDR: address being added to iface: len 148, metric 0, flags:<HOST>
sockaddrs: <NETMASK,IFP,IFA,BRD>
 ffff:ffff:ffff:ffff:: ng30 fe80::223:7dff:fee0:54de%ng30 default

got message of size 272 on Wed Sep 12 00:15:49 2012
RTM_ADD: Add Route: len 272, pid: 0, seq 0, errno 0, flags:<UP,HOST,STATIC>
locks:  inits:
sockaddrs: <DST,GATEWAY,NETMASK>
 fe80::223:7dff:fee0:54de%ng30 0.0.0.0.0.0 ffff:ffff:ffff:ffff::

got message of size 104 on Wed Sep 12 00:15:49 2012
RTM_NEWMADDR: new multicast group membership on iface: len 104,
sockaddrs: <IFP,IFA>
 ng30 ff02::1:ffe0:54de%ng30

got message of size 104 on Wed Sep 12 00:15:49 2012
RTM_NEWMADDR: new multicast group membership on iface: len 104,
sockaddrs: <IFP,IFA>
 ng30 ff02::1%ng30

got message of size 104 on Wed Sep 12 00:15:49 2012
RTM_NEWMADDR: new multicast group membership on iface: len 104,
sockaddrs: <IFP,IFA>
 ng30 ff02::2:5f65:5bb1%ng30

got message of size 104 on Wed Sep 12 00:15:49 2012
RTM_NEWMADDR: new multicast group membership on iface: len 104,
sockaddrs: <IFP,IFA>
 ng30 ff01:25::1

got message of size 344 on Wed Sep 12 00:15:49 2012
RTM_ADD: Add Route: len 344, pid: 0, seq 0, errno 0, flags:<UP,DONE>
locks:  inits:
sockaddrs: <DST,GATEWAY,NETMASK,IFP,IFA>
 fe80::%ng30  (255) ffff ffff ffff ffff ffff ffff ffff ng30 fe80::223:7dff:fee0:54de%ng30

--


-----Message d'origine-----
De : Gleb Smirnoff [mailto:glebius at FreeBSD.org] 
Envoyé : 11 septembre 2012 15:59
À : Vijay Singh
Cc : Adrian Chadd; freebsd-net at freebsd.org; Dominic Blais
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

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 
V> > from some tool/program/network event sending a routing table 
V> > update, or whether it's just plain memory corruption.
V> 
V> Could this be 
V> http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226
V> 224&pathrev=226331

Why do you suspect this one?

--
Totus tuus, Glebius.