Date: Thu, 23 Jun 2016 00:01:42 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: "Ivan Klymenko" <fidaj@ukr.net> Cc: freebsd-current@freebsd.org Subject: Re: Fatal trap 12 Message-ID: <589E375F-8518-4849-AA0C-E4FE8F1D85E1@lists.zabbadoz.net> In-Reply-To: <20160622205607.472ea221@nonamehost.local> References: <20160622203636.050ac83a@nonamehost.local> <20160622204526.427fa6ea@nonamehost.local> <20160622205607.472ea221@nonamehost.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22 Jun 2016, at 17:56, Ivan Klymenko wrote: > On Wed, 22 Jun 2016 20:45:26 +0300 > Ivan Klymenko <fidaj@ukr.net> wrote: > >> On Wed, 22 Jun 2016 20:36:36 +0300 >> Ivan Klymenko <fidaj@ukr.net> wrote: >> >>> Hello. >>> After update from r302000 to r302083 i have panic >>> http://i.imgur.com/YfvvhdS.png >>> >>> Thanks. >> Sorry, the first time discovered a revision r302060. > > There is a suspicion that the reason for this commit: > https://svnweb.freebsd.org/base?view=revision&revision=302054 Do you compile pflog into the kernel or load it from loader by any chance? I can see what might happen here. Can you try to see if this goes away if you load pflog after pf is loaded? If that helps change the SI_SUB_PSEUDO at the end of sys/netpfil/pf/if_pflog.c to SI_SUB_PROTO_FIREWALL ; that should fix it. /bz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?589E375F-8518-4849-AA0C-E4FE8F1D85E1>