From owner-freebsd-net@FreeBSD.ORG Wed Sep 12 10:28:25 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A1A71065672; Wed, 12 Sep 2012 10:28:25 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id EEF7E8FC18; Wed, 12 Sep 2012 10:28:24 +0000 (UTC) Received: by smtp1.interplex.ca (Postfix, from userid 106) id 4448850916; Wed, 12 Sep 2012 06:28:23 -0400 (EDT) Received: from smtp.interplex.ca (office.abi.ca [207.134.166.34]) by smtp1.interplex.ca (Postfix) with ESMTP id D0E1E508B4; Wed, 12 Sep 2012 06:28:22 -0400 (EDT) Received: from WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295]) by WIN2008.Domnt.abi.ca ([fe80::e06e:fea4:8702:2295%12]) with mapi; Wed, 12 Sep 2012 06:28:21 -0400 From: Dominic Blais To: Gleb Smirnoff , Vijay Singh Date: Wed, 12 Sep 2012 06:28:15 -0400 Thread-Topic: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 Thread-Index: Ac2QV9hNg6yz3+vBTKid2eQK9MzOqAAeR3oQ Message-ID: <2DE61B0869B7484997BCA012845482C7EBE62DDDC6@WIN2008.Domnt.abi.ca> References: <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <20120911195836.GQ44854@FreeBSD.org> In-Reply-To: <20120911195836.GQ44854@FreeBSD.org> Accept-Language: fr-FR, fr-CA Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , Adrian Chadd Subject: RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 10:28:25 -0000 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: 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: locks: inits: sockaddrs: 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: 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: locks: inits: sockaddrs: 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: 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: 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: locks: inits: sockaddrs: 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: 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: sockaddrs: 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: locks: inits: sockaddrs: 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: 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: 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: 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: 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: locks: inits: sockaddrs: fe80::%ng30 (255) ffff ffff ffff ffff ffff ffff ffff ng30 fe80::223:7dff:= fee0:54de%ng30 -- -----Message d'origine----- De=A0: Gleb Smirnoff [mailto:glebius@FreeBSD.org]=20 Envoy=E9=A0: 11 septembre 2012 15:59 =C0=A0: Vijay Singh Cc=A0: Adrian Chadd; freebsd-net@freebsd.org; Dominic Blais Objet=A0: 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 wrot= e: V> > On 11 September 2012 09:01, Dominic Blais 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=20 V> > from some tool/program/network event sending a routing table=20 V> > update, or whether it's just plain memory corruption. V>=20 V> Could this be=20 V> http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=3D226120&r2=3D22= 6 V> 224&pathrev=3D226331 Why do you suspect this one? -- Totus tuus, Glebius.