From owner-freebsd-net@FreeBSD.ORG Wed Nov 23 11:22:06 2011 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 8529D106566C for ; Wed, 23 Nov 2011 11:22:06 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 09B258FC1C for ; Wed, 23 Nov 2011 11:22:05 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id pANBM4OT019351; Wed, 23 Nov 2011 15:22:04 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id pANBM4Gh019350; Wed, 23 Nov 2011 15:22:04 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 23 Nov 2011 15:22:04 +0400 From: Gleb Smirnoff To: Nikos Vassiliadis Message-ID: <20111123112204.GY96616@glebius.int.ru> References: <4EC63D37.4050105@gmx.com> <20111122194833.GN96616@FreeBSD.org> <4ECCD46E.2060908@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4ECCD46E.2060908@gmx.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@FreeBSD.org Subject: Re: arprequest triggered panic 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, 23 Nov 2011 11:22:06 -0000 On Wed, Nov 23, 2011 at 01:09:34PM +0200, Nikos Vassiliadis wrote: N> On 11/22/2011 9:48 PM, Gleb Smirnoff wrote: N> > Can't reproduce this on head. May be some additional measures are needed? Traffic? N> N> Just noticed that the panic does not happen using GENERIC. N> Here is my kernel configuration, if you want to dig deeper. N> N> include GENERIC N> ident LAB N> N> options VIMAGE N> options IPSEC N> device crypto N> N> options IPFIREWALL N> options IPFIREWALL_DEFAULT_TO_ACCEPT N> options IPFIREWALL_FORWARD N> options DUMMYNET N> N> options ALTQ N> option ALTQ_CBQ N> options ALTQ_RED N> options ALTQ_RIO N> options ALTQ_HFSC N> options ALTQ_CDNR N> options ALTQ_PRIQ I'd suspect VIMAGE. Can you please try w/o it and if it appears to be VIMAGE-related, then please file a PR. -- Totus tuus, Glebius.