From owner-freebsd-current@FreeBSD.ORG Tue Feb 24 02:17:35 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3808F993 for ; Tue, 24 Feb 2015 02:17:35 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C7CA0685 for ; Tue, 24 Feb 2015 02:17:34 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t1O2I6bQ077947 for ; Mon, 23 Feb 2015 18:18:06 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <54EBD88E.3030608@freebsd.org> References: <54EBD112.8050705@freebsd.org> <5df58ef23e20d76ace021f3a25601f67@ultimatedns.net>, <54EBD88E.3030608@freebsd.org> From: "Chris H" Subject: Re: pf crash on -current Date: Mon, 23 Feb 2015 18:18:06 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit 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 02:17:35 -0000 On Mon, 23 Feb 2015 20:49:02 -0500 Allan Jude wrote > On 2015-02-23 20:44, Chris H wrote: > > On Mon, 23 Feb 2015 20:17:06 -0500 Allan Jude wrote > > > >> Upgraded my router today, because it was approaching the 24 uptime days > >> of doom > > As to the "uptime days of doom"... > > I inquired about this a week ago, and was informed the matter > > had been resolved about a week earlier. I can't find the message > > at the moment, or I'd share the revision I was provided. But > > thought you like to know. > > > > --Chris > > Yes, I was installing the latest to get that fix, I know it is fixed. Sure, of course. I just thought the time frame might help walking back revisions, till whatever cased the panic stopped. But still be ahead of the "uptime days of doom". FWIW the revision that fixed it was: r278229 > > -- > Allan Jude --Chris