Date: Thu, 23 Jun 2016 12:25:08 +0300 From: Ivan Klymenko <fidaj@ukr.net> To: Johan Hendriks <joh.hendriks@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Fatal trap 12 Message-ID: <20160623122508.73262da4@nonamehost.local> In-Reply-To: <72a04a4e-f210-7f44-20df-1834bb86c08c@gmail.com> References: <20160622203636.050ac83a@nonamehost.local> <20160622204526.427fa6ea@nonamehost.local> <20160622205607.472ea221@nonamehost.local> <589E375F-8518-4849-AA0C-E4FE8F1D85E1@lists.zabbadoz.net> <72a04a4e-f210-7f44-20df-1834bb86c08c@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 23 Jun 2016 10:54:46 +0200 Johan Hendriks <joh.hendriks@gmail.com> wrote: > I have the following in my kernel config > # pf > options ALTQ > options ALTQ_CBQ > options ALTQ_RED > options ALTQ_RIO > options ALTQ_HFSC > options ALTQ_CDNR > options ALTQ_PRIQ > device pf > device pflog > device pfsync > > I can not alter the order the modules load as far as I know. > I changed the following in /usr/src/sys/netpfil/pf/if_pflog.c > > from > > DECLARE_MODULE(pflog, pflog_mod, SI_SUB_PSEUDO, SI_ORDER_ANY); > > to > > DECLARE_MODULE(pflog, pflog_mod, SI_SUB_PROTO_FIREWALL, SI_ORDER_ANY); > > But after a buildworld the same error. > +1 > Do you compile pflog into the kernel or load it from loader by any > chance? I can see what might happen here. Yes, i have kernel options: device pf device pflog device pfsync ALTQ... > > 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 This does not solve the problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160623122508.73262da4>