From owner-freebsd-current@FreeBSD.ORG Tue Feb 24 07:05:52 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7BAAF991; Tue, 24 Feb 2015 07:05:52 +0000 (UTC) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BD6C844; Tue, 24 Feb 2015 07:05:51 +0000 (UTC) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id 94B54BE48; Tue, 24 Feb 2015 08:05:47 +0100 (CET) Received: by vega.codepro.be (Postfix, from userid 1001) id 8EA3BBB10; Tue, 24 Feb 2015 08:05:47 +0100 (CET) Date: Tue, 24 Feb 2015 08:05:47 +0100 From: Kristof Provost To: Davide Italiano Subject: Re: pf crash on -current Message-ID: <20150224070547.GH2181@vega.codepro.be> References: <54EBD112.8050705@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 X-Checked-By-NSA: Probably User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-current , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2015 07:05:52 -0000 On 2015-02-23 17:23:55 (-0800), Davide Italiano wrote: > On Mon, Feb 23, 2015 at 5:17 PM, Allan Jude wrote: > > Upgraded my router today, because it was approaching the 24 uptime days > > of doom > > > > Now, it likes to die on me, a lot > > > > > > The bt you posted suggest this could be stack overflow, probably due > to infinite recursion. > Also, as a wild guess, just looking at the stacktrace, I think this > might be related to the recent ipv6 fragment changes. Try to back them > out, and see if things gets more stable ( r278831 and r278843). > That's almost certainly what it is. Allan, can you give me a bit more information about your setup? Specifically the pf rules, the network interfaces, the IP(v6) addresses and the routes? Thanks, Kristof