Re: Fatal trap 12

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.



Op 23/06/16 om 02:01 schreef Bjoern A. Zeeb:
> On 22 Jun 2016, at 17:56, Ivan Klymenko wrote:
>
>> On Wed, 22 Jun 2016 20:45:26 +0300
>> Ivan Klymenko <fidaj_at_ukr.net> wrote:
>>
>>> On Wed, 22 Jun 2016 20:36:36 +0300
>>> Ivan Klymenko <fidaj_at_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
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe_at_freebsd.org"