Date: Wed, 04 Dec 2013 10:14:09 +0200 From: Vladimir Sharun <atz@ukr.net> To: freebsd-current Current <freebsd-current@freebsd.org> Subject: Re[2]: pf reply-to malfunction after r258468 (seems r258479) Message-ID: <1386144773.817703167.ax4sc7i4@frv45.ukr.net> In-Reply-To: <20131203181400.GA48919@glebius.int.ru> References: <1386064346.472994192.rxxiq2ll@frv45.ukr.net> <20131203115859.GU48919@FreeBSD.org> <1386093248.507170714.54to5ae0@frv45.ukr.net> <20131203181400.GA48919@glebius.int.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear Gleb, Yesterday I (finally) got my server back to work and the problem disappear. Can't reproduce it anymore on r258865. On Tue, Dec 03, 2013 at 07:54:08PM +0200, Vladimir Sharun wrote: V> Dear Gleb, V> Unfortunately can't boot both revisions kernel, it hangs on "trying to mount root from ssdzfs" (which is my zfs root). V> Vladimir, You can run the kernel that boots, but update only sys/netpfil/pf directory to suspected revision(s), if you think this is related to changes in pf. -- Totus tuus, Glebius. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Dec 4 08:16:56 2013 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 228EC4C1; Wed, 4 Dec 2013 08:16:56 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9F60D1CCE; Wed, 4 Dec 2013 08:16:54 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.7/8.14.7) with ESMTP id rB48GqYF068380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Dec 2013 12:16:52 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.7/8.14.7/Submit) id rB48GqKf068379; Wed, 4 Dec 2013 12:16:52 +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, 4 Dec 2013 12:16:52 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Craig Rodrigues <rodrigc@FreeBSD.org> Subject: Re: 10-BETA{3,4} - Consistent Kernel Panics (pf_ioctl.c:1289) Message-ID: <20131204081652.GH48919@FreeBSD.org> References: <20131204021949.GD28250@margz.perth.internal> <CAG=rPVdJkss1Hsug7pGJp0i4jb0PDOA=tUd_QZHJB7k_ftSbtg@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <CAG=rPVdJkss1Hsug7pGJp0i4jb0PDOA=tUd_QZHJB7k_ftSbtg@mail.gmail.com> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-current Current <freebsd-current@freebsd.org> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 04 Dec 2013 08:16:56 -0000 On Tue, Dec 03, 2013 at 11:21:09PM -0800, Craig Rodrigues wrote: C> > KERNCONF: C> > C> > options VIMAGE C> > C> > makeoptions DEBUG=-g C> > C> > device pf C> > device pflog C> > device pfsync C> > device carp C> > C> > C> How badly do you need VIMAGE in your kernel config? C> There are multiple known problems with VIMAGE + pf. See: C> http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-December/001787.html C> C> We need to fix all these problems in FreeBSD, of course, but someone C> needs to spend the time on it. Right now we've got some improvements in the projects/pf branch. As soon as Nikos finished his round of pf+vimage cleanups, I'll merge that to head. However, this particular bug report hasn't yet proved to be tied to vimage. -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1386144773.817703167.ax4sc7i4>